summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVenkata Harish K Kajur <vk250x@att.com>2018-01-30 14:04:13 -0500
committerVenkata Harish K Kajur <vk250x@att.com>2018-02-27 19:35:30 -0500
commitaefeb9ff5ec5c7ce3c20f420db1116c31f034615 (patch)
tree986dc4e1c6f8b897b3e6e99fba2af8df3a3f0965
parent4eae7a8de0381e013daa717626c6c431d1dca35b (diff)
Update the files for ajsc 6 changes
Issue-ID: AAI-33 Change-Id: I897566e79eb7505232b692e551f6347e69fafed6 Signed-off-by: Venkata Harish K Kajur <vk250x@att.com>
-rw-r--r--aai-client-loadbalancer/pom.xml90
-rw-r--r--aai-client-loadbalancer/src/main/java/org/onap/aai/AAIRibbonConfiguration.java54
-rw-r--r--aai-client-loadbalancer/src/main/java/org/onap/aai/config/HttpPing.java68
-rw-r--r--aai-client-loadbalancer/src/main/java/org/onap/aai/config/HttpPingImpl.java251
-rw-r--r--aai-core/pom.xml280
-rw-r--r--aai-core/src/main/java/org/onap/aai/config/DmaapConfig.java110
-rw-r--r--aai-core/src/main/java/org/onap/aai/config/SpringContextAware.java42
-rw-r--r--aai-core/src/main/java/org/onap/aai/dmaap/AAIDmaapEventJMSProducer.java14
-rw-r--r--aai-core/src/main/java/org/onap/aai/dmaap/JMSConsumer.java160
-rw-r--r--aai-core/src/main/java/org/onap/aai/dmaap/JMSProducer.java58
-rw-r--r--aai-core/src/main/java/org/onap/aai/dmaap/MessageProducer.java29
-rw-r--r--aai-core/src/main/java/org/onap/aai/introspection/ModelInjestor.java31
-rw-r--r--aai-core/src/main/java/org/onap/aai/introspection/MoxyLoader.java18
-rw-r--r--aai-core/src/main/java/org/onap/aai/util/AAIApiServerURLBase.java35
-rw-r--r--aai-core/src/main/java/org/onap/aai/util/AAICSVWriter.java168
-rw-r--r--aai-core/src/main/java/org/onap/aai/util/AAIConfig.java9
-rw-r--r--aai-core/src/main/java/org/onap/aai/util/StoreNotificationEvent.java47
-rw-r--r--aai-core/src/test/java/org/onap/aai/introspection/sideeffect/DataCopyTest.java2
-rw-r--r--aai-core/src/test/java/org/onap/aai/util/AAICSVWriterTest.java77
-rw-r--r--aai-core/src/test/java/org/onap/aai/util/StoreNotificationEventTest.java2
-rw-r--r--aai-core/src/test/resources/oxm/aai_oxm_v10.xml (renamed from aai-core/src/test/resources/bundleconfig-local/etc/oxm/aai_oxm_v10.xml)0
-rw-r--r--aai-core/src/test/resources/oxm/aai_oxm_v11.xml (renamed from aai-core/src/test/resources/bundleconfig-local/etc/oxm/aai_oxm_v11.xml)0
-rw-r--r--aai-core/src/test/resources/oxm/aai_oxm_v12.xml (renamed from aai-core/src/test/resources/bundleconfig-local/etc/oxm/aai_oxm_v12.xml)14
-rw-r--r--aai-core/src/test/resources/oxm/aai_oxm_v8.xml (renamed from aai-core/src/test/resources/bundleconfig-local/etc/oxm/aai_oxm_v8.xml)0
-rw-r--r--aai-core/src/test/resources/oxm/aai_oxm_v9.xml (renamed from aai-core/src/test/resources/bundleconfig-local/etc/oxm/aai_oxm_v9.xml)0
-rw-r--r--aai-core/src/test/resources/oxm/sideeffect/nested-case.json (renamed from aai-core/src/test/resources/bundleconfig-local/etc/oxm/sideeffect/nested-case.json)0
-rw-r--r--aai-schema/src/main/resources/aai_swagger_html/aai_swagger_v10.html24188
-rw-r--r--aai-schema/src/main/resources/aai_swagger_html/aai_swagger_v11.html26438
-rw-r--r--aai-schema/src/main/resources/aai_swagger_html/aai_swagger_v8.html24055
-rw-r--r--aai-schema/src/main/resources/aai_swagger_html/aai_swagger_v9.html24146
-rw-r--r--aai-schema/src/main/resources/aai_swagger_yaml/aai_swagger_v10.yaml26365
-rw-r--r--aai-schema/src/main/resources/aai_swagger_yaml/aai_swagger_v11.yaml29238
-rw-r--r--aai-schema/src/main/resources/aai_swagger_yaml/aai_swagger_v8.yaml24768
-rw-r--r--aai-schema/src/main/resources/aai_swagger_yaml/aai_swagger_v9.yaml26073
-rw-r--r--pom.xml1
35 files changed, 187439 insertions, 19392 deletions
diff --git a/aai-client-loadbalancer/pom.xml b/aai-client-loadbalancer/pom.xml
new file mode 100644
index 00000000..3a100371
--- /dev/null
+++ b/aai-client-loadbalancer/pom.xml
@@ -0,0 +1,90 @@
+<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
+ <modelVersion>4.0.0</modelVersion>
+ <parent>
+ <groupId>org.onap.aai.aai-common</groupId>
+ <artifactId>aai-common</artifactId>
+ <version>1.2.1-SNAPSHOT</version>
+ </parent>
+ <artifactId>aai-client-loadbalancer</artifactId>
+ <version>1.2.1-SNAPSHOT</version>
+ <build>
+ <plugins>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-compiler-plugin</artifactId>
+ <configuration>
+ <source>${java.version}</source>
+ <target>${java.version}</target>
+ </configuration>
+ </plugin>
+ </plugins>
+ </build>
+ <packaging>jar</packaging>
+
+ <name>aai-client-loadbalancer</name>
+ <description>AAI Client Side Loader Balancer to replace Dmaap</description>
+
+ <properties>
+ <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
+ <java.version>1.8</java.version>
+ </properties>
+
+ <dependencies>
+ <dependency>
+ <groupId>org.springframework.cloud</groupId>
+ <artifactId>spring-cloud-starter-ribbon</artifactId>
+ </dependency>
+ <dependency>
+ <groupId>org.springframework.cloud</groupId>
+ <artifactId>spring-cloud-commons</artifactId>
+ </dependency>
+ <dependency>
+ <groupId>org.springframework.boot</groupId>
+ <artifactId>spring-boot-starter-web</artifactId>
+ <version>1.5.2.RELEASE</version>
+ </dependency>
+ <dependency>
+ <groupId>com.att.eelf</groupId>
+ <artifactId>eelf-core</artifactId>
+ <version>1.0.0</version>
+ </dependency>
+ <dependency>
+ <groupId>org.springframework.retry</groupId>
+ <artifactId>spring-retry</artifactId>
+ <version>1.2.1.RELEASE</version>
+ </dependency>
+ </dependencies>
+
+ <dependencyManagement>
+ <dependencies>
+ <dependency>
+ <groupId>org.springframework.cloud</groupId>
+ <artifactId>spring-cloud-dependencies</artifactId>
+ <version>Camden.SR5</version>
+ <type>pom</type>
+ <scope>import</scope>
+ </dependency>
+ </dependencies>
+ </dependencyManagement>
+
+ <repositories>
+ <repository>
+ <id>spring-snapshots</id>
+ <name>Spring Snapshots</name>
+ <url>https://repo.spring.io/snapshot</url>
+ <snapshots>
+ <enabled>true</enabled>
+ </snapshots>
+ </repository>
+ <repository>
+ <id>spring-milestones</id>
+ <name>Spring Milestones</name>
+ <url>https://repo.spring.io/milestone</url>
+ <snapshots>
+ <enabled>false</enabled>
+ </snapshots>
+ </repository>
+ </repositories>
+
+</project>
diff --git a/aai-client-loadbalancer/src/main/java/org/onap/aai/AAIRibbonConfiguration.java b/aai-client-loadbalancer/src/main/java/org/onap/aai/AAIRibbonConfiguration.java
new file mode 100644
index 00000000..4c639e44
--- /dev/null
+++ b/aai-client-loadbalancer/src/main/java/org/onap/aai/AAIRibbonConfiguration.java
@@ -0,0 +1,54 @@
+/**
+ * ============LICENSE_START=======================================================
+ * org.onap.aai
+ * ================================================================================
+ * Copyright © 2017 AT&T Intellectual Property. All rights reserved.
+ * ================================================================================
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ * ============LICENSE_END=========================================================
+ *
+ * ECOMP is a trademark and service mark of AT&T Intellectual Property.
+ */
+package org.onap.aai;
+
+import com.netflix.client.config.IClientConfig;
+import com.netflix.loadbalancer.ILoadBalancer;
+import com.netflix.loadbalancer.LoadBalancerBuilder;
+import org.springframework.beans.factory.annotation.Autowired;
+import org.springframework.cloud.client.loadbalancer.LoadBalanced;
+import org.springframework.context.annotation.Bean;
+import org.springframework.web.client.RestTemplate;
+
+/**
+ * AAIRibbonConfiguration is responsible for configuring the dmaap
+ * and it reads the users the application properties class
+ * and is mostly configurable via properties
+ */
+public class AAIRibbonConfiguration {
+
+ @Autowired
+ IClientConfig ribbonClientConfig;
+
+ @Bean
+ public ILoadBalancer ribbonLoadBalancer() {
+ return LoadBalancerBuilder.newBuilder()
+ .withClientConfig(ribbonClientConfig)
+ .buildLoadBalancerFromConfigWithReflection();
+ }
+
+ @LoadBalanced
+ @Bean
+ public RestTemplate loadBalancedRestTemplate(){
+ return new RestTemplate();
+ }
+}
diff --git a/aai-client-loadbalancer/src/main/java/org/onap/aai/config/HttpPing.java b/aai-client-loadbalancer/src/main/java/org/onap/aai/config/HttpPing.java
new file mode 100644
index 00000000..4ecbfb60
--- /dev/null
+++ b/aai-client-loadbalancer/src/main/java/org/onap/aai/config/HttpPing.java
@@ -0,0 +1,68 @@
+/**
+ * ============LICENSE_START=======================================================
+ * org.onap.aai
+ * ================================================================================
+ * Copyright © 2017 AT&T Intellectual Property. All rights reserved.
+ * ================================================================================
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ * ============LICENSE_END=========================================================
+ *
+ * ECOMP is a trademark and service mark of AT&T Intellectual Property.
+ */
+package org.onap.aai.config;
+
+import java.util.Optional;
+
+/**
+ * <b>HttpPing</b> interface provides access to update the endpoint and
+ * and the security level of the server that the user is trying to access
+ */
+public interface HttpPing {
+
+ /**
+ * Sets the endpoint that the http get request will
+ * make to verify if the url can be reached
+ *
+ * @param endpoint - the endpoint of the url that is used to do healthcheck
+ */
+ void setHealthCheckEndpoint(String endpoint);
+
+ /**
+ * Returns the health check endpoint that the implementation
+ * will use in order to verify if the server is reachable at that location
+ *
+ * @return endpoint - the endpoint of the url that is used to do healthcheck
+ */
+ String getHealthCheckEndpoint();
+
+ /**
+ * Set the credentials for the rest endpoint to verify authorization
+ *
+ * @param username - the username to the server trying to connect to
+ * @param password - the password to the server trying to connect to
+ */
+ void setCredentials(String username, String password);
+
+ /**
+ * Return the base64 authorization string set from the username and password
+ *
+ * @return encoded string using base64 of the username and password values
+ * like this:
+ * <pre>
+ * @{code
+ * "username:password" => "Basic dXNlcm5hbWU6cGFzc3dvcmQ="
+ * }
+ * </pre>
+ */
+ Optional<String> getAuthorization();
+}
diff --git a/aai-client-loadbalancer/src/main/java/org/onap/aai/config/HttpPingImpl.java b/aai-client-loadbalancer/src/main/java/org/onap/aai/config/HttpPingImpl.java
new file mode 100644
index 00000000..2e5804eb
--- /dev/null
+++ b/aai-client-loadbalancer/src/main/java/org/onap/aai/config/HttpPingImpl.java
@@ -0,0 +1,251 @@
+/**
+ * ============LICENSE_START=======================================================
+ * org.onap.aai
+ * ================================================================================
+ * Copyright © 2017 AT&T Intellectual Property. All rights reserved.
+ * ================================================================================
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ * ============LICENSE_END=========================================================
+ *
+ * ECOMP is a trademark and service mark of AT&T Intellectual Property.
+ */
+package org.onap.aai.config;
+
+import com.att.eelf.configuration.EELFLogger;
+import com.att.eelf.configuration.EELFManager;
+import com.netflix.client.config.DefaultClientConfigImpl;
+import com.netflix.client.config.IClientConfig;
+import com.netflix.loadbalancer.IPing;
+import com.netflix.loadbalancer.Server;
+import org.springframework.http.*;
+import org.springframework.web.client.HttpClientErrorException;
+import org.springframework.web.client.RestTemplate;
+
+import java.io.IOException;
+import java.net.InetSocketAddress;
+import java.net.Socket;
+import java.net.SocketAddress;
+import java.util.Base64;
+import java.util.Collections;
+import java.util.Map;
+import java.util.Optional;
+
+public class HttpPingImpl implements HttpPing, IPing {
+
+ private static final EELFLogger logger = EELFManager.getInstance().getLogger(HttpPingImpl.class);
+
+ private static final Base64.Encoder base64Encoder = Base64.getEncoder();
+
+ private static final HttpHeaders HTTP_HEADERS = new HttpHeaders();
+
+ // This is a workaround for the topics that the user
+ // does not have the access to read their own topic status
+ private static final String MR_STATUS_PATTERN = ".*\"mrstatus\":\\s*4002.*";
+
+ private static final int HTTPS_PORT = 3905;
+ private static final int DEFAULT_TIMEOUT = 2;
+
+ private String healthCheckEndpoint;
+ private String username;
+ private String password;
+
+ private int timeout;
+
+ private final RestTemplate restTemplate;
+
+ public HttpPingImpl(String healthCheckEndpoint) {
+ this(new RestTemplate());
+ this.healthCheckEndpoint = healthCheckEndpoint;
+ this.timeout = DEFAULT_TIMEOUT;
+ }
+
+ public HttpPingImpl(RestTemplate restTemplate) {
+ this.restTemplate = restTemplate;
+ this.healthCheckEndpoint = "";
+ this.timeout = DEFAULT_TIMEOUT;
+ }
+
+ public HttpPingImpl() {
+ this("");
+ }
+
+ public HttpPingImpl(IClientConfig clientConfig) {
+
+ if (!(clientConfig instanceof DefaultClientConfigImpl)) {
+ throw new UnsupportedOperationException("Unable to support the client config implementation: " + clientConfig.getClass().getName());
+ }
+
+ DefaultClientConfigImpl defaultClientConfig = (DefaultClientConfigImpl) clientConfig;
+
+ Map<String, Object> map = defaultClientConfig.getProperties();
+
+ this.setCredentials(map.get("username").toString(), map.get("password").toString());
+ this.setHealthCheckEndpoint(map.get("health.endpoint").toString());
+ this.setTimeoutInSecs(Integer.valueOf(map.get("pingport.timeout").toString()));
+
+ this.restTemplate = new RestTemplate();
+ }
+
+ /**
+ * {@inheritDoc}
+ */
+ @Override
+ public void setHealthCheckEndpoint(String endpoint) {
+ this.healthCheckEndpoint = endpoint;
+ }
+
+ /**
+ * {@inheritDoc}
+ */
+ @Override
+ public String getHealthCheckEndpoint() {
+ return healthCheckEndpoint;
+ }
+
+ @Override
+ public void setCredentials(String username, String password) {
+ this.username = username;
+ this.password = password;
+ }
+
+ public void setTimeoutInSecs(int timeout) {
+ this.timeout = timeout;
+ }
+
+ @Override
+ public Optional<String> getAuthorization() {
+
+ if (username == null && password == null) {
+ return Optional.empty();
+ }
+
+ if (username == null || username.isEmpty()) {
+ logger.error("Username is null while the password is not correctly set");
+ return Optional.empty();
+ }
+
+ if (password == null || password.isEmpty()) {
+ logger.error("Password is null while the username is not correctly set");
+ return Optional.empty();
+ }
+
+ String auth = String.format("%s:%s", username, password);
+ return Optional.ofNullable("Basic " + base64Encoder.encodeToString(auth.getBytes()));
+ }
+
+ /**
+ * @{inheritDoc}
+ */
+ @Override
+ public boolean isAlive(Server server) {
+
+ String url = null;
+
+ // If unable to ping the port then return immediately
+ if (!pingPort(server)) {
+ return false;
+ }
+
+ if (server.getPort() == HTTPS_PORT) {
+ url = "https://";
+ } else {
+
+ url = "http://";
+ }
+
+ url = url + server.getId();
+ url = url + this.getHealthCheckEndpoint();
+
+ boolean isAlive = false;
+
+ Optional<String> authorization = getAuthorization();
+
+ HttpHeaders httpHeaders = new HttpHeaders();
+ httpHeaders.setAccept(Collections.singletonList(MediaType.APPLICATION_JSON));
+
+ if (authorization.isPresent()) {
+ httpHeaders.add("Authorization", authorization.get());
+ }
+
+ HttpEntity<String> httpEntity = new HttpEntity<>(httpHeaders);
+ try {
+
+ ResponseEntity<String> responseEntity = restTemplate.exchange(url, HttpMethod.GET, httpEntity, String.class);
+
+ HttpStatus httpStatus = responseEntity.getStatusCode();
+
+ if (httpStatus == HttpStatus.OK) {
+ isAlive = true;
+ logger.info("Successfully established connection to the following url {}", url);
+ return isAlive;
+ }
+
+ logger.warn("Unable to establish a connection the following url {} due to HTTP Code {}, and reason {}",
+ url, httpStatus.value(), httpStatus.getReasonPhrase());
+
+ } catch (HttpClientErrorException ex) {
+ HttpStatus httpStatus = ex.getStatusCode();
+ if (httpStatus == HttpStatus.FORBIDDEN) {
+ // This is a workaround being in play for the topics
+ // that are unable to read themselves for this user
+ // In the case of the username and password being
+ // wrong the response would be unauthorized (401) but if the
+ // user is authorized but unable to read this topic, then
+ // we get back the (403) with the message mrstatus 4002
+ // This is a temporary workaround to properly identify which server is down
+ String body = ex.getResponseBodyAsString();
+ if (body.matches(MR_STATUS_PATTERN)) {
+ isAlive = true;
+ logger.info("Successfully connected by workaround due to unable to read own topic {}", url);
+ return isAlive;
+ } else {
+ logger.warn("Unable to establish a connection to {} due to {}", server.getHostPort(), ex.getMessage());
+ }
+ } else {
+ logger.warn("Unable to establish a connection to {} due to {}", server.getHostPort(), ex.getMessage());
+ }
+ } catch (Exception ex) {
+ logger.warn("Unable to establish a connection to {} due to {}", server.getHostPort(), ex.getMessage());
+ }
+
+ return isAlive;
+ }
+
+ /**
+ * Returns true if it can connect to the host and port within
+ * the given timeout from the given server parameter
+ *
+ * @param server - server that will be taken from the src/main/resources/application.yml file
+ * @return true if it can make a successful socket connection to the port on the host
+ */
+ public boolean pingPort(Server server) {
+
+ String host = server.getHost();
+ Integer port = server.getPort();
+
+ boolean success = false;
+ SocketAddress socketAddress = new InetSocketAddress(host, port);
+
+ try (Socket socket = new Socket()) {
+ socket.connect(socketAddress, timeout * 1000);
+ if (socket.isConnected()) {
+ success = true;
+ }
+ } catch (IOException e) {
+ logger.warn("Unable to connect to the host {} on port {} due to {}", host, port, e.getLocalizedMessage());
+ success = false;
+ }
+
+ return success;
+ }
+}
diff --git a/aai-core/pom.xml b/aai-core/pom.xml
index 27b54ed8..6e525a79 100644
--- a/aai-core/pom.xml
+++ b/aai-core/pom.xml
@@ -13,17 +13,16 @@
<version>1.2.1-SNAPSHOT</version>
<packaging>jar</packaging>
<properties>
- <onap.nexus.url>https://nexus.onap.org</onap.nexus.url>
+ <gendoc.version>v12</gendoc.version>
+ <aai.wiki.link>https://wiki.onap.org/</aai.wiki.link>
+ <hbase.version>1.0.2</hbase.version>
<sonar.language>java</sonar.language>
<sonar.java.coveragePlugin>jacoco</sonar.java.coveragePlugin>
<sonar.surefire.reportsPath>${project.build.directory}/surefire-reports</sonar.surefire.reportsPath>
<sonar.jacoco.reportPath>${project.build.directory}/coverage-reports/jacoco.exec</sonar.jacoco.reportPath>
<sonar.jacoco.reportMissing.force.zero>false</sonar.jacoco.reportMissing.force.zero>
<sonar.projectVersion>${project.version}</sonar.projectVersion>
- <sonar.exclusions>org/onap/aai/domain/**</sonar.exclusions>
- <gendoc.version>v12</gendoc.version>
- <aai.wiki.link>https://wiki.onap.org/</aai.wiki.link>
- <hbase.version>1.0.2</hbase.version>
+ <httpclient.version>4.5.1</httpclient.version>
<jackson.version>2.2.3</jackson.version>
</properties>
<profiles>
@@ -142,7 +141,165 @@
</plugins>
</build>
</profile>
+ <profile>
+ <id>autoGenerate</id>
+ <activation>
+ <activeByDefault>true</activeByDefault>
+ </activation>
+ <build>
+ <plugins>
+ <plugin>
+ <groupId>org.codehaus.mojo</groupId>
+ <artifactId>exec-maven-plugin</artifactId>
+ <version>1.1.1</version>
+ <executions>
+ <execution>
+ <id>autoGenerateYaml</id>
+ <phase>process-classes</phase>
+ <goals>
+ <goal>java</goal>
+ </goals>
+ <configuration>
+ <mainClass>org.onap.aai.util.GenerateXsd</mainClass>
+ <systemProperties>
+ <systemProperty>
+ <key>gen_version</key>
+ <value>ALL</value>
+ </systemProperty>
+ <systemProperty>
+ <key>gen_type</key>
+ <value>YAML</value>
+ </systemProperty>
+ <systemProperty>
+ <key>yamlresponses_url</key>
+ <value>${aai.wiki.link}</value>
+ </systemProperty>
+ <systemProperty>
+ <key>yamlresponses_label</key>
+ <value>Response codes found in [response codes]</value>
+ </systemProperty>
+ </systemProperties>
+ </configuration>
+ </execution>
+ <execution>
+ <id>autoGenerateHtml</id>
+ <phase>process-classes</phase>
+ <goals>
+ <goal>java</goal>
+ </goals>
+ <configuration>
+ <mainClass>org.onap.aai.util.AutoGenerateHtml</mainClass>
+ <systemProperties>
+ <property>
+ <key>aai.generate.version</key>
+ <value>${gendoc.version}</value>
+ </property>
+ <property>
+ <key>aai.wiki.link</key>
+ <value>${aai.wiki.link}</value>
+ </property>
+ </systemProperties>
+ </configuration>
+ </execution>
+ </executions>
+ </plugin>
+ </plugins>
+ </build>
+ </profile>
</profiles>
+ <build>
+ <plugins>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-surefire-plugin</artifactId>
+ <version>2.12.4</version>
+ <configuration>
+ <argLine>-noverify ${argLine}</argLine>
+ <systemPropertyVariables>
+ <AJSC_HOME>.</AJSC_HOME>
+ <BUNDLECONFIG_DIR>bundleconfig-local</BUNDLECONFIG_DIR>
+ </systemPropertyVariables>
+ </configuration>
+ </plugin>
+ <plugin>
+ <groupId>org.codehaus.mojo</groupId>
+ <artifactId>sonar-maven-plugin</artifactId>
+ <version>3.2</version>
+ </plugin>
+ <plugin>
+ <groupId>org.jacoco</groupId>
+ <artifactId>jacoco-maven-plugin</artifactId>
+ <version>0.7.7.201606060606</version>
+ <configuration>
+ <dumpOnExit>true</dumpOnExit>
+ </configuration>
+ <executions>
+ <execution>
+ <id>jacoco-initialize-unit-tests</id>
+ <goals>
+ <goal>prepare-agent</goal>
+ </goals>
+ <configuration>
+ <destFile>${project.build.directory}/coverage-reports/jacoco.exec</destFile>
+ <!-- <append>true</append> -->
+ </configuration>
+ </execution>
+ <execution>
+ <id>post-unit-test</id>
+ <phase>test</phase>
+ <goals>
+ <goal>report</goal>
+ </goals>
+ <configuration>
+ <!-- Sets the path to the file which contains the execution data. -->
+ <dataFile>${project.build.directory}/coverage-reports/jacoco.exec</dataFile>
+ <!-- Sets the output directory for the code coverage report. -->
+ <outputDirectory>${project.reporting.outputDirectory}/jacoco</outputDirectory>
+ </configuration>
+ </execution>
+ </executions>
+ </plugin>
+ <plugin>
+ <artifactId>maven-source-plugin</artifactId>
+ <executions>
+ <execution>
+ <id>attach-sources</id>
+ <phase>deploy</phase>
+ <goals>
+ <goal>jar-no-fork</goal>
+ </goals>
+ </execution>
+ </executions>
+ </plugin>
+ <plugin>
+ <!-- explicitly define maven-deploy-plugin after other to force exec order -->
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-deploy-plugin</artifactId>
+ </plugin>
+ <plugin>
+ <groupId>org.sonatype.plugins</groupId>
+ <artifactId>nexus-staging-maven-plugin</artifactId>
+ </plugin>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-site-plugin</artifactId>
+ </plugin>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-surefire-plugin</artifactId>
+ <version>2.12.4</version>
+ <configuration>
+ <argLine>-noverify ${argLine}</argLine>
+ <runOrder>alphabetical</runOrder>
+ <systemPropertyVariables>
+ <AJSC_HOME>.</AJSC_HOME>
+ <BUNDLECONFIG_DIR>bundleconfig-local</BUNDLECONFIG_DIR>
+ </systemPropertyVariables>
+ </configuration>
+ </plugin>
+ </plugins>
+ </build>
+
<dependencies>
<dependency>
<groupId>org.onap.aai.aai-common</groupId>
@@ -154,30 +311,22 @@
<artifactId>commons-lang</artifactId>
<version>2.6</version>
</dependency>
- <dependency>
- <groupId>org.apache.commons</groupId>
- <artifactId>commons-text</artifactId>
- <version>1.1</version>
- <scope>compile</scope>
- </dependency>
+ <dependency>
+ <groupId>org.apache.commons</groupId>
+ <artifactId>commons-text</artifactId>
+ <version>1.1</version>
+ <scope>compile</scope>
+ </dependency>
<dependency>
<groupId>com.att.eelf</groupId>
<artifactId>eelf-core</artifactId>
<version>1.0.0</version>
</dependency>
<dependency>
- <groupId>jdk.tools</groupId>
- <artifactId>jdk.tools</artifactId>
- <version>1.8.0_101</version>
- <scope>system</scope>
- <systemPath>${JAVA_HOME}/lib/tools.jar</systemPath>
- </dependency>
- <dependency>
<groupId>org.codehaus.jackson</groupId>
<artifactId>jackson-core-asl</artifactId>
<version>1.9.13</version>
</dependency>
-
<dependency>
<groupId>org.codehaus.jackson</groupId>
<artifactId>jackson-mapper-asl</artifactId>
@@ -437,11 +586,11 @@
<artifactId>dmaapClient</artifactId>
<version>0.2.12</version>
<exclusions>
- <exclusion>
- <groupId>com.att.aft</groupId>
- <artifactId>dme2</artifactId>
- </exclusion>
- </exclusions>
+ <exclusion>
+ <groupId>com.att.aft</groupId>
+ <artifactId>dme2</artifactId>
+ </exclusion>
+ </exclusions>
</dependency>
<dependency>
<groupId>org.apache.camel</groupId>
@@ -460,78 +609,17 @@
<version>1.4.0</version>
<scope>test</scope>
</dependency>
- </dependencies>
-
- <build>
- <plugins>
- <plugin>
- <groupId>org.codehaus.mojo</groupId>
- <artifactId>sonar-maven-plugin</artifactId>
- <version>3.2</version>
- </plugin>
- <plugin>
- <groupId>org.jacoco</groupId>
- <artifactId>jacoco-maven-plugin</artifactId>
- <version>0.7.7.201606060606</version>
- <configuration>
- <dumpOnExit>true</dumpOnExit>
- <excludes>
- <exclude>**/domain/**</exclude>
- </excludes>
- </configuration>
- <executions>
- <execution>
- <id>jacoco-initialize-unit-tests</id>
- <goals>
- <goal>prepare-agent</goal>
- </goals>
- <configuration>
- <destFile>${project.build.directory}/coverage-reports/jacoco.exec</destFile>
- <!-- <append>true</append> -->
- </configuration>
- </execution>
- <execution>
- <id>post-unit-test</id>
- <phase>test</phase>
- <goals>
- <goal>report</goal>
- </goals>
- <configuration>
- <!-- Sets the path to the file which contains the execution data. -->
- <dataFile>${project.build.directory}/coverage-reports/jacoco.exec</dataFile>
- <!-- Sets the output directory for the code coverage report. -->
- <outputDirectory>${project.reporting.outputDirectory}/jacoco</outputDirectory>
- </configuration>
- </execution>
- </executions>
- </plugin>
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-site-plugin</artifactId>
- </plugin>
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-surefire-plugin</artifactId>
- <version>2.12.4</version>
- <configuration>
- <argLine>-noverify ${argLine}</argLine>
- <runOrder>alphabetical</runOrder>
- <systemPropertyVariables>
- <AJSC_HOME>.</AJSC_HOME>
- <BUNDLECONFIG_DIR>bundleconfig-local</BUNDLECONFIG_DIR>
- </systemPropertyVariables>
- </configuration>
- </plugin>
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-deploy-plugin</artifactId>
- </plugin>
- <plugin>
- <groupId>org.sonatype.plugins</groupId>
- <artifactId>nexus-staging-maven-plugin</artifactId>
- </plugin>
- </plugins>
- </build>
+ <dependency>
+ <groupId>org.apache.httpcomponents</groupId>
+ <artifactId>httpclient</artifactId>
+ <version>${httpclient.version}</version>
+ </dependency>
+ <dependency>
+ <groupId>org.onap.aai.aai-common</groupId>
+ <artifactId>aai-client-loadbalancer</artifactId>
+ <version>${project.version}</version>
+ </dependency>
+ </dependencies>
<!-- Plugins and repositories -->
<pluginRepositories>
diff --git a/aai-core/src/main/java/org/onap/aai/config/DmaapConfig.java b/aai-core/src/main/java/org/onap/aai/config/DmaapConfig.java
new file mode 100644
index 00000000..313775d9
--- /dev/null
+++ b/aai-core/src/main/java/org/onap/aai/config/DmaapConfig.java
@@ -0,0 +1,110 @@
+/**
+ * ============LICENSE_START=======================================================
+ * org.onap.aai
+ * ================================================================================
+ * Copyright © 2017 AT&T Intellectual Property. All rights reserved.
+ * ================================================================================
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ * ============LICENSE_END=========================================================
+ *
+ * ECOMP is a trademark and service mark of AT&T Intellectual Property.
+ */
+package org.onap.aai.config;
+
+import org.apache.activemq.ActiveMQConnectionFactory;
+import org.apache.activemq.broker.BrokerService;
+import org.apache.activemq.command.ActiveMQQueue;
+import org.onap.aai.dmaap.JMSConsumer;
+import org.onap.aai.dmaap.JMSProducer;
+import org.springframework.beans.factory.annotation.Value;
+import org.springframework.context.annotation.Bean;
+import org.springframework.context.annotation.Configuration;
+import org.springframework.context.annotation.Profile;
+import org.springframework.jms.connection.CachingConnectionFactory;
+import org.springframework.jms.core.JmsTemplate;
+import org.springframework.jms.listener.DefaultMessageListenerContainer;
+
+import javax.annotation.PostConstruct;
+
+@Profile("dmaap")
+@Configuration
+public class DmaapConfig {
+
+ @Value("${jms.bind.address}")
+ private String bindAddress;
+
+ @PostConstruct
+ public void init(){
+ System.setProperty("activemq.tcp.url", bindAddress);
+ }
+
+ @Bean(destroyMethod = "stop")
+ public BrokerService brokerService() throws Exception {
+
+ BrokerService broker = new BrokerService();
+ broker.addConnector(bindAddress);
+ broker.setPersistent(false);
+ broker.setUseJmx(false);
+ broker.setSchedulerSupport(false);
+ broker.start();
+
+ return broker;
+ }
+
+ @Bean(name = "connectionFactory")
+ public ActiveMQConnectionFactory activeMQConnectionFactory(){
+ return new ActiveMQConnectionFactory(bindAddress);
+ }
+
+ @Bean
+ public CachingConnectionFactory cachingConnectionFactory(){
+ return new CachingConnectionFactory(activeMQConnectionFactory());
+ }
+
+ @Bean(name = "destinationQueue")
+ public ActiveMQQueue activeMQQueue(){
+ return new ActiveMQQueue("IN_QUEUE");
+ }
+
+ @Bean
+ public JmsTemplate jmsTemplate(){
+ JmsTemplate jmsTemplate = new JmsTemplate();
+
+ jmsTemplate.setConnectionFactory(activeMQConnectionFactory());
+ jmsTemplate.setDefaultDestination(activeMQQueue());
+
+ return jmsTemplate;
+ }
+
+ @Bean
+ public JMSProducer jmsProducer(){
+ return new JMSProducer();
+ }
+
+ @Bean
+ public JMSConsumer jmsConsumer() throws Exception {
+ return new JMSConsumer();
+ }
+
+ @Bean
+ public DefaultMessageListenerContainer defaultMessageListenerContainer() throws Exception {
+
+ DefaultMessageListenerContainer messageListenerContainer = new DefaultMessageListenerContainer();
+
+ messageListenerContainer.setConnectionFactory(cachingConnectionFactory());
+ messageListenerContainer.setDestinationName("IN_QUEUE");
+ messageListenerContainer.setMessageListener(jmsConsumer());
+
+ return messageListenerContainer;
+ }
+}
diff --git a/aai-core/src/main/java/org/onap/aai/config/SpringContextAware.java b/aai-core/src/main/java/org/onap/aai/config/SpringContextAware.java
new file mode 100644
index 00000000..4ab9373a
--- /dev/null
+++ b/aai-core/src/main/java/org/onap/aai/config/SpringContextAware.java
@@ -0,0 +1,42 @@
+/**
+ * ============LICENSE_START=======================================================
+ * org.onap.aai
+ * ================================================================================
+ * Copyright © 2017 AT&T Intellectual Property. All rights reserved.
+ * ================================================================================
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ * ============LICENSE_END=========================================================
+ *
+ * ECOMP is a trademark and service mark of AT&T Intellectual Property.
+ */
+package org.onap.aai.config;
+
+import org.springframework.beans.BeansException;
+import org.springframework.context.ApplicationContext;
+import org.springframework.context.ApplicationContextAware;
+import org.springframework.stereotype.Component;
+
+@Component
+public class SpringContextAware implements ApplicationContextAware {
+
+ private static ApplicationContext context = null;
+
+ public static ApplicationContext getApplicationContext() {
+ return context;
+ }
+
+ @Override
+ public void setApplicationContext(ApplicationContext applicationContext) throws BeansException {
+ context = applicationContext;
+ }
+}
diff --git a/aai-core/src/main/java/org/onap/aai/dmaap/AAIDmaapEventJMSProducer.java b/aai-core/src/main/java/org/onap/aai/dmaap/AAIDmaapEventJMSProducer.java
index 914042d4..a034b9fb 100644
--- a/aai-core/src/main/java/org/onap/aai/dmaap/AAIDmaapEventJMSProducer.java
+++ b/aai-core/src/main/java/org/onap/aai/dmaap/AAIDmaapEventJMSProducer.java
@@ -24,20 +24,24 @@ package org.onap.aai.dmaap;
import org.apache.activemq.ActiveMQConnectionFactory;
import org.apache.activemq.command.ActiveMQQueue;
import org.json.JSONObject;
+import org.onap.aai.config.SpringContextAware;
import org.onap.aai.util.AAIConfig;
+import org.springframework.context.ApplicationContext;
import org.springframework.jms.connection.CachingConnectionFactory;
import org.springframework.jms.core.JmsTemplate;
-public class AAIDmaapEventJMSProducer {
+public class AAIDmaapEventJMSProducer implements MessageProducer {
private JmsTemplate jmsTemplate;
+ private ApplicationContext applicationContext;
+
public AAIDmaapEventJMSProducer() {
if(AAIConfig.get("aai.jms.enable", "true").equals("true")){
- this.jmsTemplate = new JmsTemplate();
- String activeMqTcpUrl = System.getProperty("activemq.tcp.url", "tcp://localhost:61447");
- this.jmsTemplate.setConnectionFactory(new CachingConnectionFactory(new ActiveMQConnectionFactory(activeMqTcpUrl)));
- this.jmsTemplate.setDefaultDestination(new ActiveMQQueue("IN_QUEUE"));
+ this.jmsTemplate = new JmsTemplate();
+ String activeMqTcpUrl = System.getProperty("activemq.tcp.url", "tcp://localhost:61547");
+ this.jmsTemplate.setConnectionFactory(new CachingConnectionFactory(new ActiveMQConnectionFactory(activeMqTcpUrl)));
+ this.jmsTemplate.setDefaultDestination(new ActiveMQQueue("IN_QUEUE"));
}
}
diff --git a/aai-core/src/main/java/org/onap/aai/dmaap/JMSConsumer.java b/aai-core/src/main/java/org/onap/aai/dmaap/JMSConsumer.java
new file mode 100644
index 00000000..b7638876
--- /dev/null
+++ b/aai-core/src/main/java/org/onap/aai/dmaap/JMSConsumer.java
@@ -0,0 +1,160 @@
+/**
+ * ============LICENSE_START=======================================================
+ * org.onap.aai
+ * ================================================================================
+ * Copyright © 2017 AT&T Intellectual Property. All rights reserved.
+ * ================================================================================
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ * ============LICENSE_END=========================================================
+ *
+ * ECOMP is a trademark and service mark of AT&T Intellectual Property.
+ */
+package org.onap.aai.dmaap;
+
+import com.att.eelf.configuration.EELFLogger;
+import com.att.eelf.configuration.EELFManager;
+import org.apache.log4j.MDC;
+import org.json.JSONException;
+import org.json.JSONObject;
+import org.onap.aai.config.SpringContextAware;
+import org.onap.aai.logging.LoggingContext.LoggingField;
+import org.onap.aai.logging.LoggingContext.StatusCode;
+import org.springframework.cloud.client.ServiceInstance;
+import org.springframework.cloud.client.loadbalancer.LoadBalancerClient;
+import org.springframework.core.env.Environment;
+import org.springframework.http.HttpEntity;
+import org.springframework.http.HttpHeaders;
+import org.springframework.http.HttpMethod;
+import org.springframework.http.MediaType;
+import org.springframework.web.client.RestTemplate;
+
+import javax.jms.JMSException;
+import javax.jms.Message;
+import javax.jms.MessageListener;
+import javax.jms.TextMessage;
+import java.util.Base64;
+import java.util.Collections;
+
+public class JMSConsumer implements MessageListener {
+
+ private static final EELFLogger LOGGER = EELFManager.getInstance().getLogger(JMSConsumer.class);
+
+ private static final int HTTPS_PORT = 3905;
+ private static final Base64.Encoder base64Encoder = Base64.getEncoder();
+
+ private HttpHeaders httpHeaders;
+ private RestTemplate restTemplate;
+
+ private Environment environment;
+ private LoadBalancerClient loadBalancerClient;
+
+ public JMSConsumer() throws Exception {
+ this((LoadBalancerClient)SpringContextAware.getApplicationContext().getBean("loadBalancerClient"));
+ }
+
+ public JMSConsumer(LoadBalancerClient loadBalancerClient) throws Exception {
+ this.loadBalancerClient = loadBalancerClient;
+ this.httpHeaders = new HttpHeaders();
+ this.httpHeaders.setAccept(Collections.singletonList(MediaType.APPLICATION_JSON));
+ this.environment = SpringContextAware.getApplicationContext().getEnvironment();
+
+ String username = this.environment.getProperty("dmaap.ribbon.username");
+ String password = this.environment.getProperty("dmaap.ribbon.password");
+
+ if(username == null || password == null){
+ throw new Exception("Unable to retrive username/password from the application properties");
+ }
+
+ String auth = String.format("%s:%s", username, password);
+ String authString = "Basic " + base64Encoder.encodeToString(auth.getBytes());
+ httpHeaders.add("Authorization", authString);
+
+ restTemplate = new RestTemplate();
+ }
+
+ @Override
+ public void onMessage(Message message) {
+
+ String jsmMessageTxt = "";
+ String aaiEvent = "";
+ String eventName = "";
+
+ String environment = System.getProperty("lrmRO");
+ if (environment == null) {
+ environment = "";
+ }
+
+ if (message instanceof TextMessage) {
+ try {
+ jsmMessageTxt = ((TextMessage) message).getText();
+ JSONObject jo = new JSONObject(jsmMessageTxt);
+
+ if (jo.has("aaiEventPayload")) {
+ aaiEvent = jo.getJSONObject("aaiEventPayload").toString();
+ } else {
+ return;
+ }
+ if (jo.getString("transId") != null) {
+ MDC.put("requestId", jo.getString("transId"));
+ }
+ if (jo.getString("fromAppId") != null) {
+ MDC.put("partnerName", jo.getString("fromAppId"));
+ }
+ MDC.put("targetEntity", "DMAAP");
+ if (jo.getString("event-topic") != null) {
+ eventName = jo.getString("event-topic");
+ MDC.put("targetServiceName", eventName);
+ }
+ MDC.put("serviceName", "AAI");
+ MDC.put(LoggingField.STATUS_CODE.toString(), StatusCode.COMPLETE.toString());
+ MDC.put(LoggingField.RESPONSE_CODE.toString(), "0");
+ LOGGER.info(eventName + "|" + aaiEvent);
+
+ HttpEntity<String> httpEntity = new HttpEntity<>(aaiEvent, httpHeaders);
+ ServiceInstance serviceInstance = loadBalancerClient.choose("dmaap");
+ String url = serviceInstance.getHost() + ":" + serviceInstance.getPort();
+
+ if(serviceInstance.getPort() == HTTPS_PORT){
+ url = "https://" + url;
+ } else {
+ url = "http://" + url;
+ }
+
+ url += "/events/" + eventName;
+
+ if ("AAI-EVENT".equals(eventName)) {
+ restTemplate.exchange(url, HttpMethod.POST, httpEntity, String.class);
+ LOGGER.info(eventName + "|Event sent.");
+ } else if ("AAI-VCE-INTERFACE-DATA".equals(eventName)) {
+ restTemplate.exchange(url, HttpMethod.POST, httpEntity, String.class);
+ String msg = "";
+ LOGGER.info(eventName + "|Event sent. " + msg);
+ } else {
+ MDC.put(LoggingField.STATUS_CODE.toString(), StatusCode.ERROR.toString());
+ MDC.put(LoggingField.RESPONSE_CODE.toString(), "900");
+ LOGGER.error(eventName + "|Event Topic invalid.");
+ }
+ } catch (JMSException | JSONException e) {
+ MDC.put(LoggingField.STATUS_CODE.toString(), StatusCode.ERROR.toString());
+ MDC.put(LoggingField.RESPONSE_CODE.toString(), "200");
+ LOGGER.error("AAI_7350 Error parsing aaievent jms message for sending to dmaap. " + jsmMessageTxt, e);
+ } catch (Exception e) {
+ MDC.put(LoggingField.STATUS_CODE.toString(), StatusCode.ERROR.toString());
+ MDC.put(LoggingField.RESPONSE_CODE.toString(), "200");
+ LOGGER.error("AAI_7350 Error sending message to dmaap. " + jsmMessageTxt, e);
+ }
+ }
+
+ }
+
+} \ No newline at end of file
diff --git a/aai-core/src/main/java/org/onap/aai/dmaap/JMSProducer.java b/aai-core/src/main/java/org/onap/aai/dmaap/JMSProducer.java
new file mode 100644
index 00000000..6dbfbb77
--- /dev/null
+++ b/aai-core/src/main/java/org/onap/aai/dmaap/JMSProducer.java
@@ -0,0 +1,58 @@
+/**
+ * ============LICENSE_START=======================================================
+ * org.onap.aai
+ * ================================================================================
+ * Copyright © 2017 AT&T Intellectual Property. All rights reserved.
+ * ================================================================================
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ * ============LICENSE_END=========================================================
+ *
+ * ECOMP is a trademark and service mark of AT&T Intellectual Property.
+ */
+package org.onap.aai.dmaap;
+
+import org.apache.activemq.ActiveMQConnectionFactory;
+import org.apache.activemq.command.ActiveMQQueue;
+import org.json.JSONObject;
+import org.onap.aai.config.SpringContextAware;
+import org.onap.aai.util.AAIConfig;
+import org.springframework.context.ApplicationContext;
+import org.springframework.jms.connection.CachingConnectionFactory;
+import org.springframework.jms.core.JmsTemplate;
+
+public class JMSProducer implements MessageProducer {
+
+ private JmsTemplate jmsTemplate;
+
+ private ApplicationContext applicationContext;
+
+ public JMSProducer() {
+ if(AAIConfig.get("aai.jms.enable", "true").equals("true")){
+ applicationContext = SpringContextAware.getApplicationContext();
+ if(applicationContext == null){
+ this.jmsTemplate = new JmsTemplate();
+ String activeMqTcpUrl = System.getProperty("activemq.tcp.url", "tcp://localhost:61547");
+ this.jmsTemplate.setConnectionFactory(new CachingConnectionFactory(new ActiveMQConnectionFactory(activeMqTcpUrl)));
+ this.jmsTemplate.setDefaultDestination(new ActiveMQQueue("IN_QUEUE"));
+ } else {
+ jmsTemplate = (JmsTemplate) applicationContext.getBean("jmsTemplate");
+ }
+ }
+ }
+
+ public void sendMessageToDefaultDestination(JSONObject finalJson) {
+ if(jmsTemplate != null){
+ jmsTemplate.convertAndSend(finalJson.toString());
+ }
+ }
+}
diff --git a/aai-core/src/main/java/org/onap/aai/dmaap/MessageProducer.java b/aai-core/src/main/java/org/onap/aai/dmaap/MessageProducer.java
new file mode 100644
index 00000000..229ba1a5
--- /dev/null
+++ b/aai-core/src/main/java/org/onap/aai/dmaap/MessageProducer.java
@@ -0,0 +1,29 @@
+/**
+ * ============LICENSE_START=======================================================
+ * org.onap.aai
+ * ================================================================================
+ * Copyright © 2017 AT&T Intellectual Property. All rights reserved.
+ * ================================================================================
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ * ============LICENSE_END=========================================================
+ *
+ * ECOMP is a trademark and service mark of AT&T Intellectual Property.
+ */
+package org.onap.aai.dmaap;
+
+import org.json.JSONObject;
+
+public interface MessageProducer {
+
+ void sendMessageToDefaultDestination(JSONObject finalJson);
+}
diff --git a/aai-core/src/main/java/org/onap/aai/introspection/ModelInjestor.java b/aai-core/src/main/java/org/onap/aai/introspection/ModelInjestor.java
index c670e946..524dcbf0 100644
--- a/aai-core/src/main/java/org/onap/aai/introspection/ModelInjestor.java
+++ b/aai-core/src/main/java/org/onap/aai/introspection/ModelInjestor.java
@@ -21,6 +21,8 @@
*/
package org.onap.aai.introspection;
+import com.att.eelf.configuration.EELFLogger;
+import com.att.eelf.configuration.EELFManager;
import org.eclipse.persistence.dynamic.DynamicType;
import org.eclipse.persistence.jaxb.JAXBContextProperties;
import org.eclipse.persistence.jaxb.dynamic.DynamicJAXBContext;
@@ -42,6 +44,7 @@ public class ModelInjestor {
private Map<Version, DynamicJAXBContext> versionContextMap = new HashMap<>();
private static final Pattern classNamePattern = Pattern.compile("\\.(v\\d+)\\.");
private static final Pattern uriPattern = Pattern.compile("(v\\d+)\\/");
+ private static final EELFLogger LOGGER = EELFManager.getInstance().getLogger(ModelInjestor.class);
/**
@@ -90,8 +93,24 @@ public class ModelInjestor {
*/
private void injestModel (Version version) throws JAXBException, FileNotFoundException {
String fileName = this.getOXMFileName(version);
- InputStream iStream = new FileInputStream(new File(fileName));
- Map<String, Object> properties = new HashMap<String, Object>();
+
+ File oxmFile = new File(AAIConstants.AAI_HOME_ETC + fileName);
+
+ // Check if the file exists on the path and if it doesn't exist then
+ // Using classloader makes it easy to have a different oxm file
+ // for unit testing the oxm files otherwise, you will be
+ // stuck with using the main oxm for even the testing
+
+ InputStream iStream;
+ if(oxmFile.exists()){
+ LOGGER.info("Oxm file exists on the system {}", oxmFile);
+ iStream = new FileInputStream(oxmFile);
+ } else {
+ LOGGER.warn("Unable to find oxm file {} on the system so using classloader", oxmFile);
+ iStream = getClass().getClassLoader().getResourceAsStream(fileName);
+ }
+
+ Map<String, Object> properties = new HashMap<String, Object>();
properties.put(JAXBContextProperties.OXM_METADATA_SOURCE, iStream);
final DynamicJAXBContext jaxbContext = DynamicJAXBContextFactory.createContextFromOXM(this.getClass().getClassLoader(), properties);
versionContextMap.put(version, jaxbContext);
@@ -168,7 +187,13 @@ public class ModelInjestor {
}
public String getOXMFileName(Version v) {
- return AAIConstants.AAI_HOME_ETC_OXM + "aai_oxm_" + v.toString() + ".xml";
+ // Changed the /oxm/aai_oxm_*.xml to oxm/aai_oxm_*.xml
+ // Modified to load from input stream using getClass().getClassLoader()
+ // As this will be able to relatively get the oxm if the oxm file is there
+ // So if there is a src/main/resources/oxm/ and src/test/resources/oxm, the
+ // test oxm will end up being used for tests and src oxm for source files
+ // Don't change this unless you understand the details specified
+ return "oxm/aai_oxm_" + v.toString() + ".xml";
}
}
diff --git a/aai-core/src/main/java/org/onap/aai/introspection/MoxyLoader.java b/aai-core/src/main/java/org/onap/aai/introspection/MoxyLoader.java
index 56ad2dc2..a2a673ec 100644
--- a/aai-core/src/main/java/org/onap/aai/introspection/MoxyLoader.java
+++ b/aai-core/src/main/java/org/onap/aai/introspection/MoxyLoader.java
@@ -34,6 +34,7 @@ import org.onap.aai.introspection.exceptions.AAIUnmarshallingException;
import org.onap.aai.logging.ErrorLogHelper;
import org.onap.aai.logging.LogFormatTools;
import org.onap.aai.restcore.MediaType;
+import org.onap.aai.util.AAIConstants;
import org.onap.aai.workarounds.NamingExceptions;
import org.w3c.dom.Document;
import org.w3c.dom.NodeList;
@@ -46,8 +47,7 @@ import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.parsers.ParserConfigurationException;
import javax.xml.transform.stream.StreamSource;
-import java.io.IOException;
-import java.io.StringReader;
+import java.io.*;
import java.util.HashSet;
import java.util.Map;
import java.util.Set;
@@ -176,7 +176,19 @@ public class MoxyLoader extends Loader {
docFactory.setFeature(XMLConstants.FEATURE_SECURE_PROCESSING, true);
final DocumentBuilder docBuilder = docFactory.newDocumentBuilder();
- final Document doc = docBuilder.parse(fileName);
+
+ InputStream inputStream;
+ File oxmFile = new File(AAIConstants.AAI_HOME_ETC + fileName);
+
+ if(oxmFile.exists()){
+ LOGGER.info("Oxm file exists on the system {}", oxmFile);
+ inputStream = new FileInputStream(oxmFile);
+ } else {
+ LOGGER.warn("Unable to find oxm file {} on the system so using classloader", oxmFile);
+ inputStream = getClass().getClassLoader().getResourceAsStream(fileName);
+ }
+
+ final Document doc = docBuilder.parse(inputStream);
final NodeList list = doc.getElementsByTagName("java-type");
for (int i = 0; i < list.getLength(); i++) {
diff --git a/aai-core/src/main/java/org/onap/aai/util/AAIApiServerURLBase.java b/aai-core/src/main/java/org/onap/aai/util/AAIApiServerURLBase.java
index e458c4f9..68869909 100644
--- a/aai-core/src/main/java/org/onap/aai/util/AAIApiServerURLBase.java
+++ b/aai-core/src/main/java/org/onap/aai/util/AAIApiServerURLBase.java
@@ -21,13 +21,6 @@
*/
package org.onap.aai.util;
-import java.util.List;
-import java.util.Map;
-
-import org.apache.cxf.helpers.CastUtils;
-import org.apache.cxf.message.Message;
-import org.apache.cxf.phase.PhaseInterceptorChain;
-
import org.onap.aai.exceptions.AAIException;
import org.onap.aai.introspection.Version;
@@ -42,20 +35,20 @@ public class AAIApiServerURLBase {
public static String get() throws AAIException {
String hostName = null;
- try {
- Message message = PhaseInterceptorChain.getCurrentMessage();
- Map<String, List<String>> headers = CastUtils.cast((Map) message.get(Message.PROTOCOL_HEADERS));
- List sa = null;
- if (headers != null) {
- sa = headers.get("host");
- }
-
- if (sa != null && sa.size() == 1) {
- hostName = "https://"+ sa.get(0).toString() + "/aai/";
- }
- } catch (Exception e) {
- // TODO: we may want to log an error here
- }
+// try {
+// Message message = PhaseInterceptorChain.getCurrentMessage();
+// Map<String, List<String>> headers = CastUtils.cast((Map) message.get(Message.PROTOCOL_HEADERS));
+// List sa = null;
+// if (headers != null) {
+// sa = headers.get("host");
+// }
+//
+// if (sa != null && sa.size() == 1) {
+// hostName = "https://"+ sa.get(0).toString() + "/aai/";
+// }
+// } catch (Exception e) {
+// // TODO: we may want to log an error here
+// }
// TODO: should this check the value a little closer and look for a pattern?
if (hostName == null) {
hostName = AAIConfig.get(AAIConstants.AAI_SERVER_URL_BASE);
diff --git a/aai-core/src/main/java/org/onap/aai/util/AAICSVWriter.java b/aai-core/src/main/java/org/onap/aai/util/AAICSVWriter.java
deleted file mode 100644
index c091fc24..00000000
--- a/aai-core/src/main/java/org/onap/aai/util/AAICSVWriter.java
+++ /dev/null
@@ -1,168 +0,0 @@
-/**
- * ============LICENSE_START=======================================================
- * org.onap.aai
- * ================================================================================
- * Copyright © 2017 AT&T Intellectual Property. All rights reserved.
- * ================================================================================
- * Licensed under the Apache License, Version 2.0 (the "License");
- * you may not use this file except in compliance with the License.
- * You may obtain a copy of the License at
- *
- * http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- * ============LICENSE_END=========================================================
- *
- * ECOMP is a trademark and service mark of AT&T Intellectual Property.
- */
-/**
- *
- */
-package org.onap.aai.util;
-
-import java.io.IOException;
-import java.io.PrintWriter;
-import java.io.Writer;
-
-import com.opencsv.CSVWriter;
-
-/**
- * had to overwrite the separate character to separate string
- * Based on the public - A very simple CSV writer released under a commercial-friendly license.
- *
-
- */
-public class AAICSVWriter extends CSVWriter {
-
- private String separatorStr;
- private char overridequotechar;
- private String overridelineEnd;
- private Writer rawWriter;
- private PrintWriter pw;
-
- /**
- * Instantiates a new AAICSV writer.
- *
- * @param writer the writer
- */
- public AAICSVWriter(Writer writer) {
- super(writer);
- // TODO Auto-generated constructor stub
- }
-
- /**
- * Constructs AAICSVWriter with supplied separator string and quote char.
- *
- * @param writer the writer to an underlying CSV source.
- * @param overrideseparator the overrideseparator
- * @param quotechar the character to use for quoted elements
- * @param lineEnd the line feed terminator to use
- */
- public AAICSVWriter(Writer writer, String overrideseparator, char quotechar, String lineEnd) {
- super(writer, CSVWriter.DEFAULT_SEPARATOR, quotechar, DEFAULT_ESCAPE_CHARACTER, lineEnd);
- separatorStr = overrideseparator;
- overridequotechar = quotechar;
- overridelineEnd = lineEnd;
- this.rawWriter = writer;
- this.pw = new PrintWriter(writer);
- }
-
- /**
- * String contains special characters.
- *
- * @param line the line
- * @return true, if successful
- */
- private boolean stringContainsSpecialCharacters(String line) {
- return line.indexOf(overridequotechar) != -1 || line.indexOf(DEFAULT_ESCAPE_CHARACTER) != -1 || line.indexOf(separatorStr) != -1 || line.contains("\n") || line.contains("\r");
- }
-
- /**
- * Close the underlying stream writer flushing any buffered content.
- *
- * @throws IOException if bad things happen
- */
- public void close() throws IOException {
- flush();
- pw.close();
- rawWriter.close();
- }
-
- /**
- * Writes the next line to the file.
- *
- * @param nextLine a string array with each comma-separated element as a separate
- * entry.
- * @param applyQuotesToAll true if all values are to be quoted. false applies quotes only
- * to values which contain the separator, escape, quote or new line characters.
- */
- public void writeNext(String[] nextLine, boolean applyQuotesToAll) {
-
- if (nextLine == null)
- return;
-
- StringBuilder sb = new StringBuilder(INITIAL_STRING_SIZE);
- for (int i = 0; i < nextLine.length; i++) {
-
- if (i != 0) {
- sb.append(separatorStr);
- }
-
- String nextElement = nextLine[i];
-
- if (nextElement == null)
- continue;
-
- Boolean stringContainsSpecialCharacters = stringContainsSpecialCharacters(nextElement);
-
- if ((applyQuotesToAll || stringContainsSpecialCharacters) && overridequotechar != NO_QUOTE_CHARACTER)
- sb.append(overridequotechar);
-
- if (stringContainsSpecialCharacters) {
- sb.append(processLine(nextElement));
- } else {
- sb.append(nextElement);
- }
-
- if ((applyQuotesToAll || stringContainsSpecialCharacters) && overridequotechar != NO_QUOTE_CHARACTER)
- sb.append(overridequotechar);
- }
-
- sb.append(overridelineEnd);
- pw.write(sb.toString());
- }
-
-
- /**
- * Writes the next line to the file ignoring all exceptions.
- *
- * @param nextLine a string array with each comma-separated element as a separate
- * entry.
- */
- public void writeColumn(String[] nextLine) {
-
- if (nextLine == null)
- return;
-
- StringBuilder sb = new StringBuilder(INITIAL_STRING_SIZE);
- for (int i = 0; i < nextLine.length; i++) {
-
-
- String nextElement = nextLine[i];
-
- if (nextElement == null)
- continue;
-
- sb.append(nextElement);
-
-
- }
-
- sb.append(overridelineEnd);
- pw.write(sb.toString());
- }
-}
diff --git a/aai-core/src/main/java/org/onap/aai/util/AAIConfig.java b/aai-core/src/main/java/org/onap/aai/util/AAIConfig.java
index 57bf2cc7..6f904970 100644
--- a/aai-core/src/main/java/org/onap/aai/util/AAIConfig.java
+++ b/aai-core/src/main/java/org/onap/aai/util/AAIConfig.java
@@ -52,8 +52,6 @@ public class AAIConfig {
// this (probably) won't change between releases, put it in the config if it gets annoying...
private static HashMap<String,ArrayList<String>> defaultBools = new HashMap<String,ArrayList<String>>();
- private static Timer timer = new Timer();
-
/**
* Instantiates a new AAI config.
*/
@@ -123,13 +121,6 @@ public class AAIConfig {
}
/**
- * Cleanup.
- */
- public static void cleanup() {
- timer.cancel();
- }
-
- /**
* Gets the config file.
*
* @return the config file
diff --git a/aai-core/src/main/java/org/onap/aai/util/StoreNotificationEvent.java b/aai-core/src/main/java/org/onap/aai/util/StoreNotificationEvent.java
index 0ad33cb9..2a64e996 100644
--- a/aai-core/src/main/java/org/onap/aai/util/StoreNotificationEvent.java
+++ b/aai-core/src/main/java/org/onap/aai/util/StoreNotificationEvent.java
@@ -27,35 +27,70 @@ import java.util.UUID;
import javax.xml.bind.Marshaller;
+import com.att.eelf.configuration.EELFLogger;
+import com.att.eelf.configuration.EELFManager;
import org.eclipse.persistence.dynamic.DynamicEntity;
import org.eclipse.persistence.jaxb.dynamic.DynamicJAXBContext;
import org.json.JSONException;
import org.json.JSONObject;
+import org.onap.aai.config.SpringContextAware;
import org.onap.aai.dmaap.AAIDmaapEventJMSProducer;
+import org.onap.aai.dmaap.JMSProducer;
+import org.onap.aai.dmaap.MessageProducer;
import org.onap.aai.domain.notificationEvent.NotificationEvent;
import org.onap.aai.exceptions.AAIException;
import org.onap.aai.introspection.Introspector;
import org.onap.aai.introspection.Loader;
import org.onap.aai.introspection.exceptions.AAIUnknownObjectException;
+import org.springframework.beans.factory.NoSuchBeanDefinitionException;
+import org.springframework.context.ApplicationContext;
+import org.springframework.core.env.Environment;
public class StoreNotificationEvent {
- private AAIDmaapEventJMSProducer messageProducer;
+ private static final EELFLogger logger = EELFManager.getInstance().getLogger(StoreNotificationEvent.class);
+ private MessageProducer messageProducer;
private String fromAppId = "";
private String transId = "";
private final String transactionId;
private final String sourceOfTruth;
+
+ private ApplicationContext context;
+ private Environment env;
+
/**
* Instantiates a new store notification event.
*/
public StoreNotificationEvent(String transactionId, String sourceOfTruth) {
- this(new AAIDmaapEventJMSProducer(), transactionId, sourceOfTruth);
+ this.context = SpringContextAware.getApplicationContext();
+ // If the context is null then this is being invoked from
+ // non spring context so creating the jms producer each time
+ // Otherwise, get the jms producer from the spring context so
+ // no need to create a instance of this each time
+ // Also check if the environment has the dmaap profile
+ // TODO - Add the constants for profile so do this when adding the https two-way ssl and one way with basic auth
+ if(this.context == null){
+ this.messageProducer = new AAIDmaapEventJMSProducer();
+ } else {
+ env = context.getEnvironment();
+ if(env.acceptsProfiles("dmaap")){
+ try {
+ this.messageProducer = (JMSProducer)context.getBean("jmsProducer");
+ } catch(NoSuchBeanDefinitionException ex){
+ logger.error("Currently using the dmaap profile but still not able to find bean so check DmaapConfig", ex);
+ }
+ } else {
+ this.messageProducer = new AAIDmaapEventJMSProducer();
+ }
+ }
+ this.transactionId = transactionId;
+ this.sourceOfTruth = sourceOfTruth;
}
-
+
public StoreNotificationEvent(AAIDmaapEventJMSProducer producer, String transactionId, String sourceOfTruth) {
- this.messageProducer = producer;
- this.transactionId = transactionId;
- this.sourceOfTruth = sourceOfTruth;
+ this.messageProducer = producer;
+ this.transactionId = transactionId;
+ this.sourceOfTruth = sourceOfTruth;
}
/**
diff --git a/aai-core/src/test/java/org/onap/aai/introspection/sideeffect/DataCopyTest.java b/aai-core/src/test/java/org/onap/aai/introspection/sideeffect/DataCopyTest.java
index 7d3cafac..65a241f0 100644
--- a/aai-core/src/test/java/org/onap/aai/introspection/sideeffect/DataCopyTest.java
+++ b/aai-core/src/test/java/org/onap/aai/introspection/sideeffect/DataCopyTest.java
@@ -261,7 +261,7 @@ public class DataCopyTest {
private String getJsonString(String filename) throws IOException {
- FileInputStream is = new FileInputStream("src/test/resources/bundleconfig-local/etc/oxm/sideeffect/" + filename);
+ FileInputStream is = new FileInputStream("src/test/resources/oxm/sideeffect/" + filename);
String s = IOUtils.toString(is, "UTF-8");
IOUtils.closeQuietly(is);
diff --git a/aai-core/src/test/java/org/onap/aai/util/AAICSVWriterTest.java b/aai-core/src/test/java/org/onap/aai/util/AAICSVWriterTest.java
deleted file mode 100644
index b149e95f..00000000
--- a/aai-core/src/test/java/org/onap/aai/util/AAICSVWriterTest.java
+++ /dev/null
@@ -1,77 +0,0 @@
-/**
- * ============LICENSE_START=======================================================
- * org.onap.aai
- * ================================================================================
- * Copyright © 2017 AT&T Intellectual Property. All rights reserved.
- * ================================================================================
- * Licensed under the Apache License, Version 2.0 (the "License");
- * you may not use this file except in compliance with the License.
- * You may obtain a copy of the License at
- *
- * http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- * ============LICENSE_END=========================================================
- *
- * ECOMP is a trademark and service mark of AT&T Intellectual Property.
- */
-package org.onap.aai.util;
-
-import java.io.File;
-import java.io.FileWriter;
-import java.io.IOException;
-
-import org.junit.Assert;
-import org.junit.Test;
-
-public class AAICSVWriterTest {
-
- private final String TEMP_DIR=System.getProperty("java.io.tmpdir")+"/test.csv";
-
- @Test
- public void writeFile() throws IOException
- {
-
-
- FileWriter fileWriter = new FileWriter(TEMP_DIR);
- AAICSVWriter aaicsvWriter = new AAICSVWriter(fileWriter, ",", '\'', null);
- aaicsvWriter.writeColumn(new String[]{"id", "name", null});
- aaicsvWriter.writeColumn(null);
- aaicsvWriter.writeNext(new String[]{"1", "Test1"}, true);
- aaicsvWriter.writeNext(new String[]{"1", "Test1"});
- aaicsvWriter.writeNext(new String[]{"1", "Test1"});
- aaicsvWriter.writeNext(new String[]{"1", "Test@"}, false);
- aaicsvWriter.writeNext(new String[]{"1", "Test1"});
- aaicsvWriter.writeNext(new String[]{"1", "Test1"});
- aaicsvWriter.writeNext(new String[]{"1", "Test1"});
- aaicsvWriter.writeNext(new String[]{"1", "Test1"});
- aaicsvWriter.writeNext(new String[]{"1", "Test1"});
- aaicsvWriter.writeNext(new String[]{"1", null});
- aaicsvWriter.writeNext(null);
- aaicsvWriter.close();
- File file = new File(TEMP_DIR);
- Assert.assertTrue("File shoud be exists", file.exists());
- }
-
- @Test
- public void writeFile1() throws IOException
- {
- FileWriter fileWriter = new FileWriter(TEMP_DIR);
- AAICSVWriter aaicsvWriter = new AAICSVWriter(fileWriter, ",", '\u0000', null);
- aaicsvWriter.writeNext(new String[]{"1", "Test1"}, true);
- aaicsvWriter.writeNext(new String[]{"1", "Tes\"t@"}, false);
- aaicsvWriter.writeNext(new String[]{"1", "Tes\t@"}, false);
- aaicsvWriter.writeNext(new String[]{"1", "Test,@"}, false);
- aaicsvWriter.writeNext(new String[]{"1", "Tes\n"}, false);
- aaicsvWriter.writeNext(new String[]{"1", "Tes\r"}, false);
- aaicsvWriter.writeNext(new String[]{"1", "Tes\u0000"}, false);
- aaicsvWriter.close();
- File file = new File(TEMP_DIR);
- Assert.assertTrue("File shoud be exists", file.exists());
-
- }
-}
diff --git a/aai-core/src/test/java/org/onap/aai/util/StoreNotificationEventTest.java b/aai-core/src/test/java/org/onap/aai/util/StoreNotificationEventTest.java
index 5c87b29e..0050c101 100644
--- a/aai-core/src/test/java/org/onap/aai/util/StoreNotificationEventTest.java
+++ b/aai-core/src/test/java/org/onap/aai/util/StoreNotificationEventTest.java
@@ -151,7 +151,7 @@ public class StoreNotificationEventTest extends AAISetup {
DynamicEntity obj = Mockito.mock(DynamicEntity.class);
DynamicJAXBContext notificationJaxbContext = Mockito.mock(DynamicJAXBContext.class);
ClassLoader cl = getClass().getClassLoader();
- InputStream is = cl.getResourceAsStream("bundleconfig-local/etc/oxm/aai_oxm_v11.xml");
+ InputStream is = cl.getResourceAsStream("oxm/aai_oxm_v11.xml");
Map<String, Object> properties = new HashMap<String, Object>();
properties.put(JAXBContextProperties.OXM_METADATA_SOURCE, is);
DynamicJAXBContext notificationJaxbContextReal = DynamicJAXBContextFactory.createContextFromOXM(cl, properties);
diff --git a/aai-core/src/test/resources/bundleconfig-local/etc/oxm/aai_oxm_v10.xml b/aai-core/src/test/resources/oxm/aai_oxm_v10.xml
index 51eaa349..51eaa349 100644
--- a/aai-core/src/test/resources/bundleconfig-local/etc/oxm/aai_oxm_v10.xml
+++ b/aai-core/src/test/resources/oxm/aai_oxm_v10.xml
diff --git a/aai-core/src/test/resources/bundleconfig-local/etc/oxm/aai_oxm_v11.xml b/aai-core/src/test/resources/oxm/aai_oxm_v11.xml
index 90d023ce..90d023ce 100644
--- a/aai-core/src/test/resources/bundleconfig-local/etc/oxm/aai_oxm_v11.xml
+++ b/aai-core/src/test/resources/oxm/aai_oxm_v11.xml
diff --git a/aai-core/src/test/resources/bundleconfig-local/etc/oxm/aai_oxm_v12.xml b/aai-core/src/test/resources/oxm/aai_oxm_v12.xml
index 2364cf82..4eff665e 100644
--- a/aai-core/src/test/resources/bundleconfig-local/etc/oxm/aai_oxm_v12.xml
+++ b/aai-core/src/test/resources/oxm/aai_oxm_v12.xml
@@ -5139,13 +5139,13 @@
</xml-properties>
<xml-root-element name="reserved-prop-names" />
<java-attributes>
- <xml-element java-attribute="lastModSourceOfTruth" name="last-mod-source-of-truth" type="java.lang.String" />
- <xml-element java-attribute="aaiNodeType" name="aai-node-type" type="java.lang.String" />
- <xml-element java-attribute="aaiCreatedTs" name="aai-created-ts" type="java.lang.Long" />
- <xml-element java-attribute="aaiUniqueKey" name="aai-unique-key" type="java.lang.String" />
- <xml-element java-attribute="aaiLastModTs" name="aai-last-mod-ts" type="java.lang.Long" />
- <xml-element java-attribute="sourceOfTruth" name="source-of-truth" type="java.lang.String" />
- <xml-element java-attribute="aaiUri" name="aai-uri" type="java.lang.String" />
+ <xml-element java-attribute="edgeLabel" name="edgeLabel" type="java.lang.String" />
+ <xml-element java-attribute="direction" name="direction" type="java.lang.String" />
+ <xml-element java-attribute="multiplicityRule" name="multiplicityRule" type="java.lang.String" />
+ <xml-element java-attribute="containsOtherV" name="contains-other-v" type="java.lang.String" />
+ <xml-element java-attribute="deleteOtherV" name="delete-other-v" type="java.lang.String" />
+ <xml-element java-attribute="svcinfra" name="SVC-INFRA" type="java.lang.String" />
+ <xml-element java-attribute="preventDelete" name="prevent-delete" type="java.lang.String" />
</java-attributes>
</java-type>
<java-type name="EdgePropNames">
diff --git a/aai-core/src/test/resources/bundleconfig-local/etc/oxm/aai_oxm_v8.xml b/aai-core/src/test/resources/oxm/aai_oxm_v8.xml
index d666b738..d666b738 100644
--- a/aai-core/src/test/resources/bundleconfig-local/etc/oxm/aai_oxm_v8.xml
+++ b/aai-core/src/test/resources/oxm/aai_oxm_v8.xml
diff --git a/aai-core/src/test/resources/bundleconfig-local/etc/oxm/aai_oxm_v9.xml b/aai-core/src/test/resources/oxm/aai_oxm_v9.xml
index ecffb2fc..ecffb2fc 100644
--- a/aai-core/src/test/resources/bundleconfig-local/etc/oxm/aai_oxm_v9.xml
+++ b/aai-core/src/test/resources/oxm/aai_oxm_v9.xml
diff --git a/aai-core/src/test/resources/bundleconfig-local/etc/oxm/sideeffect/nested-case.json b/aai-core/src/test/resources/oxm/sideeffect/nested-case.json
index 40a0493a..40a0493a 100644
--- a/aai-core/src/test/resources/bundleconfig-local/etc/oxm/sideeffect/nested-case.json
+++ b/aai-core/src/test/resources/oxm/sideeffect/nested-case.json
diff --git a/aai-schema/src/main/resources/aai_swagger_html/aai_swagger_v10.html b/aai-schema/src/main/resources/aai_swagger_html/aai_swagger_v10.html
index 16503665..5c6001cc 100644
--- a/aai-schema/src/main/resources/aai_swagger_html/aai_swagger_v10.html
+++ b/aai-schema/src/main/resources/aai_swagger_html/aai_swagger_v10.html
@@ -1,4 +1,3 @@
-
<!DOCTYPE html>
<html>
<head>
@@ -15,8 +14,11 @@
<body>
<div class="container">
<h1>Active and Available Inventory REST API.</h1>
- <p class="sw-info-version">Version: <span>v11</span></p>
- <p><p>Copyright &copy; 2017 AT&amp;T Intellectual Property. All rights reserved.<br/>
+ <p class="sw-info-version">Version: <span>v12</span></p>
+ <p><p><br/>
+[Differences versus the previous schema version](apidocs/aai_swagger_v10.diff)<br/>
+<br/>
+Copyright &copy; 2017 AT&amp;T Intellectual Property. All rights reserved.<br/>
<br/>
Licensed under the Creative Commons License, Attribution 4.0 Intl. (the &quot;License&quot;); you may not use this documentation except in compliance with the License.<br/>
<br/>
@@ -65,6 +67,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}</a></td>
+ <td><p>update an existing cloud-region</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}</a></td>
<td><p>delete an existing cloud-region</p>
</td>
@@ -85,6 +92,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--availability-zones-availability-zone--availability-zone-name--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/availability-zones/availability-zone/{availability-zone-name}</a></td>
+ <td><p>update an existing availability-zone</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--availability-zones-availability-zone--availability-zone-name--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/availability-zones/availability-zone/{availability-zone-name}</a></td>
<td><p>delete an existing availability-zone</p>
</td>
@@ -115,6 +127,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--dvs-switches-dvs-switch--switch-name--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/dvs-switches/dvs-switch/{switch-name}</a></td>
+ <td><p>update an existing dvs-switch</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--dvs-switches-dvs-switch--switch-name--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/dvs-switches/dvs-switch/{switch-name}</a></td>
<td><p>delete an existing dvs-switch</p>
</td>
@@ -145,6 +162,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--flavors-flavor--flavor-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/flavors/flavor/{flavor-id}</a></td>
+ <td><p>update an existing flavor</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--flavors-flavor--flavor-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/flavors/flavor/{flavor-id}</a></td>
<td><p>delete an existing flavor</p>
</td>
@@ -175,6 +197,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--group-assignments-group-assignment--group-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/group-assignments/group-assignment/{group-id}</a></td>
+ <td><p>update an existing group-assignment</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--group-assignments-group-assignment--group-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/group-assignments/group-assignment/{group-id}</a></td>
<td><p>delete an existing group-assignment</p>
</td>
@@ -205,6 +232,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}</a></td>
+ <td><p>update an existing image</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}</a></td>
<td><p>delete an existing image</p>
</td>
@@ -225,6 +257,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--metadata-metadatum--metaname--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}/metadata/metadatum/{metaname}</a></td>
+ <td><p>update an existing metadatum</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--metadata-metadatum--metaname--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}/metadata/metadatum/{metaname}</a></td>
<td><p>delete an existing metadatum</p>
</td>
@@ -255,6 +292,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--oam-networks-oam-network--network-uuid--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/oam-networks/oam-network/{network-uuid}</a></td>
+ <td><p>update an existing oam-network</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--oam-networks-oam-network--network-uuid--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/oam-networks/oam-network/{network-uuid}</a></td>
<td><p>delete an existing oam-network</p>
</td>
@@ -295,6 +337,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--snapshots-snapshot--snapshot-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/snapshots/snapshot/{snapshot-id}</a></td>
+ <td><p>update an existing snapshot</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--snapshots-snapshot--snapshot-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/snapshots/snapshot/{snapshot-id}</a></td>
<td><p>delete an existing snapshot</p>
</td>
@@ -325,6 +372,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}</a></td>
+ <td><p>update an existing tenant</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}</a></td>
<td><p>delete an existing tenant</p>
</td>
@@ -355,6 +407,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}</a></td>
+ <td><p>update an existing vserver</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}</a></td>
<td><p>delete an existing vserver</p>
</td>
@@ -375,6 +432,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -390,6 +452,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -415,6 +482,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -455,6 +527,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -485,6 +562,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -500,6 +582,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -525,6 +612,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -575,6 +667,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--volumes-volume--volume-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/volumes/volume/{volume-id}</a></td>
+ <td><p>update an existing volume</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--volumes-volume--volume-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/volumes/volume/{volume-id}</a></td>
<td><p>delete an existing volume</p>
</td>
@@ -605,6 +702,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--volume-groups-volume-group--volume-group-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/volume-groups/volume-group/{volume-group-id}</a></td>
+ <td><p>update an existing volume-group</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--volume-groups-volume-group--volume-group-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/volume-groups/volume-group/{volume-group-id}</a></td>
<td><p>delete an existing volume-group</p>
</td>
@@ -635,6 +737,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-complexes-complex--physical-location-id--patch">PATCH /cloud-infrastructure/complexes/complex/{physical-location-id}</a></td>
+ <td><p>update an existing complex</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-complexes-complex--physical-location-id--delete">DELETE /cloud-infrastructure/complexes/complex/{physical-location-id}</a></td>
<td><p>delete an existing complex</p>
</td>
@@ -655,6 +762,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-complexes-complex--physical-location-id--ctag-pools-ctag-pool--target-pe---availability-zone-name--patch">PATCH /cloud-infrastructure/complexes/complex/{physical-location-id}/ctag-pools/ctag-pool/{target-pe}/{availability-zone-name}</a></td>
+ <td><p>update an existing ctag-pool</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-complexes-complex--physical-location-id--ctag-pools-ctag-pool--target-pe---availability-zone-name--delete">DELETE /cloud-infrastructure/complexes/complex/{physical-location-id}/ctag-pools/ctag-pool/{target-pe}/{availability-zone-name}</a></td>
<td><p>delete an existing ctag-pool</p>
</td>
@@ -695,6 +807,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-network-profiles-network-profile--nm-profile-name--patch">PATCH /cloud-infrastructure/network-profiles/network-profile/{nm-profile-name}</a></td>
+ <td><p>update an existing network-profile</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-network-profiles-network-profile--nm-profile-name--delete">DELETE /cloud-infrastructure/network-profiles/network-profile/{nm-profile-name}</a></td>
<td><p>delete an existing network-profile</p>
</td>
@@ -725,6 +842,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}</a></td>
+ <td><p>update an existing pserver</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}</a></td>
<td><p>delete an existing pserver</p>
</td>
@@ -745,6 +867,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}</a></td>
+ <td><p>update an existing lag-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}</a></td>
<td><p>delete an existing lag-interface</p>
</td>
@@ -765,6 +892,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -780,6 +912,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -805,6 +942,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -845,6 +987,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -875,6 +1022,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -890,6 +1042,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -915,6 +1072,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -965,6 +1127,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}</a></td>
+ <td><p>update an existing p-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}</a></td>
<td><p>delete an existing p-interface</p>
</td>
@@ -985,6 +1152,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -1000,6 +1172,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -1025,6 +1202,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -1065,6 +1247,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -1095,6 +1282,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -1110,6 +1302,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -1135,6 +1332,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -1195,6 +1397,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--patch">PATCH /cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}</a></td>
+ <td><p>update an existing virtual-data-center</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--delete">DELETE /cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}</a></td>
<td><p>delete an existing virtual-data-center</p>
</td>
@@ -1239,6 +1446,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-connectors-connector--resource-instance-id--patch">PATCH /business/connectors/connector/{resource-instance-id}</a></td>
+ <td><p>update an existing connector</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-connectors-connector--resource-instance-id--delete">DELETE /business/connectors/connector/{resource-instance-id}</a></td>
<td><p>delete an existing connector</p>
</td>
@@ -1259,6 +1471,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-connectors-connector--resource-instance-id--metadata-metadatum--metaname--patch">PATCH /business/connectors/connector/{resource-instance-id}/metadata/metadatum/{metaname}</a></td>
+ <td><p>update an existing metadatum</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-connectors-connector--resource-instance-id--metadata-metadatum--metaname--delete">DELETE /business/connectors/connector/{resource-instance-id}/metadata/metadatum/{metaname}</a></td>
<td><p>delete an existing metadatum</p>
</td>
@@ -1289,6 +1506,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-customers-customer--global-customer-id--patch">PATCH /business/customers/customer/{global-customer-id}</a></td>
+ <td><p>update an existing customer</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-customers-customer--global-customer-id--delete">DELETE /business/customers/customer/{global-customer-id}</a></td>
<td><p>delete an existing customer</p>
</td>
@@ -1319,6 +1541,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--patch">PATCH /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}</a></td>
+ <td><p>update an existing service-subscription</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--delete">DELETE /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}</a></td>
<td><p>delete an existing service-subscription</p>
</td>
@@ -1349,6 +1576,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--patch">PATCH /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}</a></td>
+ <td><p>update an existing service-instance</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--delete">DELETE /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}</a></td>
<td><p>delete an existing service-instance</p>
</td>
@@ -1369,6 +1601,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--patch">PATCH /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/allotted-resources/allotted-resource/{id}</a></td>
+ <td><p>update an existing allotted-resource</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--delete">DELETE /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/allotted-resources/allotted-resource/{id}</a></td>
<td><p>delete an existing allotted-resource</p>
</td>
@@ -1399,6 +1636,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--tunnel-xconnects-tunnel-xconnect--id--patch">PATCH /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/allotted-resources/allotted-resource/{id}/tunnel-xconnects/tunnel-xconnect/{id}</a></td>
+ <td><p>update an existing tunnel-xconnect</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--tunnel-xconnects-tunnel-xconnect--id--delete">DELETE /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/allotted-resources/allotted-resource/{id}/tunnel-xconnects/tunnel-xconnect/{id}</a></td>
<td><p>delete an existing tunnel-xconnect</p>
</td>
@@ -1429,6 +1671,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--metadata-metadatum--metaname--patch">PATCH /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/metadata/metadatum/{metaname}</a></td>
+ <td><p>update an existing metadatum</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--metadata-metadatum--metaname--delete">DELETE /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/metadata/metadatum/{metaname}</a></td>
<td><p>delete an existing metadatum</p>
</td>
@@ -1473,6 +1720,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--patch">PATCH /service-design-and-creation/models/model/{model-invariant-id}</a></td>
+ <td><p>update an existing model</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--delete">DELETE /service-design-and-creation/models/model/{model-invariant-id}</a></td>
<td><p>delete an existing model</p>
</td>
@@ -1493,6 +1745,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--patch">PATCH /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}</a></td>
+ <td><p>update an existing model-ver</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--delete">DELETE /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}</a></td>
<td><p>delete an existing model-ver</p>
</td>
@@ -1513,6 +1770,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--metadata-metadatum--metaname--patch">PATCH /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/metadata/metadatum/{metaname}</a></td>
+ <td><p>update an existing metadatum</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--metadata-metadatum--metaname--delete">DELETE /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/metadata/metadatum/{metaname}</a></td>
<td><p>delete an existing metadatum</p>
</td>
@@ -1533,6 +1795,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--patch">PATCH /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}</a></td>
+ <td><p>update an existing model-element</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--delete">DELETE /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}</a></td>
<td><p>delete an existing model-element</p>
</td>
@@ -1553,6 +1820,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--patch">PATCH /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}</a></td>
+ <td><p>update an existing model-constraint</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--delete">DELETE /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}</a></td>
<td><p>delete an existing model-constraint</p>
</td>
@@ -1573,6 +1845,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--patch">PATCH /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}</a></td>
+ <td><p>update an existing constrained-element-set</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--delete">DELETE /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}</a></td>
<td><p>delete an existing constrained-element-set</p>
</td>
@@ -1593,6 +1870,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--element-choice-sets-element-choice-set--element-choice-set-uuid--patch">PATCH /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}/element-choice-sets/element-choice-set/{element-choice-set-uuid}</a></td>
+ <td><p>update an existing element-choice-set</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--element-choice-sets-element-choice-set--element-choice-set-uuid--delete">DELETE /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}/element-choice-sets/element-choice-set/{element-choice-set-uuid}</a></td>
<td><p>delete an existing element-choice-set</p>
</td>
@@ -1663,6 +1945,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--patch">PATCH /service-design-and-creation/named-queries/named-query/{named-query-uuid}</a></td>
+ <td><p>update an existing named-query</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--delete">DELETE /service-design-and-creation/named-queries/named-query/{named-query-uuid}</a></td>
<td><p>delete an existing named-query</p>
</td>
@@ -1683,6 +1970,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--patch">PATCH /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}</a></td>
+ <td><p>update an existing named-query-element</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--delete">DELETE /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}</a></td>
<td><p>delete an existing named-query-element</p>
</td>
@@ -1703,6 +1995,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--property-constraints-property-constraint--property-constraint-uuid--patch">PATCH /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/property-constraints/property-constraint/{property-constraint-uuid}</a></td>
+ <td><p>update an existing property-constraint</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--property-constraints-property-constraint--property-constraint-uuid--delete">DELETE /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/property-constraints/property-constraint/{property-constraint-uuid}</a></td>
<td><p>delete an existing property-constraint</p>
</td>
@@ -1723,6 +2020,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--related-lookups-related-lookup--related-lookup-uuid--patch">PATCH /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/related-lookups/related-lookup/{related-lookup-uuid}</a></td>
+ <td><p>update an existing related-lookup</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--related-lookups-related-lookup--related-lookup-uuid--delete">DELETE /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/related-lookups/related-lookup/{related-lookup-uuid}</a></td>
<td><p>delete an existing related-lookup</p>
</td>
@@ -1773,6 +2075,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-service-capabilities-service-capability--service-type---vnf-type--patch">PATCH /service-design-and-creation/service-capabilities/service-capability/{service-type}/{vnf-type}</a></td>
+ <td><p>update an existing service-capability</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-service-capabilities-service-capability--service-type---vnf-type--delete">DELETE /service-design-and-creation/service-capabilities/service-capability/{service-type}/{vnf-type}</a></td>
<td><p>delete an existing service-capability</p>
</td>
@@ -1803,6 +2110,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-services-service--service-id--patch">PATCH /service-design-and-creation/services/service/{service-id}</a></td>
+ <td><p>update an existing service</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-services-service--service-id--delete">DELETE /service-design-and-creation/services/service/{service-id}</a></td>
<td><p>delete an existing service</p>
</td>
@@ -1833,6 +2145,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-vnf-images-vnf-image--vnf-image-uuid--patch">PATCH /service-design-and-creation/vnf-images/vnf-image/{vnf-image-uuid}</a></td>
+ <td><p>update an existing vnf-image</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-vnf-images-vnf-image--vnf-image-uuid--delete">DELETE /service-design-and-creation/vnf-images/vnf-image/{vnf-image-uuid}</a></td>
<td><p>delete an existing vnf-image</p>
</td>
@@ -1877,6 +2194,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}</a></td>
+ <td><p>update an existing generic-vnf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}</a></td>
<td><p>delete an existing generic-vnf</p>
</td>
@@ -1897,6 +2219,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/entitlements/entitlement/{group-uuid}/{resource-uuid}</a></td>
+ <td><p>update an existing entitlement</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/entitlements/entitlement/{group-uuid}/{resource-uuid}</a></td>
<td><p>delete an existing entitlement</p>
</td>
@@ -1927,6 +2254,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -1942,6 +2274,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -1967,6 +2304,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -2007,6 +2349,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -2037,6 +2384,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -2052,6 +2404,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -2077,6 +2434,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -2117,6 +2479,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}</a></td>
+ <td><p>update an existing lag-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}</a></td>
<td><p>delete an existing lag-interface</p>
</td>
@@ -2137,6 +2504,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -2152,6 +2524,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -2177,6 +2554,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -2217,6 +2599,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -2247,6 +2634,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -2262,6 +2654,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -2287,6 +2684,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -2337,6 +2739,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--licenses-license--group-uuid---resource-uuid--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/licenses/license/{group-uuid}/{resource-uuid}</a></td>
+ <td><p>update an existing license</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--licenses-license--group-uuid---resource-uuid--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/licenses/license/{group-uuid}/{resource-uuid}</a></td>
<td><p>delete an existing license</p>
</td>
@@ -2377,6 +2784,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--vf-modules-vf-module--vf-module-id--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/vf-modules/vf-module/{vf-module-id}</a></td>
+ <td><p>update an existing vf-module</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--vf-modules-vf-module--vf-module-id--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/vf-modules/vf-module/{vf-module-id}</a></td>
<td><p>delete an existing vf-module</p>
</td>
@@ -2407,6 +2819,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-instance-groups-instance-group--id--patch">PATCH /network/instance-groups/instance-group/{id}</a></td>
+ <td><p>update an existing instance-group</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-instance-groups-instance-group--id--delete">DELETE /network/instance-groups/instance-group/{id}</a></td>
<td><p>delete an existing instance-group</p>
</td>
@@ -2437,6 +2854,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--patch">PATCH /network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}</a></td>
+ <td><p>update an existing ipsec-configuration</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--delete">DELETE /network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}</a></td>
<td><p>delete an existing ipsec-configuration</p>
</td>
@@ -2467,6 +2889,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--vig-servers-vig-server--vig-address-type--patch">PATCH /network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}/vig-servers/vig-server/{vig-address-type}</a></td>
+ <td><p>update an existing vig-server</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--vig-servers-vig-server--vig-address-type--delete">DELETE /network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}/vig-servers/vig-server/{vig-address-type}</a></td>
<td><p>delete an existing vig-server</p>
</td>
@@ -2497,6 +2924,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-l3-networks-l3-network--network-id--patch">PATCH /network/l3-networks/l3-network/{network-id}</a></td>
+ <td><p>update an existing l3-network</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-l3-networks-l3-network--network-id--delete">DELETE /network/l3-networks/l3-network/{network-id}</a></td>
<td><p>delete an existing l3-network</p>
</td>
@@ -2517,6 +2949,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-l3-networks-l3-network--network-id--ctag-assignments-ctag-assignment--vlan-id-inner--patch">PATCH /network/l3-networks/l3-network/{network-id}/ctag-assignments/ctag-assignment/{vlan-id-inner}</a></td>
+ <td><p>update an existing ctag-assignment</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-l3-networks-l3-network--network-id--ctag-assignments-ctag-assignment--vlan-id-inner--delete">DELETE /network/l3-networks/l3-network/{network-id}/ctag-assignments/ctag-assignment/{vlan-id-inner}</a></td>
<td><p>delete an existing ctag-assignment</p>
</td>
@@ -2557,6 +2994,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-l3-networks-l3-network--network-id--segmentation-assignments-segmentation-assignment--segmentation-id--patch">PATCH /network/l3-networks/l3-network/{network-id}/segmentation-assignments/segmentation-assignment/{segmentation-id}</a></td>
+ <td><p>update an existing segmentation-assignment</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-l3-networks-l3-network--network-id--segmentation-assignments-segmentation-assignment--segmentation-id--delete">DELETE /network/l3-networks/l3-network/{network-id}/segmentation-assignments/segmentation-assignment/{segmentation-id}</a></td>
<td><p>delete an existing segmentation-assignment</p>
</td>
@@ -2587,6 +3029,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-l3-networks-l3-network--network-id--subnets-subnet--subnet-id--patch">PATCH /network/l3-networks/l3-network/{network-id}/subnets/subnet/{subnet-id}</a></td>
+ <td><p>update an existing subnet</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-l3-networks-l3-network--network-id--subnets-subnet--subnet-id--delete">DELETE /network/l3-networks/l3-network/{network-id}/subnets/subnet/{subnet-id}</a></td>
<td><p>delete an existing subnet</p>
</td>
@@ -2617,6 +3064,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-lag-links-lag-link--link-name--patch">PATCH /network/lag-links/lag-link/{link-name}</a></td>
+ <td><p>update an existing lag-link</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-lag-links-lag-link--link-name--delete">DELETE /network/lag-links/lag-link/{link-name}</a></td>
<td><p>delete an existing lag-link</p>
</td>
@@ -2647,6 +3099,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-logical-links-logical-link--link-name--patch">PATCH /network/logical-links/logical-link/{link-name}</a></td>
+ <td><p>update an existing logical-link</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-logical-links-logical-link--link-name--delete">DELETE /network/logical-links/logical-link/{link-name}</a></td>
<td><p>delete an existing logical-link</p>
</td>
@@ -2677,6 +3134,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-multicast-configurations-multicast-configuration--multicast-configuration-id--patch">PATCH /network/multicast-configurations/multicast-configuration/{multicast-configuration-id}</a></td>
+ <td><p>update an existing multicast-configuration</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-multicast-configurations-multicast-configuration--multicast-configuration-id--delete">DELETE /network/multicast-configurations/multicast-configuration/{multicast-configuration-id}</a></td>
<td><p>delete an existing multicast-configuration</p>
</td>
@@ -2707,6 +3169,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-network-policies-network-policy--network-policy-id--patch">PATCH /network/network-policies/network-policy/{network-policy-id}</a></td>
+ <td><p>update an existing network-policy</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-network-policies-network-policy--network-policy-id--delete">DELETE /network/network-policies/network-policy/{network-policy-id}</a></td>
<td><p>delete an existing network-policy</p>
</td>
@@ -2737,6 +3204,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--patch">PATCH /network/newvces/newvce/{vnf-id2}</a></td>
+ <td><p>update an existing newvce</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--delete">DELETE /network/newvces/newvce/{vnf-id2}</a></td>
<td><p>delete an existing newvce</p>
</td>
@@ -2757,6 +3229,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--patch">PATCH /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--delete">DELETE /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -2772,6 +3249,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -2797,6 +3279,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -2837,6 +3324,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -2867,6 +3359,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -2882,6 +3379,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -2907,6 +3409,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -2957,6 +3464,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-physical-links-physical-link--link-name--patch">PATCH /network/physical-links/physical-link/{link-name}</a></td>
+ <td><p>update an existing physical-link</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-physical-links-physical-link--link-name--delete">DELETE /network/physical-links/physical-link/{link-name}</a></td>
<td><p>delete an existing physical-link</p>
</td>
@@ -2987,6 +3499,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--patch">PATCH /network/pnfs/pnf/{pnf-name}</a></td>
+ <td><p>update an existing pnf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--delete">DELETE /network/pnfs/pnf/{pnf-name}</a></td>
<td><p>delete an existing pnf</p>
</td>
@@ -3007,6 +3524,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}</a></td>
+ <td><p>update an existing lag-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}</a></td>
<td><p>delete an existing lag-interface</p>
</td>
@@ -3027,6 +3549,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -3042,6 +3569,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -3067,6 +3599,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -3107,6 +3644,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -3137,6 +3679,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -3152,6 +3699,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -3177,6 +3729,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -3227,6 +3784,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}</a></td>
+ <td><p>update an existing p-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}</a></td>
<td><p>delete an existing p-interface</p>
</td>
@@ -3247,6 +3809,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -3262,6 +3829,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -3287,6 +3859,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -3327,6 +3904,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -3357,6 +3939,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -3372,6 +3959,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -3397,6 +3989,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -3457,6 +4054,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-route-table-references-route-table-reference--route-table-reference-id--patch">PATCH /network/route-table-references/route-table-reference/{route-table-reference-id}</a></td>
+ <td><p>update an existing route-table-reference</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-route-table-references-route-table-reference--route-table-reference-id--delete">DELETE /network/route-table-references/route-table-reference/{route-table-reference-id}</a></td>
<td><p>delete an existing route-table-reference</p>
</td>
@@ -3487,6 +4089,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--patch">PATCH /network/site-pair-sets/site-pair-set/{site-pair-set-id}</a></td>
+ <td><p>update an existing site-pair-set</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--delete">DELETE /network/site-pair-sets/site-pair-set/{site-pair-set-id}</a></td>
<td><p>delete an existing site-pair-set</p>
</td>
@@ -3517,6 +4124,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--patch">PATCH /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}</a></td>
+ <td><p>update an existing routing-instance</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--delete">DELETE /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}</a></td>
<td><p>delete an existing routing-instance</p>
</td>
@@ -3547,6 +4159,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--patch">PATCH /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}</a></td>
+ <td><p>update an existing site-pair</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--delete">DELETE /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}</a></td>
<td><p>delete an existing site-pair</p>
</td>
@@ -3567,6 +4184,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--classes-of-service-class-of-service--cos--patch">PATCH /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}/classes-of-service/class-of-service/{cos}</a></td>
+ <td><p>update an existing class-of-service</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--classes-of-service-class-of-service--cos--delete">DELETE /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}/classes-of-service/class-of-service/{cos}</a></td>
<td><p>delete an existing class-of-service</p>
</td>
@@ -3607,6 +4229,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vces-vce--vnf-id--patch">PATCH /network/vces/vce/{vnf-id}</a></td>
+ <td><p>update an existing vce</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vces-vce--vnf-id--delete">DELETE /network/vces/vce/{vnf-id}</a></td>
<td><p>delete an existing vce</p>
</td>
@@ -3627,6 +4254,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vces-vce--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--patch">PATCH /network/vces/vce/{vnf-id}/entitlements/entitlement/{group-uuid}/{resource-uuid}</a></td>
+ <td><p>update an existing entitlement</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vces-vce--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--delete">DELETE /network/vces/vce/{vnf-id}/entitlements/entitlement/{group-uuid}/{resource-uuid}</a></td>
<td><p>delete an existing entitlement</p>
</td>
@@ -3657,6 +4289,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vces-vce--vnf-id--licenses-license--group-uuid---resource-uuid--patch">PATCH /network/vces/vce/{vnf-id}/licenses/license/{group-uuid}/{resource-uuid}</a></td>
+ <td><p>update an existing license</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vces-vce--vnf-id--licenses-license--group-uuid---resource-uuid--delete">DELETE /network/vces/vce/{vnf-id}/licenses/license/{group-uuid}/{resource-uuid}</a></td>
<td><p>delete an existing license</p>
</td>
@@ -3687,6 +4324,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--patch">PATCH /network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}</a></td>
+ <td><p>update an existing port-group</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--delete">DELETE /network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}</a></td>
<td><p>delete an existing port-group</p>
</td>
@@ -3707,6 +4349,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--cvlan-tags-cvlan-tag-entry--cvlan-tag--patch">PATCH /network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}/cvlan-tags/cvlan-tag-entry/{cvlan-tag}</a></td>
+ <td><p>update an existing cvlan-tag-entry</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--cvlan-tags-cvlan-tag-entry--cvlan-tag--delete">DELETE /network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}/cvlan-tags/cvlan-tag-entry/{cvlan-tag}</a></td>
<td><p>delete an existing cvlan-tag-entry</p>
</td>
@@ -3757,6 +4404,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vnfcs-vnfc--vnfc-name--patch">PATCH /network/vnfcs/vnfc/{vnfc-name}</a></td>
+ <td><p>update an existing vnfc</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vnfcs-vnfc--vnfc-name--delete">DELETE /network/vnfcs/vnfc/{vnfc-name}</a></td>
<td><p>delete an existing vnfc</p>
</td>
@@ -3787,6 +4439,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}</a></td>
+ <td><p>update an existing vpls-pe</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}</a></td>
<td><p>delete an existing vpls-pe</p>
</td>
@@ -3807,6 +4464,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}</a></td>
+ <td><p>update an existing lag-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}</a></td>
<td><p>delete an existing lag-interface</p>
</td>
@@ -3827,6 +4489,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -3842,6 +4509,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -3867,6 +4539,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -3907,6 +4584,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -3937,6 +4619,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -3952,6 +4639,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -3977,6 +4669,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -4027,6 +4724,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}</a></td>
+ <td><p>update an existing p-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}</a></td>
<td><p>delete an existing p-interface</p>
</td>
@@ -4047,6 +4749,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -4062,6 +4769,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -4087,6 +4799,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -4127,6 +4844,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -4157,6 +4879,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -4172,6 +4899,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -4197,6 +4929,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -4257,6 +4994,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpn-bindings-vpn-binding--vpn-id--patch">PATCH /network/vpn-bindings/vpn-binding/{vpn-id}</a></td>
+ <td><p>update an existing vpn-binding</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpn-bindings-vpn-binding--vpn-id--delete">DELETE /network/vpn-bindings/vpn-binding/{vpn-id}</a></td>
<td><p>delete an existing vpn-binding</p>
</td>
@@ -4287,6 +5029,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpn-bindings-vpn-binding--vpn-id--route-targets-route-target--global-route-target---route-target-role--patch">PATCH /network/vpn-bindings/vpn-binding/{vpn-id}/route-targets/route-target/{global-route-target}/{route-target-role}</a></td>
+ <td><p>update an existing route-target</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpn-bindings-vpn-binding--vpn-id--route-targets-route-target--global-route-target---route-target-role--delete">DELETE /network/vpn-bindings/vpn-binding/{vpn-id}/route-targets/route-target/{global-route-target}/{route-target-role}</a></td>
<td><p>delete an existing route-target</p>
</td>
@@ -4317,6 +5064,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-zones-zone--zone-id--patch">PATCH /network/zones/zone/{zone-id}</a></td>
+ <td><p>update an existing zone</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-zones-zone--zone-id--delete">DELETE /network/zones/zone/{zone-id}</a></td>
<td><p>delete an existing zone</p>
</td>
@@ -4376,7 +5128,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/connectors">/connectors</a>
+ <a class="json-schema-ref" href="#/getDefinitions/connectors">/connectors</a>
</div>
</div>
</div>
@@ -4531,7 +5283,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/connector">/connector</a>
+ <a class="json-schema-ref" href="#/getDefinitions/connector">/connector</a>
</div>
</div>
</div>
@@ -4578,7 +5330,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>connector object that needs to be created or updated</p>
+ <p><p>connector object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessConnectorsConnector.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -4649,6 +5401,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-connectors-connector--resource-instance-id--"></span>
+ <div id="operation--business-connectors-connector--resource-instance-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing connector</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/connectors/connector/{resource-instance-id}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing connector</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>connector object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/connector">/connector</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ resource-instance-id
+ </td>
+ <td>
+ <p>Unique id of resource instance.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-connectors-connector--resource-instance-id--"></span>
<div id="operation--business-connectors-connector--resource-instance-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing connector</div>
@@ -4868,7 +5709,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadata">/metadata</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadata">/metadata</a>
</div>
</div>
</div>
@@ -5038,7 +5879,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadatum">/metadatum</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadatum">/metadatum</a>
</div>
</div>
</div>
@@ -5085,7 +5926,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>metadatum object that needs to be created or updated</p>
+ <p><p>metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessConnectorsConnectorMetadataMetadatum.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -5171,6 +6012,110 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-connectors-connector--resource-instance-id--metadata-metadatum--metaname--"></span>
+ <div id="operation--business-connectors-connector--resource-instance-id--metadata-metadatum--metaname--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing metadatum</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/connectors/connector/{resource-instance-id}/metadata/metadatum/{metaname}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing metadatum</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>metadatum object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/metadatum">/metadatum</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ resource-instance-id
+ </td>
+ <td>
+ <p>Unique id of resource instance.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ metaname
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-connectors-connector--resource-instance-id--metadata-metadatum--metaname--"></span>
<div id="operation--business-connectors-connector--resource-instance-id--metadata-metadatum--metaname--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing metadatum</div>
@@ -5297,7 +6242,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessConnectorsConnector.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -5480,7 +6425,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/customers">/customers</a>
+ <a class="json-schema-ref" href="#/getDefinitions/customers">/customers</a>
</div>
</div>
</div>
@@ -5605,7 +6550,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/customer">/customer</a>
+ <a class="json-schema-ref" href="#/getDefinitions/customer">/customer</a>
</div>
</div>
</div>
@@ -5652,7 +6597,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>customer object that needs to be created or updated</p>
+ <p><p>customer object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomer.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -5723,6 +6668,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-customers-customer--global-customer-id--"></span>
+ <div id="operation--business-customers-customer--global-customer-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing customer</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/customers/customer/{global-customer-id}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing customer</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>customer object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/customer">/customer</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ global-customer-id
+ </td>
+ <td>
+ <p>Global customer id used across ECOMP to uniquely identify customer.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-customers-customer--global-customer-id--"></span>
<div id="operation--business-customers-customer--global-customer-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing customer</div>
@@ -5834,7 +6868,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomer.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -6078,7 +7112,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/service-subscriptions">/service-subscriptions</a>
+ <a class="json-schema-ref" href="#/getDefinitions/service-subscriptions">/service-subscriptions</a>
</div>
</div>
</div>
@@ -6219,7 +7253,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/service-subscription">/service-subscription</a>
+ <a class="json-schema-ref" href="#/getDefinitions/service-subscription">/service-subscription</a>
</div>
</div>
</div>
@@ -6266,7 +7300,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>service-subscription object that needs to be created or updated</p>
+ <p><p>service-subscription object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscription.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -6353,6 +7387,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--"></span>
+ <div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing service-subscription</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing service-subscription</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>service-subscription object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/service-subscription">/service-subscription</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ global-customer-id
+ </td>
+ <td>
+ <p>Global customer id used across ECOMP to uniquely identify customer.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-type
+ </td>
+ <td>
+ <p>Value defined by orchestration to identify this service across ECOMP.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--"></span>
<div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing service-subscription</div>
@@ -6480,7 +7619,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscription.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -6772,7 +7911,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/service-instances">/service-instances</a>
+ <a class="json-schema-ref" href="#/getDefinitions/service-instances">/service-instances</a>
</div>
</div>
</div>
@@ -7034,7 +8173,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/service-instance">/service-instance</a>
+ <a class="json-schema-ref" href="#/getDefinitions/service-instance">/service-instance</a>
</div>
</div>
</div>
@@ -7081,7 +8220,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>service-instance object that needs to be created or updated</p>
+ <p><p>service-instance object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -7184,6 +8323,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--"></span>
+ <div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing service-instance</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing service-instance</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>service-instance object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/service-instance">/service-instance</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ global-customer-id
+ </td>
+ <td>
+ <p>Global customer id used across ECOMP to uniquely identify customer.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-type
+ </td>
+ <td>
+ <p>Value defined by orchestration to identify this service across ECOMP.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-instance-id
+ </td>
+ <td>
+ <p>Uniquely identifies this instance of a service</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--"></span>
<div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing service-instance</div>
@@ -7542,7 +8802,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/allotted-resources">/allotted-resources</a>
+ <a class="json-schema-ref" href="#/getDefinitions/allotted-resources">/allotted-resources</a>
</div>
</div>
</div>
@@ -7880,7 +9140,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/allotted-resource">/allotted-resource</a>
+ <a class="json-schema-ref" href="#/getDefinitions/allotted-resource">/allotted-resource</a>
</div>
</div>
</div>
@@ -7927,7 +9187,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>allotted-resource object that needs to be created or updated</p>
+ <p><p>allotted-resource object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResource.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -8046,6 +9306,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--"></span>
+ <div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing allotted-resource</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/allotted-resources/allotted-resource/{id}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing allotted-resource</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>allotted-resource object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/allotted-resource">/allotted-resource</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ global-customer-id
+ </td>
+ <td>
+ <p>Global customer id used across ECOMP to uniquely identify customer.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-type
+ </td>
+ <td>
+ <p>Value defined by orchestration to identify this service across ECOMP.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-instance-id
+ </td>
+ <td>
+ <p>Uniquely identifies this instance of a service</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ id
+ </td>
+ <td>
+ <p>Allotted Resource id UUID assigned to this instance.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--"></span>
<div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing allotted-resource</div>
@@ -8205,7 +9602,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResource.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -8758,7 +10155,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/tunnel-xconnects">/tunnel-xconnects</a>
+ <a class="json-schema-ref" href="#/getDefinitions/tunnel-xconnects">/tunnel-xconnects</a>
</div>
</div>
</div>
@@ -9112,7 +10509,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/tunnel-xconnect">/tunnel-xconnect</a>
+ <a class="json-schema-ref" href="#/getDefinitions/tunnel-xconnect">/tunnel-xconnect</a>
</div>
</div>
</div>
@@ -9159,7 +10556,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>tunnel-xconnect object that needs to be created or updated</p>
+ <p><p>tunnel-xconnect object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResourceTunnelXconnectsTunnelXconnect.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -9294,6 +10691,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--tunnel-xconnects-tunnel-xconnect--id--"></span>
+ <div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--tunnel-xconnects-tunnel-xconnect--id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing tunnel-xconnect</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/allotted-resources/allotted-resource/{id}/tunnel-xconnects/tunnel-xconnect/{id}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing tunnel-xconnect</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>tunnel-xconnect object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/tunnel-xconnect">/tunnel-xconnect</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ global-customer-id
+ </td>
+ <td>
+ <p>Global customer id used across ECOMP to uniquely identify customer.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-type
+ </td>
+ <td>
+ <p>Value defined by orchestration to identify this service across ECOMP.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-instance-id
+ </td>
+ <td>
+ <p>Uniquely identifies this instance of a service</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ id
+ </td>
+ <td>
+ <p>Allotted Resource id UUID assigned to this instance.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ id
+ </td>
+ <td>
+ <p>Allotted Resource id UUID assigned to this instance.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--tunnel-xconnects-tunnel-xconnect--id--"></span>
<div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--tunnel-xconnects-tunnel-xconnect--id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing tunnel-xconnect</div>
@@ -9469,7 +11019,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResourceTunnelXconnectsTunnelXconnect.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -9978,7 +11528,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadata">/metadata</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadata">/metadata</a>
</div>
</div>
</div>
@@ -10255,7 +11805,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadatum">/metadatum</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadatum">/metadatum</a>
</div>
</div>
</div>
@@ -10302,7 +11852,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>metadatum object that needs to be created or updated</p>
+ <p><p>metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceMetadataMetadatum.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -10420,6 +11970,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--metadata-metadatum--metaname--"></span>
+ <div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--metadata-metadatum--metaname--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing metadatum</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/metadata/metadatum/{metaname}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing metadatum</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>metadatum object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/metadatum">/metadatum</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ global-customer-id
+ </td>
+ <td>
+ <p>Global customer id used across ECOMP to uniquely identify customer.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-type
+ </td>
+ <td>
+ <p>Value defined by orchestration to identify this service across ECOMP.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-instance-id
+ </td>
+ <td>
+ <p>Uniquely identifies this instance of a service</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ metaname
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--metadata-metadatum--metaname--"></span>
<div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--metadata-metadatum--metaname--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing metadatum</div>
@@ -10578,7 +12264,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -10825,7 +12511,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/cloud-regions">/cloud-regions</a>
+ <a class="json-schema-ref" href="#/getDefinitions/cloud-regions">/cloud-regions</a>
</div>
</div>
</div>
@@ -10966,7 +12652,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/cloud-region">/cloud-region</a>
+ <a class="json-schema-ref" href="#/getDefinitions/cloud-region">/cloud-region</a>
</div>
</div>
</div>
@@ -11013,7 +12699,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>cloud-region object that needs to be created or updated</p>
+ <p><p>cloud-region object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegion.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -11100,6 +12786,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing cloud-region</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing cloud-region</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>cloud-region object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/cloud-region">/cloud-region</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing cloud-region</div>
@@ -11321,7 +13112,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/availability-zones">/availability-zones</a>
+ <a class="json-schema-ref" href="#/getDefinitions/availability-zones">/availability-zones</a>
</div>
</div>
</div>
@@ -11478,7 +13269,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/availability-zone">/availability-zone</a>
+ <a class="json-schema-ref" href="#/getDefinitions/availability-zone">/availability-zone</a>
</div>
</div>
</div>
@@ -11525,7 +13316,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>availability-zone object that needs to be created or updated</p>
+ <p><p>availability-zone object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -11628,6 +13419,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--availability-zones-availability-zone--availability-zone-name--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--availability-zones-availability-zone--availability-zone-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing availability-zone</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/availability-zones/availability-zone/{availability-zone-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing availability-zone</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>availability-zone object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/availability-zone">/availability-zone</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ availability-zone-name
+ </td>
+ <td>
+ <p>Name of the availability zone. Unique across a cloud region</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--availability-zones-availability-zone--availability-zone-name--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--availability-zones-availability-zone--availability-zone-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing availability-zone</div>
@@ -11771,7 +13683,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -12095,7 +14007,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/dvs-switches">/dvs-switches</a>
+ <a class="json-schema-ref" href="#/getDefinitions/dvs-switches">/dvs-switches</a>
</div>
</div>
</div>
@@ -12267,7 +14179,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/dvs-switch">/dvs-switch</a>
+ <a class="json-schema-ref" href="#/getDefinitions/dvs-switch">/dvs-switch</a>
</div>
</div>
</div>
@@ -12314,7 +14226,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>dvs-switch object that needs to be created or updated</p>
+ <p><p>dvs-switch object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -12417,6 +14329,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--dvs-switches-dvs-switch--switch-name--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--dvs-switches-dvs-switch--switch-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing dvs-switch</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/dvs-switches/dvs-switch/{switch-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing dvs-switch</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>dvs-switch object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/dvs-switch">/dvs-switch</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ switch-name
+ </td>
+ <td>
+ <p>DVS switch name</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--dvs-switches-dvs-switch--switch-name--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--dvs-switches-dvs-switch--switch-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing dvs-switch</div>
@@ -12560,7 +14593,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -12884,7 +14917,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/flavors">/flavors</a>
+ <a class="json-schema-ref" href="#/getDefinitions/flavors">/flavors</a>
</div>
</div>
</div>
@@ -13056,7 +15089,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/flavor">/flavor</a>
+ <a class="json-schema-ref" href="#/getDefinitions/flavor">/flavor</a>
</div>
</div>
</div>
@@ -13103,7 +15136,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>flavor object that needs to be created or updated</p>
+ <p><p>flavor object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -13206,6 +15239,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--flavors-flavor--flavor-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--flavors-flavor--flavor-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing flavor</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/flavors/flavor/{flavor-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing flavor</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>flavor object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/flavor">/flavor</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ flavor-id
+ </td>
+ <td>
+ <p>Flavor id, expected to be unique across cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--flavors-flavor--flavor-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--flavors-flavor--flavor-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing flavor</div>
@@ -13349,7 +15503,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -13673,7 +15827,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/group-assignments">/group-assignments</a>
+ <a class="json-schema-ref" href="#/getDefinitions/group-assignments">/group-assignments</a>
</div>
</div>
</div>
@@ -13860,7 +16014,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/group-assignment">/group-assignment</a>
+ <a class="json-schema-ref" href="#/getDefinitions/group-assignment">/group-assignment</a>
</div>
</div>
</div>
@@ -13907,7 +16061,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>group-assignment object that needs to be created or updated</p>
+ <p><p>group-assignment object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -14010,6 +16164,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--group-assignments-group-assignment--group-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--group-assignments-group-assignment--group-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing group-assignment</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/group-assignments/group-assignment/{group-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing group-assignment</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>group-assignment object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/group-assignment">/group-assignment</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ group-id
+ </td>
+ <td>
+ <p>Group id, expected to be unique across cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--group-assignments-group-assignment--group-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--group-assignments-group-assignment--group-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing group-assignment</div>
@@ -14153,7 +16428,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -14477,7 +16752,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/images">/images</a>
+ <a class="json-schema-ref" href="#/getDefinitions/images">/images</a>
</div>
</div>
</div>
@@ -14694,7 +16969,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/image">/image</a>
+ <a class="json-schema-ref" href="#/getDefinitions/image">/image</a>
</div>
</div>
</div>
@@ -14741,7 +17016,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>image object that needs to be created or updated</p>
+ <p><p>image object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionImagesImage.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -14844,6 +17119,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing image</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing image</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>image object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/image">/image</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ image-id
+ </td>
+ <td>
+ <p>Image id, expected to be unique across cloud region</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing image</div>
@@ -15157,7 +17553,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadata">/metadata</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadata">/metadata</a>
</div>
</div>
</div>
@@ -15389,7 +17785,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadatum">/metadatum</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadatum">/metadatum</a>
</div>
</div>
</div>
@@ -15436,7 +17832,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>metadatum object that needs to be created or updated</p>
+ <p><p>metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionImagesImageMetadataMetadatum.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -15554,6 +17950,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--metadata-metadatum--metaname--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--metadata-metadatum--metaname--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing metadatum</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}/metadata/metadatum/{metaname}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing metadatum</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>metadatum object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/metadatum">/metadatum</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ image-id
+ </td>
+ <td>
+ <p>Image id, expected to be unique across cloud region</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ metaname
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--metadata-metadatum--metaname--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--metadata-metadatum--metaname--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing metadatum</div>
@@ -15712,7 +18244,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionImagesImage.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -16036,7 +18568,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/oam-networks">/oam-networks</a>
+ <a class="json-schema-ref" href="#/getDefinitions/oam-networks">/oam-networks</a>
</div>
</div>
</div>
@@ -16223,7 +18755,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/oam-network">/oam-network</a>
+ <a class="json-schema-ref" href="#/getDefinitions/oam-network">/oam-network</a>
</div>
</div>
</div>
@@ -16270,7 +18802,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>oam-network object that needs to be created or updated</p>
+ <p><p>oam-network object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -16373,6 +18905,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--oam-networks-oam-network--network-uuid--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--oam-networks-oam-network--network-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing oam-network</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/oam-networks/oam-network/{network-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing oam-network</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>oam-network object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/oam-network">/oam-network</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ network-uuid
+ </td>
+ <td>
+ <p>UUID of the network. Unique across a cloud-region</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--oam-networks-oam-network--network-uuid--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--oam-networks-oam-network--network-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing oam-network</div>
@@ -16516,7 +19169,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -16746,7 +19399,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegion.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -17038,7 +19691,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/snapshots">/snapshots</a>
+ <a class="json-schema-ref" href="#/getDefinitions/snapshots">/snapshots</a>
</div>
</div>
</div>
@@ -17270,7 +19923,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/snapshot">/snapshot</a>
+ <a class="json-schema-ref" href="#/getDefinitions/snapshot">/snapshot</a>
</div>
</div>
</div>
@@ -17317,7 +19970,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>snapshot object that needs to be created or updated</p>
+ <p><p>snapshot object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -17420,6 +20073,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--snapshots-snapshot--snapshot-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--snapshots-snapshot--snapshot-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing snapshot</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/snapshots/snapshot/{snapshot-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing snapshot</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>snapshot object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/snapshot">/snapshot</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ snapshot-id
+ </td>
+ <td>
+ <p>Snapshot id, this is the key UUID assoc associated in glance with the snapshots.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--snapshots-snapshot--snapshot-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--snapshots-snapshot--snapshot-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing snapshot</div>
@@ -17563,7 +20337,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -17887,7 +20661,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/tenants">/tenants</a>
+ <a class="json-schema-ref" href="#/getDefinitions/tenants">/tenants</a>
</div>
</div>
</div>
@@ -18059,7 +20833,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/tenant">/tenant</a>
+ <a class="json-schema-ref" href="#/getDefinitions/tenant">/tenant</a>
</div>
</div>
</div>
@@ -18106,7 +20880,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>tenant object that needs to be created or updated</p>
+ <p><p>tenant object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenant.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -18209,6 +20983,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing tenant</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing tenant</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>tenant object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/tenant">/tenant</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing tenant</div>
@@ -18352,7 +21247,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenant.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -18707,7 +21602,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vservers">/vservers</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vservers">/vservers</a>
</div>
</div>
</div>
@@ -18968,7 +21863,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vserver">/vserver</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vserver">/vserver</a>
</div>
</div>
</div>
@@ -19015,7 +21910,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vserver object that needs to be created or updated</p>
+ <p><p>vserver object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -19134,6 +22029,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vserver</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vserver</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vserver object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vserver">/vserver</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vserver</div>
@@ -19507,7 +22539,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -19829,7 +22861,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -19876,7 +22908,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -20011,6 +23043,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -20522,7 +23707,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -20569,7 +23754,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -20720,6 +23905,175 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -20911,7 +24265,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -21573,7 +24927,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -21620,7 +24974,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -21771,6 +25125,175 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -21962,7 +25485,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -22288,7 +25811,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -22857,7 +26380,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -23255,7 +26778,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -23302,7 +26825,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -23453,6 +26976,175 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -23644,7 +27336,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -24245,7 +27937,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -24613,7 +28305,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -24660,7 +28352,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -24811,6 +28503,175 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -25384,7 +29245,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -25431,7 +29292,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -25598,6 +29459,191 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -25805,7 +29851,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -26545,7 +30591,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -26592,7 +30638,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -26759,6 +30805,191 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -26966,7 +31197,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -27324,7 +31555,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -27650,7 +31881,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -28126,7 +32357,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/volumes">/volumes</a>
+ <a class="json-schema-ref" href="#/getDefinitions/volumes">/volumes</a>
</div>
</div>
</div>
@@ -28403,7 +32634,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/volume">/volume</a>
+ <a class="json-schema-ref" href="#/getDefinitions/volume">/volume</a>
</div>
</div>
</div>
@@ -28450,7 +32681,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>volume object that needs to be created or updated</p>
+ <p><p>volume object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -28585,6 +32816,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--volumes-volume--volume-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--volumes-volume--volume-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing volume</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/volumes/volume/{volume-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing volume</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>volume object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/volume">/volume</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ volume-id
+ </td>
+ <td>
+ <p>Unique ID of block storage volume relative to the vserver.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--volumes-volume--volume-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--volumes-volume--volume-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing volume</div>
@@ -28760,7 +33144,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -29148,7 +33532,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/volume-groups">/volume-groups</a>
+ <a class="json-schema-ref" href="#/getDefinitions/volume-groups">/volume-groups</a>
</div>
</div>
</div>
@@ -29350,7 +33734,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/volume-group">/volume-group</a>
+ <a class="json-schema-ref" href="#/getDefinitions/volume-group">/volume-group</a>
</div>
</div>
</div>
@@ -29397,7 +33781,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>volume-group object that needs to be created or updated</p>
+ <p><p>volume-group object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -29500,6 +33884,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--volume-groups-volume-group--volume-group-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--volume-groups-volume-group--volume-group-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing volume-group</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/volume-groups/volume-group/{volume-group-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing volume-group</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>volume-group object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/volume-group">/volume-group</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ volume-group-id
+ </td>
+ <td>
+ <p>Unique ID of volume-group.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--volume-groups-volume-group--volume-group-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--volume-groups-volume-group--volume-group-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing volume-group</div>
@@ -29643,7 +34148,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -29890,7 +34395,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/complexes">/complexes</a>
+ <a class="json-schema-ref" href="#/getDefinitions/complexes">/complexes</a>
</div>
</div>
</div>
@@ -30030,7 +34535,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/complex">/complex</a>
+ <a class="json-schema-ref" href="#/getDefinitions/complex">/complex</a>
</div>
</div>
</div>
@@ -30077,7 +34582,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>complex object that needs to be created or updated</p>
+ <p><p>complex object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureComplexesComplex.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -30148,6 +34653,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-complexes-complex--physical-location-id--"></span>
+ <div id="operation--cloud-infrastructure-complexes-complex--physical-location-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing complex</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/complexes/complex/{physical-location-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing complex</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>complex object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/complex">/complex</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ physical-location-id
+ </td>
+ <td>
+ <p>Unique identifier for physical location, e.g., CLLI</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-complexes-complex--physical-location-id--"></span>
<div id="operation--cloud-infrastructure-complexes-complex--physical-location-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing complex</div>
@@ -30352,7 +34946,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/ctag-pools">/ctag-pools</a>
+ <a class="json-schema-ref" href="#/getDefinitions/ctag-pools">/ctag-pools</a>
</div>
</div>
</div>
@@ -30524,7 +35118,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/ctag-pool">/ctag-pool</a>
+ <a class="json-schema-ref" href="#/getDefinitions/ctag-pool">/ctag-pool</a>
</div>
</div>
</div>
@@ -30571,7 +35165,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>ctag-pool object that needs to be created or updated</p>
+ <p><p>ctag-pool object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureComplexesComplexCtagPoolsCtagPool.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -30674,6 +35268,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-complexes-complex--physical-location-id--ctag-pools-ctag-pool--target-pe---availability-zone-name--"></span>
+ <div id="operation--cloud-infrastructure-complexes-complex--physical-location-id--ctag-pools-ctag-pool--target-pe---availability-zone-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing ctag-pool</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/complexes/complex/{physical-location-id}/ctag-pools/ctag-pool/{target-pe}/{availability-zone-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing ctag-pool</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>ctag-pool object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/ctag-pool">/ctag-pool</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ physical-location-id
+ </td>
+ <td>
+ <p>Unique identifier for physical location, e.g., CLLI</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ target-pe
+ </td>
+ <td>
+ <p>The Target provider edge router</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ availability-zone-name
+ </td>
+ <td>
+ <p>Name of the availability zone</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-complexes-complex--physical-location-id--ctag-pools-ctag-pool--target-pe---availability-zone-name--"></span>
<div id="operation--cloud-infrastructure-complexes-complex--physical-location-id--ctag-pools-ctag-pool--target-pe---availability-zone-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing ctag-pool</div>
@@ -30817,7 +35532,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureComplexesComplexCtagPoolsCtagPool.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -31047,7 +35762,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureComplexesComplex.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -31230,7 +35945,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/network-profiles">/network-profiles</a>
+ <a class="json-schema-ref" href="#/getDefinitions/network-profiles">/network-profiles</a>
</div>
</div>
</div>
@@ -31325,7 +36040,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/network-profile">/network-profile</a>
+ <a class="json-schema-ref" href="#/getDefinitions/network-profile">/network-profile</a>
</div>
</div>
</div>
@@ -31372,7 +36087,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>network-profile object that needs to be created or updated</p>
+ <p><p>network-profile object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureNetworkProfilesNetworkProfile.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -31443,6 +36158,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-network-profiles-network-profile--nm-profile-name--"></span>
+ <div id="operation--cloud-infrastructure-network-profiles-network-profile--nm-profile-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing network-profile</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/network-profiles/network-profile/{nm-profile-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing network-profile</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>network-profile object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/network-profile">/network-profile</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ nm-profile-name
+ </td>
+ <td>
+ <p>Unique name of network profile.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-network-profiles-network-profile--nm-profile-name--"></span>
<div id="operation--cloud-infrastructure-network-profiles-network-profile--nm-profile-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing network-profile</div>
@@ -31554,7 +36358,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureNetworkProfilesNetworkProfile.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -31737,7 +36541,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/pservers">/pservers</a>
+ <a class="json-schema-ref" href="#/getDefinitions/pservers">/pservers</a>
</div>
</div>
</div>
@@ -31891,7 +36695,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/pserver">/pserver</a>
+ <a class="json-schema-ref" href="#/getDefinitions/pserver">/pserver</a>
</div>
</div>
</div>
@@ -31938,7 +36742,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>pserver object that needs to be created or updated</p>
+ <p><p>pserver object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserver.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -32009,6 +36813,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing pserver</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing pserver</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>pserver object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/pserver">/pserver</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing pserver</div>
@@ -32227,7 +37120,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interfaces">/lag-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interfaces">/lag-interfaces</a>
</div>
</div>
</div>
@@ -32427,7 +37320,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interface">/lag-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interface">/lag-interface</a>
</div>
</div>
</div>
@@ -32474,7 +37367,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>lag-interface object that needs to be created or updated</p>
+ <p><p>lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -32561,6 +37454,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing lag-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing lag-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>lag-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/lag-interface">/lag-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing lag-interface</div>
@@ -32841,7 +37839,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -33102,7 +38100,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -33149,7 +38147,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -33252,6 +38250,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -33670,7 +38789,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -33717,7 +38836,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -33836,6 +38955,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -33995,7 +39251,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -34532,7 +39788,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -34579,7 +39835,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -34698,6 +39954,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -34857,7 +40250,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -35119,7 +40512,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -35563,7 +40956,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -35900,7 +41293,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -35947,7 +41340,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -36066,6 +41459,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -36225,7 +41755,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -36701,7 +42231,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -37008,7 +42538,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -37055,7 +42585,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -37174,6 +42704,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -37654,7 +43321,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -37701,7 +43368,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -37836,6 +43503,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -38011,7 +43831,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -38626,7 +44446,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -38673,7 +44493,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -38808,6 +44628,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -38983,7 +44956,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -39277,7 +45250,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -39539,7 +45512,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -39844,7 +45817,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/p-interfaces">/p-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/p-interfaces">/p-interfaces</a>
</div>
</div>
</div>
@@ -40029,7 +46002,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/p-interface">/p-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/p-interface">/p-interface</a>
</div>
</div>
</div>
@@ -40076,7 +46049,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>p-interface object that needs to be created or updated</p>
+ <p><p>p-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -40163,6 +46136,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing p-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing p-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>p-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/p-interface">/p-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing p-interface</div>
@@ -40428,7 +46506,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -40674,7 +46752,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -40721,7 +46799,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -40824,6 +46902,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -41227,7 +47426,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -41274,7 +47473,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -41393,6 +47592,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -41552,7 +47888,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -42074,7 +48410,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -42121,7 +48457,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -42240,6 +48576,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -42399,7 +48872,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -42661,7 +49134,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -43090,7 +49563,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -43412,7 +49885,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -43459,7 +49932,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -43578,6 +50051,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -43737,7 +50347,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -44198,7 +50808,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -44490,7 +51100,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -44537,7 +51147,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -44656,6 +51266,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -45121,7 +51868,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -45168,7 +51915,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -45303,6 +52050,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -45478,7 +52378,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -46078,7 +52978,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -46125,7 +53025,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -46260,6 +53160,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -46435,7 +53488,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -46729,7 +53782,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -46991,7 +54044,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -47189,7 +54242,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserver.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -47372,7 +54425,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/virtual-data-centers">/virtual-data-centers</a>
+ <a class="json-schema-ref" href="#/getDefinitions/virtual-data-centers">/virtual-data-centers</a>
</div>
</div>
</div>
@@ -47482,7 +54535,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/virtual-data-center">/virtual-data-center</a>
+ <a class="json-schema-ref" href="#/getDefinitions/virtual-data-center">/virtual-data-center</a>
</div>
</div>
</div>
@@ -47529,7 +54582,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>virtual-data-center object that needs to be created or updated</p>
+ <p><p>virtual-data-center object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureVirtualDataCentersVirtualDataCenter.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -47600,6 +54653,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--"></span>
+ <div id="operation--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing virtual-data-center</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing virtual-data-center</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>virtual-data-center object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/virtual-data-center">/virtual-data-center</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vdc-id
+ </td>
+ <td>
+ <p>Unique ID of the vdc</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--"></span>
<div id="operation--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing virtual-data-center</div>
@@ -47711,7 +54853,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureVirtualDataCentersVirtualDataCenter.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -47894,7 +55036,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/generic-vnfs">/generic-vnfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/generic-vnfs">/generic-vnfs</a>
</div>
</div>
</div>
@@ -48242,7 +55384,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/generic-vnf">/generic-vnf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/generic-vnf">/generic-vnf</a>
</div>
</div>
</div>
@@ -48289,7 +55431,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>generic-vnf object that needs to be created or updated</p>
+ <p><p>generic-vnf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -48360,6 +55502,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing generic-vnf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing generic-vnf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>generic-vnf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/generic-vnf">/generic-vnf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing generic-vnf</div>
@@ -48772,7 +56003,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/entitlements">/entitlements</a>
+ <a class="json-schema-ref" href="#/getDefinitions/entitlements">/entitlements</a>
</div>
</div>
</div>
@@ -49152,7 +56383,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/entitlement">/entitlement</a>
+ <a class="json-schema-ref" href="#/getDefinitions/entitlement">/entitlement</a>
</div>
</div>
</div>
@@ -49199,7 +56430,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>entitlement object that needs to be created or updated</p>
+ <p><p>entitlement object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfEntitlementsEntitlement.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -49302,6 +56533,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing entitlement</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/entitlements/entitlement/{group-uuid}/{resource-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing entitlement</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>entitlement object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/entitlement">/entitlement</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ group-uuid
+ </td>
+ <td>
+ <p>Unique ID for the entitlement group the resource comes from, should be uuid.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ resource-uuid
+ </td>
+ <td>
+ <p>Unique ID of an entitlement resource.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing entitlement</div>
@@ -49445,7 +56797,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfEntitlementsEntitlement.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -49976,7 +57328,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -50385,7 +57737,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -50432,7 +57784,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -50519,6 +57871,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -51069,7 +58526,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -51116,7 +58573,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -51219,6 +58676,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -51362,7 +58940,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -52015,7 +59593,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -52062,7 +59640,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -52165,6 +59743,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -52308,7 +60007,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -52538,7 +60237,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -53098,7 +60797,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -53583,7 +61282,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -53630,7 +61329,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -53733,6 +61432,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -53876,7 +61696,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -54468,7 +62288,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -54923,7 +62743,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -54970,7 +62790,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -55073,6 +62893,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -55685,7 +63626,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -55732,7 +63673,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -55851,6 +63792,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -56010,7 +64088,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -56741,7 +64819,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -56788,7 +64866,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -56907,6 +64985,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -57066,7 +65281,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -57328,7 +65543,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -57859,7 +66074,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interfaces">/lag-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interfaces">/lag-interfaces</a>
</div>
</div>
</div>
@@ -58253,7 +66468,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interface">/lag-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interface">/lag-interface</a>
</div>
</div>
</div>
@@ -58300,7 +66515,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>lag-interface object that needs to be created or updated</p>
+ <p><p>lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -58387,6 +66602,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing lag-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing lag-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>lag-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/lag-interface">/lag-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing lag-interface</div>
@@ -58861,7 +67181,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -59316,7 +67636,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -59363,7 +67683,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -59466,6 +67786,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -60078,7 +68519,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -60125,7 +68566,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -60244,6 +68685,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -60403,7 +68981,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -61134,7 +69712,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -61181,7 +69759,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -61300,6 +69878,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -61459,7 +70174,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -61721,7 +70436,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -62359,7 +71074,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -62890,7 +71605,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -62937,7 +71652,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -63056,6 +71771,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -63215,7 +72067,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -63885,7 +72737,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -64386,7 +73238,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -64433,7 +73285,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -64552,6 +73404,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -65226,7 +74215,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -65273,7 +74262,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -65408,6 +74397,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -65583,7 +74725,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -66392,7 +75534,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -66439,7 +75581,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -66574,6 +75716,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -66749,7 +76044,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -67043,7 +76338,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -67305,7 +76600,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -67804,7 +77099,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/licenses">/licenses</a>
+ <a class="json-schema-ref" href="#/getDefinitions/licenses">/licenses</a>
</div>
</div>
</div>
@@ -68184,7 +77479,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/license">/license</a>
+ <a class="json-schema-ref" href="#/getDefinitions/license">/license</a>
</div>
</div>
</div>
@@ -68231,7 +77526,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>license object that needs to be created or updated</p>
+ <p><p>license object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLicensesLicense.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -68334,6 +77629,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--licenses-license--group-uuid---resource-uuid--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--licenses-license--group-uuid---resource-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing license</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/licenses/license/{group-uuid}/{resource-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing license</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>license object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/license">/license</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ group-uuid
+ </td>
+ <td>
+ <p>Unique ID for the license group the resource belongs to, should be uuid.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ resource-uuid
+ </td>
+ <td>
+ <p>Unique ID of a license resource.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--licenses-license--group-uuid---resource-uuid--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--licenses-license--group-uuid---resource-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing license</div>
@@ -68477,7 +77893,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLicensesLicense.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -68707,7 +78123,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -69174,7 +78590,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vf-modules">/vf-modules</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vf-modules">/vf-modules</a>
</div>
</div>
</div>
@@ -69643,7 +79059,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vf-module">/vf-module</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vf-module">/vf-module</a>
</div>
</div>
</div>
@@ -69690,7 +79106,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vf-module object that needs to be created or updated</p>
+ <p><p>vf-module object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfVfModulesVfModule.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -69777,6 +79193,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--vf-modules-vf-module--vf-module-id--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--vf-modules-vf-module--vf-module-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vf-module</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/vf-modules/vf-module/{vf-module-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vf-module</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vf-module object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vf-module">/vf-module</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vf-module-id
+ </td>
+ <td>
+ <p>Unique ID of vf-module.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--vf-modules-vf-module--vf-module-id--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--vf-modules-vf-module--vf-module-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vf-module</div>
@@ -69904,7 +79425,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfVfModulesVfModule.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -70119,7 +79640,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/instance-groups">/instance-groups</a>
+ <a class="json-schema-ref" href="#/getDefinitions/instance-groups">/instance-groups</a>
</div>
</div>
</div>
@@ -70259,7 +79780,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/instance-group">/instance-group</a>
+ <a class="json-schema-ref" href="#/getDefinitions/instance-group">/instance-group</a>
</div>
</div>
</div>
@@ -70306,7 +79827,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>instance-group object that needs to be created or updated</p>
+ <p><p>instance-group object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkInstanceGroupsInstanceGroup.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -70377,6 +79898,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-instance-groups-instance-group--id--"></span>
+ <div id="operation--network-instance-groups-instance-group--id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing instance-group</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/instance-groups/instance-group/{id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing instance-group</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>instance-group object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/instance-group">/instance-group</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ id
+ </td>
+ <td>
+ <p>Instance Group ID, UUID assigned to this instance.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-instance-groups-instance-group--id--"></span>
<div id="operation--network-instance-groups-instance-group--id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing instance-group</div>
@@ -70488,7 +80098,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkInstanceGroupsInstanceGroup.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -70671,7 +80281,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/ipsec-configurations">/ipsec-configurations</a>
+ <a class="json-schema-ref" href="#/getDefinitions/ipsec-configurations">/ipsec-configurations</a>
</div>
</div>
</div>
@@ -70766,7 +80376,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/ipsec-configuration">/ipsec-configuration</a>
+ <a class="json-schema-ref" href="#/getDefinitions/ipsec-configuration">/ipsec-configuration</a>
</div>
</div>
</div>
@@ -70813,7 +80423,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>ipsec-configuration object that needs to be created or updated</p>
+ <p><p>ipsec-configuration object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkIpsecConfigurationsIpsecConfiguration.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -70884,6 +80494,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--"></span>
+ <div id="operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing ipsec-configuration</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing ipsec-configuration</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>ipsec-configuration object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/ipsec-configuration">/ipsec-configuration</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ ipsec-configuration-id
+ </td>
+ <td>
+ <p>UUID of this configuration</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--"></span>
<div id="operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing ipsec-configuration</div>
@@ -70995,7 +80694,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkIpsecConfigurationsIpsecConfiguration.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -71209,7 +80908,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vig-servers">/vig-servers</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vig-servers">/vig-servers</a>
</div>
</div>
</div>
@@ -71320,7 +81019,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vig-server">/vig-server</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vig-server">/vig-server</a>
</div>
</div>
</div>
@@ -71367,7 +81066,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vig-server object that needs to be created or updated</p>
+ <p><p>vig-server object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -71454,6 +81153,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--vig-servers-vig-server--vig-address-type--"></span>
+ <div id="operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--vig-servers-vig-server--vig-address-type--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vig-server</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}/vig-servers/vig-server/{vig-address-type}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vig-server</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vig-server object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vig-server">/vig-server</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ ipsec-configuration-id
+ </td>
+ <td>
+ <p>UUID of this configuration</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vig-address-type
+ </td>
+ <td>
+ <p>indicates whether the VIG is for AVPN or INTERNET</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--vig-servers-vig-server--vig-address-type--"></span>
<div id="operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--vig-servers-vig-server--vig-address-type--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vig-server</div>
@@ -71581,7 +81385,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -71796,7 +81600,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-networks">/l3-networks</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-networks">/l3-networks</a>
</div>
</div>
</div>
@@ -72026,7 +81830,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-network">/l3-network</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-network">/l3-network</a>
</div>
</div>
</div>
@@ -72073,7 +81877,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-network object that needs to be created or updated</p>
+ <p><p>l3-network object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3Network.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -72144,6 +81948,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-l3-networks-l3-network--network-id--"></span>
+ <div id="operation--network-l3-networks-l3-network--network-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-network</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/l3-networks/l3-network/{network-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-network</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-network object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-network">/l3-network</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ network-id
+ </td>
+ <td>
+ <p>Network ID, should be uuid. Unique across A&AI.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-l3-networks-l3-network--network-id--"></span>
<div id="operation--network-l3-networks-l3-network--network-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-network</div>
@@ -72438,7 +82331,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/ctag-assignments">/ctag-assignments</a>
+ <a class="json-schema-ref" href="#/getDefinitions/ctag-assignments">/ctag-assignments</a>
</div>
</div>
</div>
@@ -72684,7 +82577,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/ctag-assignment">/ctag-assignment</a>
+ <a class="json-schema-ref" href="#/getDefinitions/ctag-assignment">/ctag-assignment</a>
</div>
</div>
</div>
@@ -72731,7 +82624,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>ctag-assignment object that needs to be created or updated</p>
+ <p><p>ctag-assignment object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -72818,6 +82711,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-l3-networks-l3-network--network-id--ctag-assignments-ctag-assignment--vlan-id-inner--"></span>
+ <div id="operation--network-l3-networks-l3-network--network-id--ctag-assignments-ctag-assignment--vlan-id-inner--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing ctag-assignment</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/l3-networks/l3-network/{network-id}/ctag-assignments/ctag-assignment/{vlan-id-inner}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing ctag-assignment</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>ctag-assignment object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/ctag-assignment">/ctag-assignment</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ network-id
+ </td>
+ <td>
+ <p>Network ID, should be uuid. Unique across A&AI.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-id-inner
+ </td>
+ <td>
+ <p>id.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-l3-networks-l3-network--network-id--ctag-assignments-ctag-assignment--vlan-id-inner--"></span>
<div id="operation--network-l3-networks-l3-network--network-id--ctag-assignments-ctag-assignment--vlan-id-inner--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing ctag-assignment</div>
@@ -72945,7 +82943,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -73143,7 +83141,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3Network.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -73492,7 +83490,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/segmentation-assignments">/segmentation-assignments</a>
+ <a class="json-schema-ref" href="#/getDefinitions/segmentation-assignments">/segmentation-assignments</a>
</div>
</div>
</div>
@@ -73738,7 +83736,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/segmentation-assignment">/segmentation-assignment</a>
+ <a class="json-schema-ref" href="#/getDefinitions/segmentation-assignment">/segmentation-assignment</a>
</div>
</div>
</div>
@@ -73785,7 +83783,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>segmentation-assignment object that needs to be created or updated</p>
+ <p><p>segmentation-assignment object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -73872,6 +83870,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-l3-networks-l3-network--network-id--segmentation-assignments-segmentation-assignment--segmentation-id--"></span>
+ <div id="operation--network-l3-networks-l3-network--network-id--segmentation-assignments-segmentation-assignment--segmentation-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing segmentation-assignment</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/l3-networks/l3-network/{network-id}/segmentation-assignments/segmentation-assignment/{segmentation-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing segmentation-assignment</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>segmentation-assignment object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/segmentation-assignment">/segmentation-assignment</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ network-id
+ </td>
+ <td>
+ <p>Network ID, should be uuid. Unique across A&AI.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ segmentation-id
+ </td>
+ <td>
+ <p>Route Table Reference id, UUID assigned to this instance.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-l3-networks-l3-network--network-id--segmentation-assignments-segmentation-assignment--segmentation-id--"></span>
<div id="operation--network-l3-networks-l3-network--network-id--segmentation-assignments-segmentation-assignment--segmentation-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing segmentation-assignment</div>
@@ -73999,7 +84102,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -74380,7 +84483,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/subnets">/subnets</a>
+ <a class="json-schema-ref" href="#/getDefinitions/subnets">/subnets</a>
</div>
</div>
</div>
@@ -74641,7 +84744,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/subnet">/subnet</a>
+ <a class="json-schema-ref" href="#/getDefinitions/subnet">/subnet</a>
</div>
</div>
</div>
@@ -74688,7 +84791,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>subnet object that needs to be created or updated</p>
+ <p><p>subnet object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3NetworkSubnetsSubnet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -74775,6 +84878,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-l3-networks-l3-network--network-id--subnets-subnet--subnet-id--"></span>
+ <div id="operation--network-l3-networks-l3-network--network-id--subnets-subnet--subnet-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing subnet</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/l3-networks/l3-network/{network-id}/subnets/subnet/{subnet-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing subnet</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>subnet object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/subnet">/subnet</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ network-id
+ </td>
+ <td>
+ <p>Network ID, should be uuid. Unique across A&AI.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ subnet-id
+ </td>
+ <td>
+ <p>Subnet ID, should be UUID.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-l3-networks-l3-network--network-id--subnets-subnet--subnet-id--"></span>
<div id="operation--network-l3-networks-l3-network--network-id--subnets-subnet--subnet-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing subnet</div>
@@ -74902,7 +85110,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3NetworkSubnetsSubnet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -75117,7 +85325,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-links">/lag-links</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-links">/lag-links</a>
</div>
</div>
</div>
@@ -75212,7 +85420,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-link">/lag-link</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-link">/lag-link</a>
</div>
</div>
</div>
@@ -75259,7 +85467,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>lag-link object that needs to be created or updated</p>
+ <p><p>lag-link object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkLagLinksLagLink.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -75330,6 +85538,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-lag-links-lag-link--link-name--"></span>
+ <div id="operation--network-lag-links-lag-link--link-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing lag-link</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/lag-links/lag-link/{link-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing lag-link</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>lag-link object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/lag-link">/lag-link</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ link-name
+ </td>
+ <td>
+ <p>Alphabetical concatenation of lag-interface names</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-lag-links-lag-link--link-name--"></span>
<div id="operation--network-lag-links-lag-link--link-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing lag-link</div>
@@ -75441,7 +85738,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkLagLinksLagLink.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -75624,7 +85921,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/logical-links">/logical-links</a>
+ <a class="json-schema-ref" href="#/getDefinitions/logical-links">/logical-links</a>
</div>
</div>
</div>
@@ -75839,7 +86136,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/logical-link">/logical-link</a>
+ <a class="json-schema-ref" href="#/getDefinitions/logical-link">/logical-link</a>
</div>
</div>
</div>
@@ -75886,7 +86183,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>logical-link object that needs to be created or updated</p>
+ <p><p>logical-link object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkLogicalLinksLogicalLink.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -75957,6 +86254,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-logical-links-logical-link--link-name--"></span>
+ <div id="operation--network-logical-links-logical-link--link-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing logical-link</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/logical-links/logical-link/{link-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing logical-link</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>logical-link object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/logical-link">/logical-link</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ link-name
+ </td>
+ <td>
+ <p>e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-logical-links-logical-link--link-name--"></span>
<div id="operation--network-logical-links-logical-link--link-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing logical-link</div>
@@ -76068,7 +86454,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkLogicalLinksLogicalLink.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -76251,7 +86637,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/multicast-configurations">/multicast-configurations</a>
+ <a class="json-schema-ref" href="#/getDefinitions/multicast-configurations">/multicast-configurations</a>
</div>
</div>
</div>
@@ -76346,7 +86732,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/multicast-configuration">/multicast-configuration</a>
+ <a class="json-schema-ref" href="#/getDefinitions/multicast-configuration">/multicast-configuration</a>
</div>
</div>
</div>
@@ -76393,7 +86779,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>multicast-configuration object that needs to be created or updated</p>
+ <p><p>multicast-configuration object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkMulticastConfigurationsMulticastConfiguration.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -76464,6 +86850,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-multicast-configurations-multicast-configuration--multicast-configuration-id--"></span>
+ <div id="operation--network-multicast-configurations-multicast-configuration--multicast-configuration-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing multicast-configuration</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/multicast-configurations/multicast-configuration/{multicast-configuration-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing multicast-configuration</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>multicast-configuration object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/multicast-configuration">/multicast-configuration</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ multicast-configuration-id
+ </td>
+ <td>
+ <p>Unique id of multicast configuration.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-multicast-configurations-multicast-configuration--multicast-configuration-id--"></span>
<div id="operation--network-multicast-configurations-multicast-configuration--multicast-configuration-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing multicast-configuration</div>
@@ -76575,7 +87050,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkMulticastConfigurationsMulticastConfiguration.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -76758,7 +87233,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/network-policies">/network-policies</a>
+ <a class="json-schema-ref" href="#/getDefinitions/network-policies">/network-policies</a>
</div>
</div>
</div>
@@ -76868,7 +87343,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/network-policy">/network-policy</a>
+ <a class="json-schema-ref" href="#/getDefinitions/network-policy">/network-policy</a>
</div>
</div>
</div>
@@ -76915,7 +87390,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>network-policy object that needs to be created or updated</p>
+ <p><p>network-policy object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNetworkPoliciesNetworkPolicy.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -76986,6 +87461,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-network-policies-network-policy--network-policy-id--"></span>
+ <div id="operation--network-network-policies-network-policy--network-policy-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing network-policy</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/network-policies/network-policy/{network-policy-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing network-policy</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>network-policy object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/network-policy">/network-policy</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ network-policy-id
+ </td>
+ <td>
+ <p>UUID representing unique key to this instance</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-network-policies-network-policy--network-policy-id--"></span>
<div id="operation--network-network-policies-network-policy--network-policy-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing network-policy</div>
@@ -77097,7 +87661,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNetworkPoliciesNetworkPolicy.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -77280,7 +87844,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/newvces">/newvces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/newvces">/newvces</a>
</div>
</div>
</div>
@@ -77450,7 +88014,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/newvce">/newvce</a>
+ <a class="json-schema-ref" href="#/getDefinitions/newvce">/newvce</a>
</div>
</div>
</div>
@@ -77497,7 +88061,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>newvce object that needs to be created or updated</p>
+ <p><p>newvce object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvce.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -77568,6 +88132,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing newvce</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing newvce</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>newvce object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/newvce">/newvce</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing newvce</div>
@@ -77802,7 +88455,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -78033,7 +88686,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -78080,7 +88733,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -78167,6 +88820,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -78539,7 +89297,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -78586,7 +89344,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -78689,6 +89447,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -78832,7 +89711,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -79307,7 +90186,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -79354,7 +90233,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -79457,6 +90336,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -79600,7 +90600,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -79830,7 +90830,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -80212,7 +91212,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -80519,7 +91519,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -80566,7 +91566,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -80669,6 +91669,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -80812,7 +91933,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -81226,7 +92347,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -81503,7 +92624,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -81550,7 +92671,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -81653,6 +92774,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -82087,7 +93329,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -82134,7 +93376,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -82253,6 +93495,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -82412,7 +93791,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -82965,7 +94344,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -83012,7 +94391,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -83131,6 +94510,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -83290,7 +94806,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -83552,7 +95068,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -83782,7 +95298,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvce.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -83965,7 +95481,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/physical-links">/physical-links</a>
+ <a class="json-schema-ref" href="#/getDefinitions/physical-links">/physical-links</a>
</div>
</div>
</div>
@@ -84075,7 +95591,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/physical-link">/physical-link</a>
+ <a class="json-schema-ref" href="#/getDefinitions/physical-link">/physical-link</a>
</div>
</div>
</div>
@@ -84122,7 +95638,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>physical-link object that needs to be created or updated</p>
+ <p><p>physical-link object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPhysicalLinksPhysicalLink.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -84193,6 +95709,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-physical-links-physical-link--link-name--"></span>
+ <div id="operation--network-physical-links-physical-link--link-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing physical-link</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/physical-links/physical-link/{link-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing physical-link</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>physical-link object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/physical-link">/physical-link</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ link-name
+ </td>
+ <td>
+ <p>e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-physical-links-physical-link--link-name--"></span>
<div id="operation--network-physical-links-physical-link--link-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing physical-link</div>
@@ -84304,7 +95909,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPhysicalLinksPhysicalLink.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -84487,7 +96092,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/pnfs">/pnfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/pnfs">/pnfs</a>
</div>
</div>
</div>
@@ -84597,7 +96202,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/pnf">/pnf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/pnf">/pnf</a>
</div>
</div>
</div>
@@ -84644,7 +96249,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>pnf object that needs to be created or updated</p>
+ <p><p>pnf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -84715,6 +96320,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing pnf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing pnf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>pnf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/pnf">/pnf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing pnf</div>
@@ -84889,7 +96583,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interfaces">/lag-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interfaces">/lag-interfaces</a>
</div>
</div>
</div>
@@ -85045,7 +96739,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interface">/lag-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interface">/lag-interface</a>
</div>
</div>
</div>
@@ -85092,7 +96786,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>lag-interface object that needs to be created or updated</p>
+ <p><p>lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -85179,6 +96873,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing lag-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing lag-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>lag-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/lag-interface">/lag-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing lag-interface</div>
@@ -85415,7 +97214,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -85632,7 +97431,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -85679,7 +97478,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -85782,6 +97581,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -86156,7 +98076,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -86203,7 +98123,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -86322,6 +98242,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -86481,7 +98538,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -86974,7 +99031,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -87021,7 +99078,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -87140,6 +99197,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -87299,7 +99493,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -87561,7 +99755,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -87961,7 +100155,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -88254,7 +100448,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -88301,7 +100495,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -88420,6 +100614,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -88579,7 +100910,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -89011,7 +101342,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -89274,7 +101605,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -89321,7 +101652,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -89440,6 +101771,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -89876,7 +102344,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -89923,7 +102391,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -90058,6 +102526,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -90233,7 +102854,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -90804,7 +103425,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -90851,7 +103472,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -90986,6 +103607,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -91161,7 +103935,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -91455,7 +104229,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -91717,7 +104491,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -91978,7 +104752,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/p-interfaces">/p-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/p-interfaces">/p-interfaces</a>
</div>
</div>
</div>
@@ -92119,7 +104893,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/p-interface">/p-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/p-interface">/p-interface</a>
</div>
</div>
</div>
@@ -92166,7 +104940,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>p-interface object that needs to be created or updated</p>
+ <p><p>p-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -92253,6 +105027,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing p-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing p-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>p-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/p-interface">/p-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing p-interface</div>
@@ -92474,7 +105353,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -92676,7 +105555,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -92723,7 +105602,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -92826,6 +105705,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -93185,7 +106185,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -93232,7 +106232,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -93351,6 +106351,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -93510,7 +106647,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -93988,7 +107125,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -94035,7 +107172,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -94154,6 +107291,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -94313,7 +107587,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -94575,7 +107849,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -94960,7 +108234,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -95238,7 +108512,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -95285,7 +108559,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -95404,6 +108678,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -95563,7 +108974,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -95980,7 +109391,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -96228,7 +109639,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -96275,7 +109686,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -96394,6 +109805,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -96815,7 +110363,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -96862,7 +110410,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -96997,6 +110545,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -97172,7 +110873,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -97728,7 +111429,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -97775,7 +111476,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -97910,6 +111611,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -98085,7 +111939,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -98379,7 +112233,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -98641,7 +112495,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -98839,7 +112693,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -99022,7 +112876,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/route-table-references">/route-table-references</a>
+ <a class="json-schema-ref" href="#/getDefinitions/route-table-references">/route-table-references</a>
</div>
</div>
</div>
@@ -99132,7 +112986,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/route-table-reference">/route-table-reference</a>
+ <a class="json-schema-ref" href="#/getDefinitions/route-table-reference">/route-table-reference</a>
</div>
</div>
</div>
@@ -99179,7 +113033,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>route-table-reference object that needs to be created or updated</p>
+ <p><p>route-table-reference object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkRouteTableReferencesRouteTableReference.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -99250,6 +113104,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-route-table-references-route-table-reference--route-table-reference-id--"></span>
+ <div id="operation--network-route-table-references-route-table-reference--route-table-reference-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing route-table-reference</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/route-table-references/route-table-reference/{route-table-reference-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing route-table-reference</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>route-table-reference object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/route-table-reference">/route-table-reference</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ route-table-reference-id
+ </td>
+ <td>
+ <p>Route Table Reference id, UUID assigned to this instance.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-route-table-references-route-table-reference--route-table-reference-id--"></span>
<div id="operation--network-route-table-references-route-table-reference--route-table-reference-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing route-table-reference</div>
@@ -99361,7 +113304,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkRouteTableReferencesRouteTableReference.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -99544,7 +113487,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/site-pair-sets">/site-pair-sets</a>
+ <a class="json-schema-ref" href="#/getDefinitions/site-pair-sets">/site-pair-sets</a>
</div>
</div>
</div>
@@ -99639,7 +113582,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/site-pair-set">/site-pair-set</a>
+ <a class="json-schema-ref" href="#/getDefinitions/site-pair-set">/site-pair-set</a>
</div>
</div>
</div>
@@ -99686,7 +113629,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>site-pair-set object that needs to be created or updated</p>
+ <p><p>site-pair-set object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -99757,6 +113700,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--"></span>
+ <div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing site-pair-set</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/site-pair-sets/site-pair-set/{site-pair-set-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing site-pair-set</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>site-pair-set object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/site-pair-set">/site-pair-set</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ site-pair-set-id
+ </td>
+ <td>
+ <p>Unique id of site pair set.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--"></span>
<div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing site-pair-set</div>
@@ -99868,7 +113900,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -100082,7 +114114,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/routing-instances">/routing-instances</a>
+ <a class="json-schema-ref" href="#/getDefinitions/routing-instances">/routing-instances</a>
</div>
</div>
</div>
@@ -100193,7 +114225,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/routing-instance">/routing-instance</a>
+ <a class="json-schema-ref" href="#/getDefinitions/routing-instance">/routing-instance</a>
</div>
</div>
</div>
@@ -100240,7 +114272,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>routing-instance object that needs to be created or updated</p>
+ <p><p>routing-instance object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -100327,6 +114359,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--"></span>
+ <div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing routing-instance</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing routing-instance</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>routing-instance object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/routing-instance">/routing-instance</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ site-pair-set-id
+ </td>
+ <td>
+ <p>Unique id of site pair set.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ routing-instance-id
+ </td>
+ <td>
+ <p>Unique id of routing instance</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--"></span>
<div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing routing-instance</div>
@@ -100454,7 +114591,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -100716,7 +114853,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/site-pairs">/site-pairs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/site-pairs">/site-pairs</a>
</div>
</div>
</div>
@@ -100843,7 +114980,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/site-pair">/site-pair</a>
+ <a class="json-schema-ref" href="#/getDefinitions/site-pair">/site-pair</a>
</div>
</div>
</div>
@@ -100890,7 +115027,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>site-pair object that needs to be created or updated</p>
+ <p><p>site-pair object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -100993,6 +115130,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--"></span>
+ <div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing site-pair</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing site-pair</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>site-pair object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/site-pair">/site-pair</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ site-pair-set-id
+ </td>
+ <td>
+ <p>Unique id of site pair set.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ routing-instance-id
+ </td>
+ <td>
+ <p>Unique id of routing instance</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ site-pair-id
+ </td>
+ <td>
+ <p>unique identifier of probe</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--"></span>
<div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing site-pair</div>
@@ -101216,7 +115474,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/classes-of-service">/classes-of-service</a>
+ <a class="json-schema-ref" href="#/getDefinitions/classes-of-service">/classes-of-service</a>
</div>
</div>
</div>
@@ -101359,7 +115617,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/class-of-service">/class-of-service</a>
+ <a class="json-schema-ref" href="#/getDefinitions/class-of-service">/class-of-service</a>
</div>
</div>
</div>
@@ -101406,7 +115664,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>class-of-service object that needs to be created or updated</p>
+ <p><p>class-of-service object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -101525,6 +115783,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--classes-of-service-class-of-service--cos--"></span>
+ <div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--classes-of-service-class-of-service--cos--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing class-of-service</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}/classes-of-service/class-of-service/{cos}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing class-of-service</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>class-of-service object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/class-of-service">/class-of-service</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ site-pair-set-id
+ </td>
+ <td>
+ <p>Unique id of site pair set.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ routing-instance-id
+ </td>
+ <td>
+ <p>Unique id of routing instance</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ site-pair-id
+ </td>
+ <td>
+ <p>unique identifier of probe</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cos
+ </td>
+ <td>
+ <p>unique identifier of probe</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--classes-of-service-class-of-service--cos--"></span>
<div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--classes-of-service-class-of-service--cos--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing class-of-service</div>
@@ -101684,7 +116079,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -101946,7 +116341,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -102193,7 +116588,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vces">/vces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vces">/vces</a>
</div>
</div>
</div>
@@ -102408,7 +116803,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vce">/vce</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vce">/vce</a>
</div>
</div>
</div>
@@ -102455,7 +116850,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vce object that needs to be created or updated</p>
+ <p><p>vce object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVce.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -102526,6 +116921,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vces-vce--vnf-id--"></span>
+ <div id="operation--network-vces-vce--vnf-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vce</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vces/vce/{vnf-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vce</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vce object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vce">/vce</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vces-vce--vnf-id--"></span>
<div id="operation--network-vces-vce--vnf-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vce</div>
@@ -102805,7 +117289,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/entitlements">/entitlements</a>
+ <a class="json-schema-ref" href="#/getDefinitions/entitlements">/entitlements</a>
</div>
</div>
</div>
@@ -103052,7 +117536,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/entitlement">/entitlement</a>
+ <a class="json-schema-ref" href="#/getDefinitions/entitlement">/entitlement</a>
</div>
</div>
</div>
@@ -103099,7 +117583,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>entitlement object that needs to be created or updated</p>
+ <p><p>entitlement object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVceEntitlementsEntitlement.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -103202,6 +117686,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vces-vce--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--"></span>
+ <div id="operation--network-vces-vce--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing entitlement</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vces/vce/{vnf-id}/entitlements/entitlement/{group-uuid}/{resource-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing entitlement</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>entitlement object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/entitlement">/entitlement</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ group-uuid
+ </td>
+ <td>
+ <p>Unique ID for the entitlement group the resource comes from, should be uuid.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ resource-uuid
+ </td>
+ <td>
+ <p>Unique ID of an entitlement resource.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vces-vce--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--"></span>
<div id="operation--network-vces-vce--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing entitlement</div>
@@ -103345,7 +117950,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVceEntitlementsEntitlement.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -103743,7 +118348,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/licenses">/licenses</a>
+ <a class="json-schema-ref" href="#/getDefinitions/licenses">/licenses</a>
</div>
</div>
</div>
@@ -103990,7 +118595,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/license">/license</a>
+ <a class="json-schema-ref" href="#/getDefinitions/license">/license</a>
</div>
</div>
</div>
@@ -104037,7 +118642,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>license object that needs to be created or updated</p>
+ <p><p>license object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVceLicensesLicense.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -104140,6 +118745,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vces-vce--vnf-id--licenses-license--group-uuid---resource-uuid--"></span>
+ <div id="operation--network-vces-vce--vnf-id--licenses-license--group-uuid---resource-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing license</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vces/vce/{vnf-id}/licenses/license/{group-uuid}/{resource-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing license</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>license object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/license">/license</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ group-uuid
+ </td>
+ <td>
+ <p>Unique ID for the license group the resource belongs to, should be uuid.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ resource-uuid
+ </td>
+ <td>
+ <p>Unique ID of a license resource.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vces-vce--vnf-id--licenses-license--group-uuid---resource-uuid--"></span>
<div id="operation--network-vces-vce--vnf-id--licenses-license--group-uuid---resource-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing license</div>
@@ -104283,7 +119009,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVceLicensesLicense.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -104681,7 +119407,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/port-groups">/port-groups</a>
+ <a class="json-schema-ref" href="#/getDefinitions/port-groups">/port-groups</a>
</div>
</div>
</div>
@@ -104957,7 +119683,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/port-group">/port-group</a>
+ <a class="json-schema-ref" href="#/getDefinitions/port-group">/port-group</a>
</div>
</div>
</div>
@@ -105004,7 +119730,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>port-group object that needs to be created or updated</p>
+ <p><p>port-group object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVcePortGroupsPortGroup.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -105091,6 +119817,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vces-vce--vnf-id--port-groups-port-group--interface-id--"></span>
+ <div id="operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing port-group</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing port-group</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>port-group object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/port-group">/port-group</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-id
+ </td>
+ <td>
+ <p>Unique ID of the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vces-vce--vnf-id--port-groups-port-group--interface-id--"></span>
<div id="operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing port-group</div>
@@ -105447,7 +120278,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/cvlan-tags">/cvlan-tags</a>
+ <a class="json-schema-ref" href="#/getDefinitions/cvlan-tags">/cvlan-tags</a>
</div>
</div>
</div>
@@ -105739,7 +120570,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/cvlan-tag-entry">/cvlan-tag-entry</a>
+ <a class="json-schema-ref" href="#/getDefinitions/cvlan-tag-entry">/cvlan-tag-entry</a>
</div>
</div>
</div>
@@ -105786,7 +120617,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>cvlan-tag-entry object that needs to be created or updated</p>
+ <p><p>cvlan-tag-entry object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -105889,6 +120720,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vces-vce--vnf-id--port-groups-port-group--interface-id--cvlan-tags-cvlan-tag-entry--cvlan-tag--"></span>
+ <div id="operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--cvlan-tags-cvlan-tag-entry--cvlan-tag--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing cvlan-tag-entry</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}/cvlan-tags/cvlan-tag-entry/{cvlan-tag}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing cvlan-tag-entry</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>cvlan-tag-entry object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/cvlan-tag-entry">/cvlan-tag-entry</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-id
+ </td>
+ <td>
+ <p>Unique ID of the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cvlan-tag
+ </td>
+ <td>
+ <p>See mis-na-virtualization-platform.yang</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vces-vce--vnf-id--port-groups-port-group--interface-id--cvlan-tags-cvlan-tag-entry--cvlan-tag--"></span>
<div id="operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--cvlan-tags-cvlan-tag-entry--cvlan-tag--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing cvlan-tag-entry</div>
@@ -106032,7 +120984,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -106262,7 +121214,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVcePortGroupsPortGroup.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -106460,7 +121412,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVce.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -106643,7 +121595,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vnfcs">/vnfcs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vnfcs">/vnfcs</a>
</div>
</div>
</div>
@@ -106841,7 +121793,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vnfc">/vnfc</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vnfc">/vnfc</a>
</div>
</div>
</div>
@@ -106888,7 +121840,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vnfc object that needs to be created or updated</p>
+ <p><p>vnfc object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVnfcsVnfc.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -106959,6 +121911,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vnfcs-vnfc--vnfc-name--"></span>
+ <div id="operation--network-vnfcs-vnfc--vnfc-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vnfc</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vnfcs/vnfc/{vnfc-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vnfc</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vnfc object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vnfc">/vnfc</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnfc-name
+ </td>
+ <td>
+ <p>Unique ID of vnfc.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vnfcs-vnfc--vnfc-name--"></span>
<div id="operation--network-vnfcs-vnfc--vnfc-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vnfc</div>
@@ -107070,7 +122111,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVnfcsVnfc.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -107253,7 +122294,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vpls-pes">/vpls-pes</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vpls-pes">/vpls-pes</a>
</div>
</div>
</div>
@@ -107362,7 +122403,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vpls-pe">/vpls-pe</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vpls-pe">/vpls-pe</a>
</div>
</div>
</div>
@@ -107409,7 +122450,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vpls-pe object that needs to be created or updated</p>
+ <p><p>vpls-pe object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPe.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -107479,6 +122520,94 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vpls-pe</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vpls-pe</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vpls-pe object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vpls-pe">/vpls-pe</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vpls-pe</div>
@@ -107651,7 +122780,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interfaces">/lag-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interfaces">/lag-interfaces</a>
</div>
</div>
</div>
@@ -107806,7 +122935,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interface">/lag-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interface">/lag-interface</a>
</div>
</div>
</div>
@@ -107853,7 +122982,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>lag-interface object that needs to be created or updated</p>
+ <p><p>lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -107939,6 +123068,110 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing lag-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing lag-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>lag-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/lag-interface">/lag-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing lag-interface</div>
@@ -108173,7 +123406,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -108389,7 +123622,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -108436,7 +123669,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -108538,6 +123771,126 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -108910,7 +124263,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -108957,7 +124310,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -109075,6 +124428,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -109233,7 +124722,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -109723,7 +125212,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -109770,7 +125259,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -109888,6 +125377,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -110046,7 +125671,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -110306,7 +125931,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -110703,7 +126328,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -110995,7 +126620,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -111042,7 +126667,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -111160,6 +126785,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -111318,7 +127079,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -111747,7 +127508,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -112009,7 +127770,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -112056,7 +127817,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -112174,6 +127935,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -112608,7 +128505,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -112655,7 +128552,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -112789,6 +128686,158 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -112963,7 +129012,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -113531,7 +129580,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -113578,7 +129627,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -113712,6 +129761,158 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -113886,7 +130087,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -114178,7 +130379,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -114438,7 +130639,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -114696,7 +130897,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/p-interfaces">/p-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/p-interfaces">/p-interfaces</a>
</div>
</div>
</div>
@@ -114836,7 +131037,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/p-interface">/p-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/p-interface">/p-interface</a>
</div>
</div>
</div>
@@ -114883,7 +131084,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>p-interface object that needs to be created or updated</p>
+ <p><p>p-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -114969,6 +131170,110 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing p-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing p-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>p-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/p-interface">/p-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing p-interface</div>
@@ -115188,7 +131493,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -115389,7 +131694,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -115436,7 +131741,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -115538,6 +131843,126 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -115895,7 +132320,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -115942,7 +132367,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -116060,6 +132485,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -116218,7 +132779,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -116693,7 +133254,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -116740,7 +133301,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -116858,6 +133419,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -117016,7 +133713,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -117276,7 +133973,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -117658,7 +134355,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -117935,7 +134632,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -117982,7 +134679,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -118100,6 +134797,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -118258,7 +135091,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -118672,7 +135505,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -118919,7 +135752,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -118966,7 +135799,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -119084,6 +135917,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -119503,7 +136472,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -119550,7 +136519,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -119684,6 +136653,158 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -119858,7 +136979,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -120411,7 +137532,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -120458,7 +137579,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -120592,6 +137713,158 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -120766,7 +138039,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -121058,7 +138331,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -121318,7 +138591,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -121514,7 +138787,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPe.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -121695,7 +138968,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vpn-bindings">/vpn-bindings</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vpn-bindings">/vpn-bindings</a>
</div>
</div>
</div>
@@ -121820,7 +139093,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vpn-binding">/vpn-binding</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vpn-binding">/vpn-binding</a>
</div>
</div>
</div>
@@ -121867,7 +139140,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vpn-binding object that needs to be created or updated</p>
+ <p><p>vpn-binding object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVpnBindingsVpnBinding.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -121938,6 +139211,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpn-bindings-vpn-binding--vpn-id--"></span>
+ <div id="operation--network-vpn-bindings-vpn-binding--vpn-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vpn-binding</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpn-bindings/vpn-binding/{vpn-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vpn-binding</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vpn-binding object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vpn-binding">/vpn-binding</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vpn-id
+ </td>
+ <td>
+ <p>VPN ID, globally unique within A&AI</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpn-bindings-vpn-binding--vpn-id--"></span>
<div id="operation--network-vpn-bindings-vpn-binding--vpn-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vpn-binding</div>
@@ -122049,7 +139411,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVpnBindingsVpnBinding.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -122293,7 +139655,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/route-targets">/route-targets</a>
+ <a class="json-schema-ref" href="#/getDefinitions/route-targets">/route-targets</a>
</div>
</div>
</div>
@@ -122450,7 +139812,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/route-target">/route-target</a>
+ <a class="json-schema-ref" href="#/getDefinitions/route-target">/route-target</a>
</div>
</div>
</div>
@@ -122497,7 +139859,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>route-target object that needs to be created or updated</p>
+ <p><p>route-target object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVpnBindingsVpnBindingRouteTargetsRouteTarget.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -122600,6 +139962,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpn-bindings-vpn-binding--vpn-id--route-targets-route-target--global-route-target---route-target-role--"></span>
+ <div id="operation--network-vpn-bindings-vpn-binding--vpn-id--route-targets-route-target--global-route-target---route-target-role--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing route-target</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpn-bindings/vpn-binding/{vpn-id}/route-targets/route-target/{global-route-target}/{route-target-role}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing route-target</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>route-target object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/route-target">/route-target</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vpn-id
+ </td>
+ <td>
+ <p>VPN ID, globally unique within A&AI</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ global-route-target
+ </td>
+ <td>
+ <p>Number used to identify an RT, globally unique in the network</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ route-target-role
+ </td>
+ <td>
+ <p>Role assigned to this route target</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpn-bindings-vpn-binding--vpn-id--route-targets-route-target--global-route-target---route-target-role--"></span>
<div id="operation--network-vpn-bindings-vpn-binding--vpn-id--route-targets-route-target--global-route-target---route-target-role--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing route-target</div>
@@ -122743,7 +140226,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVpnBindingsVpnBindingRouteTargetsRouteTarget.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -122990,7 +140473,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/zones">/zones</a>
+ <a class="json-schema-ref" href="#/getDefinitions/zones">/zones</a>
</div>
</div>
</div>
@@ -123115,7 +140598,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/zone">/zone</a>
+ <a class="json-schema-ref" href="#/getDefinitions/zone">/zone</a>
</div>
</div>
</div>
@@ -123162,7 +140645,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>zone object that needs to be created or updated</p>
+ <p><p>zone object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkZonesZone.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -123233,6 +140716,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-zones-zone--zone-id--"></span>
+ <div id="operation--network-zones-zone--zone-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing zone</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/zones/zone/{zone-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing zone</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>zone object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/zone">/zone</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ zone-id
+ </td>
+ <td>
+ <p>Code assigned by AIC to the zone</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-zones-zone--zone-id--"></span>
<div id="operation--network-zones-zone--zone-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing zone</div>
@@ -123344,7 +140916,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkZonesZone.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -123527,7 +141099,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/models">/models</a>
+ <a class="json-schema-ref" href="#/getDefinitions/models">/models</a>
</div>
</div>
</div>
@@ -123637,7 +141209,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/model">/model</a>
+ <a class="json-schema-ref" href="#/getDefinitions/model">/model</a>
</div>
</div>
</div>
@@ -123684,7 +141256,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>model object that needs to be created or updated</p>
+ <p><p>model object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModel.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -123755,6 +141327,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-models-model--model-invariant-id--"></span>
+ <div id="operation--service-design-and-creation-models-model--model-invariant-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing model</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/models/model/{model-invariant-id}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing model</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>model object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/model">/model</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ model-invariant-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to the main definition of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-models-model--model-invariant-id--"></span>
<div id="operation--service-design-and-creation-models-model--model-invariant-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing model</div>
@@ -123929,7 +141590,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/model-vers">/model-vers</a>
+ <a class="json-schema-ref" href="#/getDefinitions/model-vers">/model-vers</a>
</div>
</div>
</div>
@@ -124085,7 +141746,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/model-ver">/model-ver</a>
+ <a class="json-schema-ref" href="#/getDefinitions/model-ver">/model-ver</a>
</div>
</div>
</div>
@@ -124132,7 +141793,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>model-ver object that needs to be created or updated</p>
+ <p><p>model-ver object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVer.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -124219,6 +141880,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--"></span>
+ <div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing model-ver</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing model-ver</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>model-ver object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/model-ver">/model-ver</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ model-invariant-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to the main definition of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-version-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to one version of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--"></span>
<div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing model-ver</div>
@@ -124455,7 +142221,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadata">/metadata</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadata">/metadata</a>
</div>
</div>
</div>
@@ -124626,7 +142392,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadatum">/metadatum</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadatum">/metadatum</a>
</div>
</div>
</div>
@@ -124673,7 +142439,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>metadatum object that needs to be created or updated</p>
+ <p><p>metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerMetadataMetadatum.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -124775,6 +142541,126 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--metadata-metadatum--metaname--"></span>
+ <div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--metadata-metadatum--metaname--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing metadatum</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/metadata/metadatum/{metaname}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing metadatum</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>metadatum object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/metadatum">/metadatum</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ model-invariant-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to the main definition of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-version-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to one version of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ metaname
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--metadata-metadatum--metaname--"></span>
<div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--metadata-metadatum--metaname--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing metadatum</div>
@@ -125026,7 +142912,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/model-elements">/model-elements</a>
+ <a class="json-schema-ref" href="#/getDefinitions/model-elements">/model-elements</a>
</div>
</div>
</div>
@@ -125197,7 +143083,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/model-element">/model-element</a>
+ <a class="json-schema-ref" href="#/getDefinitions/model-element">/model-element</a>
</div>
</div>
</div>
@@ -125244,7 +143130,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>model-element object that needs to be created or updated</p>
+ <p><p>model-element object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElement.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -125346,6 +143232,126 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--"></span>
+ <div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing model-element</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing model-element</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>model-element object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/model-element">/model-element</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ model-invariant-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to the main definition of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-version-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to one version of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-element-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--"></span>
<div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing model-element</div>
@@ -125612,7 +143618,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/model-constraints">/model-constraints</a>
+ <a class="json-schema-ref" href="#/getDefinitions/model-constraints">/model-constraints</a>
</div>
</div>
</div>
@@ -125798,7 +143804,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/model-constraint">/model-constraint</a>
+ <a class="json-schema-ref" href="#/getDefinitions/model-constraint">/model-constraint</a>
</div>
</div>
</div>
@@ -125845,7 +143851,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>model-constraint object that needs to be created or updated</p>
+ <p><p>model-constraint object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraint.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -125962,6 +143968,141 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--"></span>
+ <div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing model-constraint</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing model-constraint</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>model-constraint object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/model-constraint">/model-constraint</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ model-invariant-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to the main definition of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-version-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to one version of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-element-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-constraint-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--"></span>
<div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing model-constraint</div>
@@ -126258,7 +144399,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/constrained-element-sets">/constrained-element-sets</a>
+ <a class="json-schema-ref" href="#/getDefinitions/constrained-element-sets">/constrained-element-sets</a>
</div>
</div>
</div>
@@ -126459,7 +144600,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/constrained-element-set">/constrained-element-set</a>
+ <a class="json-schema-ref" href="#/getDefinitions/constrained-element-set">/constrained-element-set</a>
</div>
</div>
</div>
@@ -126506,7 +144647,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>constrained-element-set object that needs to be created or updated</p>
+ <p><p>constrained-element-set object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -126638,6 +144779,156 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--"></span>
+ <div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing constrained-element-set</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing constrained-element-set</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>constrained-element-set object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/constrained-element-set">/constrained-element-set</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ model-invariant-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to the main definition of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-version-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to one version of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-element-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-constraint-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ constrained-element-set-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--"></span>
<div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing constrained-element-set</div>
@@ -126964,7 +145255,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/element-choice-sets">/element-choice-sets</a>
+ <a class="json-schema-ref" href="#/getDefinitions/element-choice-sets">/element-choice-sets</a>
</div>
</div>
</div>
@@ -127180,7 +145471,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/element-choice-set">/element-choice-set</a>
+ <a class="json-schema-ref" href="#/getDefinitions/element-choice-set">/element-choice-set</a>
</div>
</div>
</div>
@@ -127227,7 +145518,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>element-choice-set object that needs to be created or updated</p>
+ <p><p>element-choice-set object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -127374,6 +145665,171 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--element-choice-sets-element-choice-set--element-choice-set-uuid--"></span>
+ <div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--element-choice-sets-element-choice-set--element-choice-set-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing element-choice-set</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}/element-choice-sets/element-choice-set/{element-choice-set-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing element-choice-set</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>element-choice-set object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/element-choice-set">/element-choice-set</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ model-invariant-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to the main definition of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-version-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to one version of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-element-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-constraint-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ constrained-element-set-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ element-choice-set-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--element-choice-sets-element-choice-set--element-choice-set-uuid--"></span>
<div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--element-choice-sets-element-choice-set--element-choice-set-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing element-choice-set</div>
@@ -127561,7 +146017,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -127879,7 +146335,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -128167,7 +146623,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElement.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -128395,7 +146851,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVer.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -128593,7 +147049,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModel.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -128776,7 +147232,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/named-queries">/named-queries</a>
+ <a class="json-schema-ref" href="#/getDefinitions/named-queries">/named-queries</a>
</div>
</div>
</div>
@@ -128884,7 +147340,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/named-query">/named-query</a>
+ <a class="json-schema-ref" href="#/getDefinitions/named-query">/named-query</a>
</div>
</div>
</div>
@@ -128931,7 +147387,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>named-query object that needs to be created or updated</p>
+ <p><p>named-query object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationNamedQueriesNamedQuery.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -129001,6 +147457,94 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--"></span>
+ <div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing named-query</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/named-queries/named-query/{named-query-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing named-query</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>named-query object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/named-query">/named-query</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ named-query-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--"></span>
<div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing named-query</div>
@@ -129172,7 +147716,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/named-query-elements">/named-query-elements</a>
+ <a class="json-schema-ref" href="#/getDefinitions/named-query-elements">/named-query-elements</a>
</div>
</div>
</div>
@@ -129295,7 +147839,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/named-query-element">/named-query-element</a>
+ <a class="json-schema-ref" href="#/getDefinitions/named-query-element">/named-query-element</a>
</div>
</div>
</div>
@@ -129342,7 +147886,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>named-query-element object that needs to be created or updated</p>
+ <p><p>named-query-element object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -129427,6 +147971,109 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--"></span>
+ <div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing named-query-element</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing named-query-element</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>named-query-element object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/named-query-element">/named-query-element</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ named-query-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ named-query-element-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--"></span>
<div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing named-query-element</div>
@@ -129628,7 +148275,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/property-constraints">/property-constraints</a>
+ <a class="json-schema-ref" href="#/getDefinitions/property-constraints">/property-constraints</a>
</div>
</div>
</div>
@@ -129766,7 +148413,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/property-constraint">/property-constraint</a>
+ <a class="json-schema-ref" href="#/getDefinitions/property-constraint">/property-constraint</a>
</div>
</div>
</div>
@@ -129813,7 +148460,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>property-constraint object that needs to be created or updated</p>
+ <p><p>property-constraint object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementPropertyConstraintsPropertyConstraint.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -129913,6 +148560,124 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--property-constraints-property-constraint--property-constraint-uuid--"></span>
+ <div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--property-constraints-property-constraint--property-constraint-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing property-constraint</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/property-constraints/property-constraint/{property-constraint-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing property-constraint</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>property-constraint object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/property-constraint">/property-constraint</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ named-query-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ named-query-element-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ property-constraint-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--property-constraints-property-constraint--property-constraint-uuid--"></span>
<div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--property-constraints-property-constraint--property-constraint-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing property-constraint</div>
@@ -130129,7 +148894,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/related-lookups">/related-lookups</a>
+ <a class="json-schema-ref" href="#/getDefinitions/related-lookups">/related-lookups</a>
</div>
</div>
</div>
@@ -130267,7 +149032,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/related-lookup">/related-lookup</a>
+ <a class="json-schema-ref" href="#/getDefinitions/related-lookup">/related-lookup</a>
</div>
</div>
</div>
@@ -130314,7 +149079,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>related-lookup object that needs to be created or updated</p>
+ <p><p>related-lookup object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -130414,6 +149179,124 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--related-lookups-related-lookup--related-lookup-uuid--"></span>
+ <div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--related-lookups-related-lookup--related-lookup-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing related-lookup</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/related-lookups/related-lookup/{related-lookup-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing related-lookup</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>related-lookup object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/related-lookup">/related-lookup</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ named-query-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ named-query-element-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ related-lookup-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--related-lookups-related-lookup--related-lookup-uuid--"></span>
<div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--related-lookups-related-lookup--related-lookup-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing related-lookup</div>
@@ -130554,7 +149437,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -130778,7 +149661,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -130972,7 +149855,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationNamedQueriesNamedQuery.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -131153,7 +150036,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/service-capabilities">/service-capabilities</a>
+ <a class="json-schema-ref" href="#/getDefinitions/service-capabilities">/service-capabilities</a>
</div>
</div>
</div>
@@ -131264,7 +150147,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/service-capability">/service-capability</a>
+ <a class="json-schema-ref" href="#/getDefinitions/service-capability">/service-capability</a>
</div>
</div>
</div>
@@ -131311,7 +150194,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>service-capability object that needs to be created or updated</p>
+ <p><p>service-capability object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationServiceCapabilitiesServiceCapability.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -131398,6 +150281,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-service-capabilities-service-capability--service-type---vnf-type--"></span>
+ <div id="operation--service-design-and-creation-service-capabilities-service-capability--service-type---vnf-type--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing service-capability</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/service-capabilities/service-capability/{service-type}/{vnf-type}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing service-capability</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>service-capability object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/service-capability">/service-capability</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ service-type
+ </td>
+ <td>
+ <p>This gets defined by others to provide a unique ID for the service, we accept what is sent.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vnf-type
+ </td>
+ <td>
+ <p>String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-service-capabilities-service-capability--service-type---vnf-type--"></span>
<div id="operation--service-design-and-creation-service-capabilities-service-capability--service-type---vnf-type--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing service-capability</div>
@@ -131525,7 +150513,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationServiceCapabilitiesServiceCapability.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -131740,7 +150728,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/services">/services</a>
+ <a class="json-schema-ref" href="#/getDefinitions/services">/services</a>
</div>
</div>
</div>
@@ -131850,7 +150838,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/service">/service</a>
+ <a class="json-schema-ref" href="#/getDefinitions/service">/service</a>
</div>
</div>
</div>
@@ -131897,7 +150885,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>service object that needs to be created or updated</p>
+ <p><p>service object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationServicesService.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -131968,6 +150956,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-services-service--service-id--"></span>
+ <div id="operation--service-design-and-creation-services-service--service-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing service</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/services/service/{service-id}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing service</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>service object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/service">/service</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ service-id
+ </td>
+ <td>
+ <p>This gets defined by others to provide a unique ID for the service, we accept what is sent.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-services-service--service-id--"></span>
<div id="operation--service-design-and-creation-services-service--service-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing service</div>
@@ -132079,7 +151156,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationServicesService.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -132262,7 +151339,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vnf-images">/vnf-images</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vnf-images">/vnf-images</a>
</div>
</div>
</div>
@@ -132402,7 +151479,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vnf-image">/vnf-image</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vnf-image">/vnf-image</a>
</div>
</div>
</div>
@@ -132449,7 +151526,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vnf-image object that needs to be created or updated</p>
+ <p><p>vnf-image object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationVnfImagesVnfImage.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -132520,6 +151597,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-vnf-images-vnf-image--vnf-image-uuid--"></span>
+ <div id="operation--service-design-and-creation-vnf-images-vnf-image--vnf-image-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vnf-image</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/vnf-images/vnf-image/{vnf-image-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vnf-image</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vnf-image object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vnf-image">/vnf-image</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-image-uuid
+ </td>
+ <td>
+ <p>Unique ID of this asset</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-vnf-images-vnf-image--vnf-image-uuid--"></span>
<div id="operation--service-design-and-creation-vnf-images-vnf-image--vnf-image-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vnf-image</div>
@@ -132631,7 +151797,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationVnfImagesVnfImage.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -132781,6 +151947,45 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<h2>Schema definitions</h2>
+ <div id="definition-aai-internal" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/aai-internal"></a>aai-internal:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="property-name">
+ <span class="json-property-name">property-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="property-value">
+ <span class="json-property-name">property-value:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-action" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/action"></a>action:
@@ -132941,18 +152146,17 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Represents a slice or partial piece of a resource that gets separately allotted</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO generic-vnf (Many2Many)</li>
-<li>TO l3-network (Many2Many)</li>
-<li>TO instance-group (Many2Many)</li>
-<li>TO network-policy (One2One)</li>
-<li>TO vlan (Many2Many)</li>
-<li>TO tunnel-xconnect (comprises allotted-resource, One2One)</li>
-<li>FROM service-instance (is composed of allotted-resource)</li>
-<li>FROM service-instance</li></ul>
+<li>TO generic-vnf( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY)</li>
+<li>TO instance-group( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>TO l3-network( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY)</li>
+<li>TO network-policy( allotted-resource org.onap.relationships.inventory.Uses network-policy, ONE2ONE)</li>
+<li>TO vlan( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY)</li>
+<li>TO service-instance( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)</li>
+<li>FROM tunnel-xconnect( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY)</li>
+<li>ALLOTTED-RESOURCE is DELETED when these are DELETED TUNNEL-XCONNECT</li></ul>
</section>
@@ -133188,18 +152392,17 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Availability zone, a collection of compute hosts/pservers</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_IF_ANY_IN_EDGES</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO complex (Many2Many)</li>
-<li>TO service-capability (Many2Many)</li>
-<li>FROM cloud-region (is composed of availability-zone)</li>
-<li>FROM ctag-pool</li>
-<li>FROM dvs-switch</li>
-<li>FROM generic-vnf</li>
-<li>FROM pserver</li>
-<li>FROM vce</li></ul>
+<li>TO complex( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>TO service-capability( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)</li>
+<li>TO cloud-region( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM ctag-pool( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)</li>
+<li>FROM dvs-switch( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)</li>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)</li>
+<li>FROM pserver( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)</li>
+<li>FROM vce( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)</li>
+<li>AVAILABILITY-ZONE cannot be deleted if linked to CTAG-POOL,DVS-SWITCH,GENERIC-VNF,PSERVER,VCE</li></ul>
</section>
@@ -133449,11 +152652,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<div class="panel-body">
<section class="json-schema-description">
- <h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
-<h6 id="related-nodes">Related Nodes</h6>
+ <h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM site-pair (is composed of class-of-service)</li></ul>
+<li>TO site-pair( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)</li></ul>
</section>
@@ -133706,24 +152907,24 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>cloud-region designates an installation of a cloud cluster or region or instantiation</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO complex (Many2One)</li>
-<li>TO l3-network (Many2Many)</li>
-<li>TO tenant (comprises cloud-region, One2Many)</li>
-<li>TO image (comprises cloud-region, One2Many)</li>
-<li>TO flavor (comprises cloud-region, One2Many)</li>
-<li>TO availability-zone (comprises cloud-region, One2Many)</li>
-<li>TO oam-network (comprises cloud-region, One2Many)</li>
-<li>TO dvs-switch (comprises cloud-region, One2Many)</li>
-<li>TO volume-group (comprises cloud-region, One2Many)</li>
-<li>TO group-assignment (comprises cloud-region, One2Many)</li>
-<li>TO snapshot (comprises cloud-region, One2Many)</li>
-<li>TO zone (Many2One)</li>
-<li>FROM pserver</li>
-<li>FROM logical-link</li></ul>
+<li>TO complex( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>TO l3-network( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>TO zone( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)</li>
+<li>FROM availability-zone( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM dvs-switch( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM flavor( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM group-assignment( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM image( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM oam-network( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM snapshot( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM tenant( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM volume-group( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn cloud-region, MANY2MANY)</li>
+<li>FROM pserver( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)</li>
+<li>CLOUD-REGION cannot be deleted if linked to DVS-SWITCH,FLAVOR,GROUP-ASSIGNMENT,IMAGE,OAM-NETWORK,SNAPSHOT,TENANT,VOLUME-GROUP</li>
+<li>CLOUD-REGION is DELETED when these are DELETED AVAILABILITY-ZONE</li></ul>
</section>
@@ -134092,21 +153293,21 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Collection of physical locations that can house cloud-regions.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_4_IN_EDGES_OR_CASCADE</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO ctag-pool (comprises complex, Many2Many)</li>
-<li>TO l3-network (Many2Many)</li>
-<li>FROM availability-zone</li>
-<li>FROM cloud-region</li>
-<li>FROM oam-network</li>
-<li>FROM pserver</li>
-<li>FROM pnf</li>
-<li>FROM vce</li>
-<li>FROM vpls-pe</li>
-<li>FROM volume-group</li>
-<li>FROM zone</li></ul>
+<li>TO l3-network( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>FROM availability-zone( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM ctag-pool( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)</li>
+<li>FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)</li>
+<li>FROM pnf( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM pserver( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM vce( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)</li>
+<li>FROM volume-group( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM vpls-pe( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM zone( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>COMPLEX cannot be deleted if linked to AVAILABILITY-ZONE,CLOUD-REGION,OAM-NETWORK,PNF,PSERVER,VCE,VOLUME-GROUP,VPLS-PE,ZONE</li>
+<li>COMPLEX is DELETED when these are DELETED CTAG-POOL</li></ul>
</section>
@@ -134397,6 +153598,268 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-configuration" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/configuration"></a>configuration:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Port Mirror Configuration.</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO allotted-resource( configuration org.onap.relationships.inventory.Uses allotted-resource, ONE2ONE)</li>
+<li>TO logical-link( configuration org.onap.relationships.inventory.Uses logical-link, ONE2MANY)</li>
+<li>FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo configuration, MANY2ONE)</li>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses configuration, ONE2MANY)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.Uses configuration, ONE2MANY)</li>
+<li>CONFIGURATION is DELETED when these are DELETED METADATUM</li>
+<li>CONFIGURATION deletion means associated objects of these types are also DELETED:ALLOTTED-RESOURCE,LOGICAL-LINK</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="configuration-id">
+ <span class="json-property-name">configuration-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>UUID assigned to configuration.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="management-option">
+ <span class="json-property-name">management-option:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Indicates the entity that will manage this feature. Could be an organization or the name of the application as well.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="configuration-name">
+ <span class="json-property-name">configuration-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Name of the configuration.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="configuration-type">
+ <span class="json-property-name">configuration-type:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>port-mirroring-configuration.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="configuration-sub-type">
+ <span class="json-property-name">configuration-sub-type:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>vprobe, pprobe.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="model-invariant-id">
+ <span class="json-property-name">model-invariant-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>the ASDC model id for this resource or service model.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="model-version-id">
+ <span class="json-property-name">model-version-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>the ASDC model version for this resource or service model.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="orchestration-status">
+ <span class="json-property-name">orchestration-status:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Orchestration status of the configuration.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="operational-status">
+ <span class="json-property-name">operational-status:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Indicator for whether the resource is considered operational.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="configuration-selflink">
+ <span class="json-property-name">configuration-selflink:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>URL to endpoint where AAI can get more details from SDN-GC.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="model-customization-id">
+ <span class="json-property-name">model-customization-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>id of the configuration used to customize the resource</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ <dt data-property-name="metadata">
+ <span class="json-property-name">metadata:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/metadatum">metadatum</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-configurations" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/configurations"></a>configurations:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Collection of configurations</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="configuration">
+ <span class="json-property-name">configuration:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/configuration">configuration</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-connector" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/connector"></a>connector:
@@ -134409,13 +153872,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Collection of resource instances used to connect a variety of disparate inventory widgets</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO virtual-data-center (Many2Many)</li>
-<li>TO metadatum (comprises connector, Many2Many)</li>
-<li>FROM service-instance</li></ul>
+<li>TO virtual-data-center( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)</li>
+<li>FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)</li>
+<li>CONNECTOR is DELETED when these are DELETED METADATUM</li></ul>
</section>
@@ -134603,13 +154065,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>This is how we would capture constraints defining allowed sets of elements.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO element-choice-set (comprises constrained-element-set, One2Many)</li>
-<li>FROM model-element (is composed of constrained-element-set)</li>
-<li>FROM model-constraint (is composed of constrained-element-set)</li></ul>
+<li>TO model-constraint( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)</li>
+<li>TO model-element( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)</li>
+<li>FROM element-choice-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)</li>
+<li>CONSTRAINED-ELEMENT-SET is DELETED when these are DELETED ELEMENT-CHOICE-SET</li></ul>
</section>
@@ -134754,12 +154215,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<div class="panel-body">
<section class="json-schema-description">
- <h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
-<h6 id="related-nodes">Related Nodes</h6>
+ <h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM l3-network (is composed of ctag-assignment)</li>
-<li>FROM service-instance</li></ul>
+<li>TO l3-network( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.Uses ctag-assignment, ONE2MANY)</li></ul>
</section>
@@ -134863,13 +154322,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>A collection of C tags (vlan tags) grouped for a specific purpose.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO availability-zone (Many2Many)</li>
-<li>FROM complex (is composed of ctag-pool)</li>
-<li>FROM vpls-pe</li></ul>
+<li>TO complex( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)</li>
+<li>TO availability-zone( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)</li>
+<li>FROM vpls-pe( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)</li></ul>
</section>
@@ -135011,11 +154468,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>customer identifiers to provide linkage back to BSS information.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO service-subscription (comprises customer, Many2Many)</li></ul>
+<li>FROM service-subscription( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)</li>
+<li>CUSTOMER is DELETED when these are DELETED SERVICE-SUBSCRIPTION</li></ul>
</section>
@@ -135268,12 +154724,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Digital virtual switch metadata, used by SDN-C to configure VCEs. A&AI needs to receive this data from the PO deployment team and administer it using the provisioningTool.sh into A&AI.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO availability-zone (Many2Many)</li>
-<li>FROM cloud-region (is composed of dvs-switch)</li></ul>
+<li>TO cloud-region( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>TO availability-zone( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)</li></ul>
</section>
@@ -135650,12 +155104,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>This is how we would capture constraints defining allowed sets of elements.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO model-element (comprises element-choice-set, One2Many)</li>
-<li>FROM constrained-element-set (is composed of element-choice-set)</li></ul>
+<li>TO constrained-element-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)</li>
+<li>FROM model-element( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)</li>
+<li>ELEMENT-CHOICE-SET is DELETED when these are DELETED MODEL-ELEMENT</li></ul>
</section>
@@ -135800,12 +155253,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Metadata for entitlement group.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM generic-vnf (is composed of entitlement)</li>
-<li>FROM vce (is composed of entitlement)</li></ul>
+<li>TO generic-vnf( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>TO vce( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)</li></ul>
</section>
@@ -135914,6 +155365,1111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-esr-ems" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/esr-ems"></a>esr-ems:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Persist EMS address information used by EMS driver.</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO esr-system-info (CHILD of esr-ems, esr-ems has esr-system-info, One2Many)</li>
+<li>ESR-EMS deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="ems-id">
+ <span class="json-property-name">ems-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Unique ID of EMS.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="esr-system-info-list">
+ <span class="json-property-name">esr-system-info-list:</span>
+ <span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-system-info-list">esr-system-info-list</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship-list">relationship-list</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-esr-ems-list" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/esr-ems-list"></a>esr-ems-list:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="esr-ems">
+ <span class="json-property-name">esr-ems:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-ems">esr-ems</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-esr-system-info" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/esr-system-info"></a>esr-system-info:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Persist common address information of external systems.</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>FROM esr-ems (PARENT of esr-system-info, esr-ems has esr-system-info)</li>
+<li>FROM esr-vnfm (PARENT of esr-system-info, esr-vnfm has esr-system-info)</li>
+<li>FROM esr-thirdparty-sdnc (PARENT of esr-system-info, esr-thirdparty-sdnc has esr-system-info)</li>
+<li>FROM cloud-region (PARENT of esr-system-info, cloud-region has esr-system-info)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="esr-system-info-id">
+ <span class="json-property-name">esr-system-info-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Unique ID of esr system info.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="system-name">
+ <span class="json-property-name">system-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>name of external system.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="type">
+ <span class="json-property-name">type:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>type of external systems.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="vendor">
+ <span class="json-property-name">vendor:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>vendor of external systems.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="version">
+ <span class="json-property-name">version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>version of external systems.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="service-url">
+ <span class="json-property-name">service-url:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>url used to access external systems.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="user-name">
+ <span class="json-property-name">user-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>username used to access external systems.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="password">
+ <span class="json-property-name">password:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>password used to access external systems.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="system-type">
+ <span class="json-property-name">system-type:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>it could be vim/vnfm/thirdparty-sdnc/ems-resource/ems-performance/ems-alarm.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="protocol">
+ <span class="json-property-name">protocol:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>protocol of third party SDNC, for example netconf/snmp.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="ssl-cacert">
+ <span class="json-property-name">ssl-cacert:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>ca file content if enabled ssl on auth-url.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="ssl-insecure">
+ <span class="json-property-name">ssl-insecure:</span>
+ <span class="json-property-type">boolean</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Whether to verify VIM's certificate.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="ip-address">
+ <span class="json-property-name">ip-address:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>service IP of ftp server.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="port">
+ <span class="json-property-name">port:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>service port of ftp server.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="cloud-domain">
+ <span class="json-property-name">cloud-domain:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>domain info for authentication.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="default-tenant">
+ <span class="json-property-name">default-tenant:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>default tenant of VIM.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="passive">
+ <span class="json-property-name">passive:</span>
+ <span class="json-property-type">boolean</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>ftp passive mode or not.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="remote-path">
+ <span class="json-property-name">remote-path:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>resource or performance data file path.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="system-status">
+ <span class="json-property-name">system-status:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>the status of external system.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-esr-system-info-list" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/esr-system-info-list"></a>esr-system-info-list:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Collection of persistent block-level external system auth info.</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="esr-system-info">
+ <span class="json-property-name">esr-system-info:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-system-info">esr-system-info</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-esr-thirdparty-sdnc" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/esr-thirdparty-sdnc"></a>esr-thirdparty-sdnc:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Persist SDNC address information used by ONAP SDNC.</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO esr-system-info (CHILD of esr-thirdparty-sdnc, esr-thirdparty-sdnc has esr-system-info, One2One)</li>
+<li>TO pnf( esr-thirdparty-sdnc has pnf, One2Many)</li>
+<li>ESR-THIRDPARTY-SDNC deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="thirdparty-sdnc-id">
+ <span class="json-property-name">thirdparty-sdnc-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Unique ID of SDNC.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="location">
+ <span class="json-property-name">location:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>used for DC type to indicate the location of SDNC, such as Core or Edge.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="product-name">
+ <span class="json-property-name">product-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>password used to access SDNC server.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="esr-system-info-list">
+ <span class="json-property-name">esr-system-info-list:</span>
+ <span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-system-info-list">esr-system-info-list</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship-list">relationship-list</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-esr-thirdparty-sdnc-list" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/esr-thirdparty-sdnc-list"></a>esr-thirdparty-sdnc-list:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="esr-thirdparty-sdnc">
+ <span class="json-property-name">esr-thirdparty-sdnc:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-thirdparty-sdnc">esr-thirdparty-sdnc</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-esr-vnfm" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/esr-vnfm"></a>esr-vnfm:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Persist VNFM address information used by VF-C.</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO esr-system-info (CHILD of esr-vnfm, esr-vnfm has esr-system-info, One2One)</li>
+<li>ESR-VNFM deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="vnfm-id">
+ <span class="json-property-name">vnfm-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Unique ID of VNFM.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="vim-id">
+ <span class="json-property-name">vim-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>indecate the VIM to deploy VNF.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="certificate-url">
+ <span class="json-property-name">certificate-url:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>certificate url of VNFM.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="esr-system-info-list">
+ <span class="json-property-name">esr-system-info-list:</span>
+ <span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-system-info-list">esr-system-info-list</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship-list">relationship-list</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-esr-vnfm-list" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/esr-vnfm-list"></a>esr-vnfm-list:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="esr-vnfm">
+ <span class="json-property-name">esr-vnfm:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-vnfm">esr-vnfm</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-evc" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/evc"></a>evc:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>evc object is an optional child object of the Configuration object.</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO configuration( evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="evc-id">
+ <span class="json-property-name">evc-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Unique/key field for the evc object</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="forwarding-path-topology">
+ <span class="json-property-name">forwarding-path-topology:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Point-to-Point, Multi-Point</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="cir-value">
+ <span class="json-property-name">cir-value:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Commited Information Rate</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="cir-units">
+ <span class="json-property-name">cir-units:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>CIR units</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="connection-diversity-group-id">
+ <span class="json-property-name">connection-diversity-group-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Diversity Group ID</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="service-hours">
+ <span class="json-property-name">service-hours:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>formerly Performance Group</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="esp-evc-circuit-id">
+ <span class="json-property-name">esp-evc-circuit-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>EVC Circuit ID of ESP EVC</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="esp-evc-cir-value">
+ <span class="json-property-name">esp-evc-cir-value:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Committed Information Rate (For ESP)</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="esp-evc-cir-units">
+ <span class="json-property-name">esp-evc-cir-units:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>CIR units (For ESP)</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="esp-itu-code">
+ <span class="json-property-name">esp-itu-code:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Identifies ESP</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="collector-pop-clli">
+ <span class="json-property-name">collector-pop-clli:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Collector POP CLLI (from the hostname of the access pnf)</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="inter-connect-type-ingress">
+ <span class="json-property-name">inter-connect-type-ingress:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Interconnect type on ingress side of EVC.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="tagmode-access-ingress">
+ <span class="json-property-name">tagmode-access-ingress:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>tagode for collector side of EVC</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="tagmode-access-egress">
+ <span class="json-property-name">tagmode-access-egress:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>tagMode for network side of EVC</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-evcs" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/evcs"></a>evcs:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="evc">
+ <span class="json-property-name">evc:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/evc">evc</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-external-system" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/external-system"></a>external-system:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Namespace for external system.</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="esr-ems-list">
+ <span class="json-property-name">esr-ems-list:</span>
+ <span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-ems-list">esr-ems-list</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ <dt data-property-name="esr-vnfm-list">
+ <span class="json-property-name">esr-vnfm-list:</span>
+ <span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-vnfm-list">esr-vnfm-list</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ <dt data-property-name="esr-thirdparty-sdnc-list">
+ <span class="json-property-name">esr-thirdparty-sdnc-list:</span>
+ <span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-thirdparty-sdnc-list">esr-thirdparty-sdnc-list</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-extra-properties" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/extra-properties"></a>extra-properties:
@@ -136006,12 +156562,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Openstack flavor.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_IF_ANY_IN_EDGES</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM cloud-region (is composed of flavor)</li>
-<li>FROM vserver</li></ul>
+<li>TO cloud-region( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM vserver( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)</li>
+<li>FLAVOR cannot be deleted if linked to VSERVER</li></ul>
</section>
@@ -136217,6 +156772,438 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-forwarder" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/forwarder"></a>forwarder:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Entity describing a sequenced segment of forwarding path</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO forwarding-path( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)</li>
+<li>TO l-interface( forwarder org.onap.relationships.inventory.ForwardsTo l-interface, MANY2ONE)</li>
+<li>TO configuration( forwarder org.onap.relationships.inventory.Uses configuration, ONE2ONE)</li>
+<li>TO lag-interface( forwarder org.onap.relationships.inventory.ForwardsTo lag-interface, MANY2ONE)</li>
+<li>TO p-interface( forwarder org.onap.relationships.inventory.ForwardsTo p-interface, MANY2ONE)</li>
+<li>FORWARDER deletion means associated objects of these types are also DELETED:CONFIGURATION</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="sequence">
+ <span class="json-property-name">sequence:</span>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Unique ID of this segmentation</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="forwarder-role">
+ <span class="json-property-name">forwarder-role:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>ingress, intermediate, egress</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-forwarder-evc" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/forwarder-evc"></a>forwarder-evc:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>forwarder object is an optional child object of the Configuration object.</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO configuration( forwarder-evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="forwarder-evc-id">
+ <span class="json-property-name">forwarder-evc-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Key for forwarder-evc object</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="circuit-id">
+ <span class="json-property-name">circuit-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Circuit ID from customer/ESP/ingress end of EVC, or reference to beater circuit on gateway/network/egress end of EVC</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="ivlan">
+ <span class="json-property-name">ivlan:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Internal VLAN.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="svlan">
+ <span class="json-property-name">svlan:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>SVLAN value for ingress of egress forwarder.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="cvlan">
+ <span class="json-property-name">cvlan:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>CVLAN value for ingress of egress forwarder.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-forwarder-evcs" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/forwarder-evcs"></a>forwarder-evcs:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="forwarder-evc">
+ <span class="json-property-name">forwarder-evc:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/forwarder-evc">forwarder-evc</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-forwarders" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/forwarders"></a>forwarders:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="forwarder">
+ <span class="json-property-name">forwarder:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/forwarder">forwarder</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-forwarding-path" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/forwarding-path"></a>forwarding-path:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Entity that describes the sequenced forwarding path between interfaces of services or resources</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO service-instance( forwarding-path org.onap.relationships.inventory.AppliesTo service-instance, MANY2ONE)</li>
+<li>TO configuration( forwarding-path org.onap.relationships.inventory.Uses configuration, ONE2ONE)</li>
+<li>FROM forwarder( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)</li>
+<li>FORWARDING-PATH is DELETED when these are DELETED FORWARDER</li>
+<li>FORWARDING-PATH deletion means associated objects of these types are also DELETED:CONFIGURATION</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="forwarding-path-id">
+ <span class="json-property-name">forwarding-path-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Unique ID of this FP</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="forwarding-path-name">
+ <span class="json-property-name">forwarding-path-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Name of the FP</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="selflink">
+ <span class="json-property-name">selflink:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>the self link for this FP</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ <dt data-property-name="forwarders">
+ <span class="json-property-name">forwarders:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/forwarder">forwarder</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-forwarding-paths" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/forwarding-paths"></a>forwarding-paths:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="forwarding-path">
+ <span class="json-property-name">forwarding-path:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/forwarding-path">forwarding-path</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-generic-vnf" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/generic-vnf"></a>generic-vnf:
@@ -136229,31 +157216,30 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>General purpose VNF</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO license-key-resource (Many2Many)</li>
-<li>TO l-interface (comprises generic-vnf, Many2Many)</li>
-<li>TO availability-zone (Many2Many)</li>
-<li>TO lag-interface (comprises generic-vnf, Many2Many)</li>
-<li>TO l3-network (Many2Many)</li>
-<li>TO pserver (Many2Many)</li>
-<li>TO vnf-image (Many2One)</li>
-<li>TO vserver (One2Many)</li>
-<li>TO service-instance (Many2Many)</li>
-<li>TO site-pair-set (Many2Many)</li>
-<li>TO network-profile (Many2Many)</li>
-<li>TO ipsec-configuration (Many2One)</li>
-<li>TO vf-module (comprises generic-vnf, One2Many)</li>
-<li>TO volume-group (One2Many)</li>
-<li>TO vnfc (One2Many)</li>
-<li>TO instance-group (Many2Many)</li>
-<li>TO entitlement (comprises generic-vnf, One2Many)</li>
-<li>TO license (comprises generic-vnf, One2Many)</li>
-<li>FROM virtual-data-center</li>
-<li>FROM logical-link</li>
-<li>FROM allotted-resource</li></ul>
+<li>TO availability-zone( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)</li>
+<li>TO instance-group( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>TO ipsec-configuration( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)</li>
+<li>TO l3-network( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>TO license-key-resource( generic-vnf org.onap.relationships.inventory.Uses license-key-resource, MANY2MANY)</li>
+<li>TO pserver( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)</li>
+<li>TO vnf-image( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)</li>
+<li>TO volume-group( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)</li>
+<li>TO vserver( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)</li>
+<li>TO virtual-data-center( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)</li>
+<li>FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY)</li>
+<li>FROM entitlement( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>FROM vnfc( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>FROM lag-interface( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>FROM license( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>FROM network-profile( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)</li>
+<li>FROM site-pair-set( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)</li>
+<li>FROM vf-module( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)</li>
+<li>GENERIC-VNF is DELETED when these are DELETED ENTITLEMENT,VNFC,LAG-INTERFACE,LICENSE,L-INTERFACE,VF-MODULE</li></ul>
</section>
@@ -136991,13 +157977,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Openstack group-assignment used to store exclusivity groups (EG).</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO tenant (Many2Many)</li>
-<li>TO pserver (One2Many)</li>
-<li>FROM cloud-region (is composed of group-assignment)</li></ul>
+<li>TO cloud-region( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM pserver( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)</li>
+<li>FROM tenant( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)</li></ul>
</section>
@@ -137131,6 +158115,149 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-host-route" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/host-route"></a>host-route:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO subnet( host-route org.onap.relationships.inventory.BelongsTo subnet, MANY2ONE)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="host-route-id">
+ <span class="json-property-name">host-route-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>host-route id</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="route-prefix">
+ <span class="json-property-name">route-prefix:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>subnet prefix</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="next-hop">
+ <span class="json-property-name">next-hop:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Could be ip-address, hostname, or service-instance</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="next-hop-type">
+ <span class="json-property-name">next-hop-type:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Should be ip-address, hostname, or service-instance to match next-hop</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-host-routes" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/host-routes"></a>host-routes:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="host-route">
+ <span class="json-property-name">host-route:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/host-route">host-route</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-image" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/image"></a>image:
@@ -137143,13 +158270,13 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Openstack image.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_4_IN_EDGES_OR_CASCADE</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO metadatum (comprises image, Many2Many)</li>
-<li>FROM cloud-region (is composed of image)</li>
-<li>FROM vserver</li></ul>
+<li>TO cloud-region( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)</li>
+<li>FROM vserver( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)</li>
+<li>IMAGE cannot be deleted if linked to VSERVER</li>
+<li>IMAGE is DELETED when these are DELETED METADATUM</li></ul>
</section>
@@ -137467,18 +158594,16 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>General mechanism for grouping instances</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO model (Many2Many)</li>
-<li>FROM l-interface</li>
-<li>FROM l3-interface-ipv4-address-list</li>
-<li>FROM l3-interface-ipv6-address-list</li>
-<li>FROM pnf</li>
-<li>FROM allotted-resource</li>
-<li>FROM generic-vnf</li>
-<li>FROM service-instance</li></ul>
+<li>TO model( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY)</li>
+<li>FROM allotted-resource( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)</li>
+<li>FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)</li>
+<li>FROM l-interface( l-interface org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>FROM pnf( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li></ul>
</section>
@@ -137776,7 +158901,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="json-inner-schema">
<section class="json-schema-array-items">
- <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/"></a>
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/aai-internal">aai-internal</a>
</span>
<span class="json-property-range" title="Value limits"></span>
@@ -138032,12 +159157,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>IPSec configuration node will contain various configuration data for the NMTE VNF. This node will have an edge to the generic-vnf (vnf type = TE). Starting 1607, this data will be populated by SDN-C</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO vig-server (comprises ipsec-configuration, One2Many)</li>
-<li>FROM generic-vnf</li></ul>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)</li>
+<li>FROM vig-server( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)</li>
+<li>IPSEC-CONFIGURATION is DELETED when these are DELETED VIG-SERVER</li></ul>
</section>
@@ -138440,23 +159564,23 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Logical interfaces, e.g., a vnic.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO instance-group (Many2Many)</li>
-<li>TO l3-interface-ipv4-address-list (comprises l-interface, Many2Many)</li>
-<li>TO l3-interface-ipv6-address-list (comprises l-interface, Many2Many)</li>
-<li>TO l-interface (comprises l-interface, One2Many)</li>
-<li>TO logical-link (Many2Many)</li>
-<li>TO vlan (comprises l-interface, Many2Many)</li>
-<li>TO sriov-vf (comprises l-interface, One2One)</li>
-<li>FROM generic-vnf (is composed of l-interface)</li>
-<li>FROM lag-interface (is composed of l-interface)</li>
-<li>FROM newvce (is composed of l-interface)</li>
-<li>FROM p-interface (is composed of l-interface)</li>
-<li>FROM vserver (is composed of l-interface)</li>
-<li>FROM l-interface (is composed of l-interface)</li></ul>
+<li>TO generic-vnf( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>TO lag-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)</li>
+<li>TO instance-group( l-interface org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>TO l-interface( l-interface org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)</li>
+<li>TO logical-link( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)</li>
+<li>TO newvce( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)</li>
+<li>TO p-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)</li>
+<li>TO vserver( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)</li>
+<li>FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)</li>
+<li>FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)</li>
+<li>FROM sriov-vf( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)</li>
+<li>FROM vlan( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)</li>
+<li>FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)</li>
+<li>L-INTERFACE is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST,SRIOV-VF,VLAN</li>
+<li>L-INTERFACE deletion means associated objects of these types are also DELETED:LOGICAL-LINK</li></ul>
</section>
@@ -138784,15 +159908,13 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>IPv4 Address Range</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO instance-group (Many2Many)</li>
-<li>TO l3-network (Many2Many)</li>
-<li>TO subnet (Many2Many)</li>
-<li>FROM l-interface (is composed of l3-interface-ipv4-address-list)</li>
-<li>FROM vlan (is composed of l3-interface-ipv4-address-list)</li></ul>
+<li>TO instance-group( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)</li>
+<li>TO l3-network( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)</li>
+<li>TO subnet( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)</li>
+<li>TO l-interface( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)</li>
+<li>TO vlan( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)</li></ul>
</section>
@@ -138931,15 +160053,13 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>IPv6 Address Range</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO instance-group (Many2Many)</li>
-<li>TO l3-network (Many2Many)</li>
-<li>TO subnet (Many2Many)</li>
-<li>FROM l-interface (is composed of l3-interface-ipv6-address-list)</li>
-<li>FROM vlan (is composed of l3-interface-ipv6-address-list)</li></ul>
+<li>TO instance-group( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)</li>
+<li>TO l3-network( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)</li>
+<li>TO subnet( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)</li>
+<li>TO l-interface( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)</li>
+<li>TO vlan( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)</li></ul>
</section>
@@ -139078,25 +160198,24 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Generic network definition</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO vpn-binding (Many2Many)</li>
-<li>TO subnet (comprises l3-network, Many2Many)</li>
-<li>TO service-instance (Many2Many)</li>
-<li>TO ctag-assignment (comprises l3-network, Many2Many)</li>
-<li>TO network-policy (Many2Many)</li>
-<li>TO segmentation-assignment (comprises l3-network, One2Many)</li>
-<li>TO route-table-reference (Many2Many)</li>
-<li>FROM cloud-region</li>
-<li>FROM complex</li>
-<li>FROM generic-vnf</li>
-<li>FROM l3-interface-ipv4-address-list</li>
-<li>FROM l3-interface-ipv6-address-list</li>
-<li>FROM tenant</li>
-<li>FROM vf-module</li>
-<li>FROM allotted-resource</li></ul>
+<li>TO network-policy( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)</li>
+<li>TO route-table-reference( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)</li>
+<li>TO vpn-binding( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)</li>
+<li>FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY)</li>
+<li>FROM cloud-region( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>FROM complex( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)</li>
+<li>FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)</li>
+<li>FROM ctag-assignment( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)</li>
+<li>FROM segmentation-assignment( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)</li>
+<li>FROM subnet( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)</li>
+<li>FROM tenant( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>FROM vf-module( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)</li>
+<li>L3-NETWORK is DELETED when these are DELETED CTAG-ASSIGNMENT,SEGMENTATION-ASSIGNMENT,SUBNET</li></ul>
</section>
@@ -139549,18 +160668,18 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Link aggregate interface</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO logical-link (Many2Many)</li>
-<li>TO lag-link (Many2Many)</li>
-<li>TO p-interface (Many2Many)</li>
-<li>TO l-interface (comprises lag-interface, Many2Many)</li>
-<li>FROM generic-vnf (is composed of lag-interface)</li>
-<li>FROM pserver (is composed of lag-interface)</li>
-<li>FROM pnf (is composed of lag-interface)</li>
-<li>FROM vpls-pe (is composed of lag-interface)</li></ul>
+<li>TO generic-vnf( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>TO lag-link( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)</li>
+<li>TO logical-link( lag-interface org.onap.relationships.inventory.Uses logical-link, MANY2MANY)</li>
+<li>TO p-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)</li>
+<li>TO pnf( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)</li>
+<li>TO pserver( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)</li>
+<li>TO vpls-pe( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)</li>
+<li>FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)</li>
+<li>LAG-INTERFACE is DELETED when these are DELETED L-INTERFACE</li>
+<li>LAG-INTERFACE deletion means associated objects of these types are also DELETED:LAG-LINK,LOGICAL-LINK</li></ul>
</section>
@@ -139772,12 +160891,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>LAG links can connect lag-interfaces</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM lag-interface</li>
-<li>FROM logical-link</li></ul>
+<li>FROM lag-interface( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)</li>
+<li>FROM logical-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)</li></ul>
</section>
@@ -139885,12 +161002,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Metadata for license group.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM generic-vnf (is composed of license)</li>
-<li>FROM vce (is composed of license)</li></ul>
+<li>TO generic-vnf( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>TO vce( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)</li></ul>
</section>
@@ -139999,6 +161114,116 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-line-of-business" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/line-of-business"></a>line-of-business:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>describes a line-of-business</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO generic-vnf( line-of-business org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="line-of-business-name">
+ <span class="json-property-name">line-of-business-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Name of the line-of-business (product)</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-lines-of-business" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/lines-of-business"></a>lines-of-business:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Collection of lines-of-business</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="line-of-business">
+ <span class="json-property-name">line-of-business:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/line-of-business">line-of-business</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-logical-link" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/logical-link"></a>logical-link:
@@ -140011,24 +161236,22 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Logical links generally connect l-interfaces but are used to express logical connectivity between two points</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO lag-link (Many2Many)</li>
-<li>TO pnf (Many2Many)</li>
-<li>TO logical-link (One2Many)</li>
-<li>TO generic-vnf (Many2Many)</li>
-<li>TO pserver (Many2Many)</li>
-<li>TO cloud-region (Many2Many)</li>
-<li>TO vpn-binding (Many2Many)</li>
-<li>FROM l-interface</li>
-<li>FROM lag-interface</li>
-<li>FROM p-interface</li>
-<li>FROM service-instance</li>
-<li>FROM virtual-data-center</li>
-<li>FROM vlan</li>
-<li>FROM logical-link</li></ul>
+<li>TO cloud-region( logical-link org.onap.relationships.inventory.LocatedIn cloud-region, MANY2MANY)</li>
+<li>TO generic-vnf( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)</li>
+<li>TO lag-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)</li>
+<li>TO logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, MANY2MANY)</li>
+<li>TO pnf( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)</li>
+<li>TO pserver( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)</li>
+<li>TO vpn-binding( logical-link org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)</li>
+<li>TO virtual-data-center( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)</li>
+<li>FROM lag-interface( lag-interface org.onap.relationships.inventory.Uses logical-link, MANY2MANY)</li>
+<li>FROM l-interface( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)</li>
+<li>FROM p-interface( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)</li>
+<li>FROM vlan( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)</li>
+<li>FROM logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, MANY2MANY)</li></ul>
</section>
@@ -140341,8 +161564,6 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Collection of metadatum (key/value pairs)</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
</section>
@@ -140384,14 +161605,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Key/value pairs</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM image (is composed of metadatum)</li>
-<li>FROM model-ver (is composed of metadatum)</li>
-<li>FROM service-instance (is composed of metadatum)</li>
-<li>FROM connector (is composed of metadatum)</li></ul>
+<li>TO connector( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)</li>
+<li>TO image( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)</li>
+<li>TO service-instance( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)</li>
+<li>TO model-ver( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)</li></ul>
</section>
@@ -140449,14 +161668,15 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Subgraph definition provided by ASDC to describe an inventory asset and its connections related to ASDC models, independent of version</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_4_IN_EDGES_OR_CASCADE</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO model-ver (comprises model, One2Many)</li>
-<li>FROM named-query</li>
-<li>FROM named-query-element</li>
-<li>FROM instance-group</li></ul>
+<li>TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)</li>
+<li>FROM instance-group( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY)</li>
+<li>FROM model-ver( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)</li>
+<li>FROM named-query( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)</li>
+<li>FROM named-query-element( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)</li>
+<li>MODEL cannot be deleted if linked to INSTANCE-GROUP,NAMED-QUERY,NAMED-QUERY-ELEMENT</li>
+<li>MODEL is DELETED when these are DELETED MODEL-VER</li></ul>
</section>
@@ -140659,12 +161879,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>This is how we would capture constraints defining allowed sets of elements.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO constrained-element-set (comprises model-constraint, One2Many)</li>
-<li>FROM model-element (is composed of model-constraint)</li></ul>
+<li>TO model-element( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)</li>
+<li>FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)</li>
+<li>MODEL-CONSTRAINT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET</li></ul>
</section>
@@ -140779,17 +161998,16 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Defines how other models combine to make up a higher-level model.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO model-ver (Many2One)</li>
-<li>TO model-element (comprises model-element, One2Many)</li>
-<li>TO model-constraint (comprises model-element, One2Many)</li>
-<li>TO constrained-element-set (comprises model-element, One2Many)</li>
-<li>FROM model-ver (is composed of model-element)</li>
-<li>FROM element-choice-set (is composed of model-element)</li>
-<li>FROM model-element (is composed of model-element)</li></ul>
+<li>TO element-choice-set( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)</li>
+<li>TO model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)</li>
+<li>TO model-ver( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE)</li>
+<li>TO model-ver( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)</li>
+<li>FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)</li>
+<li>FROM model-constraint( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)</li>
+<li>FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)</li>
+<li>MODEL-ELEMENT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET,MODEL-CONSTRAINT</li></ul>
</section>
@@ -140969,14 +162187,14 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Subgraph definition provided by ASDC to describe a specific version of an inventory asset and its connections related to ASDC models</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_4_IN_EDGES_OR_CASCADE</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO model-element (comprises model-ver, One2Many)</li>
-<li>TO metadatum (comprises model-ver, One2Many)</li>
-<li>FROM model (is composed of model-ver)</li>
-<li>FROM model-element</li></ul>
+<li>TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)</li>
+<li>FROM model-element( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE)</li>
+<li>FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)</li>
+<li>FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)</li>
+<li>MODEL-VER cannot be deleted if linked to MODEL-ELEMENT</li>
+<li>MODEL-VER is DELETED when these are DELETED MODEL-ELEMENT,METADATUM</li></ul>
</section>
@@ -141198,11 +162416,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<div class="panel-body">
<section class="json-schema-description">
- <h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
-<h6 id="related-nodes">Related Nodes</h6>
+ <h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM vlan</li></ul>
+<li>FROM vlan( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)</li></ul>
</section>
@@ -141373,12 +162589,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>TBD</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO model (One2Many)</li>
-<li>TO named-query-element (comprises named-query, One2One)</li></ul>
+<li>TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)</li>
+<li>TO model( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)</li>
+<li>FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)</li>
+<li>NAMED-QUERY is DELETED when these are DELETED NAMED-QUERY-ELEMENT</li></ul>
</section>
@@ -141509,16 +162725,15 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>TBD</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO named-query-element (comprises named-query-element, Many2Many)</li>
-<li>TO model (Many2One)</li>
-<li>TO property-constraint (comprises named-query-element, One2Many)</li>
-<li>TO related-lookup (comprises named-query-element, One2Many)</li>
-<li>FROM named-query (is composed of named-query-element)</li>
-<li>FROM named-query-element (is composed of named-query-element)</li></ul>
+<li>TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)</li>
+<li>TO model( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)</li>
+<li>TO named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)</li>
+<li>FROM property-constraint( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)</li>
+<li>FROM related-lookup( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)</li>
+<li>FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)</li>
+<li>NAMED-QUERY-ELEMENT is DELETED when these are DELETED PROPERTY-CONSTRAINT,RELATED-LOOKUP</li></ul>
</section>
@@ -142130,12 +163345,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<div class="panel-body">
<section class="json-schema-description">
- <h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
-<h6 id="related-nodes">Related Nodes</h6>
+ <h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM l3-network</li>
-<li>FROM allotted-resource</li></ul>
+<li>FROM allotted-resource( allotted-resource org.onap.relationships.inventory.Uses network-policy, ONE2ONE)</li>
+<li>FROM l3-network( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)</li></ul>
</section>
@@ -142226,11 +163439,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Network profile populated by SDN-GP for SNMP</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM generic-vnf</li></ul>
+<li>TO generic-vnf( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)</li></ul>
</section>
@@ -142350,11 +163561,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO l-interface (comprises newvce, Many2Many)</li></ul>
+<li>FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)</li>
+<li>NEWVCE is DELETED when these are DELETED L-INTERFACE</li></ul>
</section>
@@ -142918,13 +164128,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>OAM network, to be deprecated shortly. Do not use for new purposes.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_IF_ANY_IN_EDGES</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO complex (Many2Many)</li>
-<li>TO service-capability (Many2Many)</li>
-<li>FROM cloud-region (is composed of oam-network)</li></ul>
+<li>TO cloud-region( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>TO complex( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)</li>
+<li>TO service-capability( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)</li></ul>
</section>
@@ -143070,6 +164278,182 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-operational-environment" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/operational-environment"></a>operational-environment:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>It is a logical partition of the cloud which allows to have multiple environments in the production AIC.</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)</li>
+<li>FROM operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="operational-environment-id">
+ <span class="json-property-name">operational-environment-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>UUID of an operational environment</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="operational-environment-name">
+ <span class="json-property-name">operational-environment-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Operational Environment name</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="operational-environment-type">
+ <span class="json-property-name">operational-environment-type:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Operational Environment Type.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="operational-environment-status">
+ <span class="json-property-name">operational-environment-status:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Status</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="tenant-context">
+ <span class="json-property-name">tenant-context:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Tenant Context.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="workload-context">
+ <span class="json-property-name">workload-context:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Workload Context.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-operational-environments" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/operational-environments"></a>operational-environments:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>a logical partition of the cloud which allows to have multiple environments in the production AIC.</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="operational-environment">
+ <span class="json-property-name">operational-environment:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/operational-environment">operational-environment</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-overloaded-model" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/overloaded-model"></a>overloaded-model:
@@ -143233,6 +164617,129 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-owning-entities" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/owning-entities"></a>owning-entities:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Collection of owning-entities</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="owning-entity">
+ <span class="json-property-name">owning-entity:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/owning-entity">owning-entity</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-owning-entity" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/owning-entity"></a>owning-entity:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>describes an owning-entity</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo owning-entity, MANY2ONE)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="owning-entity-id">
+ <span class="json-property-name">owning-entity-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>UUID of an owning entity</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="owning-entity-name">
+ <span class="json-property-name">owning-entity-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Owning entity name</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-p-interface" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/p-interface"></a>p-interface:
@@ -143245,17 +164752,17 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Physical interface (e.g., nic)</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO l-interface (comprises p-interface, Many2Many)</li>
-<li>TO physical-link (Many2Many)</li>
-<li>TO logical-link (Many2One)</li>
-<li>FROM lag-interface</li>
-<li>FROM pserver (is composed of p-interface)</li>
-<li>FROM pnf (is composed of p-interface)</li>
-<li>FROM vpls-pe (is composed of p-interface)</li></ul>
+<li>TO logical-link( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)</li>
+<li>TO physical-link( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)</li>
+<li>TO pnf( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)</li>
+<li>TO pserver( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)</li>
+<li>TO vpls-pe( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)</li>
+<li>FROM lag-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)</li>
+<li>FROM l-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)</li>
+<li>P-INTERFACE is DELETED when these are DELETED L-INTERFACE</li>
+<li>P-INTERFACE deletion means associated objects of these types are also DELETED:PHYSICAL-LINK</li></ul>
</section>
@@ -143479,11 +164986,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Collection of physical connections, typically between p-interfaces</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM p-interface</li></ul>
+<li>FROM p-interface( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)</li></ul>
</section>
@@ -143651,6 +165156,116 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-platform" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/platform"></a>platform:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>describes a platform</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO generic-vnf( platform org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="platform-name">
+ <span class="json-property-name">platform-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Name of the platform</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-platforms" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/platforms"></a>platforms:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Collection of platforms</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="platform">
+ <span class="json-property-name">platform:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/platform">platform</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-pnf" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/pnf"></a>pnf:
@@ -143663,17 +165278,16 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>PNF represents a physical network function. typically equipment used in the D1 world.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO p-interface (comprises pnf, Many2Many)</li>
-<li>TO lag-interface (comprises pnf, One2Many)</li>
-<li>TO complex (Many2One)</li>
-<li>TO instance-group (Many2Many)</li>
-<li>TO zone (Many2One)</li>
-<li>FROM logical-link</li>
-<li>FROM service-instance</li></ul>
+<li>TO complex( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>TO instance-group( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>TO zone( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)</li>
+<li>FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)</li>
+<li>FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)</li>
+<li>FROM p-interface( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf pnf, ONE2MANY)</li>
+<li>PNF is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE</li></ul>
</section>
@@ -144061,12 +165675,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Used to capture the network interfaces of this VCE</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO cvlan-tag (comprises port-group, Many2Many)</li>
-<li>FROM vce (is composed of port-group)</li></ul>
+<li>TO vce( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)</li>
+<li>FROM cvlan-tag( cvlan-tag org.onap.relationships.inventory.BelongsTo port-group, MANY2ONE)</li>
+<li>PORT-GROUP is DELETED when these are DELETED CVLAN-TAG</li></ul>
</section>
@@ -144287,6 +165900,116 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-project" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/project"></a>project:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>describes the project</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO service-instance( project org.onap.relationships.inventory.Uses service-instance, ONE2MANY)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="project-name">
+ <span class="json-property-name">project-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Name of the project deploying a service</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-projects" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/projects"></a>projects:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Collection of projects</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="project">
+ <span class="json-property-name">project:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/project">project</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-properties" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/properties"></a>properties:
@@ -144342,11 +166065,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>TBD</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM named-query-element (is composed of property-constraint)</li></ul>
+<li>TO named-query-element( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)</li></ul>
</section>
@@ -144464,20 +166185,21 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Compute host whose hostname must be unique and must exactly match what is sent as a relationship to a vserver.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_4_IN_EDGES_OR_CASCADE</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO complex (Many2One)</li>
-<li>TO cloud-region (Many2One)</li>
-<li>TO availability-zone (Many2One)</li>
-<li>TO lag-interface (comprises pserver, Many2Many)</li>
-<li>TO p-interface (comprises pserver, Many2Many)</li>
-<li>TO zone (Many2One)</li>
-<li>FROM generic-vnf</li>
-<li>FROM group-assignment</li>
-<li>FROM vserver</li>
-<li>FROM logical-link</li></ul>
+<li>TO group-assignment( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)</li>
+<li>TO availability-zone( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)</li>
+<li>TO cloud-region( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)</li>
+<li>TO complex( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>TO zone( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)</li>
+<li>FROM generic-vnf( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)</li>
+<li>FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)</li>
+<li>FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)</li>
+<li>FROM p-interface( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)</li>
+<li>FROM vserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)</li>
+<li>PSERVER cannot be deleted if linked to GENERIC-VNF,LOGICAL-LINK,VSERVER</li>
+<li>PSERVER is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE</li>
+<li>PSERVER cannot be deleted if linked to GROUP-ASSIGNMENT</li></ul>
</section>
@@ -144962,11 +166684,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>TBD</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM named-query-element (is composed of related-lookup)</li></ul>
+<li>TO named-query-element( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)</li></ul>
</section>
@@ -145213,26 +166933,6 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</section> </div>
</dd>
- <dt data-property-name="related-to-property">
- <span class="json-property-name">related-to-property:</span>
- <span class="json-property-type">object[]</span>
- <span class="json-property-range" title="Value limits"></span>
-
- </dt>
- <dd>
-
- <div class="json-inner-schema">
-
- <section class="json-schema-array-items">
- <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/related-to-property">related-to-property</a>
- </span>
- <span class="json-property-range" title="Value limits"></span>
-
- <div class="json-inner-schema">
-
- </div>
- </section> </div>
- </dd>
</dl>
</section>
</div>
@@ -145509,11 +167209,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Openstack route table reference.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM l3-network</li></ul>
+<li>FROM l3-network( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)</li></ul>
</section>
@@ -145634,11 +167332,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Route target information</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM vpn-binding (is composed of route-target)</li></ul>
+<li>TO vpn-binding( route-target org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2ONE)</li></ul>
</section>
@@ -145758,12 +167454,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<div class="panel-body">
<section class="json-schema-description">
- <h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
-<h6 id="related-nodes">Related Nodes</h6>
+ <h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO site-pair (comprises routing-instance, Many2Many)</li>
-<li>FROM site-pair-set (is composed of routing-instance)</li></ul>
+<li>TO site-pair-set( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)</li>
+<li>FROM site-pair( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)</li>
+<li>ROUTING-INSTANCE is DELETED when these are DELETED SITE-PAIR</li></ul>
</section>
@@ -146206,11 +167901,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Openstack segmentation assignment.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM l3-network (is composed of segmentation-assignment)</li></ul>
+<li>TO l3-network( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)</li></ul>
</section>
@@ -146318,8 +168011,6 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Stand-in for service model definitions. Likely to be deprecated in favor of models from ASDC. Does not strictly map to ASDC services.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_IF_ANY_IN_EDGES</p>
</section>
@@ -146464,12 +168155,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Early definition of server/resource pairings, likely to be replaced by models. No new use should be made of this.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_IF_ANY_IN_EDGES</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM availability-zone</li>
-<li>FROM oam-network</li></ul>
+<li>FROM availability-zone( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)</li>
+<li>FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)</li>
+<li>SERVICE-CAPABILITY cannot be deleted if linked to AVAILABILITY-ZONE,OAM-NETWORK</li></ul>
</section>
@@ -146670,26 +168360,26 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Instance of a service</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO cvlan-tag (Many2Many)</li>
-<li>TO pnf (One2Many)</li>
-<li>TO connector (Many2Many)</li>
-<li>TO metadatum (comprises service-instance, Many2Many)</li>
-<li>TO logical-link (Many2Many)</li>
-<li>TO vlan (One2Many)</li>
-<li>TO service-instance (One2Many)</li>
-<li>TO ctag-assignment (One2Many)</li>
-<li>TO instance-group (Many2Many)</li>
-<li>TO allotted-resource (comprises service-instance, Many2Many)</li>
-<li>TO allotted-resource (Many2Many)</li>
-<li>FROM generic-vnf</li>
-<li>FROM l3-network</li>
-<li>FROM service-subscription (is composed of service-instance)</li>
-<li>FROM vce</li>
-<li>FROM service-instance</li></ul>
+<li>TO generic-vnf( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)</li>
+<li>TO l3-network( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)</li>
+<li>TO allotted-resource( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY)</li>
+<li>TO connector( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)</li>
+<li>TO ctag-assignment( service-instance org.onap.relationships.inventory.Uses ctag-assignment, ONE2MANY)</li>
+<li>TO cvlan-tag( service-instance org.onap.relationships.inventory.ComposedOf cvlan-tag, MANY2MANY)</li>
+<li>TO instance-group( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>TO logical-link( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)</li>
+<li>TO pnf( service-instance org.onap.relationships.inventory.ComposedOf pnf, ONE2MANY)</li>
+<li>TO service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)</li>
+<li>TO vlan( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)</li>
+<li>TO service-subscription( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)</li>
+<li>TO vce( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)</li>
+<li>FROM allotted-resource( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)</li>
+<li>FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)</li>
+<li>SERVICE-INSTANCE is DELETED when these are DELETED ALLOTTED-RESOURCE,METADATUM</li>
+<li>SERVICE-INSTANCE deletion means associated objects of these types are also DELETED:LOGICAL-LINK</li></ul>
</section>
@@ -147017,13 +168707,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Object that group service instances.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO service-instance (comprises service-subscription, Many2Many)</li>
-<li>FROM customer (is composed of service-subscription)</li>
-<li>FROM tenant</li></ul>
+<li>TO customer( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)</li>
+<li>TO tenant( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)</li>
+<li>SERVICE-SUBSCRIPTION is DELETED when these are DELETED SERVICE-INSTANCE</li></ul>
</section>
@@ -147203,12 +168892,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<div class="panel-body">
<section class="json-schema-description">
- <h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
-<h6 id="related-nodes">Related Nodes</h6>
+ <h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO class-of-service (comprises site-pair, Many2Many)</li>
-<li>FROM routing-instance (is composed of site-pair)</li></ul>
+<li>TO routing-instance( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)</li>
+<li>FROM class-of-service( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)</li>
+<li>SITE-PAIR is DELETED when these are DELETED CLASS-OF-SERVICE</li></ul>
</section>
@@ -147355,12 +169043,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Set of instances for probes used to measure service level agreements</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO routing-instance (comprises site-pair-set, Many2Many)</li>
-<li>FROM generic-vnf</li></ul>
+<li>TO generic-vnf( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)</li>
+<li>FROM routing-instance( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)</li>
+<li>SITE-PAIR-SET is DELETED when these are DELETED ROUTING-INSTANCE</li></ul>
</section>
@@ -147529,12 +169216,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Openstack snapshot</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM cloud-region (is composed of snapshot)</li>
-<li>FROM vserver</li></ul>
+<li>TO cloud-region( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM vserver( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)</li></ul>
</section>
@@ -147738,6 +169423,117 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-sriov-pf" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/sriov-pf"></a>sriov-pf:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>SR-IOV Physical Function</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO p-interface( sriov-pf org.onap.relationships.inventory.BelongsTo p-interface, ONE2ONE)</li>
+<li>FROM sriov-vf( sriov-vf org.onap.relationships.inventory.Uses sriov-pf, MANY2ONE)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="pf-pci-id">
+ <span class="json-property-name">pf-pci-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Identifier for the sriov-pf</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-sriov-pfs" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/sriov-pfs"></a>sriov-pfs:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Collection of SR-IOV Physical Functions.</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="sriov-pf">
+ <span class="json-property-name">sriov-pf:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/sriov-pf">sriov-pf</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-sriov-vf" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/sriov-vf"></a>sriov-vf:
@@ -147750,11 +169546,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>SR-IOV Virtual Function (not to be confused with virtual network function)</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM l-interface (is composed of sriov-vf)</li></ul>
+<li>TO l-interface( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)</li></ul>
</section>
@@ -148044,13 +169838,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<div class="panel-body">
<section class="json-schema-description">
- <h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_IF_ANY_IN_EDGES</p>
-<h6 id="related-nodes">Related Nodes</h6>
+ <h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM l3-interface-ipv4-address-list</li>
-<li>FROM l3-interface-ipv6-address-list</li>
-<li>FROM l3-network (is composed of subnet)</li></ul>
+<li>TO l3-network( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)</li>
+<li>FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)</li>
+<li>FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)</li>
+<li>SUBNET cannot be deleted if linked to L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST</li></ul>
</section>
@@ -148311,16 +170104,15 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Openstack tenant</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO l3-network (Many2Many)</li>
-<li>TO service-subscription (Many2Many)</li>
-<li>TO vserver (comprises tenant, One2Many)</li>
-<li>FROM cloud-region (is composed of tenant)</li>
-<li>FROM group-assignment</li>
-<li>FROM volume-group</li></ul>
+<li>TO cloud-region( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>TO group-assignment( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)</li>
+<li>TO l3-network( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>TO volume-group( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)</li>
+<li>FROM service-subscription( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)</li>
+<li>FROM vserver( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)</li>
+<li>TENANT cannot be deleted if linked to VSERVER</li></ul>
</section>
@@ -148461,11 +170253,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Represents the specifics of a tunnel cross connect piece of a resource that gets separately allotted</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM allotted-resource (is composed of tunnel-xconnect)</li></ul>
+<li>TO allotted-resource( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)</li></ul>
</section>
@@ -148748,17 +170538,16 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Virtual Customer Edge Router, used specifically for Gamma. This object is deprecated.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO availability-zone (Many2Many)</li>
-<li>TO complex (Many2Many)</li>
-<li>TO port-group (comprises vce, Many2Many)</li>
-<li>TO vserver (Many2Many)</li>
-<li>TO service-instance (Many2Many)</li>
-<li>TO entitlement (comprises vce, One2Many)</li>
-<li>TO license (comprises vce, One2Many)</li></ul>
+<li>TO availability-zone( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)</li>
+<li>TO complex( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)</li>
+<li>TO vserver( vce tosca.relationships.HostedOn vserver, ONE2MANY)</li>
+<li>FROM entitlement( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)</li>
+<li>FROM license( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)</li>
+<li>FROM port-group( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)</li>
+<li>VCE is DELETED when these are DELETED ENTITLEMENT,LICENSE,PORT-GROUP</li></ul>
</section>
@@ -149132,15 +170921,14 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>a deployment unit of VNFCs</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO volume-group (One2One)</li>
-<li>TO l3-network (Many2Many)</li>
-<li>TO vnfc (One2Many)</li>
-<li>FROM vserver</li>
-<li>FROM generic-vnf (is composed of vf-module)</li></ul>
+<li>TO generic-vnf( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>TO l3-network( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)</li>
+<li>TO vnfc( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)</li>
+<li>TO volume-group( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)</li>
+<li>TO vserver( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)</li>
+<li>VF-MODULE cannot be deleted if linked to VNFC</li></ul>
</section>
@@ -149404,11 +171192,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>vig-server contains information about a vig server used for IPSec-configuration. Populated by SDN-C from 1607</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM ipsec-configuration (is composed of vig-server)</li></ul>
+<li>TO ipsec-configuration( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)</li></ul>
</section>
@@ -149524,6 +171310,294 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-vip-ipv4-address-list" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/vip-ipv4-address-list"></a>vip-ipv4-address-list:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>IPv4 Address Range</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO cloud-region( vip-ipv4-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>TO instance-group( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>TO subnet( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)</li>
+<li>FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv4-address-list, MANY2MANY)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="vip-ipv4-address">
+ <span class="json-property-name">vip-ipv4-address:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>IP address</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="vip-ipv4-prefix-length">
+ <span class="json-property-name">vip-ipv4-prefix-length:</span>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Prefix length, 32 for single address</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="vlan-id-inner">
+ <span class="json-property-name">vlan-id-inner:</span>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Inner VLAN tag</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="vlan-id-outer">
+ <span class="json-property-name">vlan-id-outer:</span>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Outer VLAN tag</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="is-floating">
+ <span class="json-property-name">is-floating:</span>
+ <span class="json-property-type">boolean</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Indicator of fixed or floating address</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="neutron-network-id">
+ <span class="json-property-name">neutron-network-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Neutron network id of the interface that address belongs to</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="neutron-subnet-id">
+ <span class="json-property-name">neutron-subnet-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Neutron id of subnet that address belongs to</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-vip-ipv6-address-list" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/vip-ipv6-address-list"></a>vip-ipv6-address-list:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>IPv6 Address Range</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO cloud-region( vip-ipv6-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>TO instance-group( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>TO subnet( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)</li>
+<li>FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv6-address-list, MANY2MANY)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="vip-ipv6-address">
+ <span class="json-property-name">vip-ipv6-address:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>IP address</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="vip-ipv6-prefix-length">
+ <span class="json-property-name">vip-ipv6-prefix-length:</span>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Prefix length, 128 for single address</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="vlan-id-inner">
+ <span class="json-property-name">vlan-id-inner:</span>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Inner VLAN tag</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="vlan-id-outer">
+ <span class="json-property-name">vlan-id-outer:</span>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Outer VLAN tag</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="is-floating">
+ <span class="json-property-name">is-floating:</span>
+ <span class="json-property-type">boolean</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Indicator of fixed or floating address</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="neutron-network-id">
+ <span class="json-property-name">neutron-network-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Neutron network id of the interface that address belongs to</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="neutron-subnet-id">
+ <span class="json-property-name">neutron-subnet-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Neutron id of subnet that address belongs to</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-virtual-data-center" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/virtual-data-center"></a>virtual-data-center:
@@ -149536,13 +171610,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Virtual organization of cloud infrastructure elements in a data center context</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO generic-vnf (Many2Many)</li>
-<li>TO logical-link (Many2Many)</li>
-<li>FROM connector</li></ul>
+<li>FROM connector( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)</li>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)</li>
+<li>FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)</li></ul>
</section>
@@ -149663,17 +171735,17 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Definition of vlan</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO l3-interface-ipv4-address-list (comprises vlan, Many2Many)</li>
-<li>TO l3-interface-ipv6-address-list (comprises vlan, Many2Many)</li>
-<li>TO multicast-configuration (Many2Many)</li>
-<li>TO logical-link (Many2Many)</li>
-<li>FROM l-interface (is composed of vlan)</li>
-<li>FROM service-instance</li>
-<li>FROM allotted-resource</li></ul>
+<li>TO l-interface( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)</li>
+<li>TO logical-link( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)</li>
+<li>TO multicast-configuration( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)</li>
+<li>FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)</li>
+<li>FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)</li>
+<li>FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)</li>
+<li>VLAN is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST</li>
+<li>VLAN deletion means associated objects of these types are also DELETED:LOGICAL-LINK</li></ul>
</section>
@@ -149959,11 +172031,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Image object that pertain to a VNF that doesn't have associated vservers. This is a kludge.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_IF_ANY_IN_EDGES</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM generic-vnf</li></ul>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)</li>
+<li>VNF-IMAGE cannot be deleted if linked to GENERIC-VNF</li></ul>
</section>
@@ -150120,13 +172191,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<div class="panel-body">
<section class="json-schema-description">
- <h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
-<h6 id="related-nodes">Related Nodes</h6>
+ <h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM vserver</li>
-<li>FROM vf-module</li>
-<li>FROM generic-vnf</li></ul>
+<li>TO generic-vnf( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>TO vserver( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)</li>
+<li>FROM vf-module( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)</li></ul>
</section>
@@ -150332,11 +172401,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Ephemeral Block storage volume.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM vserver (is composed of volume)</li></ul>
+<li>FROM vserver (PARENT of volume, vserver tosca.relationships.AttachesTo volume)</li></ul>
</section>
@@ -150416,15 +172483,13 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Persistent block-level storage.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO complex (Many2Many)</li>
-<li>TO tenant (Many2Many)</li>
-<li>FROM cloud-region (is composed of volume-group)</li>
-<li>FROM vf-module</li>
-<li>FROM generic-vnf</li></ul>
+<li>TO cloud-region( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>TO complex( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)</li>
+<li>FROM vf-module( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)</li>
+<li>FROM tenant( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)</li></ul>
</section>
@@ -150647,14 +172712,13 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>VPLS Provider Edge routers.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO complex (Many2Many)</li>
-<li>TO ctag-pool (Many2Many)</li>
-<li>TO p-interface (comprises vpls-pe, Many2Many)</li>
-<li>TO lag-interface (comprises vpls-pe, Many2Many)</li></ul>
+<li>TO complex( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>TO ctag-pool( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)</li>
+<li>FROM lag-interface( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)</li>
+<li>FROM p-interface( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)</li>
+<li>VPLS-PE is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE</li></ul>
</section>
@@ -150849,13 +172913,13 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>VPN binding</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_4_IN_EDGES_OR_CASCADE</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO route-target (comprises vpn-binding, One2Many)</li>
-<li>FROM l3-network</li>
-<li>FROM logical-link</li></ul>
+<li>FROM l3-network( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)</li>
+<li>FROM logical-link( logical-link org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)</li>
+<li>FROM route-target( route-target org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2ONE)</li>
+<li>VPN-BINDING cannot be deleted if linked to L3-NETWORK,LOGICAL-LINK</li>
+<li>VPN-BINDING is DELETED when these are DELETED ROUTE-TARGET</li></ul>
</section>
@@ -151028,21 +173092,21 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Virtual Servers, aka virtual machine or VM.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO flavor (Many2One)</li>
-<li>TO image (Many2One)</li>
-<li>TO l-interface (comprises vserver, Many2Many)</li>
-<li>TO pserver (Many2One)</li>
-<li>TO volume (comprises vserver, Many2Many)</li>
-<li>TO vnfc (Many2Many)</li>
-<li>TO snapshot (One2One)</li>
-<li>TO vf-module (Many2One)</li>
-<li>FROM generic-vnf</li>
-<li>FROM tenant (is composed of vserver)</li>
-<li>FROM vce</li></ul>
+<li>TO tenant( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)</li>
+<li>TO flavor( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)</li>
+<li>TO image( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)</li>
+<li>TO pserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)</li>
+<li>TO snapshot( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)</li>
+<li>TO volume (CHILD of vserver, vserver tosca.relationships.AttachesTo volume, ONE2MANY)</li>
+<li>FROM generic-vnf( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)</li>
+<li>FROM vce( vce tosca.relationships.HostedOn vserver, ONE2MANY)</li>
+<li>FROM l-interface( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)</li>
+<li>FROM vf-module( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)</li>
+<li>FROM vnfc( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)</li>
+<li>VSERVER is DELETED when these are DELETED L-INTERFACE</li>
+<li>VSERVER deletion means associated objects of these types are also DELETED:VOLUME</li></ul>
</section>
@@ -151264,14 +173328,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>A zone is a grouping of assets in a location homing to the same connections into the CBB</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO complex (Many2One)</li>
-<li>FROM cloud-region</li>
-<li>FROM pserver</li>
-<li>FROM pnf</li></ul>
+<li>TO complex( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)</li>
+<li>FROM pnf( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)</li>
+<li>FROM pserver( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)</li></ul>
</section>
diff --git a/aai-schema/src/main/resources/aai_swagger_html/aai_swagger_v11.html b/aai-schema/src/main/resources/aai_swagger_html/aai_swagger_v11.html
index 869ad93d..06cb9d46 100644
--- a/aai-schema/src/main/resources/aai_swagger_html/aai_swagger_v11.html
+++ b/aai-schema/src/main/resources/aai_swagger_html/aai_swagger_v11.html
@@ -1,4 +1,3 @@
-
<!DOCTYPE html>
<html>
<head>
@@ -15,8 +14,11 @@
<body>
<div class="container">
<h1>Active and Available Inventory REST API.</h1>
- <p class="sw-info-version">Version: <span>v11</span></p>
- <p><p>Copyright &copy; 2017 AT&amp;T Intellectual Property. All rights reserved.<br/>
+ <p class="sw-info-version">Version: <span>v12</span></p>
+ <p><p><br/>
+[Differences versus the previous schema version](apidocs/aai_swagger_v11.diff)<br/>
+<br/>
+Copyright &copy; 2017 AT&amp;T Intellectual Property. All rights reserved.<br/>
<br/>
Licensed under the Creative Commons License, Attribution 4.0 Intl. (the &quot;License&quot;); you may not use this documentation except in compliance with the License.<br/>
<br/>
@@ -65,6 +67,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}</a></td>
+ <td><p>update an existing cloud-region</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}</a></td>
<td><p>delete an existing cloud-region</p>
</td>
@@ -85,6 +92,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--availability-zones-availability-zone--availability-zone-name--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/availability-zones/availability-zone/{availability-zone-name}</a></td>
+ <td><p>update an existing availability-zone</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--availability-zones-availability-zone--availability-zone-name--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/availability-zones/availability-zone/{availability-zone-name}</a></td>
<td><p>delete an existing availability-zone</p>
</td>
@@ -115,6 +127,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--dvs-switches-dvs-switch--switch-name--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/dvs-switches/dvs-switch/{switch-name}</a></td>
+ <td><p>update an existing dvs-switch</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--dvs-switches-dvs-switch--switch-name--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/dvs-switches/dvs-switch/{switch-name}</a></td>
<td><p>delete an existing dvs-switch</p>
</td>
@@ -145,6 +162,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--esr-system-info-list-esr-system-info--esr-system-info-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}</a></td>
+ <td><p>update an existing esr-system-info</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--esr-system-info-list-esr-system-info--esr-system-info-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}</a></td>
<td><p>delete an existing esr-system-info</p>
</td>
@@ -175,6 +197,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--flavors-flavor--flavor-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/flavors/flavor/{flavor-id}</a></td>
+ <td><p>update an existing flavor</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--flavors-flavor--flavor-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/flavors/flavor/{flavor-id}</a></td>
<td><p>delete an existing flavor</p>
</td>
@@ -205,6 +232,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--group-assignments-group-assignment--group-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/group-assignments/group-assignment/{group-id}</a></td>
+ <td><p>update an existing group-assignment</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--group-assignments-group-assignment--group-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/group-assignments/group-assignment/{group-id}</a></td>
<td><p>delete an existing group-assignment</p>
</td>
@@ -235,6 +267,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}</a></td>
+ <td><p>update an existing image</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}</a></td>
<td><p>delete an existing image</p>
</td>
@@ -255,6 +292,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--metadata-metadatum--metaname--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}/metadata/metadatum/{metaname}</a></td>
+ <td><p>update an existing metadatum</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--metadata-metadatum--metaname--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}/metadata/metadatum/{metaname}</a></td>
<td><p>delete an existing metadatum</p>
</td>
@@ -285,6 +327,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--oam-networks-oam-network--network-uuid--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/oam-networks/oam-network/{network-uuid}</a></td>
+ <td><p>update an existing oam-network</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--oam-networks-oam-network--network-uuid--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/oam-networks/oam-network/{network-uuid}</a></td>
<td><p>delete an existing oam-network</p>
</td>
@@ -325,6 +372,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--snapshots-snapshot--snapshot-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/snapshots/snapshot/{snapshot-id}</a></td>
+ <td><p>update an existing snapshot</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--snapshots-snapshot--snapshot-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/snapshots/snapshot/{snapshot-id}</a></td>
<td><p>delete an existing snapshot</p>
</td>
@@ -355,6 +407,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}</a></td>
+ <td><p>update an existing tenant</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}</a></td>
<td><p>delete an existing tenant</p>
</td>
@@ -385,6 +442,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}</a></td>
+ <td><p>update an existing vserver</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}</a></td>
<td><p>delete an existing vserver</p>
</td>
@@ -405,6 +467,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -420,6 +487,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -445,6 +517,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -485,6 +562,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -515,6 +597,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -530,6 +617,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -555,6 +647,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -605,6 +702,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--volumes-volume--volume-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/volumes/volume/{volume-id}</a></td>
+ <td><p>update an existing volume</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--volumes-volume--volume-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/volumes/volume/{volume-id}</a></td>
<td><p>delete an existing volume</p>
</td>
@@ -630,6 +732,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--vip-ipv4-address-list--vip-ipv4-address--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/vip-ipv4-address-list/{vip-ipv4-address}</a></td>
+ <td><p>update an existing vip-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--vip-ipv4-address-list--vip-ipv4-address--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/vip-ipv4-address-list/{vip-ipv4-address}</a></td>
<td><p>delete an existing vip-ipv4-address-list</p>
</td>
@@ -655,6 +762,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--vip-ipv6-address-list--vip-ipv6-address--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/vip-ipv6-address-list/{vip-ipv6-address}</a></td>
+ <td><p>update an existing vip-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--vip-ipv6-address-list--vip-ipv6-address--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/vip-ipv6-address-list/{vip-ipv6-address}</a></td>
<td><p>delete an existing vip-ipv6-address-list</p>
</td>
@@ -685,6 +797,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--volume-groups-volume-group--volume-group-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/volume-groups/volume-group/{volume-group-id}</a></td>
+ <td><p>update an existing volume-group</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--volume-groups-volume-group--volume-group-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/volume-groups/volume-group/{volume-group-id}</a></td>
<td><p>delete an existing volume-group</p>
</td>
@@ -715,6 +832,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-complexes-complex--physical-location-id--patch">PATCH /cloud-infrastructure/complexes/complex/{physical-location-id}</a></td>
+ <td><p>update an existing complex</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-complexes-complex--physical-location-id--delete">DELETE /cloud-infrastructure/complexes/complex/{physical-location-id}</a></td>
<td><p>delete an existing complex</p>
</td>
@@ -735,6 +857,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-complexes-complex--physical-location-id--ctag-pools-ctag-pool--target-pe---availability-zone-name--patch">PATCH /cloud-infrastructure/complexes/complex/{physical-location-id}/ctag-pools/ctag-pool/{target-pe}/{availability-zone-name}</a></td>
+ <td><p>update an existing ctag-pool</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-complexes-complex--physical-location-id--ctag-pools-ctag-pool--target-pe---availability-zone-name--delete">DELETE /cloud-infrastructure/complexes/complex/{physical-location-id}/ctag-pools/ctag-pool/{target-pe}/{availability-zone-name}</a></td>
<td><p>delete an existing ctag-pool</p>
</td>
@@ -775,6 +902,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-network-profiles-network-profile--nm-profile-name--patch">PATCH /cloud-infrastructure/network-profiles/network-profile/{nm-profile-name}</a></td>
+ <td><p>update an existing network-profile</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-network-profiles-network-profile--nm-profile-name--delete">DELETE /cloud-infrastructure/network-profiles/network-profile/{nm-profile-name}</a></td>
<td><p>delete an existing network-profile</p>
</td>
@@ -805,6 +937,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}</a></td>
+ <td><p>update an existing pserver</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}</a></td>
<td><p>delete an existing pserver</p>
</td>
@@ -825,6 +962,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}</a></td>
+ <td><p>update an existing lag-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}</a></td>
<td><p>delete an existing lag-interface</p>
</td>
@@ -845,6 +987,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -860,6 +1007,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -885,6 +1037,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -925,6 +1082,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -955,6 +1117,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -970,6 +1137,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -995,6 +1167,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -1045,6 +1222,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}</a></td>
+ <td><p>update an existing p-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}</a></td>
<td><p>delete an existing p-interface</p>
</td>
@@ -1065,6 +1247,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -1080,6 +1267,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -1105,6 +1297,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -1145,6 +1342,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -1175,6 +1377,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -1190,6 +1397,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -1215,6 +1427,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -1265,6 +1482,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--sriov-pfs-sriov-pf--pf-pci-id--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/sriov-pfs/sriov-pf/{pf-pci-id}</a></td>
+ <td><p>update an existing sriov-pf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--sriov-pfs-sriov-pf--pf-pci-id--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/sriov-pfs/sriov-pf/{pf-pci-id}</a></td>
<td><p>delete an existing sriov-pf</p>
</td>
@@ -1305,6 +1527,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--patch">PATCH /cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}</a></td>
+ <td><p>update an existing virtual-data-center</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--delete">DELETE /cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}</a></td>
<td><p>delete an existing virtual-data-center</p>
</td>
@@ -1323,200 +1550,6 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</table>
- <h3 id="tag-ExternalSystem" class="swagger-summary-tag">Tag: ExternalSystem</h3>
-
- <table class="table table-bordered table-condensed swagger--summary">
- <thead>
- <tr>
- <th>Operation</th>
- <th>Description</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td><a href="#operation--external-system-esr-ems-list-get">GET /external-system/esr-ems-list</a></td>
- <td><p>returns esr-ems-list</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-ems-list-esr-ems--ems-id--get">GET /external-system/esr-ems-list/esr-ems/{ems-id}</a></td>
- <td><p>returns esr-ems</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-ems-list-esr-ems--ems-id--put">PUT /external-system/esr-ems-list/esr-ems/{ems-id}</a></td>
- <td><p>create or update an existing esr-ems</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-ems-list-esr-ems--ems-id--delete">DELETE /external-system/esr-ems-list/esr-ems/{ems-id}</a></td>
- <td><p>delete an existing esr-ems</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-ems-list-esr-ems--ems-id--esr-system-info-list-get">GET /external-system/esr-ems-list/esr-ems/{ems-id}/esr-system-info-list</a></td>
- <td><p>returns esr-system-info-list</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-ems-list-esr-ems--ems-id--esr-system-info-list-esr-system-info--esr-system-info-id--get">GET /external-system/esr-ems-list/esr-ems/{ems-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}</a></td>
- <td><p>returns esr-system-info</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-ems-list-esr-ems--ems-id--esr-system-info-list-esr-system-info--esr-system-info-id--put">PUT /external-system/esr-ems-list/esr-ems/{ems-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}</a></td>
- <td><p>create or update an existing esr-system-info</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-ems-list-esr-ems--ems-id--esr-system-info-list-esr-system-info--esr-system-info-id--delete">DELETE /external-system/esr-ems-list/esr-ems/{ems-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}</a></td>
- <td><p>delete an existing esr-system-info</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-ems-list-esr-ems--ems-id--esr-system-info-list-esr-system-info--esr-system-info-id--relationship-list-relationship-put">PUT /external-system/esr-ems-list/esr-ems/{ems-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}/relationship-list/relationship</a></td>
- <td><p>see node definition for valid relationships</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-ems-list-esr-ems--ems-id--esr-system-info-list-esr-system-info--esr-system-info-id--relationship-list-relationship-delete">DELETE /external-system/esr-ems-list/esr-ems/{ems-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}/relationship-list/relationship</a></td>
- <td><p>delete an existing relationship</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-ems-list-esr-ems--ems-id--relationship-list-relationship-put">PUT /external-system/esr-ems-list/esr-ems/{ems-id}/relationship-list/relationship</a></td>
- <td><p>see node definition for valid relationships</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-ems-list-esr-ems--ems-id--relationship-list-relationship-delete">DELETE /external-system/esr-ems-list/esr-ems/{ems-id}/relationship-list/relationship</a></td>
- <td><p>delete an existing relationship</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-thirdparty-sdnc-list-get">GET /external-system/esr-thirdparty-sdnc-list</a></td>
- <td><p>returns esr-thirdparty-sdnc-list</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--get">GET /external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/{thirdparty-sdnc-id}</a></td>
- <td><p>returns esr-thirdparty-sdnc</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--put">PUT /external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/{thirdparty-sdnc-id}</a></td>
- <td><p>create or update an existing esr-thirdparty-sdnc</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--delete">DELETE /external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/{thirdparty-sdnc-id}</a></td>
- <td><p>delete an existing esr-thirdparty-sdnc</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--esr-system-info-list-get">GET /external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/{thirdparty-sdnc-id}/esr-system-info-list</a></td>
- <td><p>returns esr-system-info-list</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--esr-system-info-list-esr-system-info--esr-system-info-id--get">GET /external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/{thirdparty-sdnc-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}</a></td>
- <td><p>returns esr-system-info</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--esr-system-info-list-esr-system-info--esr-system-info-id--put">PUT /external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/{thirdparty-sdnc-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}</a></td>
- <td><p>create or update an existing esr-system-info</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--esr-system-info-list-esr-system-info--esr-system-info-id--delete">DELETE /external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/{thirdparty-sdnc-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}</a></td>
- <td><p>delete an existing esr-system-info</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--esr-system-info-list-esr-system-info--esr-system-info-id--relationship-list-relationship-put">PUT /external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/{thirdparty-sdnc-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}/relationship-list/relationship</a></td>
- <td><p>see node definition for valid relationships</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--esr-system-info-list-esr-system-info--esr-system-info-id--relationship-list-relationship-delete">DELETE /external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/{thirdparty-sdnc-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}/relationship-list/relationship</a></td>
- <td><p>delete an existing relationship</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--relationship-list-relationship-put">PUT /external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/{thirdparty-sdnc-id}/relationship-list/relationship</a></td>
- <td><p>see node definition for valid relationships</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--relationship-list-relationship-delete">DELETE /external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/{thirdparty-sdnc-id}/relationship-list/relationship</a></td>
- <td><p>delete an existing relationship</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-vnfm-list-get">GET /external-system/esr-vnfm-list</a></td>
- <td><p>returns esr-vnfm-list</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--get">GET /external-system/esr-vnfm-list/esr-vnfm/{vnfm-id}</a></td>
- <td><p>returns esr-vnfm</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--put">PUT /external-system/esr-vnfm-list/esr-vnfm/{vnfm-id}</a></td>
- <td><p>create or update an existing esr-vnfm</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--delete">DELETE /external-system/esr-vnfm-list/esr-vnfm/{vnfm-id}</a></td>
- <td><p>delete an existing esr-vnfm</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--esr-system-info-list-get">GET /external-system/esr-vnfm-list/esr-vnfm/{vnfm-id}/esr-system-info-list</a></td>
- <td><p>returns esr-system-info-list</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--esr-system-info-list-esr-system-info--esr-system-info-id--get">GET /external-system/esr-vnfm-list/esr-vnfm/{vnfm-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}</a></td>
- <td><p>returns esr-system-info</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--esr-system-info-list-esr-system-info--esr-system-info-id--put">PUT /external-system/esr-vnfm-list/esr-vnfm/{vnfm-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}</a></td>
- <td><p>create or update an existing esr-system-info</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--esr-system-info-list-esr-system-info--esr-system-info-id--delete">DELETE /external-system/esr-vnfm-list/esr-vnfm/{vnfm-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}</a></td>
- <td><p>delete an existing esr-system-info</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--esr-system-info-list-esr-system-info--esr-system-info-id--relationship-list-relationship-put">PUT /external-system/esr-vnfm-list/esr-vnfm/{vnfm-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}/relationship-list/relationship</a></td>
- <td><p>see node definition for valid relationships</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--esr-system-info-list-esr-system-info--esr-system-info-id--relationship-list-relationship-delete">DELETE /external-system/esr-vnfm-list/esr-vnfm/{vnfm-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}/relationship-list/relationship</a></td>
- <td><p>delete an existing relationship</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--relationship-list-relationship-put">PUT /external-system/esr-vnfm-list/esr-vnfm/{vnfm-id}/relationship-list/relationship</a></td>
- <td><p>see node definition for valid relationships</p>
- </td>
- </tr>
- <tr>
- <td><a href="#operation--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--relationship-list-relationship-delete">DELETE /external-system/esr-vnfm-list/esr-vnfm/{vnfm-id}/relationship-list/relationship</a></td>
- <td><p>delete an existing relationship</p>
- </td>
- </tr>
- </tbody>
- </table>
-
-
<h3 id="tag-Business" class="swagger-summary-tag">Tag: Business</h3>
<table class="table table-bordered table-condensed swagger--summary">
@@ -1543,6 +1576,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-connectors-connector--resource-instance-id--patch">PATCH /business/connectors/connector/{resource-instance-id}</a></td>
+ <td><p>update an existing connector</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-connectors-connector--resource-instance-id--delete">DELETE /business/connectors/connector/{resource-instance-id}</a></td>
<td><p>delete an existing connector</p>
</td>
@@ -1563,6 +1601,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-connectors-connector--resource-instance-id--metadata-metadatum--metaname--patch">PATCH /business/connectors/connector/{resource-instance-id}/metadata/metadatum/{metaname}</a></td>
+ <td><p>update an existing metadatum</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-connectors-connector--resource-instance-id--metadata-metadatum--metaname--delete">DELETE /business/connectors/connector/{resource-instance-id}/metadata/metadatum/{metaname}</a></td>
<td><p>delete an existing metadatum</p>
</td>
@@ -1593,6 +1636,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-customers-customer--global-customer-id--patch">PATCH /business/customers/customer/{global-customer-id}</a></td>
+ <td><p>update an existing customer</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-customers-customer--global-customer-id--delete">DELETE /business/customers/customer/{global-customer-id}</a></td>
<td><p>delete an existing customer</p>
</td>
@@ -1623,6 +1671,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--patch">PATCH /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}</a></td>
+ <td><p>update an existing service-subscription</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--delete">DELETE /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}</a></td>
<td><p>delete an existing service-subscription</p>
</td>
@@ -1653,6 +1706,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--patch">PATCH /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}</a></td>
+ <td><p>update an existing service-instance</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--delete">DELETE /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}</a></td>
<td><p>delete an existing service-instance</p>
</td>
@@ -1673,6 +1731,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--patch">PATCH /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/allotted-resources/allotted-resource/{id}</a></td>
+ <td><p>update an existing allotted-resource</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--delete">DELETE /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/allotted-resources/allotted-resource/{id}</a></td>
<td><p>delete an existing allotted-resource</p>
</td>
@@ -1703,6 +1766,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--tunnel-xconnects-tunnel-xconnect--id--patch">PATCH /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/allotted-resources/allotted-resource/{id}/tunnel-xconnects/tunnel-xconnect/{id}</a></td>
+ <td><p>update an existing tunnel-xconnect</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--tunnel-xconnects-tunnel-xconnect--id--delete">DELETE /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/allotted-resources/allotted-resource/{id}/tunnel-xconnects/tunnel-xconnect/{id}</a></td>
<td><p>delete an existing tunnel-xconnect</p>
</td>
@@ -1733,6 +1801,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--metadata-metadatum--metaname--patch">PATCH /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/metadata/metadatum/{metaname}</a></td>
+ <td><p>update an existing metadatum</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--metadata-metadatum--metaname--delete">DELETE /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/metadata/metadatum/{metaname}</a></td>
<td><p>delete an existing metadatum</p>
</td>
@@ -1763,6 +1836,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-lines-of-business-line-of-business--line-of-business-name--patch">PATCH /business/lines-of-business/line-of-business/{line-of-business-name}</a></td>
+ <td><p>update an existing line-of-business</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-lines-of-business-line-of-business--line-of-business-name--delete">DELETE /business/lines-of-business/line-of-business/{line-of-business-name}</a></td>
<td><p>delete an existing line-of-business</p>
</td>
@@ -1793,6 +1871,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-owning-entities-owning-entity--owning-entity-id--patch">PATCH /business/owning-entities/owning-entity/{owning-entity-id}</a></td>
+ <td><p>update an existing owning-entity</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-owning-entities-owning-entity--owning-entity-id--delete">DELETE /business/owning-entities/owning-entity/{owning-entity-id}</a></td>
<td><p>delete an existing owning-entity</p>
</td>
@@ -1823,6 +1906,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-platforms-platform--platform-name--patch">PATCH /business/platforms/platform/{platform-name}</a></td>
+ <td><p>update an existing platform</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-platforms-platform--platform-name--delete">DELETE /business/platforms/platform/{platform-name}</a></td>
<td><p>delete an existing platform</p>
</td>
@@ -1853,6 +1941,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-projects-project--project-name--patch">PATCH /business/projects/project/{project-name}</a></td>
+ <td><p>update an existing project</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-projects-project--project-name--delete">DELETE /business/projects/project/{project-name}</a></td>
<td><p>delete an existing project</p>
</td>
@@ -1897,6 +1990,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--patch">PATCH /service-design-and-creation/models/model/{model-invariant-id}</a></td>
+ <td><p>update an existing model</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--delete">DELETE /service-design-and-creation/models/model/{model-invariant-id}</a></td>
<td><p>delete an existing model</p>
</td>
@@ -1917,6 +2015,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--patch">PATCH /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}</a></td>
+ <td><p>update an existing model-ver</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--delete">DELETE /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}</a></td>
<td><p>delete an existing model-ver</p>
</td>
@@ -1937,6 +2040,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--metadata-metadatum--metaname--patch">PATCH /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/metadata/metadatum/{metaname}</a></td>
+ <td><p>update an existing metadatum</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--metadata-metadatum--metaname--delete">DELETE /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/metadata/metadatum/{metaname}</a></td>
<td><p>delete an existing metadatum</p>
</td>
@@ -1957,6 +2065,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--patch">PATCH /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}</a></td>
+ <td><p>update an existing model-element</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--delete">DELETE /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}</a></td>
<td><p>delete an existing model-element</p>
</td>
@@ -1977,6 +2090,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--patch">PATCH /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}</a></td>
+ <td><p>update an existing model-constraint</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--delete">DELETE /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}</a></td>
<td><p>delete an existing model-constraint</p>
</td>
@@ -1997,6 +2115,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--patch">PATCH /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}</a></td>
+ <td><p>update an existing constrained-element-set</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--delete">DELETE /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}</a></td>
<td><p>delete an existing constrained-element-set</p>
</td>
@@ -2017,6 +2140,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--element-choice-sets-element-choice-set--element-choice-set-uuid--patch">PATCH /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}/element-choice-sets/element-choice-set/{element-choice-set-uuid}</a></td>
+ <td><p>update an existing element-choice-set</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--element-choice-sets-element-choice-set--element-choice-set-uuid--delete">DELETE /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}/element-choice-sets/element-choice-set/{element-choice-set-uuid}</a></td>
<td><p>delete an existing element-choice-set</p>
</td>
@@ -2087,6 +2215,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--patch">PATCH /service-design-and-creation/named-queries/named-query/{named-query-uuid}</a></td>
+ <td><p>update an existing named-query</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--delete">DELETE /service-design-and-creation/named-queries/named-query/{named-query-uuid}</a></td>
<td><p>delete an existing named-query</p>
</td>
@@ -2107,6 +2240,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--patch">PATCH /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}</a></td>
+ <td><p>update an existing named-query-element</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--delete">DELETE /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}</a></td>
<td><p>delete an existing named-query-element</p>
</td>
@@ -2127,6 +2265,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--property-constraints-property-constraint--property-constraint-uuid--patch">PATCH /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/property-constraints/property-constraint/{property-constraint-uuid}</a></td>
+ <td><p>update an existing property-constraint</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--property-constraints-property-constraint--property-constraint-uuid--delete">DELETE /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/property-constraints/property-constraint/{property-constraint-uuid}</a></td>
<td><p>delete an existing property-constraint</p>
</td>
@@ -2147,6 +2290,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--related-lookups-related-lookup--related-lookup-uuid--patch">PATCH /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/related-lookups/related-lookup/{related-lookup-uuid}</a></td>
+ <td><p>update an existing related-lookup</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--related-lookups-related-lookup--related-lookup-uuid--delete">DELETE /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/related-lookups/related-lookup/{related-lookup-uuid}</a></td>
<td><p>delete an existing related-lookup</p>
</td>
@@ -2197,6 +2345,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-service-capabilities-service-capability--service-type---vnf-type--patch">PATCH /service-design-and-creation/service-capabilities/service-capability/{service-type}/{vnf-type}</a></td>
+ <td><p>update an existing service-capability</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-service-capabilities-service-capability--service-type---vnf-type--delete">DELETE /service-design-and-creation/service-capabilities/service-capability/{service-type}/{vnf-type}</a></td>
<td><p>delete an existing service-capability</p>
</td>
@@ -2227,6 +2380,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-services-service--service-id--patch">PATCH /service-design-and-creation/services/service/{service-id}</a></td>
+ <td><p>update an existing service</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-services-service--service-id--delete">DELETE /service-design-and-creation/services/service/{service-id}</a></td>
<td><p>delete an existing service</p>
</td>
@@ -2257,6 +2415,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-vnf-images-vnf-image--vnf-image-uuid--patch">PATCH /service-design-and-creation/vnf-images/vnf-image/{vnf-image-uuid}</a></td>
+ <td><p>update an existing vnf-image</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-vnf-images-vnf-image--vnf-image-uuid--delete">DELETE /service-design-and-creation/vnf-images/vnf-image/{vnf-image-uuid}</a></td>
<td><p>delete an existing vnf-image</p>
</td>
@@ -2286,6 +2449,66 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</thead>
<tbody>
<tr>
+ <td><a href="#operation--network-configurations-get">GET /network/configurations</a></td>
+ <td><p>returns configurations</p>
+ </td>
+ </tr>
+ <tr>
+ <td><a href="#operation--network-configurations-configuration--configuration-id--get">GET /network/configurations/configuration/{configuration-id}</a></td>
+ <td><p>returns configuration</p>
+ </td>
+ </tr>
+ <tr>
+ <td><a href="#operation--network-configurations-configuration--configuration-id--put">PUT /network/configurations/configuration/{configuration-id}</a></td>
+ <td><p>create or update an existing configuration</p>
+ </td>
+ </tr>
+ <tr>
+ <td><a href="#operation--network-configurations-configuration--configuration-id--patch">PATCH /network/configurations/configuration/{configuration-id}</a></td>
+ <td><p>update an existing configuration</p>
+ </td>
+ </tr>
+ <tr>
+ <td><a href="#operation--network-configurations-configuration--configuration-id--delete">DELETE /network/configurations/configuration/{configuration-id}</a></td>
+ <td><p>delete an existing configuration</p>
+ </td>
+ </tr>
+ <tr>
+ <td><a href="#operation--network-configurations-configuration--configuration-id--metadata-get">GET /network/configurations/configuration/{configuration-id}/metadata</a></td>
+ <td><p>returns metadata</p>
+ </td>
+ </tr>
+ <tr>
+ <td><a href="#operation--network-configurations-configuration--configuration-id--metadata-metadatum--metaname--get">GET /network/configurations/configuration/{configuration-id}/metadata/metadatum/{metaname}</a></td>
+ <td><p>returns metadatum</p>
+ </td>
+ </tr>
+ <tr>
+ <td><a href="#operation--network-configurations-configuration--configuration-id--metadata-metadatum--metaname--put">PUT /network/configurations/configuration/{configuration-id}/metadata/metadatum/{metaname}</a></td>
+ <td><p>create or update an existing metadatum</p>
+ </td>
+ </tr>
+ <tr>
+ <td><a href="#operation--network-configurations-configuration--configuration-id--metadata-metadatum--metaname--patch">PATCH /network/configurations/configuration/{configuration-id}/metadata/metadatum/{metaname}</a></td>
+ <td><p>update an existing metadatum</p>
+ </td>
+ </tr>
+ <tr>
+ <td><a href="#operation--network-configurations-configuration--configuration-id--metadata-metadatum--metaname--delete">DELETE /network/configurations/configuration/{configuration-id}/metadata/metadatum/{metaname}</a></td>
+ <td><p>delete an existing metadatum</p>
+ </td>
+ </tr>
+ <tr>
+ <td><a href="#operation--network-configurations-configuration--configuration-id--relationship-list-relationship-put">PUT /network/configurations/configuration/{configuration-id}/relationship-list/relationship</a></td>
+ <td><p>see node definition for valid relationships</p>
+ </td>
+ </tr>
+ <tr>
+ <td><a href="#operation--network-configurations-configuration--configuration-id--relationship-list-relationship-delete">DELETE /network/configurations/configuration/{configuration-id}/relationship-list/relationship</a></td>
+ <td><p>delete an existing relationship</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-get">GET /network/generic-vnfs</a></td>
<td><p>returns generic-vnfs</p>
</td>
@@ -2301,6 +2524,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}</a></td>
+ <td><p>update an existing generic-vnf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}</a></td>
<td><p>delete an existing generic-vnf</p>
</td>
@@ -2321,6 +2549,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/entitlements/entitlement/{group-uuid}/{resource-uuid}</a></td>
+ <td><p>update an existing entitlement</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/entitlements/entitlement/{group-uuid}/{resource-uuid}</a></td>
<td><p>delete an existing entitlement</p>
</td>
@@ -2351,6 +2584,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -2366,6 +2604,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -2391,6 +2634,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -2431,6 +2679,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -2461,6 +2714,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -2476,6 +2734,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -2501,6 +2764,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -2541,6 +2809,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}</a></td>
+ <td><p>update an existing lag-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}</a></td>
<td><p>delete an existing lag-interface</p>
</td>
@@ -2561,6 +2834,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -2576,6 +2854,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -2601,6 +2884,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -2641,6 +2929,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -2671,6 +2964,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -2686,6 +2984,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -2711,6 +3014,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -2761,6 +3069,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--licenses-license--group-uuid---resource-uuid--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/licenses/license/{group-uuid}/{resource-uuid}</a></td>
+ <td><p>update an existing license</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--licenses-license--group-uuid---resource-uuid--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/licenses/license/{group-uuid}/{resource-uuid}</a></td>
<td><p>delete an existing license</p>
</td>
@@ -2801,6 +3114,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--vf-modules-vf-module--vf-module-id--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/vf-modules/vf-module/{vf-module-id}</a></td>
+ <td><p>update an existing vf-module</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--vf-modules-vf-module--vf-module-id--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/vf-modules/vf-module/{vf-module-id}</a></td>
<td><p>delete an existing vf-module</p>
</td>
@@ -2831,6 +3149,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-instance-groups-instance-group--id--patch">PATCH /network/instance-groups/instance-group/{id}</a></td>
+ <td><p>update an existing instance-group</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-instance-groups-instance-group--id--delete">DELETE /network/instance-groups/instance-group/{id}</a></td>
<td><p>delete an existing instance-group</p>
</td>
@@ -2861,6 +3184,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--patch">PATCH /network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}</a></td>
+ <td><p>update an existing ipsec-configuration</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--delete">DELETE /network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}</a></td>
<td><p>delete an existing ipsec-configuration</p>
</td>
@@ -2891,6 +3219,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--vig-servers-vig-server--vig-address-type--patch">PATCH /network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}/vig-servers/vig-server/{vig-address-type}</a></td>
+ <td><p>update an existing vig-server</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--vig-servers-vig-server--vig-address-type--delete">DELETE /network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}/vig-servers/vig-server/{vig-address-type}</a></td>
<td><p>delete an existing vig-server</p>
</td>
@@ -2921,6 +3254,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-l3-networks-l3-network--network-id--patch">PATCH /network/l3-networks/l3-network/{network-id}</a></td>
+ <td><p>update an existing l3-network</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-l3-networks-l3-network--network-id--delete">DELETE /network/l3-networks/l3-network/{network-id}</a></td>
<td><p>delete an existing l3-network</p>
</td>
@@ -2941,6 +3279,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-l3-networks-l3-network--network-id--ctag-assignments-ctag-assignment--vlan-id-inner--patch">PATCH /network/l3-networks/l3-network/{network-id}/ctag-assignments/ctag-assignment/{vlan-id-inner}</a></td>
+ <td><p>update an existing ctag-assignment</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-l3-networks-l3-network--network-id--ctag-assignments-ctag-assignment--vlan-id-inner--delete">DELETE /network/l3-networks/l3-network/{network-id}/ctag-assignments/ctag-assignment/{vlan-id-inner}</a></td>
<td><p>delete an existing ctag-assignment</p>
</td>
@@ -2981,6 +3324,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-l3-networks-l3-network--network-id--segmentation-assignments-segmentation-assignment--segmentation-id--patch">PATCH /network/l3-networks/l3-network/{network-id}/segmentation-assignments/segmentation-assignment/{segmentation-id}</a></td>
+ <td><p>update an existing segmentation-assignment</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-l3-networks-l3-network--network-id--segmentation-assignments-segmentation-assignment--segmentation-id--delete">DELETE /network/l3-networks/l3-network/{network-id}/segmentation-assignments/segmentation-assignment/{segmentation-id}</a></td>
<td><p>delete an existing segmentation-assignment</p>
</td>
@@ -3011,6 +3359,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-l3-networks-l3-network--network-id--subnets-subnet--subnet-id--patch">PATCH /network/l3-networks/l3-network/{network-id}/subnets/subnet/{subnet-id}</a></td>
+ <td><p>update an existing subnet</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-l3-networks-l3-network--network-id--subnets-subnet--subnet-id--delete">DELETE /network/l3-networks/l3-network/{network-id}/subnets/subnet/{subnet-id}</a></td>
<td><p>delete an existing subnet</p>
</td>
@@ -3031,6 +3384,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-l3-networks-l3-network--network-id--subnets-subnet--subnet-id--host-routes-host-route--host-route-id--patch">PATCH /network/l3-networks/l3-network/{network-id}/subnets/subnet/{subnet-id}/host-routes/host-route/{host-route-id}</a></td>
+ <td><p>update an existing host-route</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-l3-networks-l3-network--network-id--subnets-subnet--subnet-id--host-routes-host-route--host-route-id--delete">DELETE /network/l3-networks/l3-network/{network-id}/subnets/subnet/{subnet-id}/host-routes/host-route/{host-route-id}</a></td>
<td><p>delete an existing host-route</p>
</td>
@@ -3071,6 +3429,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-lag-links-lag-link--link-name--patch">PATCH /network/lag-links/lag-link/{link-name}</a></td>
+ <td><p>update an existing lag-link</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-lag-links-lag-link--link-name--delete">DELETE /network/lag-links/lag-link/{link-name}</a></td>
<td><p>delete an existing lag-link</p>
</td>
@@ -3101,6 +3464,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-logical-links-logical-link--link-name--patch">PATCH /network/logical-links/logical-link/{link-name}</a></td>
+ <td><p>update an existing logical-link</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-logical-links-logical-link--link-name--delete">DELETE /network/logical-links/logical-link/{link-name}</a></td>
<td><p>delete an existing logical-link</p>
</td>
@@ -3131,6 +3499,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-multicast-configurations-multicast-configuration--multicast-configuration-id--patch">PATCH /network/multicast-configurations/multicast-configuration/{multicast-configuration-id}</a></td>
+ <td><p>update an existing multicast-configuration</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-multicast-configurations-multicast-configuration--multicast-configuration-id--delete">DELETE /network/multicast-configurations/multicast-configuration/{multicast-configuration-id}</a></td>
<td><p>delete an existing multicast-configuration</p>
</td>
@@ -3161,6 +3534,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-network-policies-network-policy--network-policy-id--patch">PATCH /network/network-policies/network-policy/{network-policy-id}</a></td>
+ <td><p>update an existing network-policy</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-network-policies-network-policy--network-policy-id--delete">DELETE /network/network-policies/network-policy/{network-policy-id}</a></td>
<td><p>delete an existing network-policy</p>
</td>
@@ -3191,6 +3569,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--patch">PATCH /network/newvces/newvce/{vnf-id2}</a></td>
+ <td><p>update an existing newvce</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--delete">DELETE /network/newvces/newvce/{vnf-id2}</a></td>
<td><p>delete an existing newvce</p>
</td>
@@ -3211,6 +3594,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--patch">PATCH /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--delete">DELETE /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -3226,6 +3614,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -3251,6 +3644,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -3291,6 +3689,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -3321,6 +3724,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -3336,6 +3744,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -3361,6 +3774,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -3411,6 +3829,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-physical-links-physical-link--link-name--patch">PATCH /network/physical-links/physical-link/{link-name}</a></td>
+ <td><p>update an existing physical-link</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-physical-links-physical-link--link-name--delete">DELETE /network/physical-links/physical-link/{link-name}</a></td>
<td><p>delete an existing physical-link</p>
</td>
@@ -3441,6 +3864,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--patch">PATCH /network/pnfs/pnf/{pnf-name}</a></td>
+ <td><p>update an existing pnf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--delete">DELETE /network/pnfs/pnf/{pnf-name}</a></td>
<td><p>delete an existing pnf</p>
</td>
@@ -3461,6 +3889,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}</a></td>
+ <td><p>update an existing lag-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}</a></td>
<td><p>delete an existing lag-interface</p>
</td>
@@ -3481,6 +3914,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -3496,6 +3934,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -3521,6 +3964,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -3561,6 +4009,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -3591,6 +4044,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -3606,6 +4064,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -3631,6 +4094,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -3681,6 +4149,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}</a></td>
+ <td><p>update an existing p-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}</a></td>
<td><p>delete an existing p-interface</p>
</td>
@@ -3701,6 +4174,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -3716,6 +4194,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -3741,6 +4224,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -3781,6 +4269,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -3811,6 +4304,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -3826,6 +4324,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -3851,6 +4354,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -3901,6 +4409,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--sriov-pfs-sriov-pf--pf-pci-id--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/sriov-pfs/sriov-pf/{pf-pci-id}</a></td>
+ <td><p>update an existing sriov-pf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--sriov-pfs-sriov-pf--pf-pci-id--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/sriov-pfs/sriov-pf/{pf-pci-id}</a></td>
<td><p>delete an existing sriov-pf</p>
</td>
@@ -3941,6 +4454,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-route-table-references-route-table-reference--route-table-reference-id--patch">PATCH /network/route-table-references/route-table-reference/{route-table-reference-id}</a></td>
+ <td><p>update an existing route-table-reference</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-route-table-references-route-table-reference--route-table-reference-id--delete">DELETE /network/route-table-references/route-table-reference/{route-table-reference-id}</a></td>
<td><p>delete an existing route-table-reference</p>
</td>
@@ -3971,6 +4489,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--patch">PATCH /network/site-pair-sets/site-pair-set/{site-pair-set-id}</a></td>
+ <td><p>update an existing site-pair-set</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--delete">DELETE /network/site-pair-sets/site-pair-set/{site-pair-set-id}</a></td>
<td><p>delete an existing site-pair-set</p>
</td>
@@ -4001,6 +4524,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--patch">PATCH /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}</a></td>
+ <td><p>update an existing routing-instance</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--delete">DELETE /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}</a></td>
<td><p>delete an existing routing-instance</p>
</td>
@@ -4031,6 +4559,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--patch">PATCH /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}</a></td>
+ <td><p>update an existing site-pair</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--delete">DELETE /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}</a></td>
<td><p>delete an existing site-pair</p>
</td>
@@ -4051,6 +4584,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--classes-of-service-class-of-service--cos--patch">PATCH /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}/classes-of-service/class-of-service/{cos}</a></td>
+ <td><p>update an existing class-of-service</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--classes-of-service-class-of-service--cos--delete">DELETE /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}/classes-of-service/class-of-service/{cos}</a></td>
<td><p>delete an existing class-of-service</p>
</td>
@@ -4091,6 +4629,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vces-vce--vnf-id--patch">PATCH /network/vces/vce/{vnf-id}</a></td>
+ <td><p>update an existing vce</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vces-vce--vnf-id--delete">DELETE /network/vces/vce/{vnf-id}</a></td>
<td><p>delete an existing vce</p>
</td>
@@ -4111,6 +4654,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vces-vce--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--patch">PATCH /network/vces/vce/{vnf-id}/entitlements/entitlement/{group-uuid}/{resource-uuid}</a></td>
+ <td><p>update an existing entitlement</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vces-vce--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--delete">DELETE /network/vces/vce/{vnf-id}/entitlements/entitlement/{group-uuid}/{resource-uuid}</a></td>
<td><p>delete an existing entitlement</p>
</td>
@@ -4141,6 +4689,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vces-vce--vnf-id--licenses-license--group-uuid---resource-uuid--patch">PATCH /network/vces/vce/{vnf-id}/licenses/license/{group-uuid}/{resource-uuid}</a></td>
+ <td><p>update an existing license</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vces-vce--vnf-id--licenses-license--group-uuid---resource-uuid--delete">DELETE /network/vces/vce/{vnf-id}/licenses/license/{group-uuid}/{resource-uuid}</a></td>
<td><p>delete an existing license</p>
</td>
@@ -4171,6 +4724,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--patch">PATCH /network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}</a></td>
+ <td><p>update an existing port-group</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--delete">DELETE /network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}</a></td>
<td><p>delete an existing port-group</p>
</td>
@@ -4191,6 +4749,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--cvlan-tags-cvlan-tag-entry--cvlan-tag--patch">PATCH /network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}/cvlan-tags/cvlan-tag-entry/{cvlan-tag}</a></td>
+ <td><p>update an existing cvlan-tag-entry</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--cvlan-tags-cvlan-tag-entry--cvlan-tag--delete">DELETE /network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}/cvlan-tags/cvlan-tag-entry/{cvlan-tag}</a></td>
<td><p>delete an existing cvlan-tag-entry</p>
</td>
@@ -4241,6 +4804,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vnfcs-vnfc--vnfc-name--patch">PATCH /network/vnfcs/vnfc/{vnfc-name}</a></td>
+ <td><p>update an existing vnfc</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vnfcs-vnfc--vnfc-name--delete">DELETE /network/vnfcs/vnfc/{vnfc-name}</a></td>
<td><p>delete an existing vnfc</p>
</td>
@@ -4256,6 +4824,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vnfcs-vnfc--vnfc-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/vnfcs/vnfc/{vnfc-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vnfcs-vnfc--vnfc-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/vnfcs/vnfc/{vnfc-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -4281,6 +4854,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vnfcs-vnfc--vnfc-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/vnfcs/vnfc/{vnfc-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vnfcs-vnfc--vnfc-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/vnfcs/vnfc/{vnfc-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -4321,6 +4899,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}</a></td>
+ <td><p>update an existing vpls-pe</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}</a></td>
<td><p>delete an existing vpls-pe</p>
</td>
@@ -4341,6 +4924,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}</a></td>
+ <td><p>update an existing lag-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}</a></td>
<td><p>delete an existing lag-interface</p>
</td>
@@ -4361,6 +4949,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -4376,6 +4969,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -4401,6 +4999,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -4441,6 +5044,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -4471,6 +5079,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -4486,6 +5099,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -4511,6 +5129,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -4561,6 +5184,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}</a></td>
+ <td><p>update an existing p-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}</a></td>
<td><p>delete an existing p-interface</p>
</td>
@@ -4581,6 +5209,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -4596,6 +5229,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -4621,6 +5259,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -4661,6 +5304,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -4691,6 +5339,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -4706,6 +5359,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -4731,6 +5389,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -4781,6 +5444,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--sriov-pfs-sriov-pf--pf-pci-id--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/sriov-pfs/sriov-pf/{pf-pci-id}</a></td>
+ <td><p>update an existing sriov-pf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--sriov-pfs-sriov-pf--pf-pci-id--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/sriov-pfs/sriov-pf/{pf-pci-id}</a></td>
<td><p>delete an existing sriov-pf</p>
</td>
@@ -4821,6 +5489,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpn-bindings-vpn-binding--vpn-id--patch">PATCH /network/vpn-bindings/vpn-binding/{vpn-id}</a></td>
+ <td><p>update an existing vpn-binding</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpn-bindings-vpn-binding--vpn-id--delete">DELETE /network/vpn-bindings/vpn-binding/{vpn-id}</a></td>
<td><p>delete an existing vpn-binding</p>
</td>
@@ -4851,6 +5524,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpn-bindings-vpn-binding--vpn-id--route-targets-route-target--global-route-target---route-target-role--patch">PATCH /network/vpn-bindings/vpn-binding/{vpn-id}/route-targets/route-target/{global-route-target}/{route-target-role}</a></td>
+ <td><p>update an existing route-target</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpn-bindings-vpn-binding--vpn-id--route-targets-route-target--global-route-target---route-target-role--delete">DELETE /network/vpn-bindings/vpn-binding/{vpn-id}/route-targets/route-target/{global-route-target}/{route-target-role}</a></td>
<td><p>delete an existing route-target</p>
</td>
@@ -4881,6 +5559,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-zones-zone--zone-id--patch">PATCH /network/zones/zone/{zone-id}</a></td>
+ <td><p>update an existing zone</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-zones-zone--zone-id--delete">DELETE /network/zones/zone/{zone-id}</a></td>
<td><p>delete an existing zone</p>
</td>
@@ -4940,7 +5623,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/connectors">/connectors</a>
+ <a class="json-schema-ref" href="#/getDefinitions/connectors">/connectors</a>
</div>
</div>
</div>
@@ -5095,7 +5778,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/connector">/connector</a>
+ <a class="json-schema-ref" href="#/getDefinitions/connector">/connector</a>
</div>
</div>
</div>
@@ -5142,7 +5825,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>connector object that needs to be created or updated</p>
+ <p><p>connector object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessConnectorsConnector.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -5213,6 +5896,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-connectors-connector--resource-instance-id--"></span>
+ <div id="operation--business-connectors-connector--resource-instance-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing connector</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/connectors/connector/{resource-instance-id}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing connector</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>connector object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/connector">/connector</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ resource-instance-id
+ </td>
+ <td>
+ <p>Unique id of resource instance.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-connectors-connector--resource-instance-id--"></span>
<div id="operation--business-connectors-connector--resource-instance-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing connector</div>
@@ -5432,7 +6204,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadata">/metadata</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadata">/metadata</a>
</div>
</div>
</div>
@@ -5602,7 +6374,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadatum">/metadatum</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadatum">/metadatum</a>
</div>
</div>
</div>
@@ -5649,7 +6421,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>metadatum object that needs to be created or updated</p>
+ <p><p>metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessConnectorsConnectorMetadataMetadatum.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -5735,6 +6507,110 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-connectors-connector--resource-instance-id--metadata-metadatum--metaname--"></span>
+ <div id="operation--business-connectors-connector--resource-instance-id--metadata-metadatum--metaname--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing metadatum</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/connectors/connector/{resource-instance-id}/metadata/metadatum/{metaname}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing metadatum</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>metadatum object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/metadatum">/metadatum</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ resource-instance-id
+ </td>
+ <td>
+ <p>Unique id of resource instance.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ metaname
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-connectors-connector--resource-instance-id--metadata-metadatum--metaname--"></span>
<div id="operation--business-connectors-connector--resource-instance-id--metadata-metadatum--metaname--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing metadatum</div>
@@ -5861,7 +6737,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessConnectorsConnector.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -6044,7 +6920,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/customers">/customers</a>
+ <a class="json-schema-ref" href="#/getDefinitions/customers">/customers</a>
</div>
</div>
</div>
@@ -6169,7 +7045,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/customer">/customer</a>
+ <a class="json-schema-ref" href="#/getDefinitions/customer">/customer</a>
</div>
</div>
</div>
@@ -6216,7 +7092,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>customer object that needs to be created or updated</p>
+ <p><p>customer object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessCustomersCustomer.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -6287,6 +7163,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-customers-customer--global-customer-id--"></span>
+ <div id="operation--business-customers-customer--global-customer-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing customer</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/customers/customer/{global-customer-id}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing customer</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>customer object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/customer">/customer</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ global-customer-id
+ </td>
+ <td>
+ <p>Global customer id used across ECOMP to uniquely identify customer.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-customers-customer--global-customer-id--"></span>
<div id="operation--business-customers-customer--global-customer-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing customer</div>
@@ -6398,7 +7363,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessCustomersCustomer.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -6642,7 +7607,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/service-subscriptions">/service-subscriptions</a>
+ <a class="json-schema-ref" href="#/getDefinitions/service-subscriptions">/service-subscriptions</a>
</div>
</div>
</div>
@@ -6783,7 +7748,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/service-subscription">/service-subscription</a>
+ <a class="json-schema-ref" href="#/getDefinitions/service-subscription">/service-subscription</a>
</div>
</div>
</div>
@@ -6830,7 +7795,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>service-subscription object that needs to be created or updated</p>
+ <p><p>service-subscription object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessCustomersCustomerServiceSubscriptionsServiceSubscription.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -6917,6 +7882,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--"></span>
+ <div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing service-subscription</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing service-subscription</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>service-subscription object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/service-subscription">/service-subscription</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ global-customer-id
+ </td>
+ <td>
+ <p>Global customer id used across ECOMP to uniquely identify customer.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-type
+ </td>
+ <td>
+ <p>Value defined by orchestration to identify this service across ECOMP.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--"></span>
<div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing service-subscription</div>
@@ -7044,7 +8114,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessCustomersCustomerServiceSubscriptionsServiceSubscription.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -7336,7 +8406,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/service-instances">/service-instances</a>
+ <a class="json-schema-ref" href="#/getDefinitions/service-instances">/service-instances</a>
</div>
</div>
</div>
@@ -7628,7 +8698,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/service-instance">/service-instance</a>
+ <a class="json-schema-ref" href="#/getDefinitions/service-instance">/service-instance</a>
</div>
</div>
</div>
@@ -7675,7 +8745,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>service-instance object that needs to be created or updated</p>
+ <p><p>service-instance object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -7778,6 +8848,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--"></span>
+ <div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing service-instance</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing service-instance</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>service-instance object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/service-instance">/service-instance</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ global-customer-id
+ </td>
+ <td>
+ <p>Global customer id used across ECOMP to uniquely identify customer.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-type
+ </td>
+ <td>
+ <p>Value defined by orchestration to identify this service across ECOMP.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-instance-id
+ </td>
+ <td>
+ <p>Uniquely identifies this instance of a service</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--"></span>
<div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing service-instance</div>
@@ -8166,7 +9357,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/allotted-resources">/allotted-resources</a>
+ <a class="json-schema-ref" href="#/getDefinitions/allotted-resources">/allotted-resources</a>
</div>
</div>
</div>
@@ -8534,7 +9725,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/allotted-resource">/allotted-resource</a>
+ <a class="json-schema-ref" href="#/getDefinitions/allotted-resource">/allotted-resource</a>
</div>
</div>
</div>
@@ -8581,7 +9772,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>allotted-resource object that needs to be created or updated</p>
+ <p><p>allotted-resource object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResource.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -8700,6 +9891,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--"></span>
+ <div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing allotted-resource</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/allotted-resources/allotted-resource/{id}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing allotted-resource</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>allotted-resource object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/allotted-resource">/allotted-resource</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ global-customer-id
+ </td>
+ <td>
+ <p>Global customer id used across ECOMP to uniquely identify customer.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-type
+ </td>
+ <td>
+ <p>Value defined by orchestration to identify this service across ECOMP.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-instance-id
+ </td>
+ <td>
+ <p>Uniquely identifies this instance of a service</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ id
+ </td>
+ <td>
+ <p>Allotted Resource id UUID assigned to this instance.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--"></span>
<div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing allotted-resource</div>
@@ -8859,7 +10187,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResource.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -9442,7 +10770,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/tunnel-xconnects">/tunnel-xconnects</a>
+ <a class="json-schema-ref" href="#/getDefinitions/tunnel-xconnects">/tunnel-xconnects</a>
</div>
</div>
</div>
@@ -9826,7 +11154,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/tunnel-xconnect">/tunnel-xconnect</a>
+ <a class="json-schema-ref" href="#/getDefinitions/tunnel-xconnect">/tunnel-xconnect</a>
</div>
</div>
</div>
@@ -9873,7 +11201,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>tunnel-xconnect object that needs to be created or updated</p>
+ <p><p>tunnel-xconnect object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResourceTunnelXconnectsTunnelXconnect.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -10008,6 +11336,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--tunnel-xconnects-tunnel-xconnect--id--"></span>
+ <div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--tunnel-xconnects-tunnel-xconnect--id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing tunnel-xconnect</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/allotted-resources/allotted-resource/{id}/tunnel-xconnects/tunnel-xconnect/{id}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing tunnel-xconnect</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>tunnel-xconnect object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/tunnel-xconnect">/tunnel-xconnect</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ global-customer-id
+ </td>
+ <td>
+ <p>Global customer id used across ECOMP to uniquely identify customer.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-type
+ </td>
+ <td>
+ <p>Value defined by orchestration to identify this service across ECOMP.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-instance-id
+ </td>
+ <td>
+ <p>Uniquely identifies this instance of a service</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ id
+ </td>
+ <td>
+ <p>Allotted Resource id UUID assigned to this instance.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ id
+ </td>
+ <td>
+ <p>Allotted Resource id UUID assigned to this instance.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--tunnel-xconnects-tunnel-xconnect--id--"></span>
<div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--tunnel-xconnects-tunnel-xconnect--id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing tunnel-xconnect</div>
@@ -10183,7 +11664,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResourceTunnelXconnectsTunnelXconnect.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -10722,7 +12203,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadata">/metadata</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadata">/metadata</a>
</div>
</div>
</div>
@@ -11029,7 +12510,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadatum">/metadatum</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadatum">/metadatum</a>
</div>
</div>
</div>
@@ -11076,7 +12557,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>metadatum object that needs to be created or updated</p>
+ <p><p>metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceMetadataMetadatum.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -11194,6 +12675,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--metadata-metadatum--metaname--"></span>
+ <div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--metadata-metadatum--metaname--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing metadatum</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/metadata/metadatum/{metaname}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing metadatum</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>metadatum object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/metadatum">/metadatum</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ global-customer-id
+ </td>
+ <td>
+ <p>Global customer id used across ECOMP to uniquely identify customer.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-type
+ </td>
+ <td>
+ <p>Value defined by orchestration to identify this service across ECOMP.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-instance-id
+ </td>
+ <td>
+ <p>Uniquely identifies this instance of a service</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ metaname
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--metadata-metadatum--metaname--"></span>
<div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--metadata-metadatum--metaname--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing metadatum</div>
@@ -11352,7 +12969,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -11599,7 +13216,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lines-of-business">/lines-of-business</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lines-of-business">/lines-of-business</a>
</div>
</div>
</div>
@@ -11694,7 +13311,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/line-of-business">/line-of-business</a>
+ <a class="json-schema-ref" href="#/getDefinitions/line-of-business">/line-of-business</a>
</div>
</div>
</div>
@@ -11741,7 +13358,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>line-of-business object that needs to be created or updated</p>
+ <p><p>line-of-business object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessLinesOfBusinessLineOfBusiness.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -11812,6 +13429,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-lines-of-business-line-of-business--line-of-business-name--"></span>
+ <div id="operation--business-lines-of-business-line-of-business--line-of-business-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing line-of-business</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/lines-of-business/line-of-business/{line-of-business-name}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing line-of-business</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>line-of-business object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/line-of-business">/line-of-business</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ line-of-business-name
+ </td>
+ <td>
+ <p>Name of the line-of-business (product)</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-lines-of-business-line-of-business--line-of-business-name--"></span>
<div id="operation--business-lines-of-business-line-of-business--line-of-business-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing line-of-business</div>
@@ -11923,7 +13629,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessLinesOfBusinessLineOfBusiness.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -12106,7 +13812,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/owning-entities">/owning-entities</a>
+ <a class="json-schema-ref" href="#/getDefinitions/owning-entities">/owning-entities</a>
</div>
</div>
</div>
@@ -12201,7 +13907,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/owning-entity">/owning-entity</a>
+ <a class="json-schema-ref" href="#/getDefinitions/owning-entity">/owning-entity</a>
</div>
</div>
</div>
@@ -12248,7 +13954,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>owning-entity object that needs to be created or updated</p>
+ <p><p>owning-entity object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessOwningEntitiesOwningEntity.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -12319,6 +14025,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-owning-entities-owning-entity--owning-entity-id--"></span>
+ <div id="operation--business-owning-entities-owning-entity--owning-entity-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing owning-entity</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/owning-entities/owning-entity/{owning-entity-id}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing owning-entity</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>owning-entity object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/owning-entity">/owning-entity</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ owning-entity-id
+ </td>
+ <td>
+ <p>UUID of an owning entity</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-owning-entities-owning-entity--owning-entity-id--"></span>
<div id="operation--business-owning-entities-owning-entity--owning-entity-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing owning-entity</div>
@@ -12430,7 +14225,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessOwningEntitiesOwningEntity.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -12613,7 +14408,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/platforms">/platforms</a>
+ <a class="json-schema-ref" href="#/getDefinitions/platforms">/platforms</a>
</div>
</div>
</div>
@@ -12708,7 +14503,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/platform">/platform</a>
+ <a class="json-schema-ref" href="#/getDefinitions/platform">/platform</a>
</div>
</div>
</div>
@@ -12755,7 +14550,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>platform object that needs to be created or updated</p>
+ <p><p>platform object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessPlatformsPlatform.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -12826,6 +14621,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-platforms-platform--platform-name--"></span>
+ <div id="operation--business-platforms-platform--platform-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing platform</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/platforms/platform/{platform-name}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing platform</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>platform object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/platform">/platform</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ platform-name
+ </td>
+ <td>
+ <p>Name of the platform</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-platforms-platform--platform-name--"></span>
<div id="operation--business-platforms-platform--platform-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing platform</div>
@@ -12937,7 +14821,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessPlatformsPlatform.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -13120,7 +15004,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/projects">/projects</a>
+ <a class="json-schema-ref" href="#/getDefinitions/projects">/projects</a>
</div>
</div>
</div>
@@ -13215,7 +15099,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/project">/project</a>
+ <a class="json-schema-ref" href="#/getDefinitions/project">/project</a>
</div>
</div>
</div>
@@ -13262,7 +15146,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>project object that needs to be created or updated</p>
+ <p><p>project object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessProjectsProject.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -13333,6 +15217,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-projects-project--project-name--"></span>
+ <div id="operation--business-projects-project--project-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing project</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/projects/project/{project-name}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing project</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>project object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/project">/project</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ project-name
+ </td>
+ <td>
+ <p>Name of the project deploying a service</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-projects-project--project-name--"></span>
<div id="operation--business-projects-project--project-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing project</div>
@@ -13444,7 +15417,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessProjectsProject.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -13627,7 +15600,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/cloud-regions">/cloud-regions</a>
+ <a class="json-schema-ref" href="#/getDefinitions/cloud-regions">/cloud-regions</a>
</div>
</div>
</div>
@@ -13768,7 +15741,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/cloud-region">/cloud-region</a>
+ <a class="json-schema-ref" href="#/getDefinitions/cloud-region">/cloud-region</a>
</div>
</div>
</div>
@@ -13815,7 +15788,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>cloud-region object that needs to be created or updated</p>
+ <p><p>cloud-region object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegion.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -13902,6 +15875,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing cloud-region</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing cloud-region</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>cloud-region object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/cloud-region">/cloud-region</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing cloud-region</div>
@@ -14123,7 +16201,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/availability-zones">/availability-zones</a>
+ <a class="json-schema-ref" href="#/getDefinitions/availability-zones">/availability-zones</a>
</div>
</div>
</div>
@@ -14280,7 +16358,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/availability-zone">/availability-zone</a>
+ <a class="json-schema-ref" href="#/getDefinitions/availability-zone">/availability-zone</a>
</div>
</div>
</div>
@@ -14327,7 +16405,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>availability-zone object that needs to be created or updated</p>
+ <p><p>availability-zone object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -14430,6 +16508,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--availability-zones-availability-zone--availability-zone-name--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--availability-zones-availability-zone--availability-zone-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing availability-zone</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/availability-zones/availability-zone/{availability-zone-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing availability-zone</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>availability-zone object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/availability-zone">/availability-zone</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ availability-zone-name
+ </td>
+ <td>
+ <p>Name of the availability zone. Unique across a cloud region</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--availability-zones-availability-zone--availability-zone-name--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--availability-zones-availability-zone--availability-zone-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing availability-zone</div>
@@ -14573,7 +16772,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -14897,7 +17096,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/dvs-switches">/dvs-switches</a>
+ <a class="json-schema-ref" href="#/getDefinitions/dvs-switches">/dvs-switches</a>
</div>
</div>
</div>
@@ -15069,7 +17268,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/dvs-switch">/dvs-switch</a>
+ <a class="json-schema-ref" href="#/getDefinitions/dvs-switch">/dvs-switch</a>
</div>
</div>
</div>
@@ -15116,7 +17315,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>dvs-switch object that needs to be created or updated</p>
+ <p><p>dvs-switch object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -15219,6 +17418,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--dvs-switches-dvs-switch--switch-name--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--dvs-switches-dvs-switch--switch-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing dvs-switch</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/dvs-switches/dvs-switch/{switch-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing dvs-switch</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>dvs-switch object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/dvs-switch">/dvs-switch</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ switch-name
+ </td>
+ <td>
+ <p>DVS switch name</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--dvs-switches-dvs-switch--switch-name--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--dvs-switches-dvs-switch--switch-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing dvs-switch</div>
@@ -15362,7 +17682,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -15686,7 +18006,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/esr-system-info-list">/esr-system-info-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/esr-system-info-list">/esr-system-info-list</a>
</div>
</div>
</div>
@@ -15873,7 +18193,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/esr-system-info">/esr-system-info</a>
+ <a class="json-schema-ref" href="#/getDefinitions/esr-system-info">/esr-system-info</a>
</div>
</div>
</div>
@@ -15920,7 +18240,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>esr-system-info object that needs to be created or updated</p>
+ <p><p>esr-system-info object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionEsrSystemInfoListEsrSystemInfo.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -16023,6 +18343,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--esr-system-info-list-esr-system-info--esr-system-info-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--esr-system-info-list-esr-system-info--esr-system-info-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing esr-system-info</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing esr-system-info</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>esr-system-info object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/esr-system-info">/esr-system-info</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ esr-system-info-id
+ </td>
+ <td>
+ <p>Unique ID of esr system info.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--esr-system-info-list-esr-system-info--esr-system-info-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--esr-system-info-list-esr-system-info--esr-system-info-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing esr-system-info</div>
@@ -16166,7 +18607,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionEsrSystemInfoListEsrSystemInfo.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -16490,7 +18931,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/flavors">/flavors</a>
+ <a class="json-schema-ref" href="#/getDefinitions/flavors">/flavors</a>
</div>
</div>
</div>
@@ -16662,7 +19103,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/flavor">/flavor</a>
+ <a class="json-schema-ref" href="#/getDefinitions/flavor">/flavor</a>
</div>
</div>
</div>
@@ -16709,7 +19150,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>flavor object that needs to be created or updated</p>
+ <p><p>flavor object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -16812,6 +19253,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--flavors-flavor--flavor-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--flavors-flavor--flavor-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing flavor</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/flavors/flavor/{flavor-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing flavor</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>flavor object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/flavor">/flavor</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ flavor-id
+ </td>
+ <td>
+ <p>Flavor id, expected to be unique across cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--flavors-flavor--flavor-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--flavors-flavor--flavor-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing flavor</div>
@@ -16955,7 +19517,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -17279,7 +19841,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/group-assignments">/group-assignments</a>
+ <a class="json-schema-ref" href="#/getDefinitions/group-assignments">/group-assignments</a>
</div>
</div>
</div>
@@ -17466,7 +20028,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/group-assignment">/group-assignment</a>
+ <a class="json-schema-ref" href="#/getDefinitions/group-assignment">/group-assignment</a>
</div>
</div>
</div>
@@ -17513,7 +20075,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>group-assignment object that needs to be created or updated</p>
+ <p><p>group-assignment object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -17616,6 +20178,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--group-assignments-group-assignment--group-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--group-assignments-group-assignment--group-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing group-assignment</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/group-assignments/group-assignment/{group-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing group-assignment</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>group-assignment object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/group-assignment">/group-assignment</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ group-id
+ </td>
+ <td>
+ <p>Group id, expected to be unique across cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--group-assignments-group-assignment--group-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--group-assignments-group-assignment--group-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing group-assignment</div>
@@ -17759,7 +20442,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -18083,7 +20766,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/images">/images</a>
+ <a class="json-schema-ref" href="#/getDefinitions/images">/images</a>
</div>
</div>
</div>
@@ -18300,7 +20983,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/image">/image</a>
+ <a class="json-schema-ref" href="#/getDefinitions/image">/image</a>
</div>
</div>
</div>
@@ -18347,7 +21030,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>image object that needs to be created or updated</p>
+ <p><p>image object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionImagesImage.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -18450,6 +21133,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing image</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing image</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>image object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/image">/image</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ image-id
+ </td>
+ <td>
+ <p>Image id, expected to be unique across cloud region</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing image</div>
@@ -18763,7 +21567,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadata">/metadata</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadata">/metadata</a>
</div>
</div>
</div>
@@ -18995,7 +21799,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadatum">/metadatum</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadatum">/metadatum</a>
</div>
</div>
</div>
@@ -19042,7 +21846,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>metadatum object that needs to be created or updated</p>
+ <p><p>metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionImagesImageMetadataMetadatum.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -19160,6 +21964,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--metadata-metadatum--metaname--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--metadata-metadatum--metaname--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing metadatum</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}/metadata/metadatum/{metaname}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing metadatum</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>metadatum object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/metadatum">/metadatum</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ image-id
+ </td>
+ <td>
+ <p>Image id, expected to be unique across cloud region</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ metaname
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--metadata-metadatum--metaname--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--metadata-metadatum--metaname--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing metadatum</div>
@@ -19318,7 +22258,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionImagesImage.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -19642,7 +22582,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/oam-networks">/oam-networks</a>
+ <a class="json-schema-ref" href="#/getDefinitions/oam-networks">/oam-networks</a>
</div>
</div>
</div>
@@ -19829,7 +22769,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/oam-network">/oam-network</a>
+ <a class="json-schema-ref" href="#/getDefinitions/oam-network">/oam-network</a>
</div>
</div>
</div>
@@ -19876,7 +22816,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>oam-network object that needs to be created or updated</p>
+ <p><p>oam-network object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -19979,6 +22919,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--oam-networks-oam-network--network-uuid--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--oam-networks-oam-network--network-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing oam-network</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/oam-networks/oam-network/{network-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing oam-network</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>oam-network object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/oam-network">/oam-network</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ network-uuid
+ </td>
+ <td>
+ <p>UUID of the network. Unique across a cloud-region</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--oam-networks-oam-network--network-uuid--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--oam-networks-oam-network--network-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing oam-network</div>
@@ -20122,7 +23183,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -20352,7 +23413,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegion.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -20644,7 +23705,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/snapshots">/snapshots</a>
+ <a class="json-schema-ref" href="#/getDefinitions/snapshots">/snapshots</a>
</div>
</div>
</div>
@@ -20876,7 +23937,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/snapshot">/snapshot</a>
+ <a class="json-schema-ref" href="#/getDefinitions/snapshot">/snapshot</a>
</div>
</div>
</div>
@@ -20923,7 +23984,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>snapshot object that needs to be created or updated</p>
+ <p><p>snapshot object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -21026,6 +24087,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--snapshots-snapshot--snapshot-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--snapshots-snapshot--snapshot-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing snapshot</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/snapshots/snapshot/{snapshot-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing snapshot</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>snapshot object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/snapshot">/snapshot</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ snapshot-id
+ </td>
+ <td>
+ <p>Snapshot id, this is the key UUID assoc associated in glance with the snapshots.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--snapshots-snapshot--snapshot-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--snapshots-snapshot--snapshot-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing snapshot</div>
@@ -21169,7 +24351,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -21493,7 +24675,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/tenants">/tenants</a>
+ <a class="json-schema-ref" href="#/getDefinitions/tenants">/tenants</a>
</div>
</div>
</div>
@@ -21680,7 +24862,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/tenant">/tenant</a>
+ <a class="json-schema-ref" href="#/getDefinitions/tenant">/tenant</a>
</div>
</div>
</div>
@@ -21727,7 +24909,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>tenant object that needs to be created or updated</p>
+ <p><p>tenant object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenant.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -21830,6 +25012,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing tenant</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing tenant</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>tenant object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/tenant">/tenant</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing tenant</div>
@@ -21973,7 +25276,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenant.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -22343,7 +25646,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vservers">/vservers</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vservers">/vservers</a>
</div>
</div>
</div>
@@ -22619,7 +25922,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vserver">/vserver</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vserver">/vserver</a>
</div>
</div>
</div>
@@ -22666,7 +25969,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vserver object that needs to be created or updated</p>
+ <p><p>vserver object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -22785,6 +26088,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vserver</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vserver</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vserver object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vserver">/vserver</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vserver</div>
@@ -23173,7 +26613,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -23510,7 +26950,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -23557,7 +26997,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -23692,6 +27132,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -24218,7 +27811,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -24265,7 +27858,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -24416,6 +28009,175 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -24607,7 +28369,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -25284,7 +29046,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -25331,7 +29093,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -25482,6 +29244,175 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -25673,7 +29604,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -25999,7 +29930,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -26583,7 +30514,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -26996,7 +30927,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -27043,7 +30974,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -27194,6 +31125,175 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -27385,7 +31485,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -28001,7 +32101,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -28384,7 +32484,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -28431,7 +32531,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -28582,6 +32682,175 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -29170,7 +33439,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -29217,7 +33486,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -29384,6 +33653,191 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -29591,7 +34045,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -30346,7 +34800,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -30393,7 +34847,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -30560,6 +35014,191 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -30767,7 +35406,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -31125,7 +35764,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -31451,7 +36090,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -31942,7 +36581,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/volumes">/volumes</a>
+ <a class="json-schema-ref" href="#/getDefinitions/volumes">/volumes</a>
</div>
</div>
</div>
@@ -32234,7 +36873,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/volume">/volume</a>
+ <a class="json-schema-ref" href="#/getDefinitions/volume">/volume</a>
</div>
</div>
</div>
@@ -32281,7 +36920,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>volume object that needs to be created or updated</p>
+ <p><p>volume object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -32416,6 +37055,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--volumes-volume--volume-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--volumes-volume--volume-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing volume</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/volumes/volume/{volume-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing volume</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>volume object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/volume">/volume</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ volume-id
+ </td>
+ <td>
+ <p>Unique ID of block storage volume relative to the vserver.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--volumes-volume--volume-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--volumes-volume--volume-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing volume</div>
@@ -32591,7 +37383,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -33040,7 +37832,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vip-ipv4-address-list">/vip-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vip-ipv4-address-list">/vip-ipv4-address-list</a>
</div>
</div>
</div>
@@ -33087,7 +37879,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vip-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>vip-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionVipIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -33190,6 +37982,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--vip-ipv4-address-list--vip-ipv4-address--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--vip-ipv4-address-list--vip-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vip-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/vip-ipv4-address-list/{vip-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vip-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vip-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vip-ipv4-address-list">/vip-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vip-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--vip-ipv4-address-list--vip-ipv4-address--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--vip-ipv4-address-list--vip-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vip-ipv4-address-list</div>
@@ -33333,7 +38246,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionVipIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -33718,7 +38631,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vip-ipv6-address-list">/vip-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vip-ipv6-address-list">/vip-ipv6-address-list</a>
</div>
</div>
</div>
@@ -33765,7 +38678,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vip-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>vip-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionVipIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -33868,6 +38781,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--vip-ipv6-address-list--vip-ipv6-address--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--vip-ipv6-address-list--vip-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vip-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/vip-ipv6-address-list/{vip-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vip-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vip-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vip-ipv6-address-list">/vip-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vip-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--vip-ipv6-address-list--vip-ipv6-address--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--vip-ipv6-address-list--vip-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vip-ipv6-address-list</div>
@@ -34011,7 +39045,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionVipIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -34335,7 +39369,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/volume-groups">/volume-groups</a>
+ <a class="json-schema-ref" href="#/getDefinitions/volume-groups">/volume-groups</a>
</div>
</div>
</div>
@@ -34537,7 +39571,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/volume-group">/volume-group</a>
+ <a class="json-schema-ref" href="#/getDefinitions/volume-group">/volume-group</a>
</div>
</div>
</div>
@@ -34584,7 +39618,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>volume-group object that needs to be created or updated</p>
+ <p><p>volume-group object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -34687,6 +39721,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--volume-groups-volume-group--volume-group-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--volume-groups-volume-group--volume-group-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing volume-group</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/volume-groups/volume-group/{volume-group-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing volume-group</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>volume-group object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/volume-group">/volume-group</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ volume-group-id
+ </td>
+ <td>
+ <p>Unique ID of volume-group.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--volume-groups-volume-group--volume-group-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--volume-groups-volume-group--volume-group-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing volume-group</div>
@@ -34830,7 +39985,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -35077,7 +40232,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/complexes">/complexes</a>
+ <a class="json-schema-ref" href="#/getDefinitions/complexes">/complexes</a>
</div>
</div>
</div>
@@ -35217,7 +40372,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/complex">/complex</a>
+ <a class="json-schema-ref" href="#/getDefinitions/complex">/complex</a>
</div>
</div>
</div>
@@ -35264,7 +40419,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>complex object that needs to be created or updated</p>
+ <p><p>complex object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureComplexesComplex.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -35335,6 +40490,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-complexes-complex--physical-location-id--"></span>
+ <div id="operation--cloud-infrastructure-complexes-complex--physical-location-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing complex</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/complexes/complex/{physical-location-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing complex</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>complex object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/complex">/complex</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ physical-location-id
+ </td>
+ <td>
+ <p>Unique identifier for physical location, e.g., CLLI</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-complexes-complex--physical-location-id--"></span>
<div id="operation--cloud-infrastructure-complexes-complex--physical-location-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing complex</div>
@@ -35539,7 +40783,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/ctag-pools">/ctag-pools</a>
+ <a class="json-schema-ref" href="#/getDefinitions/ctag-pools">/ctag-pools</a>
</div>
</div>
</div>
@@ -35711,7 +40955,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/ctag-pool">/ctag-pool</a>
+ <a class="json-schema-ref" href="#/getDefinitions/ctag-pool">/ctag-pool</a>
</div>
</div>
</div>
@@ -35758,7 +41002,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>ctag-pool object that needs to be created or updated</p>
+ <p><p>ctag-pool object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureComplexesComplexCtagPoolsCtagPool.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -35861,6 +41105,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-complexes-complex--physical-location-id--ctag-pools-ctag-pool--target-pe---availability-zone-name--"></span>
+ <div id="operation--cloud-infrastructure-complexes-complex--physical-location-id--ctag-pools-ctag-pool--target-pe---availability-zone-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing ctag-pool</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/complexes/complex/{physical-location-id}/ctag-pools/ctag-pool/{target-pe}/{availability-zone-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing ctag-pool</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>ctag-pool object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/ctag-pool">/ctag-pool</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ physical-location-id
+ </td>
+ <td>
+ <p>Unique identifier for physical location, e.g., CLLI</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ target-pe
+ </td>
+ <td>
+ <p>The Target provider edge router</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ availability-zone-name
+ </td>
+ <td>
+ <p>Name of the availability zone</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-complexes-complex--physical-location-id--ctag-pools-ctag-pool--target-pe---availability-zone-name--"></span>
<div id="operation--cloud-infrastructure-complexes-complex--physical-location-id--ctag-pools-ctag-pool--target-pe---availability-zone-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing ctag-pool</div>
@@ -36004,7 +41369,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureComplexesComplexCtagPoolsCtagPool.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -36234,7 +41599,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureComplexesComplex.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -36417,7 +41782,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/network-profiles">/network-profiles</a>
+ <a class="json-schema-ref" href="#/getDefinitions/network-profiles">/network-profiles</a>
</div>
</div>
</div>
@@ -36512,7 +41877,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/network-profile">/network-profile</a>
+ <a class="json-schema-ref" href="#/getDefinitions/network-profile">/network-profile</a>
</div>
</div>
</div>
@@ -36559,7 +41924,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>network-profile object that needs to be created or updated</p>
+ <p><p>network-profile object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureNetworkProfilesNetworkProfile.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -36630,6 +41995,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-network-profiles-network-profile--nm-profile-name--"></span>
+ <div id="operation--cloud-infrastructure-network-profiles-network-profile--nm-profile-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing network-profile</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/network-profiles/network-profile/{nm-profile-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing network-profile</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>network-profile object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/network-profile">/network-profile</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ nm-profile-name
+ </td>
+ <td>
+ <p>Unique name of network profile.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-network-profiles-network-profile--nm-profile-name--"></span>
<div id="operation--cloud-infrastructure-network-profiles-network-profile--nm-profile-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing network-profile</div>
@@ -36741,7 +42195,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureNetworkProfilesNetworkProfile.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -36924,7 +42378,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/pservers">/pservers</a>
+ <a class="json-schema-ref" href="#/getDefinitions/pservers">/pservers</a>
</div>
</div>
</div>
@@ -37078,7 +42532,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/pserver">/pserver</a>
+ <a class="json-schema-ref" href="#/getDefinitions/pserver">/pserver</a>
</div>
</div>
</div>
@@ -37125,7 +42579,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>pserver object that needs to be created or updated</p>
+ <p><p>pserver object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserver.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -37196,6 +42650,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing pserver</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing pserver</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>pserver object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/pserver">/pserver</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing pserver</div>
@@ -37414,7 +42957,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interfaces">/lag-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interfaces">/lag-interfaces</a>
</div>
</div>
</div>
@@ -37614,7 +43157,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interface">/lag-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interface">/lag-interface</a>
</div>
</div>
</div>
@@ -37661,7 +43204,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>lag-interface object that needs to be created or updated</p>
+ <p><p>lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -37748,6 +43291,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing lag-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing lag-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>lag-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/lag-interface">/lag-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing lag-interface</div>
@@ -38028,7 +43676,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -38289,7 +43937,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -38336,7 +43984,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -38439,6 +44087,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -38857,7 +44626,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -38904,7 +44673,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -39023,6 +44792,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -39182,7 +45088,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -39719,7 +45625,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -39766,7 +45672,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -39885,6 +45791,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -40044,7 +46087,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -40306,7 +46349,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -40750,7 +46793,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -41087,7 +47130,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -41134,7 +47177,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -41253,6 +47296,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -41412,7 +47592,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -41888,7 +48068,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -42195,7 +48375,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -42242,7 +48422,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -42361,6 +48541,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -42841,7 +49158,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -42888,7 +49205,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -43023,6 +49340,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -43198,7 +49668,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -43813,7 +50283,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -43860,7 +50330,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -43995,6 +50465,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -44170,7 +50793,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -44464,7 +51087,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -44726,7 +51349,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -45031,7 +51654,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/p-interfaces">/p-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/p-interfaces">/p-interfaces</a>
</div>
</div>
</div>
@@ -45216,7 +51839,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/p-interface">/p-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/p-interface">/p-interface</a>
</div>
</div>
</div>
@@ -45263,7 +51886,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>p-interface object that needs to be created or updated</p>
+ <p><p>p-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -45350,6 +51973,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing p-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing p-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>p-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/p-interface">/p-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing p-interface</div>
@@ -45615,7 +52343,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -45861,7 +52589,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -45908,7 +52636,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -46011,6 +52739,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -46414,7 +53263,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -46461,7 +53310,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -46580,6 +53429,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -46739,7 +53725,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -47261,7 +54247,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -47308,7 +54294,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -47427,6 +54413,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -47586,7 +54709,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -47848,7 +54971,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -48277,7 +55400,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -48599,7 +55722,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -48646,7 +55769,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -48765,6 +55888,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -48924,7 +56184,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -49385,7 +56645,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -49677,7 +56937,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -49724,7 +56984,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -49843,6 +57103,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -50308,7 +57705,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -50355,7 +57752,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -50490,6 +57887,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -50665,7 +58215,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -51265,7 +58815,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -51312,7 +58862,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -51447,6 +58997,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -51622,7 +59325,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -51916,7 +59619,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -52178,7 +59881,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -52514,7 +60217,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-pfs">/sriov-pfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-pfs">/sriov-pfs</a>
</div>
</div>
</div>
@@ -52715,7 +60418,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-pf">/sriov-pf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-pf">/sriov-pf</a>
</div>
</div>
</div>
@@ -52762,7 +60465,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-pf object that needs to be created or updated</p>
+ <p><p>sriov-pf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceSriovPfsSriovPf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -52865,22 +60568,34 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--sriov-pfs-sriov-pf--pf-pci-id--"></span>
- <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--sriov-pfs-sriov-pf--pf-pci-id--delete" class="swagger--panel-operation-delete panel">
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--sriov-pfs-sriov-pf--pf-pci-id--patch" class="swagger--panel-operation-patch panel">
<div class="panel-heading">
- <div class="operation-summary">delete an existing sriov-pf</div>
- <h3 class="panel-title"><span class="operation-name">DELETE</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/sriov-pfs/sriov-pf/{pf-pci-id}</strong></h3>
+ <div class="operation-summary">update an existing sriov-pf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/sriov-pfs/sriov-pf/{pf-pci-id}</strong></h3>
Tags:
<a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
</div>
<div class="panel-body">
<section class="sw-operation-description">
- <p>delete an existing sriov-pf</p>
+ <p>update an existing sriov-pf</p>
</section>
<section class="sw-request-body">
<p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
</p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-pf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-pf">/sriov-pf</a>
+ </div>
+ </div></div>
+ </div>
</section>
<section class="sw-request-params">
<table class="table">
@@ -52942,22 +60657,6 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<span class="json-property-required"></span>
</td>
</tr>
- <tr>
- <td>
- resource-version
- </td>
- <td>
- <p>resource-version for concurrency</p>
- </td>
- <td>query</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- <span class="json-property-required"></span>
- </td>
- </tr>
</tbody>
</table>
</section>
@@ -52989,35 +60688,23 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</div>
- <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--sriov-pfs-sriov-pf--pf-pci-id--relationship-list-relationship-"></span>
- <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--sriov-pfs-sriov-pf--pf-pci-id--relationship-list-relationship-put" class="swagger--panel-operation-put panel">
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--sriov-pfs-sriov-pf--pf-pci-id--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--sriov-pfs-sriov-pf--pf-pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
- <div class="operation-summary">see node definition for valid relationships</div>
- <h3 class="panel-title"><span class="operation-name">PUT</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/sriov-pfs/sriov-pf/{pf-pci-id}/relationship-list/relationship</strong></h3>
+ <div class="operation-summary">delete an existing sriov-pf</div>
+ <h3 class="panel-title"><span class="operation-name">DELETE</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/sriov-pfs/sriov-pf/{pf-pci-id}</strong></h3>
Tags:
<a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
</div>
<div class="panel-body">
<section class="sw-operation-description">
- <p>see node definition for valid relationships</p>
+ <p>delete an existing sriov-pf</p>
</section>
<section class="sw-request-body">
<p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
</p>
- <div class="row">
- <div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
- </p>
- </div>
- <div class="col-md-6 sw-request-model">
- <div class="panel panel-definition">
- <div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/relationship">/relationship</a>
- </div>
- </div></div>
- </div>
</section>
<section class="sw-request-params">
<table class="table">
@@ -53079,107 +60766,14 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<span class="json-property-required"></span>
</td>
</tr>
- </tbody>
- </table>
- </section>
-
- <section class="sw-responses">
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
-
- <dl>
- <dt class="sw-response-default">
- default
-
- </dt>
- <dd class="sw-response-default">
- <div class="row">
- <div class="col-md-12">
- <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
-
- </div>
- </div>
- <div class="row">
-
- <div class="col-md-6 sw-response-model">
- </div>
-
- </div> </dd>
- </dl>
- </section>
- </div>
- </div>
-
- <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--sriov-pfs-sriov-pf--pf-pci-id--relationship-list-relationship-"></span>
- <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--sriov-pfs-sriov-pf--pf-pci-id--relationship-list-relationship-delete" class="swagger--panel-operation-delete panel">
- <div class="panel-heading">
- <div class="operation-summary">delete an existing relationship</div>
- <h3 class="panel-title"><span class="operation-name">DELETE</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/sriov-pfs/sriov-pf/{pf-pci-id}/relationship-list/relationship</strong></h3>
- Tags:
- <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
- </div>
- <div class="panel-body">
- <section class="sw-operation-description">
- <p>delete an existing relationship</p>
-
- </section>
- <section class="sw-request-body">
-
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
- </section>
- <section class="sw-request-params">
- <table class="table">
- <thead>
- <tr>
- <th class="sw-param-name"></th>
- <th class="sw-param-description"></th>
- <th class="sw-param-type"></th>
- <th class="sw-param-data-type"></th>
- <th class="sw-param-annotation"></th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>
- hostname
- </td>
- <td>
- <p>Value from executing hostname on the compute node.</p>
- </td>
- <td>path</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- <span class="json-property-required"></span>
- </td>
- </tr>
- <tr>
- <td>
- interface-name
- </td>
- <td>
- <p>Name that identifies the physical interface</p>
- </td>
- <td>path</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- <span class="json-property-required"></span>
- </td>
- </tr>
<tr>
<td>
- pf-pci-id
+ resource-version
</td>
<td>
- <p>Identifier for the sriov-pf</p>
+ <p>resource-version for concurrency</p>
</td>
- <td>path</td>
+ <td>query</td>
<td>
<span class="json-property-type">string</span>
<span class="json-property-range" title="Value limits"></span>
@@ -53219,11 +60813,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</div>
- <span id="path--cloud-infrastructure-pservers-pserver--hostname--relationship-list-relationship-"></span>
- <div id="operation--cloud-infrastructure-pservers-pserver--hostname--relationship-list-relationship-put" class="swagger--panel-operation-put panel">
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--sriov-pfs-sriov-pf--pf-pci-id--relationship-list-relationship-"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--sriov-pfs-sriov-pf--pf-pci-id--relationship-list-relationship-put" class="swagger--panel-operation-put panel">
<div class="panel-heading">
<div class="operation-summary">see node definition for valid relationships</div>
- <h3 class="panel-title"><span class="operation-name">PUT</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/relationship-list/relationship</strong></h3>
+ <h3 class="panel-title"><span class="operation-name">PUT</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/sriov-pfs/sriov-pf/{pf-pci-id}/relationship-list/relationship</strong></h3>
Tags:
<a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
</div>
@@ -53238,7 +60832,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceSriovPfsSriovPf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -53277,73 +60871,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<span class="json-property-required"></span>
</td>
</tr>
- </tbody>
- </table>
- </section>
-
- <section class="sw-responses">
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
-
- <dl>
- <dt class="sw-response-default">
- default
-
- </dt>
- <dd class="sw-response-default">
- <div class="row">
- <div class="col-md-12">
- <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
-
- </div>
- </div>
- <div class="row">
-
- <div class="col-md-6 sw-response-model">
- </div>
-
- </div> </dd>
- </dl>
- </section>
- </div>
- </div>
-
- <span id="path--cloud-infrastructure-pservers-pserver--hostname--relationship-list-relationship-"></span>
- <div id="operation--cloud-infrastructure-pservers-pserver--hostname--relationship-list-relationship-delete" class="swagger--panel-operation-delete panel">
- <div class="panel-heading">
- <div class="operation-summary">delete an existing relationship</div>
- <h3 class="panel-title"><span class="operation-name">DELETE</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/relationship-list/relationship</strong></h3>
- Tags:
- <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
- </div>
- <div class="panel-body">
- <section class="sw-operation-description">
- <p>delete an existing relationship</p>
-
- </section>
- <section class="sw-request-body">
-
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
- </section>
- <section class="sw-request-params">
- <table class="table">
- <thead>
- <tr>
- <th class="sw-param-name"></th>
- <th class="sw-param-description"></th>
- <th class="sw-param-type"></th>
- <th class="sw-param-data-type"></th>
- <th class="sw-param-annotation"></th>
- </tr>
- </thead>
- <tbody>
<tr>
<td>
- hostname
+ interface-name
</td>
<td>
- <p>Value from executing hostname on the compute node.</p>
+ <p>Name that identifies the physical interface</p>
</td>
<td>path</td>
<td>
@@ -53354,132 +60887,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<span class="json-property-required"></span>
</td>
</tr>
- </tbody>
- </table>
- </section>
-
- <section class="sw-responses">
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
-
- <dl>
- <dt class="sw-response-default">
- default
-
- </dt>
- <dd class="sw-response-default">
- <div class="row">
- <div class="col-md-12">
- <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
-
- </div>
- </div>
- <div class="row">
-
- <div class="col-md-6 sw-response-model">
- </div>
-
- </div> </dd>
- </dl>
- </section>
- </div>
- </div>
-
- <span id="path--cloud-infrastructure-virtual-data-centers-"></span>
- <div id="operation--cloud-infrastructure-virtual-data-centers-get" class="swagger--panel-operation-get panel">
- <div class="panel-heading">
- <div class="operation-summary">returns virtual-data-centers</div>
- <h3 class="panel-title"><span class="operation-name">GET</span> <strong>/cloud-infrastructure/virtual-data-centers</strong></h3>
- Tags:
- <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
- </div>
- <div class="panel-body">
- <section class="sw-operation-description">
- <p>returns virtual-data-centers</p>
-
- </section>
-
- <section class="sw-responses">
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
-
- <dl>
- <dt class="sw-response-200">
- 200 OK
-
- </dt>
- <dd class="sw-response-200">
- <div class="row">
- <div class="col-md-12">
- <p>successful operation</p>
-
- </div>
- </div>
- <div class="row">
-
- <div class="col-md-6 sw-response-model">
- <div class="panel panel-definition">
-
- <div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/virtual-data-centers">/virtual-data-centers</a>
- </div>
- </div>
- </div>
-
- </div> </dd>
- <dt class="sw-response-default">
- default
-
- </dt>
- <dd class="sw-response-default">
- <div class="row">
- <div class="col-md-12">
- <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
-
- </div>
- </div>
- <div class="row">
-
- <div class="col-md-6 sw-response-model">
- </div>
-
- </div> </dd>
- </dl>
- </section>
- </div>
- </div>
-
- <span id="path--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--"></span>
- <div id="operation--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--get" class="swagger--panel-operation-get panel">
- <div class="panel-heading">
- <div class="operation-summary">returns virtual-data-center</div>
- <h3 class="panel-title"><span class="operation-name">GET</span> <strong>/cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}</strong></h3>
- Tags:
- <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
- </div>
- <div class="panel-body">
- <section class="sw-operation-description">
- <p>returns virtual-data-center</p>
-
- </section>
- <section class="sw-request-params">
- <table class="table">
- <thead>
- <tr>
- <th class="sw-param-name"></th>
- <th class="sw-param-description"></th>
- <th class="sw-param-type"></th>
- <th class="sw-param-data-type"></th>
- <th class="sw-param-annotation"></th>
- </tr>
- </thead>
- <tbody>
<tr>
<td>
- vdc-id
+ pf-pci-id
</td>
<td>
- <p>Unique ID of the vdc</p>
+ <p>Identifier for the sriov-pf</p>
</td>
<td>path</td>
<td>
@@ -53490,21 +60903,6 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<span class="json-property-required"></span>
</td>
</tr>
- <tr>
- <td>
- vdc-name
- </td>
- <td>
- <p>Name of the virtual data center</p>
- </td>
- <td>query</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- </td>
- </tr>
</tbody>
</table>
</section>
@@ -53514,29 +60912,6 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<dl>
- <dt class="sw-response-200">
- 200 OK
-
- </dt>
- <dd class="sw-response-200">
- <div class="row">
- <div class="col-md-12">
- <p>successful operation</p>
-
- </div>
- </div>
- <div class="row">
-
- <div class="col-md-6 sw-response-model">
- <div class="panel panel-definition">
-
- <div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/virtual-data-center">/virtual-data-center</a>
- </div>
- </div>
- </div>
-
- </div> </dd>
<dt class="sw-response-default">
default
@@ -53559,35 +60934,23 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</div>
- <span id="path--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--"></span>
- <div id="operation--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--put" class="swagger--panel-operation-put panel">
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--sriov-pfs-sriov-pf--pf-pci-id--relationship-list-relationship-"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--sriov-pfs-sriov-pf--pf-pci-id--relationship-list-relationship-delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
- <div class="operation-summary">create or update an existing virtual-data-center</div>
- <h3 class="panel-title"><span class="operation-name">PUT</span> <strong>/cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}</strong></h3>
+ <div class="operation-summary">delete an existing relationship</div>
+ <h3 class="panel-title"><span class="operation-name">DELETE</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/sriov-pfs/sriov-pf/{pf-pci-id}/relationship-list/relationship</strong></h3>
Tags:
<a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
</div>
<div class="panel-body">
<section class="sw-operation-description">
- <p>create or update an existing virtual-data-center</p>
+ <p>delete an existing relationship</p>
</section>
<section class="sw-request-body">
<p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
</p>
- <div class="row">
- <div class="col-md-6">
- <p><p>virtual-data-center object that needs to be created or updated</p>
- </p>
- </div>
- <div class="col-md-6 sw-request-model">
- <div class="panel panel-definition">
- <div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/virtual-data-center">/virtual-data-center</a>
- </div>
- </div></div>
- </div>
</section>
<section class="sw-request-params">
<table class="table">
@@ -53603,10 +60966,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<tbody>
<tr>
<td>
- vdc-id
+ hostname
</td>
<td>
- <p>Unique ID of the vdc</p>
+ <p>Value from executing hostname on the compute node.</p>
</td>
<td>path</td>
<td>
@@ -53617,73 +60980,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<span class="json-property-required"></span>
</td>
</tr>
- </tbody>
- </table>
- </section>
-
- <section class="sw-responses">
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
-
- <dl>
- <dt class="sw-response-default">
- default
-
- </dt>
- <dd class="sw-response-default">
- <div class="row">
- <div class="col-md-12">
- <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
-
- </div>
- </div>
- <div class="row">
-
- <div class="col-md-6 sw-response-model">
- </div>
-
- </div> </dd>
- </dl>
- </section>
- </div>
- </div>
-
- <span id="path--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--"></span>
- <div id="operation--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--delete" class="swagger--panel-operation-delete panel">
- <div class="panel-heading">
- <div class="operation-summary">delete an existing virtual-data-center</div>
- <h3 class="panel-title"><span class="operation-name">DELETE</span> <strong>/cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}</strong></h3>
- Tags:
- <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
- </div>
- <div class="panel-body">
- <section class="sw-operation-description">
- <p>delete an existing virtual-data-center</p>
-
- </section>
- <section class="sw-request-body">
-
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
- </section>
- <section class="sw-request-params">
- <table class="table">
- <thead>
- <tr>
- <th class="sw-param-name"></th>
- <th class="sw-param-description"></th>
- <th class="sw-param-type"></th>
- <th class="sw-param-data-type"></th>
- <th class="sw-param-annotation"></th>
- </tr>
- </thead>
- <tbody>
<tr>
<td>
- vdc-id
+ interface-name
</td>
<td>
- <p>Unique ID of the vdc</p>
+ <p>Name that identifies the physical interface</p>
</td>
<td>path</td>
<td>
@@ -53696,12 +60998,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</tr>
<tr>
<td>
- resource-version
+ pf-pci-id
</td>
<td>
- <p>resource-version for concurrency</p>
+ <p>Identifier for the sriov-pf</p>
</td>
- <td>query</td>
+ <td>path</td>
<td>
<span class="json-property-type">string</span>
<span class="json-property-range" title="Value limits"></span>
@@ -53741,11 +61043,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</div>
- <span id="path--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--relationship-list-relationship-"></span>
- <div id="operation--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--relationship-list-relationship-put" class="swagger--panel-operation-put panel">
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--relationship-list-relationship-"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--relationship-list-relationship-put" class="swagger--panel-operation-put panel">
<div class="panel-heading">
<div class="operation-summary">see node definition for valid relationships</div>
- <h3 class="panel-title"><span class="operation-name">PUT</span> <strong>/cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}/relationship-list/relationship</strong></h3>
+ <h3 class="panel-title"><span class="operation-name">PUT</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/relationship-list/relationship</strong></h3>
Tags:
<a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
</div>
@@ -53760,7 +61062,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserver.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -53785,10 +61087,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<tbody>
<tr>
<td>
- vdc-id
+ hostname
</td>
<td>
- <p>Unique ID of the vdc</p>
+ <p>Value from executing hostname on the compute node.</p>
</td>
<td>path</td>
<td>
@@ -53830,11 +61132,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</div>
- <span id="path--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--relationship-list-relationship-"></span>
- <div id="operation--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--relationship-list-relationship-delete" class="swagger--panel-operation-delete panel">
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--relationship-list-relationship-"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--relationship-list-relationship-delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing relationship</div>
- <h3 class="panel-title"><span class="operation-name">DELETE</span> <strong>/cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}/relationship-list/relationship</strong></h3>
+ <h3 class="panel-title"><span class="operation-name">DELETE</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/relationship-list/relationship</strong></h3>
Tags:
<a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
</div>
@@ -53862,335 +61164,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<tbody>
<tr>
<td>
- vdc-id
- </td>
- <td>
- <p>Unique ID of the vdc</p>
- </td>
- <td>path</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- <span class="json-property-required"></span>
- </td>
- </tr>
- </tbody>
- </table>
- </section>
-
- <section class="sw-responses">
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
-
- <dl>
- <dt class="sw-response-default">
- default
-
- </dt>
- <dd class="sw-response-default">
- <div class="row">
- <div class="col-md-12">
- <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
-
- </div>
- </div>
- <div class="row">
-
- <div class="col-md-6 sw-response-model">
- </div>
-
- </div> </dd>
- </dl>
- </section>
- </div>
- </div>
-
- <span id="path--external-system-esr-ems-list-"></span>
- <div id="operation--external-system-esr-ems-list-get" class="swagger--panel-operation-get panel">
- <div class="panel-heading">
- <div class="operation-summary">returns esr-ems-list</div>
- <h3 class="panel-title"><span class="operation-name">GET</span> <strong>/external-system/esr-ems-list</strong></h3>
- Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
- </div>
- <div class="panel-body">
- <section class="sw-operation-description">
- <p>returns esr-ems-list</p>
-
- </section>
-
- <section class="sw-responses">
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
-
- <dl>
- <dt class="sw-response-200">
- 200 OK
-
- </dt>
- <dd class="sw-response-200">
- <div class="row">
- <div class="col-md-12">
- <p>successful operation</p>
-
- </div>
- </div>
- <div class="row">
-
- <div class="col-md-6 sw-response-model">
- <div class="panel panel-definition">
-
- <div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/esr-ems-list">/esr-ems-list</a>
- </div>
- </div>
- </div>
-
- </div> </dd>
- <dt class="sw-response-default">
- default
-
- </dt>
- <dd class="sw-response-default">
- <div class="row">
- <div class="col-md-12">
- <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
-
- </div>
- </div>
- <div class="row">
-
- <div class="col-md-6 sw-response-model">
- </div>
-
- </div> </dd>
- </dl>
- </section>
- </div>
- </div>
-
- <span id="path--external-system-esr-ems-list-esr-ems--ems-id--"></span>
- <div id="operation--external-system-esr-ems-list-esr-ems--ems-id--get" class="swagger--panel-operation-get panel">
- <div class="panel-heading">
- <div class="operation-summary">returns esr-ems</div>
- <h3 class="panel-title"><span class="operation-name">GET</span> <strong>/external-system/esr-ems-list/esr-ems/{ems-id}</strong></h3>
- Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
- </div>
- <div class="panel-body">
- <section class="sw-operation-description">
- <p>returns esr-ems</p>
-
- </section>
- <section class="sw-request-params">
- <table class="table">
- <thead>
- <tr>
- <th class="sw-param-name"></th>
- <th class="sw-param-description"></th>
- <th class="sw-param-type"></th>
- <th class="sw-param-data-type"></th>
- <th class="sw-param-annotation"></th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>
- ems-id
- </td>
- <td>
- <p>Unique ID of EMS.</p>
- </td>
- <td>path</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- <span class="json-property-required"></span>
- </td>
- </tr>
- </tbody>
- </table>
- </section>
-
- <section class="sw-responses">
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
-
- <dl>
- <dt class="sw-response-200">
- 200 OK
-
- </dt>
- <dd class="sw-response-200">
- <div class="row">
- <div class="col-md-12">
- <p>successful operation</p>
-
- </div>
- </div>
- <div class="row">
-
- <div class="col-md-6 sw-response-model">
- <div class="panel panel-definition">
-
- <div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/esr-ems">/esr-ems</a>
- </div>
- </div>
- </div>
-
- </div> </dd>
- <dt class="sw-response-default">
- default
-
- </dt>
- <dd class="sw-response-default">
- <div class="row">
- <div class="col-md-12">
- <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
-
- </div>
- </div>
- <div class="row">
-
- <div class="col-md-6 sw-response-model">
- </div>
-
- </div> </dd>
- </dl>
- </section>
- </div>
- </div>
-
- <span id="path--external-system-esr-ems-list-esr-ems--ems-id--"></span>
- <div id="operation--external-system-esr-ems-list-esr-ems--ems-id--put" class="swagger--panel-operation-put panel">
- <div class="panel-heading">
- <div class="operation-summary">create or update an existing esr-ems</div>
- <h3 class="panel-title"><span class="operation-name">PUT</span> <strong>/external-system/esr-ems-list/esr-ems/{ems-id}</strong></h3>
- Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
- </div>
- <div class="panel-body">
- <section class="sw-operation-description">
- <p>create or update an existing esr-ems</p>
-
- </section>
- <section class="sw-request-body">
-
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
- <div class="row">
- <div class="col-md-6">
- <p><p>esr-ems object that needs to be created or updated</p>
- </p>
- </div>
- <div class="col-md-6 sw-request-model">
- <div class="panel panel-definition">
- <div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/esr-ems">/esr-ems</a>
- </div>
- </div></div>
- </div>
- </section>
- <section class="sw-request-params">
- <table class="table">
- <thead>
- <tr>
- <th class="sw-param-name"></th>
- <th class="sw-param-description"></th>
- <th class="sw-param-type"></th>
- <th class="sw-param-data-type"></th>
- <th class="sw-param-annotation"></th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>
- ems-id
- </td>
- <td>
- <p>Unique ID of EMS.</p>
- </td>
- <td>path</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- <span class="json-property-required"></span>
- </td>
- </tr>
- </tbody>
- </table>
- </section>
-
- <section class="sw-responses">
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
-
- <dl>
- <dt class="sw-response-default">
- default
-
- </dt>
- <dd class="sw-response-default">
- <div class="row">
- <div class="col-md-12">
- <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
-
- </div>
- </div>
- <div class="row">
-
- <div class="col-md-6 sw-response-model">
- </div>
-
- </div> </dd>
- </dl>
- </section>
- </div>
- </div>
-
- <span id="path--external-system-esr-ems-list-esr-ems--ems-id--"></span>
- <div id="operation--external-system-esr-ems-list-esr-ems--ems-id--delete" class="swagger--panel-operation-delete panel">
- <div class="panel-heading">
- <div class="operation-summary">delete an existing esr-ems</div>
- <h3 class="panel-title"><span class="operation-name">DELETE</span> <strong>/external-system/esr-ems-list/esr-ems/{ems-id}</strong></h3>
- Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
- </div>
- <div class="panel-body">
- <section class="sw-operation-description">
- <p>delete an existing esr-ems</p>
-
- </section>
- <section class="sw-request-body">
-
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
- </section>
- <section class="sw-request-params">
- <table class="table">
- <thead>
- <tr>
- <th class="sw-param-name"></th>
- <th class="sw-param-description"></th>
- <th class="sw-param-type"></th>
- <th class="sw-param-data-type"></th>
- <th class="sw-param-annotation"></th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>
- ems-id
+ hostname
</td>
<td>
- <p>Unique ID of EMS.</p>
+ <p>Value from executing hostname on the compute node.</p>
</td>
<td>path</td>
<td>
@@ -54201,22 +61178,6 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<span class="json-property-required"></span>
</td>
</tr>
- <tr>
- <td>
- resource-version
- </td>
- <td>
- <p>resource-version for concurrency</p>
- </td>
- <td>query</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- <span class="json-property-required"></span>
- </td>
- </tr>
</tbody>
</table>
</section>
@@ -54248,50 +61209,19 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</div>
- <span id="path--external-system-esr-ems-list-esr-ems--ems-id--esr-system-info-list-"></span>
- <div id="operation--external-system-esr-ems-list-esr-ems--ems-id--esr-system-info-list-get" class="swagger--panel-operation-get panel">
+ <span id="path--cloud-infrastructure-virtual-data-centers-"></span>
+ <div id="operation--cloud-infrastructure-virtual-data-centers-get" class="swagger--panel-operation-get panel">
<div class="panel-heading">
- <div class="operation-summary">returns esr-system-info-list</div>
- <h3 class="panel-title"><span class="operation-name">GET</span> <strong>/external-system/esr-ems-list/esr-ems/{ems-id}/esr-system-info-list</strong></h3>
+ <div class="operation-summary">returns virtual-data-centers</div>
+ <h3 class="panel-title"><span class="operation-name">GET</span> <strong>/cloud-infrastructure/virtual-data-centers</strong></h3>
Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
</div>
<div class="panel-body">
<section class="sw-operation-description">
- <p>returns esr-system-info-list</p>
+ <p>returns virtual-data-centers</p>
</section>
- <section class="sw-request-params">
- <table class="table">
- <thead>
- <tr>
- <th class="sw-param-name"></th>
- <th class="sw-param-description"></th>
- <th class="sw-param-type"></th>
- <th class="sw-param-data-type"></th>
- <th class="sw-param-annotation"></th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>
- ems-id
- </td>
- <td>
- <p>Unique ID of EMS.</p>
- </td>
- <td>path</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- <span class="json-property-required"></span>
- </td>
- </tr>
- </tbody>
- </table>
- </section>
<section class="sw-responses">
<p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
@@ -54315,7 +61245,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/esr-system-info-list">/esr-system-info-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/virtual-data-centers">/virtual-data-centers</a>
</div>
</div>
</div>
@@ -54343,17 +61273,17 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</div>
- <span id="path--external-system-esr-ems-list-esr-ems--ems-id--esr-system-info-list-esr-system-info--esr-system-info-id--"></span>
- <div id="operation--external-system-esr-ems-list-esr-ems--ems-id--esr-system-info-list-esr-system-info--esr-system-info-id--get" class="swagger--panel-operation-get panel">
+ <span id="path--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--"></span>
+ <div id="operation--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--get" class="swagger--panel-operation-get panel">
<div class="panel-heading">
- <div class="operation-summary">returns esr-system-info</div>
- <h3 class="panel-title"><span class="operation-name">GET</span> <strong>/external-system/esr-ems-list/esr-ems/{ems-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}</strong></h3>
+ <div class="operation-summary">returns virtual-data-center</div>
+ <h3 class="panel-title"><span class="operation-name">GET</span> <strong>/cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}</strong></h3>
Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
</div>
<div class="panel-body">
<section class="sw-operation-description">
- <p>returns esr-system-info</p>
+ <p>returns virtual-data-center</p>
</section>
<section class="sw-request-params">
@@ -54370,26 +61300,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<tbody>
<tr>
<td>
- ems-id
- </td>
- <td>
- <p>Unique ID of EMS.</p>
- </td>
- <td>path</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- <span class="json-property-required"></span>
- </td>
- </tr>
- <tr>
- <td>
- esr-system-info-id
+ vdc-id
</td>
<td>
- <p>Unique ID of esr system info.</p>
+ <p>Unique ID of the vdc</p>
</td>
<td>path</td>
<td>
@@ -54402,25 +61316,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</tr>
<tr>
<td>
- system-name
- </td>
- <td>
- <p>name of external system.</p>
- </td>
- <td>query</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- </td>
- </tr>
- <tr>
- <td>
- system-type
+ vdc-name
</td>
<td>
- <p>it could be vim/vnfm/thirdparty-sdnc/ems-resource/ems-performance/ems-alarm.</p>
+ <p>Name of the virtual data center</p>
</td>
<td>query</td>
<td>
@@ -54456,7 +61355,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/esr-system-info">/esr-system-info</a>
+ <a class="json-schema-ref" href="#/getDefinitions/virtual-data-center">/virtual-data-center</a>
</div>
</div>
</div>
@@ -54484,17 +61383,17 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</div>
- <span id="path--external-system-esr-ems-list-esr-ems--ems-id--esr-system-info-list-esr-system-info--esr-system-info-id--"></span>
- <div id="operation--external-system-esr-ems-list-esr-ems--ems-id--esr-system-info-list-esr-system-info--esr-system-info-id--put" class="swagger--panel-operation-put panel">
+ <span id="path--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--"></span>
+ <div id="operation--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--put" class="swagger--panel-operation-put panel">
<div class="panel-heading">
- <div class="operation-summary">create or update an existing esr-system-info</div>
- <h3 class="panel-title"><span class="operation-name">PUT</span> <strong>/external-system/esr-ems-list/esr-ems/{ems-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}</strong></h3>
+ <div class="operation-summary">create or update an existing virtual-data-center</div>
+ <h3 class="panel-title"><span class="operation-name">PUT</span> <strong>/cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}</strong></h3>
Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
</div>
<div class="panel-body">
<section class="sw-operation-description">
- <p>create or update an existing esr-system-info</p>
+ <p>create or update an existing virtual-data-center</p>
</section>
<section class="sw-request-body">
@@ -54503,13 +61402,13 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>esr-system-info object that needs to be created or updated</p>
+ <p><p>virtual-data-center object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureVirtualDataCentersVirtualDataCenter.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/esr-system-info">/esr-system-info</a>
+ <a class="json-schema-ref" href="#/definitions/virtual-data-center">/virtual-data-center</a>
</div>
</div></div>
</div>
@@ -54528,119 +61427,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<tbody>
<tr>
<td>
- ems-id
- </td>
- <td>
- <p>Unique ID of EMS.</p>
- </td>
- <td>path</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- <span class="json-property-required"></span>
- </td>
- </tr>
- <tr>
- <td>
- esr-system-info-id
- </td>
- <td>
- <p>Unique ID of esr system info.</p>
- </td>
- <td>path</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- <span class="json-property-required"></span>
- </td>
- </tr>
- </tbody>
- </table>
- </section>
-
- <section class="sw-responses">
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
-
- <dl>
- <dt class="sw-response-default">
- default
-
- </dt>
- <dd class="sw-response-default">
- <div class="row">
- <div class="col-md-12">
- <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
-
- </div>
- </div>
- <div class="row">
-
- <div class="col-md-6 sw-response-model">
- </div>
-
- </div> </dd>
- </dl>
- </section>
- </div>
- </div>
-
- <span id="path--external-system-esr-ems-list-esr-ems--ems-id--esr-system-info-list-esr-system-info--esr-system-info-id--"></span>
- <div id="operation--external-system-esr-ems-list-esr-ems--ems-id--esr-system-info-list-esr-system-info--esr-system-info-id--delete" class="swagger--panel-operation-delete panel">
- <div class="panel-heading">
- <div class="operation-summary">delete an existing esr-system-info</div>
- <h3 class="panel-title"><span class="operation-name">DELETE</span> <strong>/external-system/esr-ems-list/esr-ems/{ems-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}</strong></h3>
- Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
- </div>
- <div class="panel-body">
- <section class="sw-operation-description">
- <p>delete an existing esr-system-info</p>
-
- </section>
- <section class="sw-request-body">
-
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
- </section>
- <section class="sw-request-params">
- <table class="table">
- <thead>
- <tr>
- <th class="sw-param-name"></th>
- <th class="sw-param-description"></th>
- <th class="sw-param-type"></th>
- <th class="sw-param-data-type"></th>
- <th class="sw-param-annotation"></th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>
- ems-id
- </td>
- <td>
- <p>Unique ID of EMS.</p>
- </td>
- <td>path</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- <span class="json-property-required"></span>
- </td>
- </tr>
- <tr>
- <td>
- esr-system-info-id
+ vdc-id
</td>
<td>
- <p>Unique ID of esr system info.</p>
+ <p>Unique ID of the vdc</p>
</td>
<td>path</td>
<td>
@@ -54651,22 +61441,6 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<span class="json-property-required"></span>
</td>
</tr>
- <tr>
- <td>
- resource-version
- </td>
- <td>
- <p>resource-version for concurrency</p>
- </td>
- <td>query</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- <span class="json-property-required"></span>
- </td>
- </tr>
</tbody>
</table>
</section>
@@ -54698,17 +61472,17 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</div>
- <span id="path--external-system-esr-ems-list-esr-ems--ems-id--esr-system-info-list-esr-system-info--esr-system-info-id--relationship-list-relationship-"></span>
- <div id="operation--external-system-esr-ems-list-esr-ems--ems-id--esr-system-info-list-esr-system-info--esr-system-info-id--relationship-list-relationship-put" class="swagger--panel-operation-put panel">
+ <span id="path--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--"></span>
+ <div id="operation--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--patch" class="swagger--panel-operation-patch panel">
<div class="panel-heading">
- <div class="operation-summary">see node definition for valid relationships</div>
- <h3 class="panel-title"><span class="operation-name">PUT</span> <strong>/external-system/esr-ems-list/esr-ems/{ems-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}/relationship-list/relationship</strong></h3>
+ <div class="operation-summary">update an existing virtual-data-center</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}</strong></h3>
Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
</div>
<div class="panel-body">
<section class="sw-operation-description">
- <p>see node definition for valid relationships</p>
+ <p>update an existing virtual-data-center</p>
</section>
<section class="sw-request-body">
@@ -54717,13 +61491,13 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>virtual-data-center object that needs to be created or updated.</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/relationship">/relationship</a>
+ <a class="json-schema-ref" href="#/patchDefinitions/virtual-data-center">/virtual-data-center</a>
</div>
</div></div>
</div>
@@ -54742,26 +61516,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<tbody>
<tr>
<td>
- ems-id
- </td>
- <td>
- <p>Unique ID of EMS.</p>
- </td>
- <td>path</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- <span class="json-property-required"></span>
- </td>
- </tr>
- <tr>
- <td>
- esr-system-info-id
+ vdc-id
</td>
<td>
- <p>Unique ID of esr system info.</p>
+ <p>Unique ID of the vdc</p>
</td>
<td>path</td>
<td>
@@ -54803,17 +61561,17 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</div>
- <span id="path--external-system-esr-ems-list-esr-ems--ems-id--esr-system-info-list-esr-system-info--esr-system-info-id--relationship-list-relationship-"></span>
- <div id="operation--external-system-esr-ems-list-esr-ems--ems-id--esr-system-info-list-esr-system-info--esr-system-info-id--relationship-list-relationship-delete" class="swagger--panel-operation-delete panel">
+ <span id="path--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--"></span>
+ <div id="operation--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
- <div class="operation-summary">delete an existing relationship</div>
- <h3 class="panel-title"><span class="operation-name">DELETE</span> <strong>/external-system/esr-ems-list/esr-ems/{ems-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}/relationship-list/relationship</strong></h3>
+ <div class="operation-summary">delete an existing virtual-data-center</div>
+ <h3 class="panel-title"><span class="operation-name">DELETE</span> <strong>/cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}</strong></h3>
Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
</div>
<div class="panel-body">
<section class="sw-operation-description">
- <p>delete an existing relationship</p>
+ <p>delete an existing virtual-data-center</p>
</section>
<section class="sw-request-body">
@@ -54835,10 +61593,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<tbody>
<tr>
<td>
- ems-id
+ vdc-id
</td>
<td>
- <p>Unique ID of EMS.</p>
+ <p>Unique ID of the vdc</p>
</td>
<td>path</td>
<td>
@@ -54851,12 +61609,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</tr>
<tr>
<td>
- esr-system-info-id
+ resource-version
</td>
<td>
- <p>Unique ID of esr system info.</p>
+ <p>resource-version for concurrency</p>
</td>
- <td>path</td>
+ <td>query</td>
<td>
<span class="json-property-type">string</span>
<span class="json-property-range" title="Value limits"></span>
@@ -54896,13 +61654,13 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</div>
- <span id="path--external-system-esr-ems-list-esr-ems--ems-id--relationship-list-relationship-"></span>
- <div id="operation--external-system-esr-ems-list-esr-ems--ems-id--relationship-list-relationship-put" class="swagger--panel-operation-put panel">
+ <span id="path--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--relationship-list-relationship-"></span>
+ <div id="operation--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--relationship-list-relationship-put" class="swagger--panel-operation-put panel">
<div class="panel-heading">
<div class="operation-summary">see node definition for valid relationships</div>
- <h3 class="panel-title"><span class="operation-name">PUT</span> <strong>/external-system/esr-ems-list/esr-ems/{ems-id}/relationship-list/relationship</strong></h3>
+ <h3 class="panel-title"><span class="operation-name">PUT</span> <strong>/cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}/relationship-list/relationship</strong></h3>
Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
</div>
<div class="panel-body">
<section class="sw-operation-description">
@@ -54915,7 +61673,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureVirtualDataCentersVirtualDataCenter.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -54940,10 +61698,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<tbody>
<tr>
<td>
- ems-id
+ vdc-id
</td>
<td>
- <p>Unique ID of EMS.</p>
+ <p>Unique ID of the vdc</p>
</td>
<td>path</td>
<td>
@@ -54985,13 +61743,13 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</div>
- <span id="path--external-system-esr-ems-list-esr-ems--ems-id--relationship-list-relationship-"></span>
- <div id="operation--external-system-esr-ems-list-esr-ems--ems-id--relationship-list-relationship-delete" class="swagger--panel-operation-delete panel">
+ <span id="path--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--relationship-list-relationship-"></span>
+ <div id="operation--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--relationship-list-relationship-delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing relationship</div>
- <h3 class="panel-title"><span class="operation-name">DELETE</span> <strong>/external-system/esr-ems-list/esr-ems/{ems-id}/relationship-list/relationship</strong></h3>
+ <h3 class="panel-title"><span class="operation-name">DELETE</span> <strong>/cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}/relationship-list/relationship</strong></h3>
Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
</div>
<div class="panel-body">
<section class="sw-operation-description">
@@ -55017,335 +61775,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<tbody>
<tr>
<td>
- ems-id
- </td>
- <td>
- <p>Unique ID of EMS.</p>
- </td>
- <td>path</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- <span class="json-property-required"></span>
- </td>
- </tr>
- </tbody>
- </table>
- </section>
-
- <section class="sw-responses">
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
-
- <dl>
- <dt class="sw-response-default">
- default
-
- </dt>
- <dd class="sw-response-default">
- <div class="row">
- <div class="col-md-12">
- <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
-
- </div>
- </div>
- <div class="row">
-
- <div class="col-md-6 sw-response-model">
- </div>
-
- </div> </dd>
- </dl>
- </section>
- </div>
- </div>
-
- <span id="path--external-system-esr-thirdparty-sdnc-list-"></span>
- <div id="operation--external-system-esr-thirdparty-sdnc-list-get" class="swagger--panel-operation-get panel">
- <div class="panel-heading">
- <div class="operation-summary">returns esr-thirdparty-sdnc-list</div>
- <h3 class="panel-title"><span class="operation-name">GET</span> <strong>/external-system/esr-thirdparty-sdnc-list</strong></h3>
- Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
- </div>
- <div class="panel-body">
- <section class="sw-operation-description">
- <p>returns esr-thirdparty-sdnc-list</p>
-
- </section>
-
- <section class="sw-responses">
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
-
- <dl>
- <dt class="sw-response-200">
- 200 OK
-
- </dt>
- <dd class="sw-response-200">
- <div class="row">
- <div class="col-md-12">
- <p>successful operation</p>
-
- </div>
- </div>
- <div class="row">
-
- <div class="col-md-6 sw-response-model">
- <div class="panel panel-definition">
-
- <div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/esr-thirdparty-sdnc-list">/esr-thirdparty-sdnc-list</a>
- </div>
- </div>
- </div>
-
- </div> </dd>
- <dt class="sw-response-default">
- default
-
- </dt>
- <dd class="sw-response-default">
- <div class="row">
- <div class="col-md-12">
- <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
-
- </div>
- </div>
- <div class="row">
-
- <div class="col-md-6 sw-response-model">
- </div>
-
- </div> </dd>
- </dl>
- </section>
- </div>
- </div>
-
- <span id="path--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--"></span>
- <div id="operation--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--get" class="swagger--panel-operation-get panel">
- <div class="panel-heading">
- <div class="operation-summary">returns esr-thirdparty-sdnc</div>
- <h3 class="panel-title"><span class="operation-name">GET</span> <strong>/external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/{thirdparty-sdnc-id}</strong></h3>
- Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
- </div>
- <div class="panel-body">
- <section class="sw-operation-description">
- <p>returns esr-thirdparty-sdnc</p>
-
- </section>
- <section class="sw-request-params">
- <table class="table">
- <thead>
- <tr>
- <th class="sw-param-name"></th>
- <th class="sw-param-description"></th>
- <th class="sw-param-type"></th>
- <th class="sw-param-data-type"></th>
- <th class="sw-param-annotation"></th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>
- thirdparty-sdnc-id
- </td>
- <td>
- <p>Unique ID of SDNC.</p>
- </td>
- <td>path</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- <span class="json-property-required"></span>
- </td>
- </tr>
- </tbody>
- </table>
- </section>
-
- <section class="sw-responses">
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
-
- <dl>
- <dt class="sw-response-200">
- 200 OK
-
- </dt>
- <dd class="sw-response-200">
- <div class="row">
- <div class="col-md-12">
- <p>successful operation</p>
-
- </div>
- </div>
- <div class="row">
-
- <div class="col-md-6 sw-response-model">
- <div class="panel panel-definition">
-
- <div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/esr-thirdparty-sdnc">/esr-thirdparty-sdnc</a>
- </div>
- </div>
- </div>
-
- </div> </dd>
- <dt class="sw-response-default">
- default
-
- </dt>
- <dd class="sw-response-default">
- <div class="row">
- <div class="col-md-12">
- <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
-
- </div>
- </div>
- <div class="row">
-
- <div class="col-md-6 sw-response-model">
- </div>
-
- </div> </dd>
- </dl>
- </section>
- </div>
- </div>
-
- <span id="path--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--"></span>
- <div id="operation--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--put" class="swagger--panel-operation-put panel">
- <div class="panel-heading">
- <div class="operation-summary">create or update an existing esr-thirdparty-sdnc</div>
- <h3 class="panel-title"><span class="operation-name">PUT</span> <strong>/external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/{thirdparty-sdnc-id}</strong></h3>
- Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
- </div>
- <div class="panel-body">
- <section class="sw-operation-description">
- <p>create or update an existing esr-thirdparty-sdnc</p>
-
- </section>
- <section class="sw-request-body">
-
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
- <div class="row">
- <div class="col-md-6">
- <p><p>esr-thirdparty-sdnc object that needs to be created or updated</p>
- </p>
- </div>
- <div class="col-md-6 sw-request-model">
- <div class="panel panel-definition">
- <div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/esr-thirdparty-sdnc">/esr-thirdparty-sdnc</a>
- </div>
- </div></div>
- </div>
- </section>
- <section class="sw-request-params">
- <table class="table">
- <thead>
- <tr>
- <th class="sw-param-name"></th>
- <th class="sw-param-description"></th>
- <th class="sw-param-type"></th>
- <th class="sw-param-data-type"></th>
- <th class="sw-param-annotation"></th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>
- thirdparty-sdnc-id
- </td>
- <td>
- <p>Unique ID of SDNC.</p>
- </td>
- <td>path</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- <span class="json-property-required"></span>
- </td>
- </tr>
- </tbody>
- </table>
- </section>
-
- <section class="sw-responses">
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
-
- <dl>
- <dt class="sw-response-default">
- default
-
- </dt>
- <dd class="sw-response-default">
- <div class="row">
- <div class="col-md-12">
- <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
-
- </div>
- </div>
- <div class="row">
-
- <div class="col-md-6 sw-response-model">
- </div>
-
- </div> </dd>
- </dl>
- </section>
- </div>
- </div>
-
- <span id="path--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--"></span>
- <div id="operation--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--delete" class="swagger--panel-operation-delete panel">
- <div class="panel-heading">
- <div class="operation-summary">delete an existing esr-thirdparty-sdnc</div>
- <h3 class="panel-title"><span class="operation-name">DELETE</span> <strong>/external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/{thirdparty-sdnc-id}</strong></h3>
- Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
- </div>
- <div class="panel-body">
- <section class="sw-operation-description">
- <p>delete an existing esr-thirdparty-sdnc</p>
-
- </section>
- <section class="sw-request-body">
-
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
- </section>
- <section class="sw-request-params">
- <table class="table">
- <thead>
- <tr>
- <th class="sw-param-name"></th>
- <th class="sw-param-description"></th>
- <th class="sw-param-type"></th>
- <th class="sw-param-data-type"></th>
- <th class="sw-param-annotation"></th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>
- thirdparty-sdnc-id
+ vdc-id
</td>
<td>
- <p>Unique ID of SDNC.</p>
+ <p>Unique ID of the vdc</p>
</td>
<td>path</td>
<td>
@@ -55356,22 +61789,6 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<span class="json-property-required"></span>
</td>
</tr>
- <tr>
- <td>
- resource-version
- </td>
- <td>
- <p>resource-version for concurrency</p>
- </td>
- <td>query</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- <span class="json-property-required"></span>
- </td>
- </tr>
</tbody>
</table>
</section>
@@ -55403,50 +61820,19 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</div>
- <span id="path--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--esr-system-info-list-"></span>
- <div id="operation--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--esr-system-info-list-get" class="swagger--panel-operation-get panel">
+ <span id="path--network-configurations-"></span>
+ <div id="operation--network-configurations-get" class="swagger--panel-operation-get panel">
<div class="panel-heading">
- <div class="operation-summary">returns esr-system-info-list</div>
- <h3 class="panel-title"><span class="operation-name">GET</span> <strong>/external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/{thirdparty-sdnc-id}/esr-system-info-list</strong></h3>
+ <div class="operation-summary">returns configurations</div>
+ <h3 class="panel-title"><span class="operation-name">GET</span> <strong>/network/configurations</strong></h3>
Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
+ <a href="#tag-Network">Network</a>
</div>
<div class="panel-body">
<section class="sw-operation-description">
- <p>returns esr-system-info-list</p>
+ <p>returns configurations</p>
</section>
- <section class="sw-request-params">
- <table class="table">
- <thead>
- <tr>
- <th class="sw-param-name"></th>
- <th class="sw-param-description"></th>
- <th class="sw-param-type"></th>
- <th class="sw-param-data-type"></th>
- <th class="sw-param-annotation"></th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>
- thirdparty-sdnc-id
- </td>
- <td>
- <p>Unique ID of SDNC.</p>
- </td>
- <td>path</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- <span class="json-property-required"></span>
- </td>
- </tr>
- </tbody>
- </table>
- </section>
<section class="sw-responses">
<p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
@@ -55470,7 +61856,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/esr-system-info-list">/esr-system-info-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/configurations">/configurations</a>
</div>
</div>
</div>
@@ -55498,17 +61884,17 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</div>
- <span id="path--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--esr-system-info-list-esr-system-info--esr-system-info-id--"></span>
- <div id="operation--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--esr-system-info-list-esr-system-info--esr-system-info-id--get" class="swagger--panel-operation-get panel">
+ <span id="path--network-configurations-configuration--configuration-id--"></span>
+ <div id="operation--network-configurations-configuration--configuration-id--get" class="swagger--panel-operation-get panel">
<div class="panel-heading">
- <div class="operation-summary">returns esr-system-info</div>
- <h3 class="panel-title"><span class="operation-name">GET</span> <strong>/external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/{thirdparty-sdnc-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}</strong></h3>
+ <div class="operation-summary">returns configuration</div>
+ <h3 class="panel-title"><span class="operation-name">GET</span> <strong>/network/configurations/configuration/{configuration-id}</strong></h3>
Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
+ <a href="#tag-Network">Network</a>
</div>
<div class="panel-body">
<section class="sw-operation-description">
- <p>returns esr-system-info</p>
+ <p>returns configuration</p>
</section>
<section class="sw-request-params">
@@ -55525,26 +61911,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<tbody>
<tr>
<td>
- thirdparty-sdnc-id
- </td>
- <td>
- <p>Unique ID of SDNC.</p>
- </td>
- <td>path</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- <span class="json-property-required"></span>
- </td>
- </tr>
- <tr>
- <td>
- esr-system-info-id
+ configuration-id
</td>
<td>
- <p>Unique ID of esr system info.</p>
+ <p>UUID assigned to configuration.</p>
</td>
<td>path</td>
<td>
@@ -55557,10 +61927,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</tr>
<tr>
<td>
- system-name
+ model-invariant-id
</td>
<td>
- <p>name of external system.</p>
+ <p>the ASDC model id for this resource or service model.</p>
</td>
<td>query</td>
<td>
@@ -55572,10 +61942,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</tr>
<tr>
<td>
- system-type
+ model-version-id
</td>
<td>
- <p>it could be vim/vnfm/thirdparty-sdnc/ems-resource/ems-performance/ems-alarm.</p>
+ <p>the ASDC model version for this resource or service model.</p>
</td>
<td>query</td>
<td>
@@ -55611,7 +61981,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/esr-system-info">/esr-system-info</a>
+ <a class="json-schema-ref" href="#/getDefinitions/configuration">/configuration</a>
</div>
</div>
</div>
@@ -55639,231 +62009,17 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</div>
- <span id="path--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--esr-system-info-list-esr-system-info--esr-system-info-id--"></span>
- <div id="operation--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--esr-system-info-list-esr-system-info--esr-system-info-id--put" class="swagger--panel-operation-put panel">
- <div class="panel-heading">
- <div class="operation-summary">create or update an existing esr-system-info</div>
- <h3 class="panel-title"><span class="operation-name">PUT</span> <strong>/external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/{thirdparty-sdnc-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}</strong></h3>
- Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
- </div>
- <div class="panel-body">
- <section class="sw-operation-description">
- <p>create or update an existing esr-system-info</p>
-
- </section>
- <section class="sw-request-body">
-
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
- <div class="row">
- <div class="col-md-6">
- <p><p>esr-system-info object that needs to be created or updated</p>
- </p>
- </div>
- <div class="col-md-6 sw-request-model">
- <div class="panel panel-definition">
- <div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/esr-system-info">/esr-system-info</a>
- </div>
- </div></div>
- </div>
- </section>
- <section class="sw-request-params">
- <table class="table">
- <thead>
- <tr>
- <th class="sw-param-name"></th>
- <th class="sw-param-description"></th>
- <th class="sw-param-type"></th>
- <th class="sw-param-data-type"></th>
- <th class="sw-param-annotation"></th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>
- thirdparty-sdnc-id
- </td>
- <td>
- <p>Unique ID of SDNC.</p>
- </td>
- <td>path</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- <span class="json-property-required"></span>
- </td>
- </tr>
- <tr>
- <td>
- esr-system-info-id
- </td>
- <td>
- <p>Unique ID of esr system info.</p>
- </td>
- <td>path</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- <span class="json-property-required"></span>
- </td>
- </tr>
- </tbody>
- </table>
- </section>
-
- <section class="sw-responses">
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
-
- <dl>
- <dt class="sw-response-default">
- default
-
- </dt>
- <dd class="sw-response-default">
- <div class="row">
- <div class="col-md-12">
- <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
-
- </div>
- </div>
- <div class="row">
-
- <div class="col-md-6 sw-response-model">
- </div>
-
- </div> </dd>
- </dl>
- </section>
- </div>
- </div>
-
- <span id="path--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--esr-system-info-list-esr-system-info--esr-system-info-id--"></span>
- <div id="operation--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--esr-system-info-list-esr-system-info--esr-system-info-id--delete" class="swagger--panel-operation-delete panel">
+ <span id="path--network-configurations-configuration--configuration-id--"></span>
+ <div id="operation--network-configurations-configuration--configuration-id--put" class="swagger--panel-operation-put panel">
<div class="panel-heading">
- <div class="operation-summary">delete an existing esr-system-info</div>
- <h3 class="panel-title"><span class="operation-name">DELETE</span> <strong>/external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/{thirdparty-sdnc-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}</strong></h3>
+ <div class="operation-summary">create or update an existing configuration</div>
+ <h3 class="panel-title"><span class="operation-name">PUT</span> <strong>/network/configurations/configuration/{configuration-id}</strong></h3>
Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
- </div>
- <div class="panel-body">
- <section class="sw-operation-description">
- <p>delete an existing esr-system-info</p>
-
- </section>
- <section class="sw-request-body">
-
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
- </section>
- <section class="sw-request-params">
- <table class="table">
- <thead>
- <tr>
- <th class="sw-param-name"></th>
- <th class="sw-param-description"></th>
- <th class="sw-param-type"></th>
- <th class="sw-param-data-type"></th>
- <th class="sw-param-annotation"></th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>
- thirdparty-sdnc-id
- </td>
- <td>
- <p>Unique ID of SDNC.</p>
- </td>
- <td>path</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- <span class="json-property-required"></span>
- </td>
- </tr>
- <tr>
- <td>
- esr-system-info-id
- </td>
- <td>
- <p>Unique ID of esr system info.</p>
- </td>
- <td>path</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- <span class="json-property-required"></span>
- </td>
- </tr>
- <tr>
- <td>
- resource-version
- </td>
- <td>
- <p>resource-version for concurrency</p>
- </td>
- <td>query</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- <span class="json-property-required"></span>
- </td>
- </tr>
- </tbody>
- </table>
- </section>
-
- <section class="sw-responses">
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
-
- <dl>
- <dt class="sw-response-default">
- default
-
- </dt>
- <dd class="sw-response-default">
- <div class="row">
- <div class="col-md-12">
- <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
-
- </div>
- </div>
- <div class="row">
-
- <div class="col-md-6 sw-response-model">
- </div>
-
- </div> </dd>
- </dl>
- </section>
- </div>
- </div>
-
- <span id="path--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--esr-system-info-list-esr-system-info--esr-system-info-id--relationship-list-relationship-"></span>
- <div id="operation--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--esr-system-info-list-esr-system-info--esr-system-info-id--relationship-list-relationship-put" class="swagger--panel-operation-put panel">
- <div class="panel-heading">
- <div class="operation-summary">see node definition for valid relationships</div>
- <h3 class="panel-title"><span class="operation-name">PUT</span> <strong>/external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/{thirdparty-sdnc-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}/relationship-list/relationship</strong></h3>
- Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
+ <a href="#tag-Network">Network</a>
</div>
<div class="panel-body">
<section class="sw-operation-description">
- <p>see node definition for valid relationships</p>
+ <p>create or update an existing configuration</p>
</section>
<section class="sw-request-body">
@@ -55872,13 +62028,13 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>configuration object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkConfigurationsConfiguration.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/relationship">/relationship</a>
+ <a class="json-schema-ref" href="#/definitions/configuration">/configuration</a>
</div>
</div></div>
</div>
@@ -55897,26 +62053,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<tbody>
<tr>
<td>
- thirdparty-sdnc-id
- </td>
- <td>
- <p>Unique ID of SDNC.</p>
- </td>
- <td>path</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- <span class="json-property-required"></span>
- </td>
- </tr>
- <tr>
- <td>
- esr-system-info-id
+ configuration-id
</td>
<td>
- <p>Unique ID of esr system info.</p>
+ <p>UUID assigned to configuration.</p>
</td>
<td>path</td>
<td>
@@ -55958,110 +62098,17 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</div>
- <span id="path--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--esr-system-info-list-esr-system-info--esr-system-info-id--relationship-list-relationship-"></span>
- <div id="operation--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--esr-system-info-list-esr-system-info--esr-system-info-id--relationship-list-relationship-delete" class="swagger--panel-operation-delete panel">
+ <span id="path--network-configurations-configuration--configuration-id--"></span>
+ <div id="operation--network-configurations-configuration--configuration-id--patch" class="swagger--panel-operation-patch panel">
<div class="panel-heading">
- <div class="operation-summary">delete an existing relationship</div>
- <h3 class="panel-title"><span class="operation-name">DELETE</span> <strong>/external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/{thirdparty-sdnc-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}/relationship-list/relationship</strong></h3>
+ <div class="operation-summary">update an existing configuration</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/configurations/configuration/{configuration-id}</strong></h3>
Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
- </div>
- <div class="panel-body">
- <section class="sw-operation-description">
- <p>delete an existing relationship</p>
-
- </section>
- <section class="sw-request-body">
-
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
- </section>
- <section class="sw-request-params">
- <table class="table">
- <thead>
- <tr>
- <th class="sw-param-name"></th>
- <th class="sw-param-description"></th>
- <th class="sw-param-type"></th>
- <th class="sw-param-data-type"></th>
- <th class="sw-param-annotation"></th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>
- thirdparty-sdnc-id
- </td>
- <td>
- <p>Unique ID of SDNC.</p>
- </td>
- <td>path</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- <span class="json-property-required"></span>
- </td>
- </tr>
- <tr>
- <td>
- esr-system-info-id
- </td>
- <td>
- <p>Unique ID of esr system info.</p>
- </td>
- <td>path</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- <span class="json-property-required"></span>
- </td>
- </tr>
- </tbody>
- </table>
- </section>
-
- <section class="sw-responses">
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
-
- <dl>
- <dt class="sw-response-default">
- default
-
- </dt>
- <dd class="sw-response-default">
- <div class="row">
- <div class="col-md-12">
- <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
-
- </div>
- </div>
- <div class="row">
-
- <div class="col-md-6 sw-response-model">
- </div>
-
- </div> </dd>
- </dl>
- </section>
- </div>
- </div>
-
- <span id="path--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--relationship-list-relationship-"></span>
- <div id="operation--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--relationship-list-relationship-put" class="swagger--panel-operation-put panel">
- <div class="panel-heading">
- <div class="operation-summary">see node definition for valid relationships</div>
- <h3 class="panel-title"><span class="operation-name">PUT</span> <strong>/external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/{thirdparty-sdnc-id}/relationship-list/relationship</strong></h3>
- Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
+ <a href="#tag-Network">Network</a>
</div>
<div class="panel-body">
<section class="sw-operation-description">
- <p>see node definition for valid relationships</p>
+ <p>update an existing configuration</p>
</section>
<section class="sw-request-body">
@@ -56070,13 +62117,13 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>configuration object that needs to be created or updated.</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/relationship">/relationship</a>
+ <a class="json-schema-ref" href="#/patchDefinitions/configuration">/configuration</a>
</div>
</div></div>
</div>
@@ -56095,10 +62142,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<tbody>
<tr>
<td>
- thirdparty-sdnc-id
+ configuration-id
</td>
<td>
- <p>Unique ID of SDNC.</p>
+ <p>UUID assigned to configuration.</p>
</td>
<td>path</td>
<td>
@@ -56140,17 +62187,17 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</div>
- <span id="path--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--relationship-list-relationship-"></span>
- <div id="operation--external-system-esr-thirdparty-sdnc-list-esr-thirdparty-sdnc--thirdparty-sdnc-id--relationship-list-relationship-delete" class="swagger--panel-operation-delete panel">
+ <span id="path--network-configurations-configuration--configuration-id--"></span>
+ <div id="operation--network-configurations-configuration--configuration-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
- <div class="operation-summary">delete an existing relationship</div>
- <h3 class="panel-title"><span class="operation-name">DELETE</span> <strong>/external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/{thirdparty-sdnc-id}/relationship-list/relationship</strong></h3>
+ <div class="operation-summary">delete an existing configuration</div>
+ <h3 class="panel-title"><span class="operation-name">DELETE</span> <strong>/network/configurations/configuration/{configuration-id}</strong></h3>
Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
+ <a href="#tag-Network">Network</a>
</div>
<div class="panel-body">
<section class="sw-operation-description">
- <p>delete an existing relationship</p>
+ <p>delete an existing configuration</p>
</section>
<section class="sw-request-body">
@@ -56172,146 +62219,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<tbody>
<tr>
<td>
- thirdparty-sdnc-id
- </td>
- <td>
- <p>Unique ID of SDNC.</p>
- </td>
- <td>path</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- <span class="json-property-required"></span>
- </td>
- </tr>
- </tbody>
- </table>
- </section>
-
- <section class="sw-responses">
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
-
- <dl>
- <dt class="sw-response-default">
- default
-
- </dt>
- <dd class="sw-response-default">
- <div class="row">
- <div class="col-md-12">
- <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
-
- </div>
- </div>
- <div class="row">
-
- <div class="col-md-6 sw-response-model">
- </div>
-
- </div> </dd>
- </dl>
- </section>
- </div>
- </div>
-
- <span id="path--external-system-esr-vnfm-list-"></span>
- <div id="operation--external-system-esr-vnfm-list-get" class="swagger--panel-operation-get panel">
- <div class="panel-heading">
- <div class="operation-summary">returns esr-vnfm-list</div>
- <h3 class="panel-title"><span class="operation-name">GET</span> <strong>/external-system/esr-vnfm-list</strong></h3>
- Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
- </div>
- <div class="panel-body">
- <section class="sw-operation-description">
- <p>returns esr-vnfm-list</p>
-
- </section>
-
- <section class="sw-responses">
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
-
- <dl>
- <dt class="sw-response-200">
- 200 OK
-
- </dt>
- <dd class="sw-response-200">
- <div class="row">
- <div class="col-md-12">
- <p>successful operation</p>
-
- </div>
- </div>
- <div class="row">
-
- <div class="col-md-6 sw-response-model">
- <div class="panel panel-definition">
-
- <div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/esr-vnfm-list">/esr-vnfm-list</a>
- </div>
- </div>
- </div>
-
- </div> </dd>
- <dt class="sw-response-default">
- default
-
- </dt>
- <dd class="sw-response-default">
- <div class="row">
- <div class="col-md-12">
- <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
-
- </div>
- </div>
- <div class="row">
-
- <div class="col-md-6 sw-response-model">
- </div>
-
- </div> </dd>
- </dl>
- </section>
- </div>
- </div>
-
- <span id="path--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--"></span>
- <div id="operation--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--get" class="swagger--panel-operation-get panel">
- <div class="panel-heading">
- <div class="operation-summary">returns esr-vnfm</div>
- <h3 class="panel-title"><span class="operation-name">GET</span> <strong>/external-system/esr-vnfm-list/esr-vnfm/{vnfm-id}</strong></h3>
- Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
- </div>
- <div class="panel-body">
- <section class="sw-operation-description">
- <p>returns esr-vnfm</p>
-
- </section>
- <section class="sw-request-params">
- <table class="table">
- <thead>
- <tr>
- <th class="sw-param-name"></th>
- <th class="sw-param-description"></th>
- <th class="sw-param-type"></th>
- <th class="sw-param-data-type"></th>
- <th class="sw-param-annotation"></th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>
- vnfm-id
+ configuration-id
</td>
<td>
- <p>Unique ID of VNFM.</p>
+ <p>UUID assigned to configuration.</p>
</td>
<td>path</td>
<td>
@@ -56322,110 +62233,14 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<span class="json-property-required"></span>
</td>
</tr>
- </tbody>
- </table>
- </section>
-
- <section class="sw-responses">
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
-
- <dl>
- <dt class="sw-response-200">
- 200 OK
-
- </dt>
- <dd class="sw-response-200">
- <div class="row">
- <div class="col-md-12">
- <p>successful operation</p>
-
- </div>
- </div>
- <div class="row">
-
- <div class="col-md-6 sw-response-model">
- <div class="panel panel-definition">
-
- <div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/esr-vnfm">/esr-vnfm</a>
- </div>
- </div>
- </div>
-
- </div> </dd>
- <dt class="sw-response-default">
- default
-
- </dt>
- <dd class="sw-response-default">
- <div class="row">
- <div class="col-md-12">
- <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
-
- </div>
- </div>
- <div class="row">
-
- <div class="col-md-6 sw-response-model">
- </div>
-
- </div> </dd>
- </dl>
- </section>
- </div>
- </div>
-
- <span id="path--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--"></span>
- <div id="operation--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--put" class="swagger--panel-operation-put panel">
- <div class="panel-heading">
- <div class="operation-summary">create or update an existing esr-vnfm</div>
- <h3 class="panel-title"><span class="operation-name">PUT</span> <strong>/external-system/esr-vnfm-list/esr-vnfm/{vnfm-id}</strong></h3>
- Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
- </div>
- <div class="panel-body">
- <section class="sw-operation-description">
- <p>create or update an existing esr-vnfm</p>
-
- </section>
- <section class="sw-request-body">
-
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
- <div class="row">
- <div class="col-md-6">
- <p><p>esr-vnfm object that needs to be created or updated</p>
- </p>
- </div>
- <div class="col-md-6 sw-request-model">
- <div class="panel panel-definition">
- <div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/esr-vnfm">/esr-vnfm</a>
- </div>
- </div></div>
- </div>
- </section>
- <section class="sw-request-params">
- <table class="table">
- <thead>
- <tr>
- <th class="sw-param-name"></th>
- <th class="sw-param-description"></th>
- <th class="sw-param-type"></th>
- <th class="sw-param-data-type"></th>
- <th class="sw-param-annotation"></th>
- </tr>
- </thead>
- <tbody>
<tr>
<td>
- vnfm-id
+ resource-version
</td>
<td>
- <p>Unique ID of VNFM.</p>
+ <p>resource-version for concurrency</p>
</td>
- <td>path</td>
+ <td>query</td>
<td>
<span class="json-property-type">string</span>
<span class="json-property-range" title="Value limits"></span>
@@ -56465,24 +62280,19 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</div>
- <span id="path--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--"></span>
- <div id="operation--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--delete" class="swagger--panel-operation-delete panel">
+ <span id="path--network-configurations-configuration--configuration-id--metadata-"></span>
+ <div id="operation--network-configurations-configuration--configuration-id--metadata-get" class="swagger--panel-operation-get panel">
<div class="panel-heading">
- <div class="operation-summary">delete an existing esr-vnfm</div>
- <h3 class="panel-title"><span class="operation-name">DELETE</span> <strong>/external-system/esr-vnfm-list/esr-vnfm/{vnfm-id}</strong></h3>
+ <div class="operation-summary">returns metadata</div>
+ <h3 class="panel-title"><span class="operation-name">GET</span> <strong>/network/configurations/configuration/{configuration-id}/metadata</strong></h3>
Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
+ <a href="#tag-Network">Network</a>
</div>
<div class="panel-body">
<section class="sw-operation-description">
- <p>delete an existing esr-vnfm</p>
+ <p>returns metadata</p>
</section>
- <section class="sw-request-body">
-
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
- </section>
<section class="sw-request-params">
<table class="table">
<thead>
@@ -56497,10 +62307,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<tbody>
<tr>
<td>
- vnfm-id
+ configuration-id
</td>
<td>
- <p>Unique ID of VNFM.</p>
+ <p>UUID assigned to configuration.</p>
</td>
<td>path</td>
<td>
@@ -56513,10 +62323,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</tr>
<tr>
<td>
- resource-version
+ model-invariant-id
</td>
<td>
- <p>resource-version for concurrency</p>
+ <p>the ASDC model id for this resource or service model.</p>
</td>
<td>query</td>
<td>
@@ -56524,79 +62334,21 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<span class="json-property-range" title="Value limits"></span>
</td>
<td>
- <span class="json-property-required"></span>
</td>
</tr>
- </tbody>
- </table>
- </section>
-
- <section class="sw-responses">
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
-
- <dl>
- <dt class="sw-response-default">
- default
-
- </dt>
- <dd class="sw-response-default">
- <div class="row">
- <div class="col-md-12">
- <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
-
- </div>
- </div>
- <div class="row">
-
- <div class="col-md-6 sw-response-model">
- </div>
-
- </div> </dd>
- </dl>
- </section>
- </div>
- </div>
-
- <span id="path--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--esr-system-info-list-"></span>
- <div id="operation--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--esr-system-info-list-get" class="swagger--panel-operation-get panel">
- <div class="panel-heading">
- <div class="operation-summary">returns esr-system-info-list</div>
- <h3 class="panel-title"><span class="operation-name">GET</span> <strong>/external-system/esr-vnfm-list/esr-vnfm/{vnfm-id}/esr-system-info-list</strong></h3>
- Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
- </div>
- <div class="panel-body">
- <section class="sw-operation-description">
- <p>returns esr-system-info-list</p>
-
- </section>
- <section class="sw-request-params">
- <table class="table">
- <thead>
- <tr>
- <th class="sw-param-name"></th>
- <th class="sw-param-description"></th>
- <th class="sw-param-type"></th>
- <th class="sw-param-data-type"></th>
- <th class="sw-param-annotation"></th>
- </tr>
- </thead>
- <tbody>
<tr>
<td>
- vnfm-id
+ model-version-id
</td>
<td>
- <p>Unique ID of VNFM.</p>
+ <p>the ASDC model version for this resource or service model.</p>
</td>
- <td>path</td>
+ <td>query</td>
<td>
<span class="json-property-type">string</span>
<span class="json-property-range" title="Value limits"></span>
</td>
<td>
- <span class="json-property-required"></span>
</td>
</tr>
</tbody>
@@ -56625,7 +62377,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/esr-system-info-list">/esr-system-info-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadata">/metadata</a>
</div>
</div>
</div>
@@ -56653,17 +62405,17 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</div>
- <span id="path--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--esr-system-info-list-esr-system-info--esr-system-info-id--"></span>
- <div id="operation--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--esr-system-info-list-esr-system-info--esr-system-info-id--get" class="swagger--panel-operation-get panel">
+ <span id="path--network-configurations-configuration--configuration-id--metadata-metadatum--metaname--"></span>
+ <div id="operation--network-configurations-configuration--configuration-id--metadata-metadatum--metaname--get" class="swagger--panel-operation-get panel">
<div class="panel-heading">
- <div class="operation-summary">returns esr-system-info</div>
- <h3 class="panel-title"><span class="operation-name">GET</span> <strong>/external-system/esr-vnfm-list/esr-vnfm/{vnfm-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}</strong></h3>
+ <div class="operation-summary">returns metadatum</div>
+ <h3 class="panel-title"><span class="operation-name">GET</span> <strong>/network/configurations/configuration/{configuration-id}/metadata/metadatum/{metaname}</strong></h3>
Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
+ <a href="#tag-Network">Network</a>
</div>
<div class="panel-body">
<section class="sw-operation-description">
- <p>returns esr-system-info</p>
+ <p>returns metadatum</p>
</section>
<section class="sw-request-params">
@@ -56680,10 +62432,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<tbody>
<tr>
<td>
- vnfm-id
+ configuration-id
</td>
<td>
- <p>Unique ID of VNFM.</p>
+ <p>UUID assigned to configuration.</p>
</td>
<td>path</td>
<td>
@@ -56696,10 +62448,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</tr>
<tr>
<td>
- esr-system-info-id
+ metaname
</td>
<td>
- <p>Unique ID of esr system info.</p>
</td>
<td>path</td>
<td>
@@ -56712,10 +62463,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</tr>
<tr>
<td>
- system-name
+ model-invariant-id
</td>
<td>
- <p>name of external system.</p>
+ <p>the ASDC model id for this resource or service model.</p>
</td>
<td>query</td>
<td>
@@ -56727,10 +62478,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</tr>
<tr>
<td>
- system-type
+ model-version-id
</td>
<td>
- <p>it could be vim/vnfm/thirdparty-sdnc/ems-resource/ems-performance/ems-alarm.</p>
+ <p>the ASDC model version for this resource or service model.</p>
</td>
<td>query</td>
<td>
@@ -56766,7 +62517,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/esr-system-info">/esr-system-info</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadatum">/metadatum</a>
</div>
</div>
</div>
@@ -56794,17 +62545,17 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</div>
- <span id="path--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--esr-system-info-list-esr-system-info--esr-system-info-id--"></span>
- <div id="operation--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--esr-system-info-list-esr-system-info--esr-system-info-id--put" class="swagger--panel-operation-put panel">
+ <span id="path--network-configurations-configuration--configuration-id--metadata-metadatum--metaname--"></span>
+ <div id="operation--network-configurations-configuration--configuration-id--metadata-metadatum--metaname--put" class="swagger--panel-operation-put panel">
<div class="panel-heading">
- <div class="operation-summary">create or update an existing esr-system-info</div>
- <h3 class="panel-title"><span class="operation-name">PUT</span> <strong>/external-system/esr-vnfm-list/esr-vnfm/{vnfm-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}</strong></h3>
+ <div class="operation-summary">create or update an existing metadatum</div>
+ <h3 class="panel-title"><span class="operation-name">PUT</span> <strong>/network/configurations/configuration/{configuration-id}/metadata/metadatum/{metaname}</strong></h3>
Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
+ <a href="#tag-Network">Network</a>
</div>
<div class="panel-body">
<section class="sw-operation-description">
- <p>create or update an existing esr-system-info</p>
+ <p>create or update an existing metadatum</p>
</section>
<section class="sw-request-body">
@@ -56813,13 +62564,13 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>esr-system-info object that needs to be created or updated</p>
+ <p><p>metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkConfigurationsConfigurationMetadataMetadatum.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/esr-system-info">/esr-system-info</a>
+ <a class="json-schema-ref" href="#/definitions/metadatum">/metadatum</a>
</div>
</div></div>
</div>
@@ -56838,10 +62589,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<tbody>
<tr>
<td>
- vnfm-id
+ configuration-id
</td>
<td>
- <p>Unique ID of VNFM.</p>
+ <p>UUID assigned to configuration.</p>
</td>
<td>path</td>
<td>
@@ -56854,10 +62605,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</tr>
<tr>
<td>
- esr-system-info-id
+ metaname
</td>
<td>
- <p>Unique ID of esr system info.</p>
</td>
<td>path</td>
<td>
@@ -56899,23 +62649,35 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</div>
- <span id="path--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--esr-system-info-list-esr-system-info--esr-system-info-id--"></span>
- <div id="operation--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--esr-system-info-list-esr-system-info--esr-system-info-id--delete" class="swagger--panel-operation-delete panel">
+ <span id="path--network-configurations-configuration--configuration-id--metadata-metadatum--metaname--"></span>
+ <div id="operation--network-configurations-configuration--configuration-id--metadata-metadatum--metaname--patch" class="swagger--panel-operation-patch panel">
<div class="panel-heading">
- <div class="operation-summary">delete an existing esr-system-info</div>
- <h3 class="panel-title"><span class="operation-name">DELETE</span> <strong>/external-system/esr-vnfm-list/esr-vnfm/{vnfm-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}</strong></h3>
+ <div class="operation-summary">update an existing metadatum</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/configurations/configuration/{configuration-id}/metadata/metadatum/{metaname}</strong></h3>
Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
+ <a href="#tag-Network">Network</a>
</div>
<div class="panel-body">
<section class="sw-operation-description">
- <p>delete an existing esr-system-info</p>
+ <p>update an existing metadatum</p>
</section>
<section class="sw-request-body">
<p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
</p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>metadatum object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/metadatum">/metadatum</a>
+ </div>
+ </div></div>
+ </div>
</section>
<section class="sw-request-params">
<table class="table">
@@ -56931,10 +62693,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<tbody>
<tr>
<td>
- vnfm-id
+ configuration-id
</td>
<td>
- <p>Unique ID of VNFM.</p>
+ <p>UUID assigned to configuration.</p>
</td>
<td>path</td>
<td>
@@ -56947,10 +62709,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</tr>
<tr>
<td>
- esr-system-info-id
+ metaname
</td>
<td>
- <p>Unique ID of esr system info.</p>
</td>
<td>path</td>
<td>
@@ -56961,22 +62722,6 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<span class="json-property-required"></span>
</td>
</tr>
- <tr>
- <td>
- resource-version
- </td>
- <td>
- <p>resource-version for concurrency</p>
- </td>
- <td>query</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- <span class="json-property-required"></span>
- </td>
- </tr>
</tbody>
</table>
</section>
@@ -57008,35 +62753,23 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</div>
- <span id="path--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--esr-system-info-list-esr-system-info--esr-system-info-id--relationship-list-relationship-"></span>
- <div id="operation--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--esr-system-info-list-esr-system-info--esr-system-info-id--relationship-list-relationship-put" class="swagger--panel-operation-put panel">
+ <span id="path--network-configurations-configuration--configuration-id--metadata-metadatum--metaname--"></span>
+ <div id="operation--network-configurations-configuration--configuration-id--metadata-metadatum--metaname--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
- <div class="operation-summary">see node definition for valid relationships</div>
- <h3 class="panel-title"><span class="operation-name">PUT</span> <strong>/external-system/esr-vnfm-list/esr-vnfm/{vnfm-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}/relationship-list/relationship</strong></h3>
+ <div class="operation-summary">delete an existing metadatum</div>
+ <h3 class="panel-title"><span class="operation-name">DELETE</span> <strong>/network/configurations/configuration/{configuration-id}/metadata/metadatum/{metaname}</strong></h3>
Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
+ <a href="#tag-Network">Network</a>
</div>
<div class="panel-body">
<section class="sw-operation-description">
- <p>see node definition for valid relationships</p>
+ <p>delete an existing metadatum</p>
</section>
<section class="sw-request-body">
<p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
</p>
- <div class="row">
- <div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
- </p>
- </div>
- <div class="col-md-6 sw-request-model">
- <div class="panel panel-definition">
- <div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/relationship">/relationship</a>
- </div>
- </div></div>
- </div>
</section>
<section class="sw-request-params">
<table class="table">
@@ -57052,26 +62785,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<tbody>
<tr>
<td>
- vnfm-id
- </td>
- <td>
- <p>Unique ID of VNFM.</p>
- </td>
- <td>path</td>
- <td>
- <span class="json-property-type">string</span>
- <span class="json-property-range" title="Value limits"></span>
- </td>
- <td>
- <span class="json-property-required"></span>
- </td>
- </tr>
- <tr>
- <td>
- esr-system-info-id
+ configuration-id
</td>
<td>
- <p>Unique ID of esr system info.</p>
+ <p>UUID assigned to configuration.</p>
</td>
<td>path</td>
<td>
@@ -57082,73 +62799,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<span class="json-property-required"></span>
</td>
</tr>
- </tbody>
- </table>
- </section>
-
- <section class="sw-responses">
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
-
- <dl>
- <dt class="sw-response-default">
- default
-
- </dt>
- <dd class="sw-response-default">
- <div class="row">
- <div class="col-md-12">
- <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
-
- </div>
- </div>
- <div class="row">
-
- <div class="col-md-6 sw-response-model">
- </div>
-
- </div> </dd>
- </dl>
- </section>
- </div>
- </div>
-
- <span id="path--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--esr-system-info-list-esr-system-info--esr-system-info-id--relationship-list-relationship-"></span>
- <div id="operation--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--esr-system-info-list-esr-system-info--esr-system-info-id--relationship-list-relationship-delete" class="swagger--panel-operation-delete panel">
- <div class="panel-heading">
- <div class="operation-summary">delete an existing relationship</div>
- <h3 class="panel-title"><span class="operation-name">DELETE</span> <strong>/external-system/esr-vnfm-list/esr-vnfm/{vnfm-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}/relationship-list/relationship</strong></h3>
- Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
- </div>
- <div class="panel-body">
- <section class="sw-operation-description">
- <p>delete an existing relationship</p>
-
- </section>
- <section class="sw-request-body">
-
- <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
- </p>
- </section>
- <section class="sw-request-params">
- <table class="table">
- <thead>
- <tr>
- <th class="sw-param-name"></th>
- <th class="sw-param-description"></th>
- <th class="sw-param-type"></th>
- <th class="sw-param-data-type"></th>
- <th class="sw-param-annotation"></th>
- </tr>
- </thead>
- <tbody>
<tr>
<td>
- vnfm-id
+ metaname
</td>
<td>
- <p>Unique ID of VNFM.</p>
</td>
<td>path</td>
<td>
@@ -57161,12 +62816,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</tr>
<tr>
<td>
- esr-system-info-id
+ resource-version
</td>
<td>
- <p>Unique ID of esr system info.</p>
+ <p>resource-version for concurrency</p>
</td>
- <td>path</td>
+ <td>query</td>
<td>
<span class="json-property-type">string</span>
<span class="json-property-range" title="Value limits"></span>
@@ -57206,13 +62861,13 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</div>
- <span id="path--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--relationship-list-relationship-"></span>
- <div id="operation--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--relationship-list-relationship-put" class="swagger--panel-operation-put panel">
+ <span id="path--network-configurations-configuration--configuration-id--relationship-list-relationship-"></span>
+ <div id="operation--network-configurations-configuration--configuration-id--relationship-list-relationship-put" class="swagger--panel-operation-put panel">
<div class="panel-heading">
<div class="operation-summary">see node definition for valid relationships</div>
- <h3 class="panel-title"><span class="operation-name">PUT</span> <strong>/external-system/esr-vnfm-list/esr-vnfm/{vnfm-id}/relationship-list/relationship</strong></h3>
+ <h3 class="panel-title"><span class="operation-name">PUT</span> <strong>/network/configurations/configuration/{configuration-id}/relationship-list/relationship</strong></h3>
Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
+ <a href="#tag-Network">Network</a>
</div>
<div class="panel-body">
<section class="sw-operation-description">
@@ -57225,7 +62880,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkConfigurationsConfiguration.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -57250,10 +62905,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<tbody>
<tr>
<td>
- vnfm-id
+ configuration-id
</td>
<td>
- <p>Unique ID of VNFM.</p>
+ <p>UUID assigned to configuration.</p>
</td>
<td>path</td>
<td>
@@ -57295,13 +62950,13 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</div>
- <span id="path--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--relationship-list-relationship-"></span>
- <div id="operation--external-system-esr-vnfm-list-esr-vnfm--vnfm-id--relationship-list-relationship-delete" class="swagger--panel-operation-delete panel">
+ <span id="path--network-configurations-configuration--configuration-id--relationship-list-relationship-"></span>
+ <div id="operation--network-configurations-configuration--configuration-id--relationship-list-relationship-delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing relationship</div>
- <h3 class="panel-title"><span class="operation-name">DELETE</span> <strong>/external-system/esr-vnfm-list/esr-vnfm/{vnfm-id}/relationship-list/relationship</strong></h3>
+ <h3 class="panel-title"><span class="operation-name">DELETE</span> <strong>/network/configurations/configuration/{configuration-id}/relationship-list/relationship</strong></h3>
Tags:
- <a href="#tag-ExternalSystem">ExternalSystem</a>
+ <a href="#tag-Network">Network</a>
</div>
<div class="panel-body">
<section class="sw-operation-description">
@@ -57327,10 +62982,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<tbody>
<tr>
<td>
- vnfm-id
+ configuration-id
</td>
<td>
- <p>Unique ID of VNFM.</p>
+ <p>UUID assigned to configuration.</p>
</td>
<td>path</td>
<td>
@@ -57408,7 +63063,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/generic-vnfs">/generic-vnfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/generic-vnfs">/generic-vnfs</a>
</div>
</div>
</div>
@@ -57756,7 +63411,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/generic-vnf">/generic-vnf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/generic-vnf">/generic-vnf</a>
</div>
</div>
</div>
@@ -57803,7 +63458,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>generic-vnf object that needs to be created or updated</p>
+ <p><p>generic-vnf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -57874,6 +63529,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing generic-vnf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing generic-vnf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>generic-vnf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/generic-vnf">/generic-vnf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing generic-vnf</div>
@@ -58286,7 +64030,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/entitlements">/entitlements</a>
+ <a class="json-schema-ref" href="#/getDefinitions/entitlements">/entitlements</a>
</div>
</div>
</div>
@@ -58666,7 +64410,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/entitlement">/entitlement</a>
+ <a class="json-schema-ref" href="#/getDefinitions/entitlement">/entitlement</a>
</div>
</div>
</div>
@@ -58713,7 +64457,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>entitlement object that needs to be created or updated</p>
+ <p><p>entitlement object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfEntitlementsEntitlement.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -58816,6 +64560,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing entitlement</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/entitlements/entitlement/{group-uuid}/{resource-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing entitlement</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>entitlement object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/entitlement">/entitlement</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ group-uuid
+ </td>
+ <td>
+ <p>Unique ID for the entitlement group the resource comes from, should be uuid.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ resource-uuid
+ </td>
+ <td>
+ <p>Unique ID of an entitlement resource.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing entitlement</div>
@@ -58959,7 +64824,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfEntitlementsEntitlement.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -59490,7 +65355,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -59899,7 +65764,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -59946,7 +65811,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -60033,6 +65898,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -60583,7 +66553,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -60630,7 +66600,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -60733,6 +66703,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -60876,7 +66967,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -61529,7 +67620,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -61576,7 +67667,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -61679,6 +67770,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -61822,7 +68034,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -62052,7 +68264,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -62612,7 +68824,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -63097,7 +69309,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -63144,7 +69356,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -63247,6 +69459,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -63390,7 +69723,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -63982,7 +70315,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -64437,7 +70770,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -64484,7 +70817,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -64587,6 +70920,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -65199,7 +71653,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -65246,7 +71700,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -65365,6 +71819,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -65524,7 +72115,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -66255,7 +72846,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -66302,7 +72893,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -66421,6 +73012,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -66580,7 +73308,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -66842,7 +73570,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -67373,7 +74101,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interfaces">/lag-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interfaces">/lag-interfaces</a>
</div>
</div>
</div>
@@ -67767,7 +74495,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interface">/lag-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interface">/lag-interface</a>
</div>
</div>
</div>
@@ -67814,7 +74542,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>lag-interface object that needs to be created or updated</p>
+ <p><p>lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -67901,6 +74629,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing lag-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing lag-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>lag-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/lag-interface">/lag-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing lag-interface</div>
@@ -68375,7 +75208,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -68830,7 +75663,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -68877,7 +75710,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -68980,6 +75813,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -69592,7 +76546,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -69639,7 +76593,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -69758,6 +76712,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -69917,7 +77008,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -70648,7 +77739,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -70695,7 +77786,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -70814,6 +77905,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -70973,7 +78201,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -71235,7 +78463,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -71873,7 +79101,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -72404,7 +79632,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -72451,7 +79679,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -72570,6 +79798,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -72729,7 +80094,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -73399,7 +80764,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -73900,7 +81265,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -73947,7 +81312,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -74066,6 +81431,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -74740,7 +82242,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -74787,7 +82289,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -74922,6 +82424,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -75097,7 +82752,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -75906,7 +83561,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -75953,7 +83608,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -76088,6 +83743,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -76263,7 +84071,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -76557,7 +84365,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -76819,7 +84627,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -77318,7 +85126,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/licenses">/licenses</a>
+ <a class="json-schema-ref" href="#/getDefinitions/licenses">/licenses</a>
</div>
</div>
</div>
@@ -77698,7 +85506,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/license">/license</a>
+ <a class="json-schema-ref" href="#/getDefinitions/license">/license</a>
</div>
</div>
</div>
@@ -77745,7 +85553,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>license object that needs to be created or updated</p>
+ <p><p>license object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLicensesLicense.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -77848,6 +85656,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--licenses-license--group-uuid---resource-uuid--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--licenses-license--group-uuid---resource-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing license</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/licenses/license/{group-uuid}/{resource-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing license</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>license object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/license">/license</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ group-uuid
+ </td>
+ <td>
+ <p>Unique ID for the license group the resource belongs to, should be uuid.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ resource-uuid
+ </td>
+ <td>
+ <p>Unique ID of a license resource.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--licenses-license--group-uuid---resource-uuid--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--licenses-license--group-uuid---resource-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing license</div>
@@ -77991,7 +85920,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLicensesLicense.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -78221,7 +86150,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -78688,7 +86617,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vf-modules">/vf-modules</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vf-modules">/vf-modules</a>
</div>
</div>
</div>
@@ -79157,7 +87086,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vf-module">/vf-module</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vf-module">/vf-module</a>
</div>
</div>
</div>
@@ -79204,7 +87133,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vf-module object that needs to be created or updated</p>
+ <p><p>vf-module object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfVfModulesVfModule.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -79291,6 +87220,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--vf-modules-vf-module--vf-module-id--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--vf-modules-vf-module--vf-module-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vf-module</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/vf-modules/vf-module/{vf-module-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vf-module</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vf-module object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vf-module">/vf-module</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vf-module-id
+ </td>
+ <td>
+ <p>Unique ID of vf-module.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--vf-modules-vf-module--vf-module-id--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--vf-modules-vf-module--vf-module-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vf-module</div>
@@ -79418,7 +87452,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfVfModulesVfModule.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -79633,7 +87667,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/instance-groups">/instance-groups</a>
+ <a class="json-schema-ref" href="#/getDefinitions/instance-groups">/instance-groups</a>
</div>
</div>
</div>
@@ -79773,7 +87807,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/instance-group">/instance-group</a>
+ <a class="json-schema-ref" href="#/getDefinitions/instance-group">/instance-group</a>
</div>
</div>
</div>
@@ -79820,7 +87854,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>instance-group object that needs to be created or updated</p>
+ <p><p>instance-group object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkInstanceGroupsInstanceGroup.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -79891,6 +87925,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-instance-groups-instance-group--id--"></span>
+ <div id="operation--network-instance-groups-instance-group--id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing instance-group</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/instance-groups/instance-group/{id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing instance-group</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>instance-group object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/instance-group">/instance-group</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ id
+ </td>
+ <td>
+ <p>Instance Group ID, UUID assigned to this instance.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-instance-groups-instance-group--id--"></span>
<div id="operation--network-instance-groups-instance-group--id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing instance-group</div>
@@ -80002,7 +88125,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkInstanceGroupsInstanceGroup.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -80185,7 +88308,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/ipsec-configurations">/ipsec-configurations</a>
+ <a class="json-schema-ref" href="#/getDefinitions/ipsec-configurations">/ipsec-configurations</a>
</div>
</div>
</div>
@@ -80280,7 +88403,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/ipsec-configuration">/ipsec-configuration</a>
+ <a class="json-schema-ref" href="#/getDefinitions/ipsec-configuration">/ipsec-configuration</a>
</div>
</div>
</div>
@@ -80327,7 +88450,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>ipsec-configuration object that needs to be created or updated</p>
+ <p><p>ipsec-configuration object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkIpsecConfigurationsIpsecConfiguration.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -80398,6 +88521,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--"></span>
+ <div id="operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing ipsec-configuration</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing ipsec-configuration</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>ipsec-configuration object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/ipsec-configuration">/ipsec-configuration</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ ipsec-configuration-id
+ </td>
+ <td>
+ <p>UUID of this configuration</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--"></span>
<div id="operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing ipsec-configuration</div>
@@ -80509,7 +88721,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkIpsecConfigurationsIpsecConfiguration.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -80723,7 +88935,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vig-servers">/vig-servers</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vig-servers">/vig-servers</a>
</div>
</div>
</div>
@@ -80834,7 +89046,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vig-server">/vig-server</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vig-server">/vig-server</a>
</div>
</div>
</div>
@@ -80881,7 +89093,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vig-server object that needs to be created or updated</p>
+ <p><p>vig-server object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -80968,6 +89180,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--vig-servers-vig-server--vig-address-type--"></span>
+ <div id="operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--vig-servers-vig-server--vig-address-type--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vig-server</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}/vig-servers/vig-server/{vig-address-type}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vig-server</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vig-server object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vig-server">/vig-server</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ ipsec-configuration-id
+ </td>
+ <td>
+ <p>UUID of this configuration</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vig-address-type
+ </td>
+ <td>
+ <p>indicates whether the VIG is for AVPN or INTERNET</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--vig-servers-vig-server--vig-address-type--"></span>
<div id="operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--vig-servers-vig-server--vig-address-type--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vig-server</div>
@@ -81095,7 +89412,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -81310,7 +89627,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-networks">/l3-networks</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-networks">/l3-networks</a>
</div>
</div>
</div>
@@ -81540,7 +89857,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-network">/l3-network</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-network">/l3-network</a>
</div>
</div>
</div>
@@ -81587,7 +89904,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-network object that needs to be created or updated</p>
+ <p><p>l3-network object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkL3NetworksL3Network.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -81658,6 +89975,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-l3-networks-l3-network--network-id--"></span>
+ <div id="operation--network-l3-networks-l3-network--network-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-network</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/l3-networks/l3-network/{network-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-network</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-network object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-network">/l3-network</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ network-id
+ </td>
+ <td>
+ <p>Network ID, should be uuid. Unique across A&AI.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-l3-networks-l3-network--network-id--"></span>
<div id="operation--network-l3-networks-l3-network--network-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-network</div>
@@ -81952,7 +90358,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/ctag-assignments">/ctag-assignments</a>
+ <a class="json-schema-ref" href="#/getDefinitions/ctag-assignments">/ctag-assignments</a>
</div>
</div>
</div>
@@ -82198,7 +90604,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/ctag-assignment">/ctag-assignment</a>
+ <a class="json-schema-ref" href="#/getDefinitions/ctag-assignment">/ctag-assignment</a>
</div>
</div>
</div>
@@ -82245,7 +90651,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>ctag-assignment object that needs to be created or updated</p>
+ <p><p>ctag-assignment object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -82332,6 +90738,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-l3-networks-l3-network--network-id--ctag-assignments-ctag-assignment--vlan-id-inner--"></span>
+ <div id="operation--network-l3-networks-l3-network--network-id--ctag-assignments-ctag-assignment--vlan-id-inner--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing ctag-assignment</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/l3-networks/l3-network/{network-id}/ctag-assignments/ctag-assignment/{vlan-id-inner}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing ctag-assignment</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>ctag-assignment object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/ctag-assignment">/ctag-assignment</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ network-id
+ </td>
+ <td>
+ <p>Network ID, should be uuid. Unique across A&AI.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-id-inner
+ </td>
+ <td>
+ <p>id.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-l3-networks-l3-network--network-id--ctag-assignments-ctag-assignment--vlan-id-inner--"></span>
<div id="operation--network-l3-networks-l3-network--network-id--ctag-assignments-ctag-assignment--vlan-id-inner--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing ctag-assignment</div>
@@ -82459,7 +90970,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -82657,7 +91168,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkL3NetworksL3Network.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -83006,7 +91517,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/segmentation-assignments">/segmentation-assignments</a>
+ <a class="json-schema-ref" href="#/getDefinitions/segmentation-assignments">/segmentation-assignments</a>
</div>
</div>
</div>
@@ -83252,7 +91763,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/segmentation-assignment">/segmentation-assignment</a>
+ <a class="json-schema-ref" href="#/getDefinitions/segmentation-assignment">/segmentation-assignment</a>
</div>
</div>
</div>
@@ -83299,7 +91810,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>segmentation-assignment object that needs to be created or updated</p>
+ <p><p>segmentation-assignment object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -83386,6 +91897,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-l3-networks-l3-network--network-id--segmentation-assignments-segmentation-assignment--segmentation-id--"></span>
+ <div id="operation--network-l3-networks-l3-network--network-id--segmentation-assignments-segmentation-assignment--segmentation-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing segmentation-assignment</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/l3-networks/l3-network/{network-id}/segmentation-assignments/segmentation-assignment/{segmentation-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing segmentation-assignment</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>segmentation-assignment object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/segmentation-assignment">/segmentation-assignment</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ network-id
+ </td>
+ <td>
+ <p>Network ID, should be uuid. Unique across A&AI.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ segmentation-id
+ </td>
+ <td>
+ <p>Route Table Reference id, UUID assigned to this instance.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-l3-networks-l3-network--network-id--segmentation-assignments-segmentation-assignment--segmentation-id--"></span>
<div id="operation--network-l3-networks-l3-network--network-id--segmentation-assignments-segmentation-assignment--segmentation-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing segmentation-assignment</div>
@@ -83513,7 +92129,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -83894,7 +92510,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/subnets">/subnets</a>
+ <a class="json-schema-ref" href="#/getDefinitions/subnets">/subnets</a>
</div>
</div>
</div>
@@ -84155,7 +92771,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/subnet">/subnet</a>
+ <a class="json-schema-ref" href="#/getDefinitions/subnet">/subnet</a>
</div>
</div>
</div>
@@ -84202,7 +92818,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>subnet object that needs to be created or updated</p>
+ <p><p>subnet object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkL3NetworksL3NetworkSubnetsSubnet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -84289,6 +92905,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-l3-networks-l3-network--network-id--subnets-subnet--subnet-id--"></span>
+ <div id="operation--network-l3-networks-l3-network--network-id--subnets-subnet--subnet-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing subnet</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/l3-networks/l3-network/{network-id}/subnets/subnet/{subnet-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing subnet</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>subnet object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/subnet">/subnet</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ network-id
+ </td>
+ <td>
+ <p>Network ID, should be uuid. Unique across A&AI.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ subnet-id
+ </td>
+ <td>
+ <p>Subnet ID, should be UUID.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-l3-networks-l3-network--network-id--subnets-subnet--subnet-id--"></span>
<div id="operation--network-l3-networks-l3-network--network-id--subnets-subnet--subnet-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing subnet</div>
@@ -84630,7 +93351,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/host-routes">/host-routes</a>
+ <a class="json-schema-ref" href="#/getDefinitions/host-routes">/host-routes</a>
</div>
</div>
</div>
@@ -84907,7 +93628,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/host-route">/host-route</a>
+ <a class="json-schema-ref" href="#/getDefinitions/host-route">/host-route</a>
</div>
</div>
</div>
@@ -84954,7 +93675,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>host-route object that needs to be created or updated</p>
+ <p><p>host-route object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkL3NetworksL3NetworkSubnetsSubnetHostRoutesHostRoute.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -85057,6 +93778,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-l3-networks-l3-network--network-id--subnets-subnet--subnet-id--host-routes-host-route--host-route-id--"></span>
+ <div id="operation--network-l3-networks-l3-network--network-id--subnets-subnet--subnet-id--host-routes-host-route--host-route-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing host-route</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/l3-networks/l3-network/{network-id}/subnets/subnet/{subnet-id}/host-routes/host-route/{host-route-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing host-route</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>host-route object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/host-route">/host-route</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ network-id
+ </td>
+ <td>
+ <p>Network ID, should be uuid. Unique across A&AI.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ subnet-id
+ </td>
+ <td>
+ <p>Subnet ID, should be UUID.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ host-route-id
+ </td>
+ <td>
+ <p>host-route id</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-l3-networks-l3-network--network-id--subnets-subnet--subnet-id--host-routes-host-route--host-route-id--"></span>
<div id="operation--network-l3-networks-l3-network--network-id--subnets-subnet--subnet-id--host-routes-host-route--host-route-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing host-route</div>
@@ -85200,7 +94042,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkL3NetworksL3NetworkSubnetsSubnetHostRoutesHostRoute.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -85430,7 +94272,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkL3NetworksL3NetworkSubnetsSubnet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -85645,7 +94487,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-links">/lag-links</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-links">/lag-links</a>
</div>
</div>
</div>
@@ -85740,7 +94582,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-link">/lag-link</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-link">/lag-link</a>
</div>
</div>
</div>
@@ -85787,7 +94629,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>lag-link object that needs to be created or updated</p>
+ <p><p>lag-link object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkLagLinksLagLink.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -85858,6 +94700,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-lag-links-lag-link--link-name--"></span>
+ <div id="operation--network-lag-links-lag-link--link-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing lag-link</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/lag-links/lag-link/{link-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing lag-link</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>lag-link object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/lag-link">/lag-link</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ link-name
+ </td>
+ <td>
+ <p>Alphabetical concatenation of lag-interface names</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-lag-links-lag-link--link-name--"></span>
<div id="operation--network-lag-links-lag-link--link-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing lag-link</div>
@@ -85969,7 +94900,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkLagLinksLagLink.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -86152,7 +95083,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/logical-links">/logical-links</a>
+ <a class="json-schema-ref" href="#/getDefinitions/logical-links">/logical-links</a>
</div>
</div>
</div>
@@ -86367,7 +95298,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/logical-link">/logical-link</a>
+ <a class="json-schema-ref" href="#/getDefinitions/logical-link">/logical-link</a>
</div>
</div>
</div>
@@ -86414,7 +95345,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>logical-link object that needs to be created or updated</p>
+ <p><p>logical-link object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkLogicalLinksLogicalLink.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -86485,6 +95416,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-logical-links-logical-link--link-name--"></span>
+ <div id="operation--network-logical-links-logical-link--link-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing logical-link</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/logical-links/logical-link/{link-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing logical-link</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>logical-link object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/logical-link">/logical-link</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ link-name
+ </td>
+ <td>
+ <p>e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-logical-links-logical-link--link-name--"></span>
<div id="operation--network-logical-links-logical-link--link-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing logical-link</div>
@@ -86596,7 +95616,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkLogicalLinksLogicalLink.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -86779,7 +95799,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/multicast-configurations">/multicast-configurations</a>
+ <a class="json-schema-ref" href="#/getDefinitions/multicast-configurations">/multicast-configurations</a>
</div>
</div>
</div>
@@ -86874,7 +95894,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/multicast-configuration">/multicast-configuration</a>
+ <a class="json-schema-ref" href="#/getDefinitions/multicast-configuration">/multicast-configuration</a>
</div>
</div>
</div>
@@ -86921,7 +95941,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>multicast-configuration object that needs to be created or updated</p>
+ <p><p>multicast-configuration object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkMulticastConfigurationsMulticastConfiguration.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -86992,6 +96012,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-multicast-configurations-multicast-configuration--multicast-configuration-id--"></span>
+ <div id="operation--network-multicast-configurations-multicast-configuration--multicast-configuration-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing multicast-configuration</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/multicast-configurations/multicast-configuration/{multicast-configuration-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing multicast-configuration</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>multicast-configuration object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/multicast-configuration">/multicast-configuration</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ multicast-configuration-id
+ </td>
+ <td>
+ <p>Unique id of multicast configuration.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-multicast-configurations-multicast-configuration--multicast-configuration-id--"></span>
<div id="operation--network-multicast-configurations-multicast-configuration--multicast-configuration-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing multicast-configuration</div>
@@ -87103,7 +96212,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkMulticastConfigurationsMulticastConfiguration.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -87286,7 +96395,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/network-policies">/network-policies</a>
+ <a class="json-schema-ref" href="#/getDefinitions/network-policies">/network-policies</a>
</div>
</div>
</div>
@@ -87396,7 +96505,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/network-policy">/network-policy</a>
+ <a class="json-schema-ref" href="#/getDefinitions/network-policy">/network-policy</a>
</div>
</div>
</div>
@@ -87443,7 +96552,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>network-policy object that needs to be created or updated</p>
+ <p><p>network-policy object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNetworkPoliciesNetworkPolicy.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -87514,6 +96623,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-network-policies-network-policy--network-policy-id--"></span>
+ <div id="operation--network-network-policies-network-policy--network-policy-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing network-policy</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/network-policies/network-policy/{network-policy-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing network-policy</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>network-policy object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/network-policy">/network-policy</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ network-policy-id
+ </td>
+ <td>
+ <p>UUID representing unique key to this instance</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-network-policies-network-policy--network-policy-id--"></span>
<div id="operation--network-network-policies-network-policy--network-policy-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing network-policy</div>
@@ -87625,7 +96823,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNetworkPoliciesNetworkPolicy.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -87808,7 +97006,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/newvces">/newvces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/newvces">/newvces</a>
</div>
</div>
</div>
@@ -87978,7 +97176,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/newvce">/newvce</a>
+ <a class="json-schema-ref" href="#/getDefinitions/newvce">/newvce</a>
</div>
</div>
</div>
@@ -88025,7 +97223,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>newvce object that needs to be created or updated</p>
+ <p><p>newvce object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvce.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -88096,6 +97294,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing newvce</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing newvce</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>newvce object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/newvce">/newvce</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing newvce</div>
@@ -88330,7 +97617,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -88561,7 +97848,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -88608,7 +97895,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -88695,6 +97982,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -89067,7 +98459,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -89114,7 +98506,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -89217,6 +98609,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -89360,7 +98873,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -89835,7 +99348,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -89882,7 +99395,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -89985,6 +99498,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -90128,7 +99762,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -90358,7 +99992,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -90740,7 +100374,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -91047,7 +100681,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -91094,7 +100728,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -91197,6 +100831,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -91340,7 +101095,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -91754,7 +101509,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -92031,7 +101786,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -92078,7 +101833,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -92181,6 +101936,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -92615,7 +102491,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -92662,7 +102538,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -92781,6 +102657,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -92940,7 +102953,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -93493,7 +103506,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -93540,7 +103553,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -93659,6 +103672,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -93818,7 +103968,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -94080,7 +104230,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -94310,7 +104460,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvce.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -94493,7 +104643,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/physical-links">/physical-links</a>
+ <a class="json-schema-ref" href="#/getDefinitions/physical-links">/physical-links</a>
</div>
</div>
</div>
@@ -94603,7 +104753,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/physical-link">/physical-link</a>
+ <a class="json-schema-ref" href="#/getDefinitions/physical-link">/physical-link</a>
</div>
</div>
</div>
@@ -94650,7 +104800,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>physical-link object that needs to be created or updated</p>
+ <p><p>physical-link object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPhysicalLinksPhysicalLink.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -94721,6 +104871,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-physical-links-physical-link--link-name--"></span>
+ <div id="operation--network-physical-links-physical-link--link-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing physical-link</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/physical-links/physical-link/{link-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing physical-link</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>physical-link object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/physical-link">/physical-link</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ link-name
+ </td>
+ <td>
+ <p>e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-physical-links-physical-link--link-name--"></span>
<div id="operation--network-physical-links-physical-link--link-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing physical-link</div>
@@ -94832,7 +105071,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPhysicalLinksPhysicalLink.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -95015,7 +105254,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/pnfs">/pnfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/pnfs">/pnfs</a>
</div>
</div>
</div>
@@ -95125,7 +105364,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/pnf">/pnf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/pnf">/pnf</a>
</div>
</div>
</div>
@@ -95172,7 +105411,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>pnf object that needs to be created or updated</p>
+ <p><p>pnf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -95243,6 +105482,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing pnf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing pnf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>pnf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/pnf">/pnf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing pnf</div>
@@ -95417,7 +105745,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interfaces">/lag-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interfaces">/lag-interfaces</a>
</div>
</div>
</div>
@@ -95573,7 +105901,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interface">/lag-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interface">/lag-interface</a>
</div>
</div>
</div>
@@ -95620,7 +105948,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>lag-interface object that needs to be created or updated</p>
+ <p><p>lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -95707,6 +106035,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing lag-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing lag-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>lag-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/lag-interface">/lag-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing lag-interface</div>
@@ -95943,7 +106376,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -96160,7 +106593,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -96207,7 +106640,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -96310,6 +106743,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -96684,7 +107238,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -96731,7 +107285,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -96850,6 +107404,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -97009,7 +107700,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -97502,7 +108193,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -97549,7 +108240,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -97668,6 +108359,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -97827,7 +108655,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -98089,7 +108917,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -98489,7 +109317,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -98782,7 +109610,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -98829,7 +109657,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -98948,6 +109776,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -99107,7 +110072,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -99539,7 +110504,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -99802,7 +110767,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -99849,7 +110814,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -99968,6 +110933,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -100404,7 +111506,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -100451,7 +111553,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -100586,6 +111688,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -100761,7 +112016,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -101332,7 +112587,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -101379,7 +112634,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -101514,6 +112769,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -101689,7 +113097,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -101983,7 +113391,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -102245,7 +113653,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -102506,7 +113914,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/p-interfaces">/p-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/p-interfaces">/p-interfaces</a>
</div>
</div>
</div>
@@ -102647,7 +114055,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/p-interface">/p-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/p-interface">/p-interface</a>
</div>
</div>
</div>
@@ -102694,7 +114102,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>p-interface object that needs to be created or updated</p>
+ <p><p>p-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -102781,6 +114189,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing p-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing p-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>p-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/p-interface">/p-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing p-interface</div>
@@ -103002,7 +114515,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -103204,7 +114717,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -103251,7 +114764,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -103354,6 +114867,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -103713,7 +115347,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -103760,7 +115394,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -103879,6 +115513,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -104038,7 +115809,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -104516,7 +116287,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -104563,7 +116334,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -104682,6 +116453,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -104841,7 +116749,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -105103,7 +117011,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -105488,7 +117396,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -105766,7 +117674,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -105813,7 +117721,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -105932,6 +117840,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -106091,7 +118136,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -106508,7 +118553,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -106756,7 +118801,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -106803,7 +118848,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -106922,6 +118967,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -107343,7 +119525,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -107390,7 +119572,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -107525,6 +119707,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -107700,7 +120035,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -108256,7 +120591,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -108303,7 +120638,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -108438,6 +120773,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -108613,7 +121101,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -108907,7 +121395,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -109169,7 +121657,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -109461,7 +121949,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-pfs">/sriov-pfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-pfs">/sriov-pfs</a>
</div>
</div>
</div>
@@ -109618,7 +122106,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-pf">/sriov-pf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-pf">/sriov-pf</a>
</div>
</div>
</div>
@@ -109665,7 +122153,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-pf object that needs to be created or updated</p>
+ <p><p>sriov-pf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceSriovPfsSriovPf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -109768,6 +122256,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--sriov-pfs-sriov-pf--pf-pci-id--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--sriov-pfs-sriov-pf--pf-pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-pf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/sriov-pfs/sriov-pf/{pf-pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-pf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-pf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-pf">/sriov-pf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pf-pci-id
+ </td>
+ <td>
+ <p>Identifier for the sriov-pf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--sriov-pfs-sriov-pf--pf-pci-id--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--sriov-pfs-sriov-pf--pf-pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-pf</div>
@@ -109911,7 +122520,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceSriovPfsSriovPf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -110141,7 +122750,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -110324,7 +122933,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/route-table-references">/route-table-references</a>
+ <a class="json-schema-ref" href="#/getDefinitions/route-table-references">/route-table-references</a>
</div>
</div>
</div>
@@ -110434,7 +123043,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/route-table-reference">/route-table-reference</a>
+ <a class="json-schema-ref" href="#/getDefinitions/route-table-reference">/route-table-reference</a>
</div>
</div>
</div>
@@ -110481,7 +123090,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>route-table-reference object that needs to be created or updated</p>
+ <p><p>route-table-reference object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkRouteTableReferencesRouteTableReference.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -110552,6 +123161,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-route-table-references-route-table-reference--route-table-reference-id--"></span>
+ <div id="operation--network-route-table-references-route-table-reference--route-table-reference-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing route-table-reference</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/route-table-references/route-table-reference/{route-table-reference-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing route-table-reference</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>route-table-reference object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/route-table-reference">/route-table-reference</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ route-table-reference-id
+ </td>
+ <td>
+ <p>Route Table Reference id, UUID assigned to this instance.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-route-table-references-route-table-reference--route-table-reference-id--"></span>
<div id="operation--network-route-table-references-route-table-reference--route-table-reference-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing route-table-reference</div>
@@ -110663,7 +123361,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkRouteTableReferencesRouteTableReference.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -110846,7 +123544,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/site-pair-sets">/site-pair-sets</a>
+ <a class="json-schema-ref" href="#/getDefinitions/site-pair-sets">/site-pair-sets</a>
</div>
</div>
</div>
@@ -110941,7 +123639,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/site-pair-set">/site-pair-set</a>
+ <a class="json-schema-ref" href="#/getDefinitions/site-pair-set">/site-pair-set</a>
</div>
</div>
</div>
@@ -110988,7 +123686,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>site-pair-set object that needs to be created or updated</p>
+ <p><p>site-pair-set object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkSitePairSetsSitePairSet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -111059,6 +123757,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--"></span>
+ <div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing site-pair-set</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/site-pair-sets/site-pair-set/{site-pair-set-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing site-pair-set</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>site-pair-set object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/site-pair-set">/site-pair-set</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ site-pair-set-id
+ </td>
+ <td>
+ <p>Unique id of site pair set.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--"></span>
<div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing site-pair-set</div>
@@ -111170,7 +123957,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkSitePairSetsSitePairSet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -111384,7 +124171,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/routing-instances">/routing-instances</a>
+ <a class="json-schema-ref" href="#/getDefinitions/routing-instances">/routing-instances</a>
</div>
</div>
</div>
@@ -111495,7 +124282,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/routing-instance">/routing-instance</a>
+ <a class="json-schema-ref" href="#/getDefinitions/routing-instance">/routing-instance</a>
</div>
</div>
</div>
@@ -111542,7 +124329,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>routing-instance object that needs to be created or updated</p>
+ <p><p>routing-instance object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -111629,6 +124416,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--"></span>
+ <div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing routing-instance</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing routing-instance</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>routing-instance object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/routing-instance">/routing-instance</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ site-pair-set-id
+ </td>
+ <td>
+ <p>Unique id of site pair set.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ routing-instance-id
+ </td>
+ <td>
+ <p>Unique id of routing instance</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--"></span>
<div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing routing-instance</div>
@@ -111756,7 +124648,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -112018,7 +124910,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/site-pairs">/site-pairs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/site-pairs">/site-pairs</a>
</div>
</div>
</div>
@@ -112145,7 +125037,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/site-pair">/site-pair</a>
+ <a class="json-schema-ref" href="#/getDefinitions/site-pair">/site-pair</a>
</div>
</div>
</div>
@@ -112192,7 +125084,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>site-pair object that needs to be created or updated</p>
+ <p><p>site-pair object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -112295,6 +125187,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--"></span>
+ <div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing site-pair</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing site-pair</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>site-pair object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/site-pair">/site-pair</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ site-pair-set-id
+ </td>
+ <td>
+ <p>Unique id of site pair set.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ routing-instance-id
+ </td>
+ <td>
+ <p>Unique id of routing instance</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ site-pair-id
+ </td>
+ <td>
+ <p>unique identifier of probe</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--"></span>
<div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing site-pair</div>
@@ -112518,7 +125531,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/classes-of-service">/classes-of-service</a>
+ <a class="json-schema-ref" href="#/getDefinitions/classes-of-service">/classes-of-service</a>
</div>
</div>
</div>
@@ -112661,7 +125674,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/class-of-service">/class-of-service</a>
+ <a class="json-schema-ref" href="#/getDefinitions/class-of-service">/class-of-service</a>
</div>
</div>
</div>
@@ -112708,7 +125721,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>class-of-service object that needs to be created or updated</p>
+ <p><p>class-of-service object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -112827,6 +125840,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--classes-of-service-class-of-service--cos--"></span>
+ <div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--classes-of-service-class-of-service--cos--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing class-of-service</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}/classes-of-service/class-of-service/{cos}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing class-of-service</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>class-of-service object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/class-of-service">/class-of-service</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ site-pair-set-id
+ </td>
+ <td>
+ <p>Unique id of site pair set.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ routing-instance-id
+ </td>
+ <td>
+ <p>Unique id of routing instance</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ site-pair-id
+ </td>
+ <td>
+ <p>unique identifier of probe</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cos
+ </td>
+ <td>
+ <p>unique identifier of probe</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--classes-of-service-class-of-service--cos--"></span>
<div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--classes-of-service-class-of-service--cos--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing class-of-service</div>
@@ -112986,7 +126136,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -113248,7 +126398,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -113495,7 +126645,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vces">/vces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vces">/vces</a>
</div>
</div>
</div>
@@ -113710,7 +126860,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vce">/vce</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vce">/vce</a>
</div>
</div>
</div>
@@ -113757,7 +126907,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vce object that needs to be created or updated</p>
+ <p><p>vce object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVcesVce.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -113828,6 +126978,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vces-vce--vnf-id--"></span>
+ <div id="operation--network-vces-vce--vnf-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vce</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vces/vce/{vnf-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vce</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vce object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vce">/vce</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vces-vce--vnf-id--"></span>
<div id="operation--network-vces-vce--vnf-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vce</div>
@@ -114107,7 +127346,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/entitlements">/entitlements</a>
+ <a class="json-schema-ref" href="#/getDefinitions/entitlements">/entitlements</a>
</div>
</div>
</div>
@@ -114354,7 +127593,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/entitlement">/entitlement</a>
+ <a class="json-schema-ref" href="#/getDefinitions/entitlement">/entitlement</a>
</div>
</div>
</div>
@@ -114401,7 +127640,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>entitlement object that needs to be created or updated</p>
+ <p><p>entitlement object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVcesVceEntitlementsEntitlement.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -114504,6 +127743,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vces-vce--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--"></span>
+ <div id="operation--network-vces-vce--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing entitlement</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vces/vce/{vnf-id}/entitlements/entitlement/{group-uuid}/{resource-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing entitlement</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>entitlement object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/entitlement">/entitlement</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ group-uuid
+ </td>
+ <td>
+ <p>Unique ID for the entitlement group the resource comes from, should be uuid.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ resource-uuid
+ </td>
+ <td>
+ <p>Unique ID of an entitlement resource.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vces-vce--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--"></span>
<div id="operation--network-vces-vce--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing entitlement</div>
@@ -114647,7 +128007,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVcesVceEntitlementsEntitlement.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -115045,7 +128405,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/licenses">/licenses</a>
+ <a class="json-schema-ref" href="#/getDefinitions/licenses">/licenses</a>
</div>
</div>
</div>
@@ -115292,7 +128652,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/license">/license</a>
+ <a class="json-schema-ref" href="#/getDefinitions/license">/license</a>
</div>
</div>
</div>
@@ -115339,7 +128699,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>license object that needs to be created or updated</p>
+ <p><p>license object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVcesVceLicensesLicense.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -115442,6 +128802,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vces-vce--vnf-id--licenses-license--group-uuid---resource-uuid--"></span>
+ <div id="operation--network-vces-vce--vnf-id--licenses-license--group-uuid---resource-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing license</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vces/vce/{vnf-id}/licenses/license/{group-uuid}/{resource-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing license</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>license object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/license">/license</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ group-uuid
+ </td>
+ <td>
+ <p>Unique ID for the license group the resource belongs to, should be uuid.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ resource-uuid
+ </td>
+ <td>
+ <p>Unique ID of a license resource.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vces-vce--vnf-id--licenses-license--group-uuid---resource-uuid--"></span>
<div id="operation--network-vces-vce--vnf-id--licenses-license--group-uuid---resource-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing license</div>
@@ -115585,7 +129066,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVcesVceLicensesLicense.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -115983,7 +129464,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/port-groups">/port-groups</a>
+ <a class="json-schema-ref" href="#/getDefinitions/port-groups">/port-groups</a>
</div>
</div>
</div>
@@ -116259,7 +129740,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/port-group">/port-group</a>
+ <a class="json-schema-ref" href="#/getDefinitions/port-group">/port-group</a>
</div>
</div>
</div>
@@ -116306,7 +129787,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>port-group object that needs to be created or updated</p>
+ <p><p>port-group object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVcesVcePortGroupsPortGroup.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -116393,6 +129874,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vces-vce--vnf-id--port-groups-port-group--interface-id--"></span>
+ <div id="operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing port-group</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing port-group</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>port-group object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/port-group">/port-group</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-id
+ </td>
+ <td>
+ <p>Unique ID of the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vces-vce--vnf-id--port-groups-port-group--interface-id--"></span>
<div id="operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing port-group</div>
@@ -116749,7 +130335,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/cvlan-tags">/cvlan-tags</a>
+ <a class="json-schema-ref" href="#/getDefinitions/cvlan-tags">/cvlan-tags</a>
</div>
</div>
</div>
@@ -117041,7 +130627,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/cvlan-tag-entry">/cvlan-tag-entry</a>
+ <a class="json-schema-ref" href="#/getDefinitions/cvlan-tag-entry">/cvlan-tag-entry</a>
</div>
</div>
</div>
@@ -117088,7 +130674,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>cvlan-tag-entry object that needs to be created or updated</p>
+ <p><p>cvlan-tag-entry object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -117191,6 +130777,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vces-vce--vnf-id--port-groups-port-group--interface-id--cvlan-tags-cvlan-tag-entry--cvlan-tag--"></span>
+ <div id="operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--cvlan-tags-cvlan-tag-entry--cvlan-tag--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing cvlan-tag-entry</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}/cvlan-tags/cvlan-tag-entry/{cvlan-tag}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing cvlan-tag-entry</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>cvlan-tag-entry object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/cvlan-tag-entry">/cvlan-tag-entry</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-id
+ </td>
+ <td>
+ <p>Unique ID of the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cvlan-tag
+ </td>
+ <td>
+ <p>See mis-na-virtualization-platform.yang</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vces-vce--vnf-id--port-groups-port-group--interface-id--cvlan-tags-cvlan-tag-entry--cvlan-tag--"></span>
<div id="operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--cvlan-tags-cvlan-tag-entry--cvlan-tag--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing cvlan-tag-entry</div>
@@ -117334,7 +131041,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -117564,7 +131271,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVcesVcePortGroupsPortGroup.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -117762,7 +131469,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVcesVce.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -117945,7 +131652,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vnfcs">/vnfcs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vnfcs">/vnfcs</a>
</div>
</div>
</div>
@@ -118173,7 +131880,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vnfc">/vnfc</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vnfc">/vnfc</a>
</div>
</div>
</div>
@@ -118220,7 +131927,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vnfc object that needs to be created or updated</p>
+ <p><p>vnfc object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVnfcsVnfc.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -118291,6 +131998,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vnfcs-vnfc--vnfc-name--"></span>
+ <div id="operation--network-vnfcs-vnfc--vnfc-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vnfc</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vnfcs/vnfc/{vnfc-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vnfc</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vnfc object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vnfc">/vnfc</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnfc-name
+ </td>
+ <td>
+ <p>Unique ID of vnfc.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vnfcs-vnfc--vnfc-name--"></span>
<div id="operation--network-vnfcs-vnfc--vnfc-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vnfc</div>
@@ -118644,7 +132440,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -118691,7 +132487,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVnfcsVnfcL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -118778,6 +132574,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vnfcs-vnfc--vnfc-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-vnfcs-vnfc--vnfc-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vnfcs/vnfc/{vnfc-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnfc-name
+ </td>
+ <td>
+ <p>Unique ID of vnfc.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vnfcs-vnfc--vnfc-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-vnfcs-vnfc--vnfc-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -118905,7 +132806,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVnfcsVnfcL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -119345,7 +133246,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -119392,7 +133293,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVnfcsVnfcL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -119479,6 +133380,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vnfcs-vnfc--vnfc-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-vnfcs-vnfc--vnfc-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vnfcs/vnfc/{vnfc-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnfc-name
+ </td>
+ <td>
+ <p>Unique ID of vnfc.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vnfcs-vnfc--vnfc-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-vnfcs-vnfc--vnfc-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -119606,7 +133612,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVnfcsVnfcL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -119804,7 +133810,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVnfcsVnfc.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -119987,7 +133993,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vpls-pes">/vpls-pes</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vpls-pes">/vpls-pes</a>
</div>
</div>
</div>
@@ -120096,7 +134102,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vpls-pe">/vpls-pe</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vpls-pe">/vpls-pe</a>
</div>
</div>
</div>
@@ -120143,7 +134149,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vpls-pe object that needs to be created or updated</p>
+ <p><p>vpls-pe object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPe.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -120213,6 +134219,94 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vpls-pe</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vpls-pe</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vpls-pe object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vpls-pe">/vpls-pe</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vpls-pe</div>
@@ -120385,7 +134479,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interfaces">/lag-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interfaces">/lag-interfaces</a>
</div>
</div>
</div>
@@ -120540,7 +134634,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interface">/lag-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interface">/lag-interface</a>
</div>
</div>
</div>
@@ -120587,7 +134681,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>lag-interface object that needs to be created or updated</p>
+ <p><p>lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -120673,6 +134767,110 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing lag-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing lag-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>lag-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/lag-interface">/lag-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing lag-interface</div>
@@ -120907,7 +135105,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -121123,7 +135321,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -121170,7 +135368,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -121272,6 +135470,126 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -121644,7 +135962,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -121691,7 +136009,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -121809,6 +136127,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -121967,7 +136421,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -122457,7 +136911,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -122504,7 +136958,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -122622,6 +137076,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -122780,7 +137370,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -123040,7 +137630,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -123437,7 +138027,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -123729,7 +138319,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -123776,7 +138366,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -123894,6 +138484,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -124052,7 +138778,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -124481,7 +139207,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -124743,7 +139469,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -124790,7 +139516,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -124908,6 +139634,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -125342,7 +140204,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -125389,7 +140251,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -125523,6 +140385,158 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -125697,7 +140711,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -126265,7 +141279,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -126312,7 +141326,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -126446,6 +141460,158 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -126620,7 +141786,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -126912,7 +142078,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -127172,7 +142338,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -127430,7 +142596,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/p-interfaces">/p-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/p-interfaces">/p-interfaces</a>
</div>
</div>
</div>
@@ -127570,7 +142736,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/p-interface">/p-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/p-interface">/p-interface</a>
</div>
</div>
</div>
@@ -127617,7 +142783,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>p-interface object that needs to be created or updated</p>
+ <p><p>p-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -127703,6 +142869,110 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing p-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing p-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>p-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/p-interface">/p-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing p-interface</div>
@@ -127922,7 +143192,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -128123,7 +143393,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -128170,7 +143440,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -128272,6 +143542,126 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -128629,7 +144019,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -128676,7 +144066,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -128794,6 +144184,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -128952,7 +144478,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -129427,7 +144953,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -129474,7 +145000,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -129592,6 +145118,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -129750,7 +145412,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -130010,7 +145672,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -130392,7 +146054,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -130669,7 +146331,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -130716,7 +146378,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -130834,6 +146496,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -130992,7 +146790,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -131406,7 +147204,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -131653,7 +147451,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -131700,7 +147498,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -131818,6 +147616,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -132237,7 +148171,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -132284,7 +148218,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -132418,6 +148352,158 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -132592,7 +148678,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -133145,7 +149231,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -133192,7 +149278,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -133326,6 +149412,158 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -133500,7 +149738,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -133792,7 +150030,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -134052,7 +150290,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -134341,7 +150579,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-pfs">/sriov-pfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-pfs">/sriov-pfs</a>
</div>
</div>
</div>
@@ -134497,7 +150735,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-pf">/sriov-pf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-pf">/sriov-pf</a>
</div>
</div>
</div>
@@ -134544,7 +150782,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-pf object that needs to be created or updated</p>
+ <p><p>sriov-pf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceSriovPfsSriovPf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -134646,6 +150884,126 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--sriov-pfs-sriov-pf--pf-pci-id--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--sriov-pfs-sriov-pf--pf-pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-pf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/sriov-pfs/sriov-pf/{pf-pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-pf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-pf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-pf">/sriov-pf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pf-pci-id
+ </td>
+ <td>
+ <p>Identifier for the sriov-pf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--sriov-pfs-sriov-pf--pf-pci-id--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--sriov-pfs-sriov-pf--pf-pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-pf</div>
@@ -134788,7 +151146,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceSriovPfsSriovPf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -135016,7 +151374,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPe.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -135197,7 +151555,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vpn-bindings">/vpn-bindings</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vpn-bindings">/vpn-bindings</a>
</div>
</div>
</div>
@@ -135322,7 +151680,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vpn-binding">/vpn-binding</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vpn-binding">/vpn-binding</a>
</div>
</div>
</div>
@@ -135369,7 +151727,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vpn-binding object that needs to be created or updated</p>
+ <p><p>vpn-binding object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVpnBindingsVpnBinding.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -135440,6 +151798,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpn-bindings-vpn-binding--vpn-id--"></span>
+ <div id="operation--network-vpn-bindings-vpn-binding--vpn-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vpn-binding</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpn-bindings/vpn-binding/{vpn-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vpn-binding</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vpn-binding object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vpn-binding">/vpn-binding</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vpn-id
+ </td>
+ <td>
+ <p>VPN ID, globally unique within A&AI</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpn-bindings-vpn-binding--vpn-id--"></span>
<div id="operation--network-vpn-bindings-vpn-binding--vpn-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vpn-binding</div>
@@ -135551,7 +151998,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVpnBindingsVpnBinding.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -135795,7 +152242,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/route-targets">/route-targets</a>
+ <a class="json-schema-ref" href="#/getDefinitions/route-targets">/route-targets</a>
</div>
</div>
</div>
@@ -135952,7 +152399,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/route-target">/route-target</a>
+ <a class="json-schema-ref" href="#/getDefinitions/route-target">/route-target</a>
</div>
</div>
</div>
@@ -135999,7 +152446,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>route-target object that needs to be created or updated</p>
+ <p><p>route-target object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVpnBindingsVpnBindingRouteTargetsRouteTarget.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -136102,6 +152549,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpn-bindings-vpn-binding--vpn-id--route-targets-route-target--global-route-target---route-target-role--"></span>
+ <div id="operation--network-vpn-bindings-vpn-binding--vpn-id--route-targets-route-target--global-route-target---route-target-role--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing route-target</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpn-bindings/vpn-binding/{vpn-id}/route-targets/route-target/{global-route-target}/{route-target-role}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing route-target</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>route-target object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/route-target">/route-target</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vpn-id
+ </td>
+ <td>
+ <p>VPN ID, globally unique within A&AI</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ global-route-target
+ </td>
+ <td>
+ <p>Number used to identify an RT, globally unique in the network</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ route-target-role
+ </td>
+ <td>
+ <p>Role assigned to this route target</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpn-bindings-vpn-binding--vpn-id--route-targets-route-target--global-route-target---route-target-role--"></span>
<div id="operation--network-vpn-bindings-vpn-binding--vpn-id--route-targets-route-target--global-route-target---route-target-role--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing route-target</div>
@@ -136245,7 +152813,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVpnBindingsVpnBindingRouteTargetsRouteTarget.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -136492,7 +153060,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/zones">/zones</a>
+ <a class="json-schema-ref" href="#/getDefinitions/zones">/zones</a>
</div>
</div>
</div>
@@ -136617,7 +153185,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/zone">/zone</a>
+ <a class="json-schema-ref" href="#/getDefinitions/zone">/zone</a>
</div>
</div>
</div>
@@ -136664,7 +153232,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>zone object that needs to be created or updated</p>
+ <p><p>zone object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkZonesZone.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -136735,6 +153303,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-zones-zone--zone-id--"></span>
+ <div id="operation--network-zones-zone--zone-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing zone</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/zones/zone/{zone-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing zone</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>zone object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/zone">/zone</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ zone-id
+ </td>
+ <td>
+ <p>Code assigned by AIC to the zone</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-zones-zone--zone-id--"></span>
<div id="operation--network-zones-zone--zone-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing zone</div>
@@ -136846,7 +153503,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkZonesZone.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -137029,7 +153686,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/models">/models</a>
+ <a class="json-schema-ref" href="#/getDefinitions/models">/models</a>
</div>
</div>
</div>
@@ -137139,7 +153796,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/model">/model</a>
+ <a class="json-schema-ref" href="#/getDefinitions/model">/model</a>
</div>
</div>
</div>
@@ -137186,7 +153843,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>model object that needs to be created or updated</p>
+ <p><p>model object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationModelsModel.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -137257,6 +153914,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-models-model--model-invariant-id--"></span>
+ <div id="operation--service-design-and-creation-models-model--model-invariant-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing model</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/models/model/{model-invariant-id}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing model</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>model object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/model">/model</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ model-invariant-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to the main definition of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-models-model--model-invariant-id--"></span>
<div id="operation--service-design-and-creation-models-model--model-invariant-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing model</div>
@@ -137431,7 +154177,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/model-vers">/model-vers</a>
+ <a class="json-schema-ref" href="#/getDefinitions/model-vers">/model-vers</a>
</div>
</div>
</div>
@@ -137587,7 +154333,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/model-ver">/model-ver</a>
+ <a class="json-schema-ref" href="#/getDefinitions/model-ver">/model-ver</a>
</div>
</div>
</div>
@@ -137634,7 +154380,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>model-ver object that needs to be created or updated</p>
+ <p><p>model-ver object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationModelsModelModelVersModelVer.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -137721,6 +154467,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--"></span>
+ <div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing model-ver</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing model-ver</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>model-ver object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/model-ver">/model-ver</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ model-invariant-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to the main definition of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-version-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to one version of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--"></span>
<div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing model-ver</div>
@@ -137957,7 +154808,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadata">/metadata</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadata">/metadata</a>
</div>
</div>
</div>
@@ -138128,7 +154979,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadatum">/metadatum</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadatum">/metadatum</a>
</div>
</div>
</div>
@@ -138175,7 +155026,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>metadatum object that needs to be created or updated</p>
+ <p><p>metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationModelsModelModelVersModelVerMetadataMetadatum.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -138277,6 +155128,126 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--metadata-metadatum--metaname--"></span>
+ <div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--metadata-metadatum--metaname--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing metadatum</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/metadata/metadatum/{metaname}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing metadatum</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>metadatum object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/metadatum">/metadatum</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ model-invariant-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to the main definition of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-version-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to one version of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ metaname
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--metadata-metadatum--metaname--"></span>
<div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--metadata-metadatum--metaname--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing metadatum</div>
@@ -138528,7 +155499,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/model-elements">/model-elements</a>
+ <a class="json-schema-ref" href="#/getDefinitions/model-elements">/model-elements</a>
</div>
</div>
</div>
@@ -138699,7 +155670,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/model-element">/model-element</a>
+ <a class="json-schema-ref" href="#/getDefinitions/model-element">/model-element</a>
</div>
</div>
</div>
@@ -138746,7 +155717,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>model-element object that needs to be created or updated</p>
+ <p><p>model-element object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElement.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -138848,6 +155819,126 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--"></span>
+ <div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing model-element</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing model-element</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>model-element object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/model-element">/model-element</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ model-invariant-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to the main definition of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-version-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to one version of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-element-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--"></span>
<div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing model-element</div>
@@ -139114,7 +156205,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/model-constraints">/model-constraints</a>
+ <a class="json-schema-ref" href="#/getDefinitions/model-constraints">/model-constraints</a>
</div>
</div>
</div>
@@ -139300,7 +156391,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/model-constraint">/model-constraint</a>
+ <a class="json-schema-ref" href="#/getDefinitions/model-constraint">/model-constraint</a>
</div>
</div>
</div>
@@ -139347,7 +156438,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>model-constraint object that needs to be created or updated</p>
+ <p><p>model-constraint object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraint.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -139464,6 +156555,141 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--"></span>
+ <div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing model-constraint</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing model-constraint</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>model-constraint object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/model-constraint">/model-constraint</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ model-invariant-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to the main definition of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-version-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to one version of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-element-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-constraint-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--"></span>
<div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing model-constraint</div>
@@ -139760,7 +156986,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/constrained-element-sets">/constrained-element-sets</a>
+ <a class="json-schema-ref" href="#/getDefinitions/constrained-element-sets">/constrained-element-sets</a>
</div>
</div>
</div>
@@ -139961,7 +157187,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/constrained-element-set">/constrained-element-set</a>
+ <a class="json-schema-ref" href="#/getDefinitions/constrained-element-set">/constrained-element-set</a>
</div>
</div>
</div>
@@ -140008,7 +157234,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>constrained-element-set object that needs to be created or updated</p>
+ <p><p>constrained-element-set object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -140140,6 +157366,156 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--"></span>
+ <div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing constrained-element-set</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing constrained-element-set</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>constrained-element-set object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/constrained-element-set">/constrained-element-set</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ model-invariant-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to the main definition of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-version-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to one version of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-element-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-constraint-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ constrained-element-set-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--"></span>
<div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing constrained-element-set</div>
@@ -140466,7 +157842,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/element-choice-sets">/element-choice-sets</a>
+ <a class="json-schema-ref" href="#/getDefinitions/element-choice-sets">/element-choice-sets</a>
</div>
</div>
</div>
@@ -140682,7 +158058,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/element-choice-set">/element-choice-set</a>
+ <a class="json-schema-ref" href="#/getDefinitions/element-choice-set">/element-choice-set</a>
</div>
</div>
</div>
@@ -140729,7 +158105,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>element-choice-set object that needs to be created or updated</p>
+ <p><p>element-choice-set object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -140876,6 +158252,171 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--element-choice-sets-element-choice-set--element-choice-set-uuid--"></span>
+ <div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--element-choice-sets-element-choice-set--element-choice-set-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing element-choice-set</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}/element-choice-sets/element-choice-set/{element-choice-set-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing element-choice-set</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>element-choice-set object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/element-choice-set">/element-choice-set</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ model-invariant-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to the main definition of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-version-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to one version of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-element-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-constraint-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ constrained-element-set-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ element-choice-set-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--element-choice-sets-element-choice-set--element-choice-set-uuid--"></span>
<div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--element-choice-sets-element-choice-set--element-choice-set-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing element-choice-set</div>
@@ -141063,7 +158604,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -141381,7 +158922,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -141669,7 +159210,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElement.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -141897,7 +159438,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationModelsModelModelVersModelVer.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -142095,7 +159636,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationModelsModel.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -142278,7 +159819,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/named-queries">/named-queries</a>
+ <a class="json-schema-ref" href="#/getDefinitions/named-queries">/named-queries</a>
</div>
</div>
</div>
@@ -142386,7 +159927,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/named-query">/named-query</a>
+ <a class="json-schema-ref" href="#/getDefinitions/named-query">/named-query</a>
</div>
</div>
</div>
@@ -142433,7 +159974,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>named-query object that needs to be created or updated</p>
+ <p><p>named-query object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationNamedQueriesNamedQuery.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -142503,6 +160044,94 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--"></span>
+ <div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing named-query</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/named-queries/named-query/{named-query-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing named-query</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>named-query object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/named-query">/named-query</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ named-query-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--"></span>
<div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing named-query</div>
@@ -142674,7 +160303,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/named-query-elements">/named-query-elements</a>
+ <a class="json-schema-ref" href="#/getDefinitions/named-query-elements">/named-query-elements</a>
</div>
</div>
</div>
@@ -142797,7 +160426,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/named-query-element">/named-query-element</a>
+ <a class="json-schema-ref" href="#/getDefinitions/named-query-element">/named-query-element</a>
</div>
</div>
</div>
@@ -142844,7 +160473,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>named-query-element object that needs to be created or updated</p>
+ <p><p>named-query-element object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -142929,6 +160558,109 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--"></span>
+ <div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing named-query-element</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing named-query-element</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>named-query-element object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/named-query-element">/named-query-element</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ named-query-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ named-query-element-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--"></span>
<div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing named-query-element</div>
@@ -143130,7 +160862,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/property-constraints">/property-constraints</a>
+ <a class="json-schema-ref" href="#/getDefinitions/property-constraints">/property-constraints</a>
</div>
</div>
</div>
@@ -143268,7 +161000,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/property-constraint">/property-constraint</a>
+ <a class="json-schema-ref" href="#/getDefinitions/property-constraint">/property-constraint</a>
</div>
</div>
</div>
@@ -143315,7 +161047,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>property-constraint object that needs to be created or updated</p>
+ <p><p>property-constraint object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementPropertyConstraintsPropertyConstraint.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -143415,6 +161147,124 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--property-constraints-property-constraint--property-constraint-uuid--"></span>
+ <div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--property-constraints-property-constraint--property-constraint-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing property-constraint</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/property-constraints/property-constraint/{property-constraint-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing property-constraint</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>property-constraint object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/property-constraint">/property-constraint</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ named-query-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ named-query-element-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ property-constraint-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--property-constraints-property-constraint--property-constraint-uuid--"></span>
<div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--property-constraints-property-constraint--property-constraint-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing property-constraint</div>
@@ -143631,7 +161481,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/related-lookups">/related-lookups</a>
+ <a class="json-schema-ref" href="#/getDefinitions/related-lookups">/related-lookups</a>
</div>
</div>
</div>
@@ -143769,7 +161619,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/related-lookup">/related-lookup</a>
+ <a class="json-schema-ref" href="#/getDefinitions/related-lookup">/related-lookup</a>
</div>
</div>
</div>
@@ -143816,7 +161666,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>related-lookup object that needs to be created or updated</p>
+ <p><p>related-lookup object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -143916,6 +161766,124 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--related-lookups-related-lookup--related-lookup-uuid--"></span>
+ <div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--related-lookups-related-lookup--related-lookup-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing related-lookup</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/related-lookups/related-lookup/{related-lookup-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing related-lookup</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>related-lookup object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/related-lookup">/related-lookup</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ named-query-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ named-query-element-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ related-lookup-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--related-lookups-related-lookup--related-lookup-uuid--"></span>
<div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--related-lookups-related-lookup--related-lookup-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing related-lookup</div>
@@ -144056,7 +162024,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -144280,7 +162248,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -144474,7 +162442,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationNamedQueriesNamedQuery.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -144655,7 +162623,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/service-capabilities">/service-capabilities</a>
+ <a class="json-schema-ref" href="#/getDefinitions/service-capabilities">/service-capabilities</a>
</div>
</div>
</div>
@@ -144766,7 +162734,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/service-capability">/service-capability</a>
+ <a class="json-schema-ref" href="#/getDefinitions/service-capability">/service-capability</a>
</div>
</div>
</div>
@@ -144813,7 +162781,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>service-capability object that needs to be created or updated</p>
+ <p><p>service-capability object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationServiceCapabilitiesServiceCapability.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -144900,6 +162868,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-service-capabilities-service-capability--service-type---vnf-type--"></span>
+ <div id="operation--service-design-and-creation-service-capabilities-service-capability--service-type---vnf-type--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing service-capability</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/service-capabilities/service-capability/{service-type}/{vnf-type}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing service-capability</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>service-capability object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/service-capability">/service-capability</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ service-type
+ </td>
+ <td>
+ <p>This gets defined by others to provide a unique ID for the service, we accept what is sent.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vnf-type
+ </td>
+ <td>
+ <p>String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-service-capabilities-service-capability--service-type---vnf-type--"></span>
<div id="operation--service-design-and-creation-service-capabilities-service-capability--service-type---vnf-type--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing service-capability</div>
@@ -145027,7 +163100,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationServiceCapabilitiesServiceCapability.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -145242,7 +163315,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/services">/services</a>
+ <a class="json-schema-ref" href="#/getDefinitions/services">/services</a>
</div>
</div>
</div>
@@ -145352,7 +163425,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/service">/service</a>
+ <a class="json-schema-ref" href="#/getDefinitions/service">/service</a>
</div>
</div>
</div>
@@ -145399,7 +163472,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>service object that needs to be created or updated</p>
+ <p><p>service object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationServicesService.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -145470,6 +163543,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-services-service--service-id--"></span>
+ <div id="operation--service-design-and-creation-services-service--service-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing service</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/services/service/{service-id}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing service</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>service object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/service">/service</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ service-id
+ </td>
+ <td>
+ <p>This gets defined by others to provide a unique ID for the service, we accept what is sent.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-services-service--service-id--"></span>
<div id="operation--service-design-and-creation-services-service--service-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing service</div>
@@ -145581,7 +163743,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationServicesService.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -145764,7 +163926,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vnf-images">/vnf-images</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vnf-images">/vnf-images</a>
</div>
</div>
</div>
@@ -145904,7 +164066,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vnf-image">/vnf-image</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vnf-image">/vnf-image</a>
</div>
</div>
</div>
@@ -145951,7 +164113,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vnf-image object that needs to be created or updated</p>
+ <p><p>vnf-image object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationVnfImagesVnfImage.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -146022,6 +164184,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-vnf-images-vnf-image--vnf-image-uuid--"></span>
+ <div id="operation--service-design-and-creation-vnf-images-vnf-image--vnf-image-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vnf-image</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/vnf-images/vnf-image/{vnf-image-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vnf-image</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vnf-image object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vnf-image">/vnf-image</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-image-uuid
+ </td>
+ <td>
+ <p>Unique ID of this asset</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-vnf-images-vnf-image--vnf-image-uuid--"></span>
<div id="operation--service-design-and-creation-vnf-images-vnf-image--vnf-image-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vnf-image</div>
@@ -146133,7 +164384,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationVnfImagesVnfImage.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -146283,6 +164534,45 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<h2>Schema definitions</h2>
+ <div id="definition-aai-internal" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/aai-internal"></a>aai-internal:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="property-name">
+ <span class="json-property-name">property-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="property-value">
+ <span class="json-property-name">property-value:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-action" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/action"></a>action:
@@ -146445,19 +164735,20 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Represents a slice or partial piece of a resource that gets separately allotted</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO generic-vnf (Many2Many)</li>
-<li>TO l3-network (Many2Many)</li>
-<li>TO instance-group (Many2Many)</li>
-<li>TO network-policy (One2One)</li>
-<li>TO vlan (Many2Many)</li>
-<li>TO l-interface (One2Many)</li>
-<li>TO tunnel-xconnect (comprises allotted-resource, One2One)</li>
-<li>TO vpn-binding (Many2Many)</li>
-<li>TO allotted-resource (One2One)</li>
-<li>FROM configuration</li>
-<li>FROM service-instance (is composed of allotted-resource)</li>
-<li>FROM service-instance</li>
-<li>FROM allotted-resource</li></ul>
+<li>TO allotted-resource( allotted-resource tosca.relationships.network.BindsTo allotted-resource, ONE2ONE)</li>
+<li>TO generic-vnf( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY)</li>
+<li>TO instance-group( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>TO l3-network( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY)</li>
+<li>TO l-interface( allotted-resource org.onap.relationships.inventory.Uses l-interface, ONE2MANY)</li>
+<li>TO network-policy( allotted-resource org.onap.relationships.inventory.Uses network-policy, ONE2ONE)</li>
+<li>TO vlan( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY)</li>
+<li>TO vpn-binding( allotted-resource org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2MANY)</li>
+<li>TO service-instance( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)</li>
+<li>FROM tunnel-xconnect( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)</li>
+<li>FROM configuration( configuration org.onap.relationships.inventory.Uses allotted-resource, ONE2ONE)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY)</li>
+<li>FROM allotted-resource( allotted-resource tosca.relationships.network.BindsTo allotted-resource, ONE2ONE)</li>
+<li>ALLOTTED-RESOURCE is DELETED when these are DELETED TUNNEL-XCONNECT</li></ul>
</section>
@@ -146695,14 +164986,15 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Availability zone, a collection of compute hosts/pservers</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO complex (Many2Many)</li>
-<li>TO service-capability (Many2Many)</li>
-<li>FROM cloud-region (is composed of availability-zone)</li>
-<li>FROM ctag-pool</li>
-<li>FROM dvs-switch</li>
-<li>FROM generic-vnf</li>
-<li>FROM pserver</li>
-<li>FROM vce</li></ul>
+<li>TO complex( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>TO service-capability( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)</li>
+<li>TO cloud-region( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM ctag-pool( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)</li>
+<li>FROM dvs-switch( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)</li>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)</li>
+<li>FROM pserver( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)</li>
+<li>FROM vce( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)</li>
+<li>AVAILABILITY-ZONE cannot be deleted if linked to CTAG-POOL,DVS-SWITCH,GENERIC-VNF,PSERVER,VCE</li></ul>
</section>
@@ -147034,7 +165326,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<section class="json-schema-description">
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM site-pair (is composed of class-of-service)</li></ul>
+<li>TO site-pair( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)</li></ul>
</section>
@@ -147289,23 +165581,26 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>cloud-region designates an installation of a cloud cluster or region or instantiation.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO esr-system-info (comprises cloud-region, One2Many)</li>
-<li>TO complex (Many2One)</li>
-<li>TO l3-network (Many2Many)</li>
-<li>TO tenant (comprises cloud-region, One2Many)</li>
-<li>TO image (comprises cloud-region, One2Many)</li>
-<li>TO flavor (comprises cloud-region, One2Many)</li>
-<li>TO availability-zone (comprises cloud-region, One2Many)</li>
-<li>TO oam-network (comprises cloud-region, One2Many)</li>
-<li>TO dvs-switch (comprises cloud-region, One2Many)</li>
-<li>TO volume-group (comprises cloud-region, One2Many)</li>
-<li>TO group-assignment (comprises cloud-region, One2Many)</li>
-<li>TO snapshot (comprises cloud-region, One2Many)</li>
-<li>TO zone (Many2One)</li>
-<li>TO vip-ipv4-address-list (comprises cloud-region, One2Many)</li>
-<li>TO vip-ipv6-address-list (comprises cloud-region, One2Many)</li>
-<li>FROM pserver</li>
-<li>FROM logical-link</li></ul>
+<li>TO esr-system-info (CHILD of cloud-region, cloud-region has esr-system-info, One2Many)</li>
+<li>TO complex( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>TO l3-network( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>TO zone( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)</li>
+<li>FROM availability-zone( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM dvs-switch( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM flavor( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM group-assignment( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM image( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM oam-network( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM snapshot( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM tenant( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM vip-ipv4-address-list( vip-ipv4-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM vip-ipv6-address-list( vip-ipv6-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM volume-group( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn cloud-region, MANY2MANY)</li>
+<li>FROM pserver( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)</li>
+<li>CLOUD-REGION cannot be deleted if linked to DVS-SWITCH,FLAVOR,GROUP-ASSIGNMENT,IMAGE,OAM-NETWORK,SNAPSHOT,TENANT,VIP-IPV4-ADDRESS-LIST,VIP-IPV6-ADDRESS-LIST,VOLUME-GROUP</li>
+<li>CLOUD-REGION is DELETED when these are DELETED AVAILABILITY-ZONE</li>
+<li>CLOUD-REGION deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO</li></ul>
</section>
@@ -147772,18 +166067,20 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Collection of physical locations that can house cloud-regions.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO ctag-pool (comprises complex, Many2Many)</li>
-<li>TO l3-network (Many2Many)</li>
-<li>FROM availability-zone</li>
-<li>FROM cloud-region</li>
-<li>FROM oam-network</li>
-<li>FROM pserver</li>
-<li>FROM pnf</li>
-<li>FROM vce</li>
-<li>FROM vpls-pe</li>
-<li>FROM volume-group</li>
-<li>FROM zone</li>
-<li>FROM generic-vnf</li></ul>
+<li>TO l3-network( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>FROM availability-zone( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM ctag-pool( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)</li>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)</li>
+<li>FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)</li>
+<li>FROM pnf( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM pserver( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM vce( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)</li>
+<li>FROM volume-group( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM vpls-pe( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM zone( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>COMPLEX cannot be deleted if linked to AVAILABILITY-ZONE,CLOUD-REGION,GENERIC-VNF,OAM-NETWORK,PNF,PSERVER,VCE,VOLUME-GROUP,VPLS-PE,ZONE</li>
+<li>COMPLEX is DELETED when these are DELETED CTAG-POOL</li></ul>
</section>
@@ -148088,37 +166385,39 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Port Mirror Configuration.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO logical-link (One2Many)</li>
-<li>TO metadatum (comprises configuration, One2Many)</li>
-<li>TO allotted-resource (One2One)</li>
-<li>FROM service-instance</li>
-<li>FROM generic-vnf</li></ul>
+<li>TO allotted-resource( configuration org.onap.relationships.inventory.Uses allotted-resource, ONE2ONE)</li>
+<li>TO logical-link( configuration org.onap.relationships.inventory.Uses logical-link, ONE2MANY)</li>
+<li>FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo configuration, MANY2ONE)</li>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses configuration, ONE2MANY)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.Uses configuration, ONE2MANY)</li>
+<li>CONFIGURATION is DELETED when these are DELETED METADATUM</li>
+<li>CONFIGURATION deletion means associated objects of these types are also DELETED:ALLOTTED-RESOURCE,LOGICAL-LINK</li></ul>
</section>
<section class="json-schema-properties">
<dl>
- <dt data-property-name="management-option">
- <span class="json-property-name">management-option:</span>
+ <dt data-property-name="configuration-id">
+ <span class="json-property-name">configuration-id:</span>
<span class="json-property-type">string</span>
<span class="json-property-range" title="Value limits"></span>
+ <span class="json-property-required"></span>
</dt>
<dd>
- <p>Indicates the entity that will manage this feature. Could be an organization or the name of the application as well.</p>
+ <p>UUID assigned to configuration.</p>
<div class="json-inner-schema">
</div>
</dd>
- <dt data-property-name="configuration-id">
- <span class="json-property-name">configuration-id:</span>
+ <dt data-property-name="management-option">
+ <span class="json-property-name">management-option:</span>
<span class="json-property-type">string</span>
<span class="json-property-range" title="Value limits"></span>
- <span class="json-property-required"></span>
</dt>
<dd>
- <p>UUID assigned to configuration.</p>
+ <p>Indicates the entity that will manage this feature. Could be an organization or the name of the application as well.</p>
<div class="json-inner-schema">
</div>
@@ -148251,7 +166550,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</dd>
<dt data-property-name="relationship-list">
<span class="json-property-name">relationship-list:</span>
- <span class="json-property-type">object</span>
+ <span class="json-property-type">object[]</span>
<span class="json-property-range" title="Value limits"></span>
</dt>
@@ -148260,7 +166559,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="json-inner-schema">
<section class="json-schema-array-items">
- <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship-list">relationship-list</a>
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
</span>
<span class="json-property-range" title="Value limits"></span>
@@ -148271,7 +166570,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</dd>
<dt data-property-name="metadata">
<span class="json-property-name">metadata:</span>
- <span class="json-property-type">object</span>
+ <span class="json-property-type">object[]</span>
<span class="json-property-range" title="Value limits"></span>
</dt>
@@ -148280,7 +166579,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="json-inner-schema">
<section class="json-schema-array-items">
- <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/metadata">metadata</a>
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/metadatum">metadatum</a>
</span>
<span class="json-property-range" title="Value limits"></span>
@@ -148348,9 +166647,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Collection of resource instances used to connect a variety of disparate inventory widgets</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO virtual-data-center (Many2Many)</li>
-<li>TO metadatum (comprises connector, Many2Many)</li>
-<li>FROM service-instance</li></ul>
+<li>TO virtual-data-center( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)</li>
+<li>FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)</li>
+<li>CONNECTOR is DELETED when these are DELETED METADATUM</li></ul>
</section>
@@ -148540,9 +166840,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>This is how we would capture constraints defining allowed sets of elements.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO element-choice-set (comprises constrained-element-set, One2Many)</li>
-<li>FROM model-element (is composed of constrained-element-set)</li>
-<li>FROM model-constraint (is composed of constrained-element-set)</li></ul>
+<li>TO model-constraint( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)</li>
+<li>TO model-element( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)</li>
+<li>FROM element-choice-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)</li>
+<li>CONSTRAINED-ELEMENT-SET is DELETED when these are DELETED ELEMENT-CHOICE-SET</li></ul>
</section>
@@ -148689,8 +166990,8 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<section class="json-schema-description">
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM l3-network (is composed of ctag-assignment)</li>
-<li>FROM service-instance</li></ul>
+<li>TO l3-network( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.Uses ctag-assignment, ONE2MANY)</li></ul>
</section>
@@ -148796,10 +167097,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>A collection of C tags (vlan tags) grouped for a specific purpose.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO availability-zone (Many2Many)</li>
-<li>FROM complex (is composed of ctag-pool)</li>
-<li>FROM vpls-pe</li>
-<li>FROM generic-vnf</li></ul>
+<li>TO complex( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)</li>
+<li>TO availability-zone( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)</li>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)</li>
+<li>FROM vpls-pe( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)</li></ul>
</section>
@@ -148943,7 +167244,8 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>customer identifiers to provide linkage back to BSS information.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO service-subscription (comprises customer, Many2Many)</li></ul>
+<li>FROM service-subscription( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)</li>
+<li>CUSTOMER is DELETED when these are DELETED SERVICE-SUBSCRIPTION</li></ul>
</section>
@@ -149198,8 +167500,8 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Digital virtual switch metadata, used by SDN-C to configure VCEs. A&AI needs to receive this data from the PO deployment team and administer it using the provisioningTool.sh into A&AI.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO availability-zone (Many2Many)</li>
-<li>FROM cloud-region (is composed of dvs-switch)</li></ul>
+<li>TO cloud-region( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>TO availability-zone( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)</li></ul>
</section>
@@ -149567,8 +167869,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>This is how we would capture constraints defining allowed sets of elements.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO model-element (comprises element-choice-set, One2Many)</li>
-<li>FROM constrained-element-set (is composed of element-choice-set)</li></ul>
+<li>TO constrained-element-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)</li>
+<li>FROM model-element( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)</li>
+<li>ELEMENT-CHOICE-SET is DELETED when these are DELETED MODEL-ELEMENT</li></ul>
</section>
@@ -149715,8 +168018,8 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Metadata for entitlement group.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM generic-vnf (is composed of entitlement)</li>
-<li>FROM vce (is composed of entitlement)</li></ul>
+<li>TO generic-vnf( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>TO vce( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)</li></ul>
</section>
@@ -149839,7 +168142,8 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Persist EMS address information used by EMS driver.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO esr-system-info (comprises esr-ems, One2Many)</li></ul>
+<li>TO esr-system-info (CHILD of esr-ems, esr-ems has esr-system-info, One2Many)</li>
+<li>ESR-EMS deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO</li></ul>
</section>
@@ -149872,7 +168176,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</dd>
<dt data-property-name="esr-system-info-list">
<span class="json-property-name">esr-system-info-list:</span>
- <span class="json-property-type">object[]</span>
+ <span class="json-property-type">object</span>
<span class="json-property-range" title="Value limits"></span>
</dt>
@@ -149881,7 +168185,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="json-inner-schema">
<section class="json-schema-array-items">
- <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-system-info">esr-system-info</a>
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-system-info-list">esr-system-info-list</a>
</span>
<span class="json-property-range" title="Value limits"></span>
@@ -149892,7 +168196,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</dd>
<dt data-property-name="relationship-list">
<span class="json-property-name">relationship-list:</span>
- <span class="json-property-type">object[]</span>
+ <span class="json-property-type">object</span>
<span class="json-property-range" title="Value limits"></span>
</dt>
@@ -149901,7 +168205,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="json-inner-schema">
<section class="json-schema-array-items">
- <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship-list">relationship-list</a>
</span>
<span class="json-property-range" title="Value limits"></span>
@@ -149965,10 +168269,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Persist common address information of external systems.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM esr-ems (is composed of esr-system-info)</li>
-<li>FROM esr-vnfm (is composed of esr-system-info)</li>
-<li>FROM esr-thirdparty-sdnc (is composed of esr-system-info)</li>
-<li>FROM cloud-region (is composed of esr-system-info)</li></ul>
+<li>FROM esr-ems (PARENT of esr-system-info, esr-ems has esr-system-info)</li>
+<li>FROM esr-vnfm (PARENT of esr-system-info, esr-vnfm has esr-system-info)</li>
+<li>FROM esr-thirdparty-sdnc (PARENT of esr-system-info, esr-thirdparty-sdnc has esr-system-info)</li>
+<li>FROM cloud-region (PARENT of esr-system-info, cloud-region has esr-system-info)</li></ul>
</section>
@@ -150297,8 +168601,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Persist SDNC address information used by ONAP SDNC.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO esr-system-info (comprises esr-thirdparty-sdnc, One2One)</li>
-<li>TO pnf (One2Many)</li></ul>
+<li>TO esr-system-info (CHILD of esr-thirdparty-sdnc, esr-thirdparty-sdnc has esr-system-info, One2One)</li>
+<li>TO pnf( esr-thirdparty-sdnc has pnf, One2Many)</li>
+<li>ESR-THIRDPARTY-SDNC deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO</li></ul>
</section>
@@ -150355,7 +168660,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</dd>
<dt data-property-name="esr-system-info-list">
<span class="json-property-name">esr-system-info-list:</span>
- <span class="json-property-type">object[]</span>
+ <span class="json-property-type">object</span>
<span class="json-property-range" title="Value limits"></span>
</dt>
@@ -150364,7 +168669,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="json-inner-schema">
<section class="json-schema-array-items">
- <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-system-info">esr-system-info</a>
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-system-info-list">esr-system-info-list</a>
</span>
<span class="json-property-range" title="Value limits"></span>
@@ -150375,7 +168680,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</dd>
<dt data-property-name="relationship-list">
<span class="json-property-name">relationship-list:</span>
- <span class="json-property-type">object[]</span>
+ <span class="json-property-type">object</span>
<span class="json-property-range" title="Value limits"></span>
</dt>
@@ -150384,7 +168689,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="json-inner-schema">
<section class="json-schema-array-items">
- <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship-list">relationship-list</a>
</span>
<span class="json-property-range" title="Value limits"></span>
@@ -150448,7 +168753,8 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Persist VNFM address information used by VF-C.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO esr-system-info (comprises esr-vnfm, One2One)</li></ul>
+<li>TO esr-system-info (CHILD of esr-vnfm, esr-vnfm has esr-system-info, One2One)</li>
+<li>ESR-VNFM deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO</li></ul>
</section>
@@ -150505,7 +168811,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</dd>
<dt data-property-name="esr-system-info-list">
<span class="json-property-name">esr-system-info-list:</span>
- <span class="json-property-type">object[]</span>
+ <span class="json-property-type">object</span>
<span class="json-property-range" title="Value limits"></span>
</dt>
@@ -150514,7 +168820,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="json-inner-schema">
<section class="json-schema-array-items">
- <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-system-info">esr-system-info</a>
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-system-info-list">esr-system-info-list</a>
</span>
<span class="json-property-range" title="Value limits"></span>
@@ -150525,7 +168831,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</dd>
<dt data-property-name="relationship-list">
<span class="json-property-name">relationship-list:</span>
- <span class="json-property-type">object[]</span>
+ <span class="json-property-type">object</span>
<span class="json-property-range" title="Value limits"></span>
</dt>
@@ -150534,7 +168840,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="json-inner-schema">
<section class="json-schema-array-items">
- <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship-list">relationship-list</a>
</span>
<span class="json-property-range" title="Value limits"></span>
@@ -150584,6 +168890,268 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-evc" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/evc"></a>evc:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>evc object is an optional child object of the Configuration object.</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO configuration( evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="evc-id">
+ <span class="json-property-name">evc-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Unique/key field for the evc object</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="forwarding-path-topology">
+ <span class="json-property-name">forwarding-path-topology:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Point-to-Point, Multi-Point</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="cir-value">
+ <span class="json-property-name">cir-value:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Commited Information Rate</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="cir-units">
+ <span class="json-property-name">cir-units:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>CIR units</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="connection-diversity-group-id">
+ <span class="json-property-name">connection-diversity-group-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Diversity Group ID</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="service-hours">
+ <span class="json-property-name">service-hours:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>formerly Performance Group</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="esp-evc-circuit-id">
+ <span class="json-property-name">esp-evc-circuit-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>EVC Circuit ID of ESP EVC</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="esp-evc-cir-value">
+ <span class="json-property-name">esp-evc-cir-value:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Committed Information Rate (For ESP)</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="esp-evc-cir-units">
+ <span class="json-property-name">esp-evc-cir-units:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>CIR units (For ESP)</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="esp-itu-code">
+ <span class="json-property-name">esp-itu-code:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Identifies ESP</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="collector-pop-clli">
+ <span class="json-property-name">collector-pop-clli:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Collector POP CLLI (from the hostname of the access pnf)</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="inter-connect-type-ingress">
+ <span class="json-property-name">inter-connect-type-ingress:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Interconnect type on ingress side of EVC.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="tagmode-access-ingress">
+ <span class="json-property-name">tagmode-access-ingress:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>tagode for collector side of EVC</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="tagmode-access-egress">
+ <span class="json-property-name">tagmode-access-egress:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>tagMode for network side of EVC</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-evcs" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/evcs"></a>evcs:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="evc">
+ <span class="json-property-name">evc:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/evc">evc</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-external-system" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/external-system"></a>external-system:
@@ -150603,7 +169171,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<dl>
<dt data-property-name="esr-ems-list">
<span class="json-property-name">esr-ems-list:</span>
- <span class="json-property-type">object[]</span>
+ <span class="json-property-type">object</span>
<span class="json-property-range" title="Value limits"></span>
</dt>
@@ -150612,7 +169180,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="json-inner-schema">
<section class="json-schema-array-items">
- <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-ems">esr-ems</a>
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-ems-list">esr-ems-list</a>
</span>
<span class="json-property-range" title="Value limits"></span>
@@ -150623,7 +169191,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</dd>
<dt data-property-name="esr-vnfm-list">
<span class="json-property-name">esr-vnfm-list:</span>
- <span class="json-property-type">object[]</span>
+ <span class="json-property-type">object</span>
<span class="json-property-range" title="Value limits"></span>
</dt>
@@ -150632,7 +169200,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="json-inner-schema">
<section class="json-schema-array-items">
- <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-vnfm">esr-vnfm</a>
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-vnfm-list">esr-vnfm-list</a>
</span>
<span class="json-property-range" title="Value limits"></span>
@@ -150643,7 +169211,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</dd>
<dt data-property-name="esr-thirdparty-sdnc-list">
<span class="json-property-name">esr-thirdparty-sdnc-list:</span>
- <span class="json-property-type">object[]</span>
+ <span class="json-property-type">object</span>
<span class="json-property-range" title="Value limits"></span>
</dt>
@@ -150652,7 +169220,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="json-inner-schema">
<section class="json-schema-array-items">
- <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-thirdparty-sdnc">esr-thirdparty-sdnc</a>
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-thirdparty-sdnc-list">esr-thirdparty-sdnc-list</a>
</span>
<span class="json-property-range" title="Value limits"></span>
@@ -150759,8 +169327,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Openstack flavor.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM cloud-region (is composed of flavor)</li>
-<li>FROM vserver</li></ul>
+<li>TO cloud-region( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM vserver( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)</li>
+<li>FLAVOR cannot be deleted if linked to VSERVER</li></ul>
</section>
@@ -150966,6 +169535,438 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-forwarder" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/forwarder"></a>forwarder:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Entity describing a sequenced segment of forwarding path</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO forwarding-path( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)</li>
+<li>TO l-interface( forwarder org.onap.relationships.inventory.ForwardsTo l-interface, MANY2ONE)</li>
+<li>TO configuration( forwarder org.onap.relationships.inventory.Uses configuration, ONE2ONE)</li>
+<li>TO lag-interface( forwarder org.onap.relationships.inventory.ForwardsTo lag-interface, MANY2ONE)</li>
+<li>TO p-interface( forwarder org.onap.relationships.inventory.ForwardsTo p-interface, MANY2ONE)</li>
+<li>FORWARDER deletion means associated objects of these types are also DELETED:CONFIGURATION</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="sequence">
+ <span class="json-property-name">sequence:</span>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Unique ID of this segmentation</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="forwarder-role">
+ <span class="json-property-name">forwarder-role:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>ingress, intermediate, egress</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-forwarder-evc" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/forwarder-evc"></a>forwarder-evc:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>forwarder object is an optional child object of the Configuration object.</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO configuration( forwarder-evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="forwarder-evc-id">
+ <span class="json-property-name">forwarder-evc-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Key for forwarder-evc object</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="circuit-id">
+ <span class="json-property-name">circuit-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Circuit ID from customer/ESP/ingress end of EVC, or reference to beater circuit on gateway/network/egress end of EVC</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="ivlan">
+ <span class="json-property-name">ivlan:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Internal VLAN.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="svlan">
+ <span class="json-property-name">svlan:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>SVLAN value for ingress of egress forwarder.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="cvlan">
+ <span class="json-property-name">cvlan:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>CVLAN value for ingress of egress forwarder.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-forwarder-evcs" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/forwarder-evcs"></a>forwarder-evcs:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="forwarder-evc">
+ <span class="json-property-name">forwarder-evc:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/forwarder-evc">forwarder-evc</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-forwarders" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/forwarders"></a>forwarders:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="forwarder">
+ <span class="json-property-name">forwarder:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/forwarder">forwarder</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-forwarding-path" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/forwarding-path"></a>forwarding-path:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Entity that describes the sequenced forwarding path between interfaces of services or resources</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO service-instance( forwarding-path org.onap.relationships.inventory.AppliesTo service-instance, MANY2ONE)</li>
+<li>TO configuration( forwarding-path org.onap.relationships.inventory.Uses configuration, ONE2ONE)</li>
+<li>FROM forwarder( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)</li>
+<li>FORWARDING-PATH is DELETED when these are DELETED FORWARDER</li>
+<li>FORWARDING-PATH deletion means associated objects of these types are also DELETED:CONFIGURATION</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="forwarding-path-id">
+ <span class="json-property-name">forwarding-path-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Unique ID of this FP</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="forwarding-path-name">
+ <span class="json-property-name">forwarding-path-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Name of the FP</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="selflink">
+ <span class="json-property-name">selflink:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>the self link for this FP</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ <dt data-property-name="forwarders">
+ <span class="json-property-name">forwarders:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/forwarder">forwarder</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-forwarding-paths" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/forwarding-paths"></a>forwarding-paths:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="forwarding-path">
+ <span class="json-property-name">forwarding-path:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/forwarding-path">forwarding-path</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-generic-vnf" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/generic-vnf"></a>generic-vnf:
@@ -150980,33 +169981,35 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>General purpose VNF</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO license-key-resource (Many2Many)</li>
-<li>TO l-interface (comprises generic-vnf, Many2Many)</li>
-<li>TO availability-zone (Many2Many)</li>
-<li>TO lag-interface (comprises generic-vnf, Many2Many)</li>
-<li>TO l3-network (Many2Many)</li>
-<li>TO pserver (Many2Many)</li>
-<li>TO vnf-image (Many2One)</li>
-<li>TO vserver (One2Many)</li>
-<li>TO service-instance (Many2Many)</li>
-<li>TO site-pair-set (Many2Many)</li>
-<li>TO network-profile (Many2Many)</li>
-<li>TO pnf (Many2Many)</li>
-<li>TO ipsec-configuration (Many2One)</li>
-<li>TO configuration (One2Many)</li>
-<li>TO vf-module (comprises generic-vnf, One2Many)</li>
-<li>TO volume-group (One2Many)</li>
-<li>TO vnfc (One2Many)</li>
-<li>TO instance-group (Many2Many)</li>
-<li>TO entitlement (comprises generic-vnf, One2Many)</li>
-<li>TO license (comprises generic-vnf, One2Many)</li>
-<li>TO complex (Many2Many)</li>
-<li>TO ctag-pool (Many2Many)</li>
-<li>FROM line-of-business</li>
-<li>FROM platform</li>
-<li>FROM virtual-data-center</li>
-<li>FROM logical-link</li>
-<li>FROM allotted-resource</li></ul>
+<li>TO availability-zone( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)</li>
+<li>TO complex( generic-vnf org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)</li>
+<li>TO configuration( generic-vnf org.onap.relationships.inventory.Uses configuration, ONE2MANY)</li>
+<li>TO ctag-pool( generic-vnf org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)</li>
+<li>TO instance-group( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>TO ipsec-configuration( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)</li>
+<li>TO l3-network( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>TO license-key-resource( generic-vnf org.onap.relationships.inventory.Uses license-key-resource, MANY2MANY)</li>
+<li>TO pnf( generic-vnf tosca.relationships.HostedOn pnf, MANY2MANY)</li>
+<li>TO pserver( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)</li>
+<li>TO vnf-image( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)</li>
+<li>TO volume-group( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)</li>
+<li>TO vserver( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)</li>
+<li>TO virtual-data-center( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)</li>
+<li>FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY)</li>
+<li>FROM entitlement( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>FROM vnfc( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>FROM lag-interface( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>FROM license( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>FROM network-profile( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)</li>
+<li>FROM site-pair-set( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)</li>
+<li>FROM vf-module( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>FROM line-of-business( line-of-business org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)</li>
+<li>FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)</li>
+<li>FROM platform( platform org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)</li>
+<li>GENERIC-VNF is DELETED when these are DELETED ENTITLEMENT,VNFC,LAG-INTERFACE,LICENSE,L-INTERFACE,VF-MODULE</li>
+<li>GENERIC-VNF deletion means associated objects of these types are also DELETED:CONFIGURATION</li></ul>
</section>
@@ -151025,6 +170028,19 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</dd>
+ <dt data-property-name="vnf-instance-id">
+ <span class="json-property-name">vnf-instance-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>vnf instance id.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
<dt data-property-name="vnf-name">
<span class="json-property-name">vnf-name:</span>
<span class="json-property-type">string</span>
@@ -151147,6 +170163,44 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</dd>
+ <dt data-property-name="vnf-package-name">
+ <span class="json-property-name">vnf-package-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="vnf-discriptor-name">
+ <span class="json-property-name">vnf-discriptor-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>vnf discriptor name</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="job-id">
+ <span class="json-property-name">job-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>job id corresponding to vnf</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
<dt data-property-name="heat-stack-id">
<span class="json-property-name">heat-stack-id:</span>
<span class="json-property-type">string</span>
@@ -151303,6 +170357,42 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</dd>
+ <dt data-property-name="nshd">
+ <span class="json-property-name">nshd:</span>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>number of associated SHD in vnf.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="nvm">
+ <span class="json-property-name">nvm:</span>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>number of vms in vnf.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="nnet">
+ <span class="json-property-name">nnet:</span>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>number of network in vnf.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
<dt data-property-name="in-maint">
<span class="json-property-name">in-maint:</span>
<span class="json-property-type">boolean</span>
@@ -151794,9 +170884,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Openstack group-assignment used to store exclusivity groups (EG).</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO tenant (Many2Many)</li>
-<li>TO pserver (One2Many)</li>
-<li>FROM cloud-region (is composed of group-assignment)</li></ul>
+<li>TO cloud-region( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM pserver( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)</li>
+<li>FROM tenant( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)</li></ul>
</section>
@@ -151943,7 +171033,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<section class="json-schema-description">
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM subnet (is composed of host-route)</li></ul>
+<li>TO subnet( host-route org.onap.relationships.inventory.BelongsTo subnet, MANY2ONE)</li></ul>
</section>
@@ -152087,9 +171177,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Openstack image.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO metadatum (comprises image, Many2Many)</li>
-<li>FROM cloud-region (is composed of image)</li>
-<li>FROM vserver</li></ul>
+<li>TO cloud-region( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)</li>
+<li>FROM vserver( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)</li>
+<li>IMAGE cannot be deleted if linked to VSERVER</li>
+<li>IMAGE is DELETED when these are DELETED METADATUM</li></ul>
</section>
@@ -152409,18 +171501,18 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>General mechanism for grouping instances</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO model (Many2Many)</li>
-<li>FROM l-interface</li>
-<li>FROM vnfc</li>
-<li>FROM l3-interface-ipv4-address-list</li>
-<li>FROM l3-interface-ipv6-address-list</li>
-<li>FROM l3-network</li>
-<li>FROM pnf</li>
-<li>FROM allotted-resource</li>
-<li>FROM generic-vnf</li>
-<li>FROM service-instance</li>
-<li>FROM vip-ipv4-address-list</li>
-<li>FROM vip-ipv6-address-list</li></ul>
+<li>TO model( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY)</li>
+<li>FROM allotted-resource( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)</li>
+<li>FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)</li>
+<li>FROM l3-network( l3-network org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>FROM l-interface( l-interface org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>FROM pnf( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>FROM vip-ipv4-address-list( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>FROM vip-ipv6-address-list( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>FROM vnfc( vnfc org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li></ul>
</section>
@@ -152777,7 +171869,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="json-inner-schema">
<section class="json-schema-array-items">
- <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/"></a>
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/aai-internal">aai-internal</a>
</span>
<span class="json-property-range" title="Value limits"></span>
@@ -153035,8 +172127,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>IPSec configuration node will contain various configuration data for the NMTE VNF. This node will have an edge to the generic-vnf (vnf type = TE). Starting 1607, this data will be populated by SDN-C</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO vig-server (comprises ipsec-configuration, One2Many)</li>
-<li>FROM generic-vnf</li></ul>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)</li>
+<li>FROM vig-server( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)</li>
+<li>IPSEC-CONFIGURATION is DELETED when these are DELETED VIG-SERVER</li></ul>
</section>
@@ -153441,20 +172534,22 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Logical interfaces, e.g., a vnic.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO instance-group (Many2Many)</li>
-<li>TO l3-interface-ipv4-address-list (comprises l-interface, Many2Many)</li>
-<li>TO l3-interface-ipv6-address-list (comprises l-interface, Many2Many)</li>
-<li>TO l-interface (comprises l-interface, One2Many)</li>
-<li>TO logical-link (Many2Many)</li>
-<li>TO vlan (comprises l-interface, Many2Many)</li>
-<li>TO sriov-vf (comprises l-interface, One2One)</li>
-<li>FROM generic-vnf (is composed of l-interface)</li>
-<li>FROM lag-interface (is composed of l-interface)</li>
-<li>FROM newvce (is composed of l-interface)</li>
-<li>FROM p-interface (is composed of l-interface)</li>
-<li>FROM vserver (is composed of l-interface)</li>
-<li>FROM allotted-resource</li>
-<li>FROM l-interface (is composed of l-interface)</li></ul>
+<li>TO generic-vnf( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>TO lag-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)</li>
+<li>TO instance-group( l-interface org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>TO l-interface( l-interface org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)</li>
+<li>TO logical-link( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)</li>
+<li>TO newvce( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)</li>
+<li>TO p-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)</li>
+<li>TO vserver( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)</li>
+<li>FROM allotted-resource( allotted-resource org.onap.relationships.inventory.Uses l-interface, ONE2MANY)</li>
+<li>FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)</li>
+<li>FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)</li>
+<li>FROM sriov-vf( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)</li>
+<li>FROM vlan( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)</li>
+<li>FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)</li>
+<li>L-INTERFACE is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST,SRIOV-VF,VLAN</li>
+<li>L-INTERFACE deletion means associated objects of these types are also DELETED:LOGICAL-LINK</li></ul>
</section>
@@ -153820,12 +172915,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>IPv4 Address Range</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO instance-group (Many2Many)</li>
-<li>TO l3-network (Many2Many)</li>
-<li>TO subnet (Many2Many)</li>
-<li>TO vnfc (is composed of l3-interface-ipv4-address-list, Many2One)</li>
-<li>FROM l-interface (is composed of l3-interface-ipv4-address-list)</li>
-<li>FROM vlan (is composed of l3-interface-ipv4-address-list)</li></ul>
+<li>TO instance-group( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)</li>
+<li>TO l3-network( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)</li>
+<li>TO subnet( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)</li>
+<li>TO l-interface( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)</li>
+<li>TO vlan( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)</li>
+<li>TO vnfc( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vnfc, MANY2ONE)</li></ul>
</section>
@@ -153966,12 +173061,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>IPv6 Address Range</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO instance-group (Many2Many)</li>
-<li>TO l3-network (Many2Many)</li>
-<li>TO subnet (Many2Many)</li>
-<li>TO vnfc (is composed of l3-interface-ipv6-address-list, Many2One)</li>
-<li>FROM l-interface (is composed of l3-interface-ipv6-address-list)</li>
-<li>FROM vlan (is composed of l3-interface-ipv6-address-list)</li></ul>
+<li>TO instance-group( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)</li>
+<li>TO l3-network( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)</li>
+<li>TO subnet( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)</li>
+<li>TO l-interface( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)</li>
+<li>TO vlan( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)</li>
+<li>TO vnfc( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vnfc, MANY2ONE)</li></ul>
</section>
@@ -154112,22 +173207,23 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Generic network definition</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO vpn-binding (Many2Many)</li>
-<li>TO instance-group (Many2Many)</li>
-<li>TO subnet (comprises l3-network, Many2Many)</li>
-<li>TO service-instance (Many2Many)</li>
-<li>TO ctag-assignment (comprises l3-network, Many2Many)</li>
-<li>TO network-policy (Many2Many)</li>
-<li>TO segmentation-assignment (comprises l3-network, One2Many)</li>
-<li>TO route-table-reference (Many2Many)</li>
-<li>FROM cloud-region</li>
-<li>FROM complex</li>
-<li>FROM generic-vnf</li>
-<li>FROM l3-interface-ipv4-address-list</li>
-<li>FROM l3-interface-ipv6-address-list</li>
-<li>FROM tenant</li>
-<li>FROM vf-module</li>
-<li>FROM allotted-resource</li></ul>
+<li>TO instance-group( l3-network org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>TO network-policy( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)</li>
+<li>TO route-table-reference( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)</li>
+<li>TO vpn-binding( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)</li>
+<li>FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY)</li>
+<li>FROM cloud-region( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>FROM complex( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)</li>
+<li>FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)</li>
+<li>FROM ctag-assignment( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)</li>
+<li>FROM segmentation-assignment( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)</li>
+<li>FROM subnet( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)</li>
+<li>FROM tenant( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>FROM vf-module( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)</li>
+<li>L3-NETWORK is DELETED when these are DELETED CTAG-ASSIGNMENT,SEGMENTATION-ASSIGNMENT,SUBNET</li></ul>
</section>
@@ -154582,14 +173678,16 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Link aggregate interface</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO logical-link (Many2Many)</li>
-<li>TO lag-link (Many2Many)</li>
-<li>TO p-interface (Many2Many)</li>
-<li>TO l-interface (comprises lag-interface, Many2Many)</li>
-<li>FROM generic-vnf (is composed of lag-interface)</li>
-<li>FROM pserver (is composed of lag-interface)</li>
-<li>FROM pnf (is composed of lag-interface)</li>
-<li>FROM vpls-pe (is composed of lag-interface)</li></ul>
+<li>TO generic-vnf( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>TO lag-link( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)</li>
+<li>TO logical-link( lag-interface org.onap.relationships.inventory.Uses logical-link, MANY2MANY)</li>
+<li>TO p-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)</li>
+<li>TO pnf( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)</li>
+<li>TO pserver( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)</li>
+<li>TO vpls-pe( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)</li>
+<li>FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)</li>
+<li>LAG-INTERFACE is DELETED when these are DELETED L-INTERFACE</li>
+<li>LAG-INTERFACE deletion means associated objects of these types are also DELETED:LAG-LINK,LOGICAL-LINK</li></ul>
</section>
@@ -154803,8 +173901,8 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>LAG links can connect lag-interfaces</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM lag-interface</li>
-<li>FROM logical-link</li></ul>
+<li>FROM lag-interface( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)</li>
+<li>FROM logical-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)</li></ul>
</section>
@@ -154914,8 +174012,8 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Metadata for license group.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM generic-vnf (is composed of license)</li>
-<li>FROM vce (is composed of license)</li></ul>
+<li>TO generic-vnf( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>TO vce( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)</li></ul>
</section>
@@ -155038,7 +174136,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>describes a line-of-business</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO generic-vnf (Many2Many)</li></ul>
+<li>TO generic-vnf( line-of-business org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)</li></ul>
</section>
@@ -155148,21 +174246,21 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Logical links generally connect l-interfaces but are used to express logical connectivity between two points</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO lag-link (Many2Many)</li>
-<li>TO pnf (Many2Many)</li>
-<li>TO logical-link (One2Many)</li>
-<li>TO generic-vnf (Many2Many)</li>
-<li>TO pserver (Many2Many)</li>
-<li>TO cloud-region (Many2Many)</li>
-<li>TO vpn-binding (Many2Many)</li>
-<li>FROM configuration</li>
-<li>FROM l-interface</li>
-<li>FROM lag-interface</li>
-<li>FROM p-interface</li>
-<li>FROM service-instance</li>
-<li>FROM virtual-data-center</li>
-<li>FROM vlan</li>
-<li>FROM logical-link</li></ul>
+<li>TO cloud-region( logical-link org.onap.relationships.inventory.LocatedIn cloud-region, MANY2MANY)</li>
+<li>TO generic-vnf( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)</li>
+<li>TO lag-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)</li>
+<li>TO logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, MANY2MANY)</li>
+<li>TO pnf( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)</li>
+<li>TO pserver( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)</li>
+<li>TO vpn-binding( logical-link org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)</li>
+<li>TO virtual-data-center( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)</li>
+<li>FROM configuration( configuration org.onap.relationships.inventory.Uses logical-link, ONE2MANY)</li>
+<li>FROM lag-interface( lag-interface org.onap.relationships.inventory.Uses logical-link, MANY2MANY)</li>
+<li>FROM l-interface( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)</li>
+<li>FROM p-interface( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)</li>
+<li>FROM vlan( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)</li>
+<li>FROM logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, MANY2MANY)</li></ul>
</section>
@@ -155530,11 +174628,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Key/value pairs</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM configuration (is composed of metadatum)</li>
-<li>FROM image (is composed of metadatum)</li>
-<li>FROM model-ver (is composed of metadatum)</li>
-<li>FROM service-instance (is composed of metadatum)</li>
-<li>FROM connector (is composed of metadatum)</li></ul>
+<li>TO configuration( metadatum org.onap.relationships.inventory.BelongsTo configuration, MANY2ONE)</li>
+<li>TO connector( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)</li>
+<li>TO image( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)</li>
+<li>TO service-instance( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)</li>
+<li>TO model-ver( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)</li></ul>
</section>
@@ -155594,10 +174692,13 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Subgraph definition provided by ASDC to describe an inventory asset and its connections related to ASDC models, independent of version</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO model-ver (comprises model, One2Many)</li>
-<li>FROM named-query</li>
-<li>FROM named-query-element</li>
-<li>FROM instance-group</li></ul>
+<li>TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)</li>
+<li>FROM instance-group( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY)</li>
+<li>FROM model-ver( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)</li>
+<li>FROM named-query( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)</li>
+<li>FROM named-query-element( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)</li>
+<li>MODEL cannot be deleted if linked to INSTANCE-GROUP,NAMED-QUERY,NAMED-QUERY-ELEMENT</li>
+<li>MODEL is DELETED when these are DELETED MODEL-VER</li></ul>
</section>
@@ -155802,8 +174903,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>This is how we would capture constraints defining allowed sets of elements.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO constrained-element-set (comprises model-constraint, One2Many)</li>
-<li>FROM model-element (is composed of model-constraint)</li></ul>
+<li>TO model-element( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)</li>
+<li>FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)</li>
+<li>MODEL-CONSTRAINT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET</li></ul>
</section>
@@ -155920,13 +175022,14 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Defines how other models combine to make up a higher-level model.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO model-ver (Many2One)</li>
-<li>TO model-element (comprises model-element, One2Many)</li>
-<li>TO model-constraint (comprises model-element, One2Many)</li>
-<li>TO constrained-element-set (comprises model-element, One2Many)</li>
-<li>FROM model-ver (is composed of model-element)</li>
-<li>FROM element-choice-set (is composed of model-element)</li>
-<li>FROM model-element (is composed of model-element)</li></ul>
+<li>TO element-choice-set( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)</li>
+<li>TO model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)</li>
+<li>TO model-ver( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE)</li>
+<li>TO model-ver( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)</li>
+<li>FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)</li>
+<li>FROM model-constraint( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)</li>
+<li>FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)</li>
+<li>MODEL-ELEMENT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET,MODEL-CONSTRAINT</li></ul>
</section>
@@ -156108,10 +175211,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Subgraph definition provided by ASDC to describe a specific version of an inventory asset and its connections related to ASDC models</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO model-element (comprises model-ver, One2Many)</li>
-<li>TO metadatum (comprises model-ver, One2Many)</li>
-<li>FROM model (is composed of model-ver)</li>
-<li>FROM model-element</li></ul>
+<li>TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)</li>
+<li>FROM model-element( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE)</li>
+<li>FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)</li>
+<li>FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)</li>
+<li>MODEL-VER cannot be deleted if linked to MODEL-ELEMENT</li>
+<li>MODEL-VER is DELETED when these are DELETED MODEL-ELEMENT,METADATUM</li></ul>
</section>
@@ -156335,7 +175440,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<section class="json-schema-description">
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM vlan</li></ul>
+<li>FROM vlan( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)</li></ul>
</section>
@@ -156508,8 +175613,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>TBD</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO model (One2Many)</li>
-<li>TO named-query-element (comprises named-query, One2One)</li></ul>
+<li>TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)</li>
+<li>TO model( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)</li>
+<li>FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)</li>
+<li>NAMED-QUERY is DELETED when these are DELETED NAMED-QUERY-ELEMENT</li></ul>
</section>
@@ -156642,12 +175749,13 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>TBD</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO named-query-element (comprises named-query-element, Many2Many)</li>
-<li>TO model (Many2One)</li>
-<li>TO property-constraint (comprises named-query-element, One2Many)</li>
-<li>TO related-lookup (comprises named-query-element, One2Many)</li>
-<li>FROM named-query (is composed of named-query-element)</li>
-<li>FROM named-query-element (is composed of named-query-element)</li></ul>
+<li>TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)</li>
+<li>TO model( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)</li>
+<li>TO named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)</li>
+<li>FROM property-constraint( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)</li>
+<li>FROM related-lookup( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)</li>
+<li>FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)</li>
+<li>NAMED-QUERY-ELEMENT is DELETED when these are DELETED PROPERTY-CONSTRAINT,RELATED-LOOKUP</li></ul>
</section>
@@ -157207,6 +176315,26 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</section> </div>
</dd>
+ <dt data-property-name="configurations">
+ <span class="json-property-name">configurations:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/configurations">configurations</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
</dl>
</section>
</div>
@@ -157261,8 +176389,8 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<section class="json-schema-description">
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM l3-network</li>
-<li>FROM allotted-resource</li></ul>
+<li>FROM allotted-resource( allotted-resource org.onap.relationships.inventory.Uses network-policy, ONE2ONE)</li>
+<li>FROM l3-network( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)</li></ul>
</section>
@@ -157355,7 +176483,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Network profile populated by SDN-GP for SNMP</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM generic-vnf</li></ul>
+<li>TO generic-vnf( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)</li></ul>
</section>
@@ -157477,7 +176605,8 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO l-interface (comprises newvce, Many2Many)</li></ul>
+<li>FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)</li>
+<li>NEWVCE is DELETED when these are DELETED L-INTERFACE</li></ul>
</section>
@@ -158043,9 +177172,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>OAM network, to be deprecated shortly. Do not use for new purposes.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO complex (Many2Many)</li>
-<li>TO service-capability (Many2Many)</li>
-<li>FROM cloud-region (is composed of oam-network)</li></ul>
+<li>TO cloud-region( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>TO complex( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)</li>
+<li>TO service-capability( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)</li></ul>
</section>
@@ -158191,6 +177320,182 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-operational-environment" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/operational-environment"></a>operational-environment:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>It is a logical partition of the cloud which allows to have multiple environments in the production AIC.</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)</li>
+<li>FROM operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="operational-environment-id">
+ <span class="json-property-name">operational-environment-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>UUID of an operational environment</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="operational-environment-name">
+ <span class="json-property-name">operational-environment-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Operational Environment name</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="operational-environment-type">
+ <span class="json-property-name">operational-environment-type:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Operational Environment Type.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="operational-environment-status">
+ <span class="json-property-name">operational-environment-status:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Status</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="tenant-context">
+ <span class="json-property-name">tenant-context:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Tenant Context.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="workload-context">
+ <span class="json-property-name">workload-context:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Workload Context.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-operational-environments" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/operational-environments"></a>operational-environments:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>a logical partition of the cloud which allows to have multiple environments in the production AIC.</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="operational-environment">
+ <span class="json-property-name">operational-environment:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/operational-environment">operational-environment</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-overloaded-model" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/overloaded-model"></a>overloaded-model:
@@ -158409,7 +177714,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>describes an owning-entity</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO service-instance (One2Many)</li></ul>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo owning-entity, MANY2ONE)</li></ul>
</section>
@@ -158491,14 +177796,16 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Physical interface (e.g., nic)</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO l-interface (comprises p-interface, Many2Many)</li>
-<li>TO physical-link (Many2Many)</li>
-<li>TO logical-link (Many2One)</li>
-<li>TO sriov-pf (comprises p-interface, One2One)</li>
-<li>FROM lag-interface</li>
-<li>FROM pserver (is composed of p-interface)</li>
-<li>FROM pnf (is composed of p-interface)</li>
-<li>FROM vpls-pe (is composed of p-interface)</li></ul>
+<li>TO logical-link( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)</li>
+<li>TO physical-link( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)</li>
+<li>TO pnf( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)</li>
+<li>TO pserver( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)</li>
+<li>TO vpls-pe( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)</li>
+<li>FROM lag-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)</li>
+<li>FROM l-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)</li>
+<li>FROM sriov-pf( sriov-pf org.onap.relationships.inventory.BelongsTo p-interface, ONE2ONE)</li>
+<li>P-INTERFACE is DELETED when these are DELETED L-INTERFACE,SRIOV-PF</li>
+<li>P-INTERFACE deletion means associated objects of these types are also DELETED:PHYSICAL-LINK</li></ul>
</section>
@@ -158768,7 +178075,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Collection of physical connections, typically between p-interfaces</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM p-interface</li></ul>
+<li>FROM p-interface( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)</li></ul>
</section>
@@ -158998,7 +178305,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>describes a platform</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO generic-vnf (Many2Many)</li></ul>
+<li>TO generic-vnf( platform org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)</li></ul>
</section>
@@ -159108,15 +178415,16 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>PNF represents a physical network function. typically equipment used in the D1 world. in 1607, this will be populated by SDN-C to represent a premises router that a uCPE connects to. But this can be used to represent any physical device that is not an AIC node or uCPE.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO p-interface (comprises pnf, Many2Many)</li>
-<li>TO lag-interface (comprises pnf, One2Many)</li>
-<li>TO complex (Many2One)</li>
-<li>TO instance-group (Many2Many)</li>
-<li>TO zone (Many2One)</li>
-<li>FROM esr-thirdparty-sdnc</li>
-<li>FROM generic-vnf</li>
-<li>FROM logical-link</li>
-<li>FROM service-instance</li></ul>
+<li>TO complex( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>TO instance-group( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>TO zone( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)</li>
+<li>FROM esr-thirdparty-sdnc( esr-thirdparty-sdnc has pnf, One2Many)</li>
+<li>FROM generic-vnf( generic-vnf tosca.relationships.HostedOn pnf, MANY2MANY)</li>
+<li>FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)</li>
+<li>FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)</li>
+<li>FROM p-interface( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf pnf, ONE2MANY)</li>
+<li>PNF is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE</li></ul>
</section>
@@ -159506,8 +178814,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Used to capture the network interfaces of this VCE</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO cvlan-tag (comprises port-group, Many2Many)</li>
-<li>FROM vce (is composed of port-group)</li></ul>
+<li>TO vce( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)</li>
+<li>FROM cvlan-tag( cvlan-tag org.onap.relationships.inventory.BelongsTo port-group, MANY2ONE)</li>
+<li>PORT-GROUP is DELETED when these are DELETED CVLAN-TAG</li></ul>
</section>
@@ -159742,7 +179051,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>describes the project</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO service-instance (One2Many)</li></ul>
+<li>TO service-instance( project org.onap.relationships.inventory.Uses service-instance, ONE2MANY)</li></ul>
</section>
@@ -159895,7 +179204,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>TBD</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM named-query-element (is composed of property-constraint)</li></ul>
+<li>TO named-query-element( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)</li></ul>
</section>
@@ -160015,16 +179324,19 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Compute host whose hostname must be unique and must exactly match what is sent as a relationship to a vserver.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO complex (Many2One)</li>
-<li>TO cloud-region (Many2One)</li>
-<li>TO availability-zone (Many2One)</li>
-<li>TO lag-interface (comprises pserver, Many2Many)</li>
-<li>TO p-interface (comprises pserver, Many2Many)</li>
-<li>TO zone (Many2One)</li>
-<li>FROM generic-vnf</li>
-<li>FROM group-assignment</li>
-<li>FROM vserver</li>
-<li>FROM logical-link</li></ul>
+<li>TO group-assignment( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)</li>
+<li>TO availability-zone( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)</li>
+<li>TO cloud-region( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)</li>
+<li>TO complex( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>TO zone( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)</li>
+<li>FROM generic-vnf( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)</li>
+<li>FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)</li>
+<li>FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)</li>
+<li>FROM p-interface( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)</li>
+<li>FROM vserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)</li>
+<li>PSERVER cannot be deleted if linked to GENERIC-VNF,LOGICAL-LINK,VSERVER</li>
+<li>PSERVER is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE</li>
+<li>PSERVER cannot be deleted if linked to GROUP-ASSIGNMENT</li></ul>
</section>
@@ -160535,7 +179847,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>TBD</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM named-query-element (is composed of related-lookup)</li></ul>
+<li>TO named-query-element( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)</li></ul>
</section>
@@ -160782,26 +180094,6 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</section> </div>
</dd>
- <dt data-property-name="related-to-property">
- <span class="json-property-name">related-to-property:</span>
- <span class="json-property-type">object[]</span>
- <span class="json-property-range" title="Value limits"></span>
-
- </dt>
- <dd>
-
- <div class="json-inner-schema">
-
- <section class="json-schema-array-items">
- <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/related-to-property">related-to-property</a>
- </span>
- <span class="json-property-range" title="Value limits"></span>
-
- <div class="json-inner-schema">
-
- </div>
- </section> </div>
- </dd>
</dl>
</section>
</div>
@@ -161080,7 +180372,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Openstack route table reference.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM l3-network</li></ul>
+<li>FROM l3-network( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)</li></ul>
</section>
@@ -161203,7 +180495,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Route target information</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM vpn-binding (is composed of route-target)</li></ul>
+<li>TO vpn-binding( route-target org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2ONE)</li></ul>
</section>
@@ -161325,8 +180617,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<section class="json-schema-description">
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO site-pair (comprises routing-instance, Many2Many)</li>
-<li>FROM site-pair-set (is composed of routing-instance)</li></ul>
+<li>TO site-pair-set( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)</li>
+<li>FROM site-pair( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)</li>
+<li>ROUTING-INSTANCE is DELETED when these are DELETED SITE-PAIR</li></ul>
</section>
@@ -161771,7 +181064,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Openstack segmentation assignment.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM l3-network (is composed of segmentation-assignment)</li></ul>
+<li>TO l3-network( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)</li></ul>
</section>
@@ -162025,8 +181318,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Early definition of server/resource pairings, likely to be replaced by models. No new use should be made of this.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM availability-zone</li>
-<li>FROM oam-network</li></ul>
+<li>FROM availability-zone( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)</li>
+<li>FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)</li>
+<li>SERVICE-CAPABILITY cannot be deleted if linked to AVAILABILITY-ZONE,OAM-NETWORK</li></ul>
</section>
@@ -162229,26 +181523,28 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Instance of a service</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO configuration (One2Many)</li>
-<li>TO zone (Many2One)</li>
-<li>TO cvlan-tag (Many2Many)</li>
-<li>TO pnf (One2Many)</li>
-<li>TO connector (Many2Many)</li>
-<li>TO metadatum (comprises service-instance, Many2Many)</li>
-<li>TO logical-link (Many2Many)</li>
-<li>TO vlan (One2Many)</li>
-<li>TO service-instance (One2Many)</li>
-<li>TO ctag-assignment (One2Many)</li>
-<li>TO instance-group (Many2Many)</li>
-<li>TO allotted-resource (comprises service-instance, Many2Many)</li>
-<li>TO allotted-resource (Many2Many)</li>
-<li>FROM generic-vnf</li>
-<li>FROM l3-network</li>
-<li>FROM owning-entity</li>
-<li>FROM project</li>
-<li>FROM service-subscription (is composed of service-instance)</li>
-<li>FROM vce</li>
-<li>FROM service-instance</li></ul>
+<li>TO generic-vnf( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)</li>
+<li>TO l3-network( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)</li>
+<li>TO owning-entity( service-instance org.onap.relationships.inventory.BelongsTo owning-entity, MANY2ONE)</li>
+<li>TO allotted-resource( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY)</li>
+<li>TO configuration( service-instance org.onap.relationships.inventory.Uses configuration, ONE2MANY)</li>
+<li>TO connector( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)</li>
+<li>TO ctag-assignment( service-instance org.onap.relationships.inventory.Uses ctag-assignment, ONE2MANY)</li>
+<li>TO cvlan-tag( service-instance org.onap.relationships.inventory.ComposedOf cvlan-tag, MANY2MANY)</li>
+<li>TO instance-group( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>TO logical-link( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)</li>
+<li>TO pnf( service-instance org.onap.relationships.inventory.ComposedOf pnf, ONE2MANY)</li>
+<li>TO service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)</li>
+<li>TO vlan( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)</li>
+<li>TO zone( service-instance org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)</li>
+<li>TO service-subscription( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)</li>
+<li>TO vce( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)</li>
+<li>FROM project( project org.onap.relationships.inventory.Uses service-instance, ONE2MANY)</li>
+<li>FROM allotted-resource( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)</li>
+<li>FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)</li>
+<li>SERVICE-INSTANCE is DELETED when these are DELETED ALLOTTED-RESOURCE,METADATUM</li>
+<li>SERVICE-INSTANCE deletion means associated objects of these types are also DELETED:LOGICAL-LINK</li></ul>
</section>
@@ -162329,6 +181625,45 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</dd>
+ <dt data-property-name="created-at">
+ <span class="json-property-name">created-at:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>create time of Network Service.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="updated-at">
+ <span class="json-property-name">updated-at:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>last update of Network Service.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="description">
+ <span class="json-property-name">description:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>short description for service-instance.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
<dt data-property-name="model-invariant-id">
<span class="json-property-name">model-invariant-id:</span>
<span class="json-property-type">string</span>
@@ -162628,9 +181963,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Object that group service instances.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO service-instance (comprises service-subscription, Many2Many)</li>
-<li>FROM customer (is composed of service-subscription)</li>
-<li>FROM tenant</li></ul>
+<li>TO customer( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)</li>
+<li>TO tenant( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)</li>
+<li>SERVICE-SUBSCRIPTION is DELETED when these are DELETED SERVICE-INSTANCE</li></ul>
</section>
@@ -162812,8 +182148,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<section class="json-schema-description">
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO class-of-service (comprises site-pair, Many2Many)</li>
-<li>FROM routing-instance (is composed of site-pair)</li></ul>
+<li>TO routing-instance( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)</li>
+<li>FROM class-of-service( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)</li>
+<li>SITE-PAIR is DELETED when these are DELETED CLASS-OF-SERVICE</li></ul>
</section>
@@ -162962,8 +182299,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Set of instances for probes used to measure service level agreements</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO routing-instance (comprises site-pair-set, Many2Many)</li>
-<li>FROM generic-vnf</li></ul>
+<li>TO generic-vnf( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)</li>
+<li>FROM routing-instance( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)</li>
+<li>SITE-PAIR-SET is DELETED when these are DELETED ROUTING-INSTANCE</li></ul>
</section>
@@ -163134,8 +182472,8 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Openstack snapshot</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM cloud-region (is composed of snapshot)</li>
-<li>FROM vserver</li></ul>
+<li>TO cloud-region( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM vserver( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)</li></ul>
</section>
@@ -163353,8 +182691,8 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>SR-IOV Physical Function</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM p-interface (is composed of sriov-pf)</li>
-<li>FROM sriov-vf</li></ul>
+<li>TO p-interface( sriov-pf org.onap.relationships.inventory.BelongsTo p-interface, ONE2ONE)</li>
+<li>FROM sriov-vf( sriov-vf org.onap.relationships.inventory.Uses sriov-pf, MANY2ONE)</li></ul>
</section>
@@ -163464,8 +182802,8 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>SR-IOV Virtual Function (not to be confused with virtual network function)</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO sriov-pf (Many2One)</li>
-<li>FROM l-interface (is composed of sriov-vf)</li></ul>
+<li>TO l-interface( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)</li>
+<li>TO sriov-pf( sriov-vf org.onap.relationships.inventory.Uses sriov-pf, MANY2ONE)</li></ul>
</section>
@@ -163757,12 +183095,14 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<section class="json-schema-description">
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO host-route (comprises subnet, One2Many)</li>
-<li>FROM l3-interface-ipv4-address-list</li>
-<li>FROM l3-interface-ipv6-address-list</li>
-<li>FROM l3-network (is composed of subnet)</li>
-<li>FROM vip-ipv4-address-list</li>
-<li>FROM vip-ipv6-address-list</li></ul>
+<li>TO l3-network( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)</li>
+<li>FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)</li>
+<li>FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)</li>
+<li>FROM host-route( host-route org.onap.relationships.inventory.BelongsTo subnet, MANY2ONE)</li>
+<li>FROM vip-ipv4-address-list( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)</li>
+<li>FROM vip-ipv6-address-list( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)</li>
+<li>SUBNET cannot be deleted if linked to L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST,VIP-IPV4-ADDRESS-LIST,VIP-IPV6-ADDRESS-LIST</li>
+<li>SUBNET is DELETED when these are DELETED HOST-ROUTE</li></ul>
</section>
@@ -164081,12 +183421,13 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Openstack tenant</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO l3-network (Many2Many)</li>
-<li>TO service-subscription (Many2Many)</li>
-<li>TO vserver (comprises tenant, One2Many)</li>
-<li>FROM cloud-region (is composed of tenant)</li>
-<li>FROM group-assignment</li>
-<li>FROM volume-group</li></ul>
+<li>TO cloud-region( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>TO group-assignment( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)</li>
+<li>TO l3-network( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>TO volume-group( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)</li>
+<li>FROM service-subscription( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)</li>
+<li>FROM vserver( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)</li>
+<li>TENANT cannot be deleted if linked to VSERVER</li></ul>
</section>
@@ -164241,7 +183582,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Represents the specifics of a tunnel cross connect piece of a resource that gets separately allotted</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM allotted-resource (is composed of tunnel-xconnect)</li></ul>
+<li>TO allotted-resource( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)</li></ul>
</section>
@@ -164526,13 +183867,14 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Virtual Customer Edge Router, used specifically for Gamma. This object is deprecated.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO availability-zone (Many2Many)</li>
-<li>TO complex (Many2Many)</li>
-<li>TO port-group (comprises vce, Many2Many)</li>
-<li>TO vserver (Many2Many)</li>
-<li>TO service-instance (Many2Many)</li>
-<li>TO entitlement (comprises vce, One2Many)</li>
-<li>TO license (comprises vce, One2Many)</li></ul>
+<li>TO availability-zone( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)</li>
+<li>TO complex( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)</li>
+<li>TO vserver( vce tosca.relationships.HostedOn vserver, ONE2MANY)</li>
+<li>FROM entitlement( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)</li>
+<li>FROM license( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)</li>
+<li>FROM port-group( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)</li>
+<li>VCE is DELETED when these are DELETED ENTITLEMENT,LICENSE,PORT-GROUP</li></ul>
</section>
@@ -164908,11 +184250,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>a deployment unit of VNFCs</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO volume-group (One2One)</li>
-<li>TO l3-network (Many2Many)</li>
-<li>TO vnfc (One2Many)</li>
-<li>FROM vserver</li>
-<li>FROM generic-vnf (is composed of vf-module)</li></ul>
+<li>TO generic-vnf( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>TO l3-network( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)</li>
+<li>TO vnfc( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)</li>
+<li>TO volume-group( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)</li>
+<li>TO vserver( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)</li>
+<li>VF-MODULE cannot be deleted if linked to VNFC</li></ul>
</section>
@@ -165178,7 +184521,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>vig-server contains information about a vig server used for IPSec-configuration. Populated by SDN-C from 1607</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM ipsec-configuration (is composed of vig-server)</li></ul>
+<li>TO ipsec-configuration( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)</li></ul>
</section>
@@ -165308,10 +184651,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>IPv4 Address Range</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO instance-group (Many2Many)</li>
-<li>TO subnet (Many2Many)</li>
-<li>FROM vnfc</li>
-<li>FROM cloud-region (is composed of vip-ipv4-address-list)</li></ul>
+<li>TO cloud-region( vip-ipv4-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>TO instance-group( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>TO subnet( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)</li>
+<li>FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv4-address-list, MANY2MANY)</li></ul>
</section>
@@ -165452,10 +184795,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>IPv6 Address Range</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO instance-group (Many2Many)</li>
-<li>TO subnet (Many2Many)</li>
-<li>FROM vnfc</li>
-<li>FROM cloud-region (is composed of vip-ipv6-address-list)</li></ul>
+<li>TO cloud-region( vip-ipv6-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>TO instance-group( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>TO subnet( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)</li>
+<li>FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv6-address-list, MANY2MANY)</li></ul>
</section>
@@ -165596,9 +184939,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Virtual organization of cloud infrastructure elements in a data center context</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO generic-vnf (Many2Many)</li>
-<li>TO logical-link (Many2Many)</li>
-<li>FROM connector</li></ul>
+<li>FROM connector( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)</li>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)</li>
+<li>FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)</li></ul>
</section>
@@ -165721,13 +185064,15 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Definition of vlan</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO l3-interface-ipv4-address-list (comprises vlan, Many2Many)</li>
-<li>TO l3-interface-ipv6-address-list (comprises vlan, Many2Many)</li>
-<li>TO multicast-configuration (Many2Many)</li>
-<li>TO logical-link (Many2Many)</li>
-<li>FROM l-interface (is composed of vlan)</li>
-<li>FROM service-instance</li>
-<li>FROM allotted-resource</li></ul>
+<li>TO l-interface( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)</li>
+<li>TO logical-link( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)</li>
+<li>TO multicast-configuration( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)</li>
+<li>FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)</li>
+<li>FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)</li>
+<li>FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)</li>
+<li>VLAN is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST</li>
+<li>VLAN deletion means associated objects of these types are also DELETED:LOGICAL-LINK</li></ul>
</section>
@@ -166039,7 +185384,8 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Image object that pertain to a VNF that doesn't have associated vservers. This is a kludge.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM generic-vnf</li></ul>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)</li>
+<li>VNF-IMAGE cannot be deleted if linked to GENERIC-VNF</li></ul>
</section>
@@ -166198,14 +185544,15 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<section class="json-schema-description">
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO instance-group (Many2Many)</li>
-<li>TO vip-ipv4-address-list (Many2Many)</li>
-<li>TO vip-ipv6-address-list (Many2Many)</li>
-<li>FROM vserver</li>
-<li>FROM vf-module</li>
-<li>FROM generic-vnf</li>
-<li>FROM l3-interface-ipv4-address-list (comprises vnfc)</li>
-<li>FROM l3-interface-ipv6-address-list (comprises vnfc)</li></ul>
+<li>TO generic-vnf( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>TO instance-group( vnfc org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>TO vip-ipv4-address-list( vnfc org.onap.relationships.inventory.Uses vip-ipv4-address-list, MANY2MANY)</li>
+<li>TO vip-ipv6-address-list( vnfc org.onap.relationships.inventory.Uses vip-ipv6-address-list, MANY2MANY)</li>
+<li>TO vserver( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)</li>
+<li>FROM vf-module( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)</li>
+<li>FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vnfc, MANY2ONE)</li>
+<li>FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vnfc, MANY2ONE)</li>
+<li>VNFC is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST</li></ul>
</section>
@@ -166477,7 +185824,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Ephemeral Block storage volume.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM vserver (is composed of volume)</li></ul>
+<li>FROM vserver (PARENT of volume, vserver tosca.relationships.AttachesTo volume)</li></ul>
</section>
@@ -166559,11 +185906,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Persistent block-level storage.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO complex (Many2Many)</li>
-<li>TO tenant (Many2Many)</li>
-<li>FROM cloud-region (is composed of volume-group)</li>
-<li>FROM vf-module</li>
-<li>FROM generic-vnf</li></ul>
+<li>TO cloud-region( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>TO complex( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)</li>
+<li>FROM vf-module( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)</li>
+<li>FROM tenant( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)</li></ul>
</section>
@@ -166788,10 +186135,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>VPLS Provider Edge routers.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO complex (Many2Many)</li>
-<li>TO ctag-pool (Many2Many)</li>
-<li>TO p-interface (comprises vpls-pe, Many2Many)</li>
-<li>TO lag-interface (comprises vpls-pe, Many2Many)</li></ul>
+<li>TO complex( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>TO ctag-pool( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)</li>
+<li>FROM lag-interface( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)</li>
+<li>FROM p-interface( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)</li>
+<li>VPLS-PE is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE</li></ul>
</section>
@@ -166988,10 +186336,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>VPN binding</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO route-target (comprises vpn-binding, One2Many)</li>
-<li>FROM l3-network</li>
-<li>FROM logical-link</li>
-<li>FROM allotted-resource</li></ul>
+<li>FROM allotted-resource( allotted-resource org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2MANY)</li>
+<li>FROM l3-network( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)</li>
+<li>FROM logical-link( logical-link org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)</li>
+<li>FROM route-target( route-target org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2ONE)</li>
+<li>VPN-BINDING cannot be deleted if linked to ALLOTTED-RESOURCE,L3-NETWORK,LOGICAL-LINK</li>
+<li>VPN-BINDING is DELETED when these are DELETED ROUTE-TARGET</li></ul>
</section>
@@ -167190,17 +186540,19 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Virtual Servers, aka virtual machine or VM.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO flavor (Many2One)</li>
-<li>TO image (Many2One)</li>
-<li>TO l-interface (comprises vserver, Many2Many)</li>
-<li>TO pserver (Many2One)</li>
-<li>TO volume (comprises vserver, Many2Many)</li>
-<li>TO vnfc (Many2Many)</li>
-<li>TO snapshot (One2One)</li>
-<li>TO vf-module (Many2One)</li>
-<li>FROM generic-vnf</li>
-<li>FROM tenant (is composed of vserver)</li>
-<li>FROM vce</li></ul>
+<li>TO tenant( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)</li>
+<li>TO flavor( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)</li>
+<li>TO image( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)</li>
+<li>TO pserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)</li>
+<li>TO snapshot( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)</li>
+<li>TO volume (CHILD of vserver, vserver tosca.relationships.AttachesTo volume, ONE2MANY)</li>
+<li>FROM generic-vnf( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)</li>
+<li>FROM vce( vce tosca.relationships.HostedOn vserver, ONE2MANY)</li>
+<li>FROM l-interface( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)</li>
+<li>FROM vf-module( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)</li>
+<li>FROM vnfc( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)</li>
+<li>VSERVER is DELETED when these are DELETED L-INTERFACE</li>
+<li>VSERVER deletion means associated objects of these types are also DELETED:VOLUME</li></ul>
</section>
@@ -167424,11 +186776,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>A zone is a grouping of assets in a location homing to the same connections into the CBB</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO complex (Many2One)</li>
-<li>FROM cloud-region</li>
-<li>FROM pserver</li>
-<li>FROM pnf</li>
-<li>FROM service-instance</li></ul>
+<li>TO complex( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)</li>
+<li>FROM pnf( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)</li>
+<li>FROM pserver( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)</li></ul>
</section>
diff --git a/aai-schema/src/main/resources/aai_swagger_html/aai_swagger_v8.html b/aai-schema/src/main/resources/aai_swagger_html/aai_swagger_v8.html
index d4cfa0c8..be07b77b 100644
--- a/aai-schema/src/main/resources/aai_swagger_html/aai_swagger_v8.html
+++ b/aai-schema/src/main/resources/aai_swagger_html/aai_swagger_v8.html
@@ -15,7 +15,10 @@
<div class="container">
<h1>Active and Available Inventory REST API.</h1>
<p class="sw-info-version">Version: <span>v12</span></p>
- <p><p>Copyright &copy; 2017 AT&amp;T Intellectual Property. All rights reserved.<br/>
+ <p><p><br/>
+[Differences versus the previous schema version](apidocs/aai_swagger_v8.diff)<br/>
+<br/>
+Copyright &copy; 2017 AT&amp;T Intellectual Property. All rights reserved.<br/>
<br/>
Licensed under the Creative Commons License, Attribution 4.0 Intl. (the &quot;License&quot;); you may not use this documentation except in compliance with the License.<br/>
<br/>
@@ -64,6 +67,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}</a></td>
+ <td><p>update an existing cloud-region</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}</a></td>
<td><p>delete an existing cloud-region</p>
</td>
@@ -84,6 +92,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--availability-zones-availability-zone--availability-zone-name--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/availability-zones/availability-zone/{availability-zone-name}</a></td>
+ <td><p>update an existing availability-zone</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--availability-zones-availability-zone--availability-zone-name--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/availability-zones/availability-zone/{availability-zone-name}</a></td>
<td><p>delete an existing availability-zone</p>
</td>
@@ -114,6 +127,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--dvs-switches-dvs-switch--switch-name--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/dvs-switches/dvs-switch/{switch-name}</a></td>
+ <td><p>update an existing dvs-switch</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--dvs-switches-dvs-switch--switch-name--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/dvs-switches/dvs-switch/{switch-name}</a></td>
<td><p>delete an existing dvs-switch</p>
</td>
@@ -144,6 +162,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--flavors-flavor--flavor-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/flavors/flavor/{flavor-id}</a></td>
+ <td><p>update an existing flavor</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--flavors-flavor--flavor-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/flavors/flavor/{flavor-id}</a></td>
<td><p>delete an existing flavor</p>
</td>
@@ -174,6 +197,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--group-assignments-group-assignment--group-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/group-assignments/group-assignment/{group-id}</a></td>
+ <td><p>update an existing group-assignment</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--group-assignments-group-assignment--group-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/group-assignments/group-assignment/{group-id}</a></td>
<td><p>delete an existing group-assignment</p>
</td>
@@ -204,6 +232,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}</a></td>
+ <td><p>update an existing image</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}</a></td>
<td><p>delete an existing image</p>
</td>
@@ -224,6 +257,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--metadata-metadatum--metaname--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}/metadata/metadatum/{metaname}</a></td>
+ <td><p>update an existing metadatum</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--metadata-metadatum--metaname--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}/metadata/metadatum/{metaname}</a></td>
<td><p>delete an existing metadatum</p>
</td>
@@ -254,6 +292,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--oam-networks-oam-network--network-uuid--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/oam-networks/oam-network/{network-uuid}</a></td>
+ <td><p>update an existing oam-network</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--oam-networks-oam-network--network-uuid--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/oam-networks/oam-network/{network-uuid}</a></td>
<td><p>delete an existing oam-network</p>
</td>
@@ -294,6 +337,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--snapshots-snapshot--snapshot-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/snapshots/snapshot/{snapshot-id}</a></td>
+ <td><p>update an existing snapshot</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--snapshots-snapshot--snapshot-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/snapshots/snapshot/{snapshot-id}</a></td>
<td><p>delete an existing snapshot</p>
</td>
@@ -324,6 +372,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}</a></td>
+ <td><p>update an existing tenant</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}</a></td>
<td><p>delete an existing tenant</p>
</td>
@@ -354,6 +407,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}</a></td>
+ <td><p>update an existing vserver</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}</a></td>
<td><p>delete an existing vserver</p>
</td>
@@ -374,6 +432,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -389,6 +452,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -414,6 +482,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -454,6 +527,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -484,6 +562,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -499,6 +582,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -524,6 +612,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -574,6 +667,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--volumes-volume--volume-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/volumes/volume/{volume-id}</a></td>
+ <td><p>update an existing volume</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--volumes-volume--volume-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/volumes/volume/{volume-id}</a></td>
<td><p>delete an existing volume</p>
</td>
@@ -604,6 +702,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--volume-groups-volume-group--volume-group-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/volume-groups/volume-group/{volume-group-id}</a></td>
+ <td><p>update an existing volume-group</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--volume-groups-volume-group--volume-group-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/volume-groups/volume-group/{volume-group-id}</a></td>
<td><p>delete an existing volume-group</p>
</td>
@@ -634,6 +737,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-complexes-complex--physical-location-id--patch">PATCH /cloud-infrastructure/complexes/complex/{physical-location-id}</a></td>
+ <td><p>update an existing complex</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-complexes-complex--physical-location-id--delete">DELETE /cloud-infrastructure/complexes/complex/{physical-location-id}</a></td>
<td><p>delete an existing complex</p>
</td>
@@ -654,6 +762,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-complexes-complex--physical-location-id--ctag-pools-ctag-pool--target-pe---availability-zone-name--patch">PATCH /cloud-infrastructure/complexes/complex/{physical-location-id}/ctag-pools/ctag-pool/{target-pe}/{availability-zone-name}</a></td>
+ <td><p>update an existing ctag-pool</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-complexes-complex--physical-location-id--ctag-pools-ctag-pool--target-pe---availability-zone-name--delete">DELETE /cloud-infrastructure/complexes/complex/{physical-location-id}/ctag-pools/ctag-pool/{target-pe}/{availability-zone-name}</a></td>
<td><p>delete an existing ctag-pool</p>
</td>
@@ -694,6 +807,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-network-profiles-network-profile--nm-profile-name--patch">PATCH /cloud-infrastructure/network-profiles/network-profile/{nm-profile-name}</a></td>
+ <td><p>update an existing network-profile</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-network-profiles-network-profile--nm-profile-name--delete">DELETE /cloud-infrastructure/network-profiles/network-profile/{nm-profile-name}</a></td>
<td><p>delete an existing network-profile</p>
</td>
@@ -724,6 +842,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}</a></td>
+ <td><p>update an existing pserver</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}</a></td>
<td><p>delete an existing pserver</p>
</td>
@@ -744,6 +867,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}</a></td>
+ <td><p>update an existing lag-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}</a></td>
<td><p>delete an existing lag-interface</p>
</td>
@@ -764,6 +892,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -779,6 +912,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -804,6 +942,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -844,6 +987,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -874,6 +1022,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -889,6 +1042,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -914,6 +1072,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -964,6 +1127,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}</a></td>
+ <td><p>update an existing p-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}</a></td>
<td><p>delete an existing p-interface</p>
</td>
@@ -984,6 +1152,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -999,6 +1172,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -1024,6 +1202,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -1064,6 +1247,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -1094,6 +1282,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -1109,6 +1302,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -1134,6 +1332,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -1194,6 +1397,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--patch">PATCH /cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}</a></td>
+ <td><p>update an existing virtual-data-center</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--delete">DELETE /cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}</a></td>
<td><p>delete an existing virtual-data-center</p>
</td>
@@ -1238,6 +1446,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-connectors-connector--resource-instance-id--patch">PATCH /business/connectors/connector/{resource-instance-id}</a></td>
+ <td><p>update an existing connector</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-connectors-connector--resource-instance-id--delete">DELETE /business/connectors/connector/{resource-instance-id}</a></td>
<td><p>delete an existing connector</p>
</td>
@@ -1258,6 +1471,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-connectors-connector--resource-instance-id--metadata-metadatum--metaname--patch">PATCH /business/connectors/connector/{resource-instance-id}/metadata/metadatum/{metaname}</a></td>
+ <td><p>update an existing metadatum</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-connectors-connector--resource-instance-id--metadata-metadatum--metaname--delete">DELETE /business/connectors/connector/{resource-instance-id}/metadata/metadatum/{metaname}</a></td>
<td><p>delete an existing metadatum</p>
</td>
@@ -1288,6 +1506,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-customers-customer--global-customer-id--patch">PATCH /business/customers/customer/{global-customer-id}</a></td>
+ <td><p>update an existing customer</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-customers-customer--global-customer-id--delete">DELETE /business/customers/customer/{global-customer-id}</a></td>
<td><p>delete an existing customer</p>
</td>
@@ -1318,6 +1541,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--patch">PATCH /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}</a></td>
+ <td><p>update an existing service-subscription</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--delete">DELETE /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}</a></td>
<td><p>delete an existing service-subscription</p>
</td>
@@ -1348,6 +1576,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--patch">PATCH /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}</a></td>
+ <td><p>update an existing service-instance</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--delete">DELETE /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}</a></td>
<td><p>delete an existing service-instance</p>
</td>
@@ -1368,6 +1601,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--metadata-metadatum--metaname--patch">PATCH /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/metadata/metadatum/{metaname}</a></td>
+ <td><p>update an existing metadatum</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--metadata-metadatum--metaname--delete">DELETE /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/metadata/metadatum/{metaname}</a></td>
<td><p>delete an existing metadatum</p>
</td>
@@ -1412,6 +1650,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-models-model--model-name-version-id--patch">PATCH /service-design-and-creation/models/model/{model-name-version-id}</a></td>
+ <td><p>update an existing model</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-models-model--model-name-version-id--delete">DELETE /service-design-and-creation/models/model/{model-name-version-id}</a></td>
<td><p>delete an existing model</p>
</td>
@@ -1432,6 +1675,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-models-model--model-name-version-id--metadata-metadatum--metaname--patch">PATCH /service-design-and-creation/models/model/{model-name-version-id}/metadata/metadatum/{metaname}</a></td>
+ <td><p>update an existing metadatum</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-models-model--model-name-version-id--metadata-metadatum--metaname--delete">DELETE /service-design-and-creation/models/model/{model-name-version-id}/metadata/metadatum/{metaname}</a></td>
<td><p>delete an existing metadatum</p>
</td>
@@ -1452,6 +1700,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-models-model--model-name-version-id--model-elements-model-element--model-element-uuid--patch">PATCH /service-design-and-creation/models/model/{model-name-version-id}/model-elements/model-element/{model-element-uuid}</a></td>
+ <td><p>update an existing model-element</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-models-model--model-name-version-id--model-elements-model-element--model-element-uuid--delete">DELETE /service-design-and-creation/models/model/{model-name-version-id}/model-elements/model-element/{model-element-uuid}</a></td>
<td><p>delete an existing model-element</p>
</td>
@@ -1472,6 +1725,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-models-model--model-name-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--patch">PATCH /service-design-and-creation/models/model/{model-name-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}</a></td>
+ <td><p>update an existing model-constraint</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-models-model--model-name-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--delete">DELETE /service-design-and-creation/models/model/{model-name-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}</a></td>
<td><p>delete an existing model-constraint</p>
</td>
@@ -1492,6 +1750,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-models-model--model-name-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--patch">PATCH /service-design-and-creation/models/model/{model-name-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}</a></td>
+ <td><p>update an existing constrained-element-set</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-models-model--model-name-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--delete">DELETE /service-design-and-creation/models/model/{model-name-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}</a></td>
<td><p>delete an existing constrained-element-set</p>
</td>
@@ -1512,6 +1775,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-models-model--model-name-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--element-choice-sets-element-choice-set--element-choice-set-uuid--patch">PATCH /service-design-and-creation/models/model/{model-name-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}/element-choice-sets/element-choice-set/{element-choice-set-uuid}</a></td>
+ <td><p>update an existing element-choice-set</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-models-model--model-name-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--element-choice-sets-element-choice-set--element-choice-set-uuid--delete">DELETE /service-design-and-creation/models/model/{model-name-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}/element-choice-sets/element-choice-set/{element-choice-set-uuid}</a></td>
<td><p>delete an existing element-choice-set</p>
</td>
@@ -1572,6 +1840,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--patch">PATCH /service-design-and-creation/named-queries/named-query/{named-query-uuid}</a></td>
+ <td><p>update an existing named-query</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--delete">DELETE /service-design-and-creation/named-queries/named-query/{named-query-uuid}</a></td>
<td><p>delete an existing named-query</p>
</td>
@@ -1592,6 +1865,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--patch">PATCH /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}</a></td>
+ <td><p>update an existing named-query-element</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--delete">DELETE /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}</a></td>
<td><p>delete an existing named-query-element</p>
</td>
@@ -1612,6 +1890,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--property-constraints-property-constraint--property-constraint-uuid--patch">PATCH /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/property-constraints/property-constraint/{property-constraint-uuid}</a></td>
+ <td><p>update an existing property-constraint</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--property-constraints-property-constraint--property-constraint-uuid--delete">DELETE /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/property-constraints/property-constraint/{property-constraint-uuid}</a></td>
<td><p>delete an existing property-constraint</p>
</td>
@@ -1632,6 +1915,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--related-lookups-related-lookup--related-lookup-uuid--patch">PATCH /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/related-lookups/related-lookup/{related-lookup-uuid}</a></td>
+ <td><p>update an existing related-lookup</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--related-lookups-related-lookup--related-lookup-uuid--delete">DELETE /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/related-lookups/related-lookup/{related-lookup-uuid}</a></td>
<td><p>delete an existing related-lookup</p>
</td>
@@ -1682,6 +1970,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-service-capabilities-service-capability--service-type---vnf-type--patch">PATCH /service-design-and-creation/service-capabilities/service-capability/{service-type}/{vnf-type}</a></td>
+ <td><p>update an existing service-capability</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-service-capabilities-service-capability--service-type---vnf-type--delete">DELETE /service-design-and-creation/service-capabilities/service-capability/{service-type}/{vnf-type}</a></td>
<td><p>delete an existing service-capability</p>
</td>
@@ -1712,6 +2005,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-services-service--service-id--patch">PATCH /service-design-and-creation/services/service/{service-id}</a></td>
+ <td><p>update an existing service</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-services-service--service-id--delete">DELETE /service-design-and-creation/services/service/{service-id}</a></td>
<td><p>delete an existing service</p>
</td>
@@ -1742,6 +2040,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-vnf-images-vnf-image--vnf-image-uuid--patch">PATCH /service-design-and-creation/vnf-images/vnf-image/{vnf-image-uuid}</a></td>
+ <td><p>update an existing vnf-image</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-vnf-images-vnf-image--vnf-image-uuid--delete">DELETE /service-design-and-creation/vnf-images/vnf-image/{vnf-image-uuid}</a></td>
<td><p>delete an existing vnf-image</p>
</td>
@@ -1786,6 +2089,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}</a></td>
+ <td><p>update an existing generic-vnf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}</a></td>
<td><p>delete an existing generic-vnf</p>
</td>
@@ -1806,6 +2114,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -1821,6 +2134,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -1846,6 +2164,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -1886,6 +2209,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -1916,6 +2244,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -1931,6 +2264,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -1956,6 +2294,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -1996,6 +2339,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}</a></td>
+ <td><p>update an existing lag-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}</a></td>
<td><p>delete an existing lag-interface</p>
</td>
@@ -2016,6 +2364,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -2031,6 +2384,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -2056,6 +2414,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -2096,6 +2459,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -2126,6 +2494,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -2141,6 +2514,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -2166,6 +2544,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -2226,6 +2609,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--vf-modules-vf-module--vf-module-id--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/vf-modules/vf-module/{vf-module-id}</a></td>
+ <td><p>update an existing vf-module</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--vf-modules-vf-module--vf-module-id--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/vf-modules/vf-module/{vf-module-id}</a></td>
<td><p>delete an existing vf-module</p>
</td>
@@ -2256,6 +2644,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--patch">PATCH /network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}</a></td>
+ <td><p>update an existing ipsec-configuration</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--delete">DELETE /network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}</a></td>
<td><p>delete an existing ipsec-configuration</p>
</td>
@@ -2286,6 +2679,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--vig-servers-vig-server--vig-address-type--patch">PATCH /network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}/vig-servers/vig-server/{vig-address-type}</a></td>
+ <td><p>update an existing vig-server</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--vig-servers-vig-server--vig-address-type--delete">DELETE /network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}/vig-servers/vig-server/{vig-address-type}</a></td>
<td><p>delete an existing vig-server</p>
</td>
@@ -2316,6 +2714,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-l3-networks-l3-network--network-id--patch">PATCH /network/l3-networks/l3-network/{network-id}</a></td>
+ <td><p>update an existing l3-network</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-l3-networks-l3-network--network-id--delete">DELETE /network/l3-networks/l3-network/{network-id}</a></td>
<td><p>delete an existing l3-network</p>
</td>
@@ -2336,6 +2739,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-l3-networks-l3-network--network-id--ctag-assignments-ctag-assignment--vlan-id-inner--patch">PATCH /network/l3-networks/l3-network/{network-id}/ctag-assignments/ctag-assignment/{vlan-id-inner}</a></td>
+ <td><p>update an existing ctag-assignment</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-l3-networks-l3-network--network-id--ctag-assignments-ctag-assignment--vlan-id-inner--delete">DELETE /network/l3-networks/l3-network/{network-id}/ctag-assignments/ctag-assignment/{vlan-id-inner}</a></td>
<td><p>delete an existing ctag-assignment</p>
</td>
@@ -2376,6 +2784,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-l3-networks-l3-network--network-id--segmentation-assignments-segmentation-assignment--segmentation-id--patch">PATCH /network/l3-networks/l3-network/{network-id}/segmentation-assignments/segmentation-assignment/{segmentation-id}</a></td>
+ <td><p>update an existing segmentation-assignment</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-l3-networks-l3-network--network-id--segmentation-assignments-segmentation-assignment--segmentation-id--delete">DELETE /network/l3-networks/l3-network/{network-id}/segmentation-assignments/segmentation-assignment/{segmentation-id}</a></td>
<td><p>delete an existing segmentation-assignment</p>
</td>
@@ -2406,6 +2819,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-l3-networks-l3-network--network-id--subnets-subnet--subnet-id--patch">PATCH /network/l3-networks/l3-network/{network-id}/subnets/subnet/{subnet-id}</a></td>
+ <td><p>update an existing subnet</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-l3-networks-l3-network--network-id--subnets-subnet--subnet-id--delete">DELETE /network/l3-networks/l3-network/{network-id}/subnets/subnet/{subnet-id}</a></td>
<td><p>delete an existing subnet</p>
</td>
@@ -2436,6 +2854,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-lag-links-lag-link--link-name--patch">PATCH /network/lag-links/lag-link/{link-name}</a></td>
+ <td><p>update an existing lag-link</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-lag-links-lag-link--link-name--delete">DELETE /network/lag-links/lag-link/{link-name}</a></td>
<td><p>delete an existing lag-link</p>
</td>
@@ -2466,6 +2889,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-logical-links-logical-link--link-name--patch">PATCH /network/logical-links/logical-link/{link-name}</a></td>
+ <td><p>update an existing logical-link</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-logical-links-logical-link--link-name--delete">DELETE /network/logical-links/logical-link/{link-name}</a></td>
<td><p>delete an existing logical-link</p>
</td>
@@ -2496,6 +2924,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-multicast-configurations-multicast-configuration--multicast-configuration-id--patch">PATCH /network/multicast-configurations/multicast-configuration/{multicast-configuration-id}</a></td>
+ <td><p>update an existing multicast-configuration</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-multicast-configurations-multicast-configuration--multicast-configuration-id--delete">DELETE /network/multicast-configurations/multicast-configuration/{multicast-configuration-id}</a></td>
<td><p>delete an existing multicast-configuration</p>
</td>
@@ -2526,6 +2959,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-network-policies-network-policy--network-policy-id--patch">PATCH /network/network-policies/network-policy/{network-policy-id}</a></td>
+ <td><p>update an existing network-policy</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-network-policies-network-policy--network-policy-id--delete">DELETE /network/network-policies/network-policy/{network-policy-id}</a></td>
<td><p>delete an existing network-policy</p>
</td>
@@ -2556,6 +2994,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--patch">PATCH /network/newvces/newvce/{vnf-id2}</a></td>
+ <td><p>update an existing newvce</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--delete">DELETE /network/newvces/newvce/{vnf-id2}</a></td>
<td><p>delete an existing newvce</p>
</td>
@@ -2576,6 +3019,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--patch">PATCH /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--delete">DELETE /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -2591,6 +3039,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -2616,6 +3069,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -2656,6 +3114,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -2686,6 +3149,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -2701,6 +3169,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -2726,6 +3199,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -2776,6 +3254,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-physical-links-physical-link--link-name--patch">PATCH /network/physical-links/physical-link/{link-name}</a></td>
+ <td><p>update an existing physical-link</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-physical-links-physical-link--link-name--delete">DELETE /network/physical-links/physical-link/{link-name}</a></td>
<td><p>delete an existing physical-link</p>
</td>
@@ -2806,6 +3289,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--patch">PATCH /network/pnfs/pnf/{pnf-name}</a></td>
+ <td><p>update an existing pnf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--delete">DELETE /network/pnfs/pnf/{pnf-name}</a></td>
<td><p>delete an existing pnf</p>
</td>
@@ -2826,6 +3314,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}</a></td>
+ <td><p>update an existing lag-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}</a></td>
<td><p>delete an existing lag-interface</p>
</td>
@@ -2846,6 +3339,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -2861,6 +3359,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -2886,6 +3389,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -2926,6 +3434,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -2956,6 +3469,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -2971,6 +3489,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -2996,6 +3519,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -3046,6 +3574,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}</a></td>
+ <td><p>update an existing p-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}</a></td>
<td><p>delete an existing p-interface</p>
</td>
@@ -3066,6 +3599,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -3081,6 +3619,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -3106,6 +3649,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -3146,6 +3694,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -3176,6 +3729,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -3191,6 +3749,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -3216,6 +3779,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -3276,6 +3844,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-route-table-references-route-table-reference--route-table-reference-id--patch">PATCH /network/route-table-references/route-table-reference/{route-table-reference-id}</a></td>
+ <td><p>update an existing route-table-reference</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-route-table-references-route-table-reference--route-table-reference-id--delete">DELETE /network/route-table-references/route-table-reference/{route-table-reference-id}</a></td>
<td><p>delete an existing route-table-reference</p>
</td>
@@ -3306,6 +3879,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--patch">PATCH /network/site-pair-sets/site-pair-set/{site-pair-set-id}</a></td>
+ <td><p>update an existing site-pair-set</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--delete">DELETE /network/site-pair-sets/site-pair-set/{site-pair-set-id}</a></td>
<td><p>delete an existing site-pair-set</p>
</td>
@@ -3336,6 +3914,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--patch">PATCH /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}</a></td>
+ <td><p>update an existing routing-instance</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--delete">DELETE /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}</a></td>
<td><p>delete an existing routing-instance</p>
</td>
@@ -3366,6 +3949,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--patch">PATCH /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}</a></td>
+ <td><p>update an existing site-pair</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--delete">DELETE /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}</a></td>
<td><p>delete an existing site-pair</p>
</td>
@@ -3386,6 +3974,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--classes-of-service-class-of-service--cos--patch">PATCH /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}/classes-of-service/class-of-service/{cos}</a></td>
+ <td><p>update an existing class-of-service</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--classes-of-service-class-of-service--cos--delete">DELETE /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}/classes-of-service/class-of-service/{cos}</a></td>
<td><p>delete an existing class-of-service</p>
</td>
@@ -3426,6 +4019,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vces-vce--vnf-id--patch">PATCH /network/vces/vce/{vnf-id}</a></td>
+ <td><p>update an existing vce</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vces-vce--vnf-id--delete">DELETE /network/vces/vce/{vnf-id}</a></td>
<td><p>delete an existing vce</p>
</td>
@@ -3446,6 +4044,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--patch">PATCH /network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}</a></td>
+ <td><p>update an existing port-group</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--delete">DELETE /network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}</a></td>
<td><p>delete an existing port-group</p>
</td>
@@ -3466,6 +4069,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--cvlan-tags-cvlan-tag-entry--cvlan-tag--patch">PATCH /network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}/cvlan-tags/cvlan-tag-entry/{cvlan-tag}</a></td>
+ <td><p>update an existing cvlan-tag-entry</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--cvlan-tags-cvlan-tag-entry--cvlan-tag--delete">DELETE /network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}/cvlan-tags/cvlan-tag-entry/{cvlan-tag}</a></td>
<td><p>delete an existing cvlan-tag-entry</p>
</td>
@@ -3516,6 +4124,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vnfcs-vnfc--vnfc-name--patch">PATCH /network/vnfcs/vnfc/{vnfc-name}</a></td>
+ <td><p>update an existing vnfc</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vnfcs-vnfc--vnfc-name--delete">DELETE /network/vnfcs/vnfc/{vnfc-name}</a></td>
<td><p>delete an existing vnfc</p>
</td>
@@ -3546,6 +4159,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}</a></td>
+ <td><p>update an existing vpls-pe</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}</a></td>
<td><p>delete an existing vpls-pe</p>
</td>
@@ -3566,6 +4184,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}</a></td>
+ <td><p>update an existing lag-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}</a></td>
<td><p>delete an existing lag-interface</p>
</td>
@@ -3586,6 +4209,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -3601,6 +4229,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -3626,6 +4259,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -3666,6 +4304,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -3696,6 +4339,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -3711,6 +4359,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -3736,6 +4389,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -3786,6 +4444,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}</a></td>
+ <td><p>update an existing p-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}</a></td>
<td><p>delete an existing p-interface</p>
</td>
@@ -3806,6 +4469,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -3821,6 +4489,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -3846,6 +4519,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -3886,6 +4564,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -3916,6 +4599,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -3931,6 +4619,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -3956,6 +4649,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -4016,6 +4714,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpn-bindings-vpn-binding--vpn-id--patch">PATCH /network/vpn-bindings/vpn-binding/{vpn-id}</a></td>
+ <td><p>update an existing vpn-binding</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpn-bindings-vpn-binding--vpn-id--delete">DELETE /network/vpn-bindings/vpn-binding/{vpn-id}</a></td>
<td><p>delete an existing vpn-binding</p>
</td>
@@ -4075,7 +4778,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/connectors">/connectors</a>
+ <a class="json-schema-ref" href="#/getDefinitions/connectors">/connectors</a>
</div>
</div>
</div>
@@ -4230,7 +4933,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/connector">/connector</a>
+ <a class="json-schema-ref" href="#/getDefinitions/connector">/connector</a>
</div>
</div>
</div>
@@ -4277,7 +4980,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>connector object that needs to be created or updated</p>
+ <p><p>connector object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/BusinessConnectorsConnector.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -4348,6 +5051,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-connectors-connector--resource-instance-id--"></span>
+ <div id="operation--business-connectors-connector--resource-instance-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing connector</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/connectors/connector/{resource-instance-id}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing connector</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>connector object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/connector">/connector</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ resource-instance-id
+ </td>
+ <td>
+ <p>Unique id of resource instance.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-connectors-connector--resource-instance-id--"></span>
<div id="operation--business-connectors-connector--resource-instance-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing connector</div>
@@ -4567,7 +5359,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadata">/metadata</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadata">/metadata</a>
</div>
</div>
</div>
@@ -4737,7 +5529,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadatum">/metadatum</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadatum">/metadatum</a>
</div>
</div>
</div>
@@ -4784,7 +5576,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>metadatum object that needs to be created or updated</p>
+ <p><p>metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/BusinessConnectorsConnectorMetadataMetadatum.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -4870,6 +5662,110 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-connectors-connector--resource-instance-id--metadata-metadatum--metaname--"></span>
+ <div id="operation--business-connectors-connector--resource-instance-id--metadata-metadatum--metaname--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing metadatum</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/connectors/connector/{resource-instance-id}/metadata/metadatum/{metaname}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing metadatum</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>metadatum object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/metadatum">/metadatum</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ resource-instance-id
+ </td>
+ <td>
+ <p>Unique id of resource instance.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ metaname
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-connectors-connector--resource-instance-id--metadata-metadatum--metaname--"></span>
<div id="operation--business-connectors-connector--resource-instance-id--metadata-metadatum--metaname--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing metadatum</div>
@@ -4996,7 +5892,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/BusinessConnectorsConnector.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -5179,7 +6075,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/customers">/customers</a>
+ <a class="json-schema-ref" href="#/getDefinitions/customers">/customers</a>
</div>
</div>
</div>
@@ -5304,7 +6200,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/customer">/customer</a>
+ <a class="json-schema-ref" href="#/getDefinitions/customer">/customer</a>
</div>
</div>
</div>
@@ -5351,7 +6247,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>customer object that needs to be created or updated</p>
+ <p><p>customer object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/BusinessCustomersCustomer.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -5422,6 +6318,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-customers-customer--global-customer-id--"></span>
+ <div id="operation--business-customers-customer--global-customer-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing customer</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/customers/customer/{global-customer-id}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing customer</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>customer object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/customer">/customer</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ global-customer-id
+ </td>
+ <td>
+ <p>Global customer id used across ECOMP to uniquely identify customer.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-customers-customer--global-customer-id--"></span>
<div id="operation--business-customers-customer--global-customer-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing customer</div>
@@ -5533,7 +6518,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/BusinessCustomersCustomer.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -5777,7 +6762,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/service-subscriptions">/service-subscriptions</a>
+ <a class="json-schema-ref" href="#/getDefinitions/service-subscriptions">/service-subscriptions</a>
</div>
</div>
</div>
@@ -5918,7 +6903,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/service-subscription">/service-subscription</a>
+ <a class="json-schema-ref" href="#/getDefinitions/service-subscription">/service-subscription</a>
</div>
</div>
</div>
@@ -5965,7 +6950,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>service-subscription object that needs to be created or updated</p>
+ <p><p>service-subscription object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/BusinessCustomersCustomerServiceSubscriptionsServiceSubscription.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -6052,6 +7037,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--"></span>
+ <div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing service-subscription</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing service-subscription</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>service-subscription object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/service-subscription">/service-subscription</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ global-customer-id
+ </td>
+ <td>
+ <p>Global customer id used across ECOMP to uniquely identify customer.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-type
+ </td>
+ <td>
+ <p>Value defined by orchestration to identify this service across ECOMP.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--"></span>
<div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing service-subscription</div>
@@ -6179,7 +7269,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/BusinessCustomersCustomerServiceSubscriptionsServiceSubscription.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -6471,7 +7561,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/service-instances">/service-instances</a>
+ <a class="json-schema-ref" href="#/getDefinitions/service-instances">/service-instances</a>
</div>
</div>
</div>
@@ -6718,7 +7808,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/service-instance">/service-instance</a>
+ <a class="json-schema-ref" href="#/getDefinitions/service-instance">/service-instance</a>
</div>
</div>
</div>
@@ -6765,7 +7855,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>service-instance object that needs to be created or updated</p>
+ <p><p>service-instance object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -6868,6 +7958,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--"></span>
+ <div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing service-instance</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing service-instance</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>service-instance object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/service-instance">/service-instance</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ global-customer-id
+ </td>
+ <td>
+ <p>Global customer id used across ECOMP to uniquely identify customer.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-type
+ </td>
+ <td>
+ <p>Value defined by orchestration to identify this service across ECOMP.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-instance-id
+ </td>
+ <td>
+ <p>Uniquely identifies this instance of a service</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--"></span>
<div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing service-instance</div>
@@ -7211,7 +8422,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadata">/metadata</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadata">/metadata</a>
</div>
</div>
</div>
@@ -7473,7 +8684,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadatum">/metadatum</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadatum">/metadatum</a>
</div>
</div>
</div>
@@ -7520,7 +8731,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>metadatum object that needs to be created or updated</p>
+ <p><p>metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceMetadataMetadatum.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -7638,6 +8849,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--metadata-metadatum--metaname--"></span>
+ <div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--metadata-metadatum--metaname--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing metadatum</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/metadata/metadatum/{metaname}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing metadatum</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>metadatum object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/metadatum">/metadatum</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ global-customer-id
+ </td>
+ <td>
+ <p>Global customer id used across ECOMP to uniquely identify customer.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-type
+ </td>
+ <td>
+ <p>Value defined by orchestration to identify this service across ECOMP.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-instance-id
+ </td>
+ <td>
+ <p>Uniquely identifies this instance of a service</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ metaname
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--metadata-metadatum--metaname--"></span>
<div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--metadata-metadatum--metaname--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing metadatum</div>
@@ -7796,7 +9143,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -8043,7 +9390,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/cloud-regions">/cloud-regions</a>
+ <a class="json-schema-ref" href="#/getDefinitions/cloud-regions">/cloud-regions</a>
</div>
</div>
</div>
@@ -8184,7 +9531,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/cloud-region">/cloud-region</a>
+ <a class="json-schema-ref" href="#/getDefinitions/cloud-region">/cloud-region</a>
</div>
</div>
</div>
@@ -8231,7 +9578,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>cloud-region object that needs to be created or updated</p>
+ <p><p>cloud-region object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegion.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -8318,6 +9665,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing cloud-region</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing cloud-region</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>cloud-region object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/cloud-region">/cloud-region</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing cloud-region</div>
@@ -8539,7 +9991,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/availability-zones">/availability-zones</a>
+ <a class="json-schema-ref" href="#/getDefinitions/availability-zones">/availability-zones</a>
</div>
</div>
</div>
@@ -8696,7 +10148,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/availability-zone">/availability-zone</a>
+ <a class="json-schema-ref" href="#/getDefinitions/availability-zone">/availability-zone</a>
</div>
</div>
</div>
@@ -8743,7 +10195,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>availability-zone object that needs to be created or updated</p>
+ <p><p>availability-zone object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -8846,6 +10298,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--availability-zones-availability-zone--availability-zone-name--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--availability-zones-availability-zone--availability-zone-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing availability-zone</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/availability-zones/availability-zone/{availability-zone-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing availability-zone</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>availability-zone object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/availability-zone">/availability-zone</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ availability-zone-name
+ </td>
+ <td>
+ <p>Name of the availability zone. Unique across a cloud region</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--availability-zones-availability-zone--availability-zone-name--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--availability-zones-availability-zone--availability-zone-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing availability-zone</div>
@@ -8989,7 +10562,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -9313,7 +10886,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/dvs-switches">/dvs-switches</a>
+ <a class="json-schema-ref" href="#/getDefinitions/dvs-switches">/dvs-switches</a>
</div>
</div>
</div>
@@ -9485,7 +11058,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/dvs-switch">/dvs-switch</a>
+ <a class="json-schema-ref" href="#/getDefinitions/dvs-switch">/dvs-switch</a>
</div>
</div>
</div>
@@ -9532,7 +11105,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>dvs-switch object that needs to be created or updated</p>
+ <p><p>dvs-switch object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -9635,6 +11208,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--dvs-switches-dvs-switch--switch-name--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--dvs-switches-dvs-switch--switch-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing dvs-switch</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/dvs-switches/dvs-switch/{switch-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing dvs-switch</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>dvs-switch object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/dvs-switch">/dvs-switch</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ switch-name
+ </td>
+ <td>
+ <p>DVS switch name</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--dvs-switches-dvs-switch--switch-name--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--dvs-switches-dvs-switch--switch-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing dvs-switch</div>
@@ -9778,7 +11472,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -10102,7 +11796,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/flavors">/flavors</a>
+ <a class="json-schema-ref" href="#/getDefinitions/flavors">/flavors</a>
</div>
</div>
</div>
@@ -10274,7 +11968,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/flavor">/flavor</a>
+ <a class="json-schema-ref" href="#/getDefinitions/flavor">/flavor</a>
</div>
</div>
</div>
@@ -10321,7 +12015,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>flavor object that needs to be created or updated</p>
+ <p><p>flavor object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -10424,6 +12118,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--flavors-flavor--flavor-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--flavors-flavor--flavor-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing flavor</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/flavors/flavor/{flavor-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing flavor</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>flavor object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/flavor">/flavor</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ flavor-id
+ </td>
+ <td>
+ <p>Flavor id, expected to be unique across cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--flavors-flavor--flavor-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--flavors-flavor--flavor-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing flavor</div>
@@ -10567,7 +12382,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -10891,7 +12706,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/group-assignments">/group-assignments</a>
+ <a class="json-schema-ref" href="#/getDefinitions/group-assignments">/group-assignments</a>
</div>
</div>
</div>
@@ -11078,7 +12893,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/group-assignment">/group-assignment</a>
+ <a class="json-schema-ref" href="#/getDefinitions/group-assignment">/group-assignment</a>
</div>
</div>
</div>
@@ -11125,7 +12940,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>group-assignment object that needs to be created or updated</p>
+ <p><p>group-assignment object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -11228,6 +13043,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--group-assignments-group-assignment--group-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--group-assignments-group-assignment--group-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing group-assignment</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/group-assignments/group-assignment/{group-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing group-assignment</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>group-assignment object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/group-assignment">/group-assignment</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ group-id
+ </td>
+ <td>
+ <p>Group id, expected to be unique across cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--group-assignments-group-assignment--group-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--group-assignments-group-assignment--group-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing group-assignment</div>
@@ -11371,7 +13307,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -11695,7 +13631,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/images">/images</a>
+ <a class="json-schema-ref" href="#/getDefinitions/images">/images</a>
</div>
</div>
</div>
@@ -11912,7 +13848,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/image">/image</a>
+ <a class="json-schema-ref" href="#/getDefinitions/image">/image</a>
</div>
</div>
</div>
@@ -11959,7 +13895,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>image object that needs to be created or updated</p>
+ <p><p>image object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionImagesImage.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -12062,6 +13998,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing image</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing image</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>image object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/image">/image</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ image-id
+ </td>
+ <td>
+ <p>Image id, expected to be unique across cloud region</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing image</div>
@@ -12375,7 +14432,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadata">/metadata</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadata">/metadata</a>
</div>
</div>
</div>
@@ -12607,7 +14664,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadatum">/metadatum</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadatum">/metadatum</a>
</div>
</div>
</div>
@@ -12654,7 +14711,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>metadatum object that needs to be created or updated</p>
+ <p><p>metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionImagesImageMetadataMetadatum.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -12772,6 +14829,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--metadata-metadatum--metaname--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--metadata-metadatum--metaname--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing metadatum</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}/metadata/metadatum/{metaname}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing metadatum</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>metadatum object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/metadatum">/metadatum</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ image-id
+ </td>
+ <td>
+ <p>Image id, expected to be unique across cloud region</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ metaname
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--metadata-metadatum--metaname--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--metadata-metadatum--metaname--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing metadatum</div>
@@ -12930,7 +15123,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionImagesImage.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -13254,7 +15447,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/oam-networks">/oam-networks</a>
+ <a class="json-schema-ref" href="#/getDefinitions/oam-networks">/oam-networks</a>
</div>
</div>
</div>
@@ -13441,7 +15634,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/oam-network">/oam-network</a>
+ <a class="json-schema-ref" href="#/getDefinitions/oam-network">/oam-network</a>
</div>
</div>
</div>
@@ -13488,7 +15681,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>oam-network object that needs to be created or updated</p>
+ <p><p>oam-network object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -13591,6 +15784,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--oam-networks-oam-network--network-uuid--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--oam-networks-oam-network--network-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing oam-network</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/oam-networks/oam-network/{network-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing oam-network</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>oam-network object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/oam-network">/oam-network</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ network-uuid
+ </td>
+ <td>
+ <p>UUID of the network. Unique across a cloud-region</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--oam-networks-oam-network--network-uuid--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--oam-networks-oam-network--network-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing oam-network</div>
@@ -13734,7 +16048,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -13964,7 +16278,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegion.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -14256,7 +16570,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/snapshots">/snapshots</a>
+ <a class="json-schema-ref" href="#/getDefinitions/snapshots">/snapshots</a>
</div>
</div>
</div>
@@ -14488,7 +16802,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/snapshot">/snapshot</a>
+ <a class="json-schema-ref" href="#/getDefinitions/snapshot">/snapshot</a>
</div>
</div>
</div>
@@ -14535,7 +16849,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>snapshot object that needs to be created or updated</p>
+ <p><p>snapshot object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -14638,6 +16952,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--snapshots-snapshot--snapshot-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--snapshots-snapshot--snapshot-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing snapshot</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/snapshots/snapshot/{snapshot-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing snapshot</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>snapshot object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/snapshot">/snapshot</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ snapshot-id
+ </td>
+ <td>
+ <p>Snapshot id, this is the key UUID assoc associated in glance with the snapshots.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--snapshots-snapshot--snapshot-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--snapshots-snapshot--snapshot-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing snapshot</div>
@@ -14781,7 +17216,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -15105,7 +17540,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/tenants">/tenants</a>
+ <a class="json-schema-ref" href="#/getDefinitions/tenants">/tenants</a>
</div>
</div>
</div>
@@ -15277,7 +17712,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/tenant">/tenant</a>
+ <a class="json-schema-ref" href="#/getDefinitions/tenant">/tenant</a>
</div>
</div>
</div>
@@ -15324,7 +17759,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>tenant object that needs to be created or updated</p>
+ <p><p>tenant object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenant.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -15427,6 +17862,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing tenant</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing tenant</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>tenant object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/tenant">/tenant</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing tenant</div>
@@ -15570,7 +18126,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenant.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -15925,7 +18481,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vservers">/vservers</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vservers">/vservers</a>
</div>
</div>
</div>
@@ -16186,7 +18742,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vserver">/vserver</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vserver">/vserver</a>
</div>
</div>
</div>
@@ -16233,7 +18789,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vserver object that needs to be created or updated</p>
+ <p><p>vserver object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -16352,6 +18908,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vserver</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vserver</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vserver object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vserver">/vserver</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vserver</div>
@@ -16725,7 +19418,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -17047,7 +19740,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -17094,7 +19787,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -17229,6 +19922,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -17740,7 +20586,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -17787,7 +20633,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -17938,6 +20784,175 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -18129,7 +21144,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -18791,7 +21806,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -18838,7 +21853,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -18989,6 +22004,175 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -19180,7 +22364,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -19506,7 +22690,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -20075,7 +23259,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -20473,7 +23657,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -20520,7 +23704,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -20671,6 +23855,175 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -20862,7 +24215,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -21463,7 +24816,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -21831,7 +25184,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -21878,7 +25231,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -22029,6 +25382,175 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -22602,7 +26124,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -22649,7 +26171,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -22816,6 +26338,191 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -23023,7 +26730,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -23763,7 +27470,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -23810,7 +27517,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -23977,6 +27684,191 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -24184,7 +28076,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -24542,7 +28434,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -24868,7 +28760,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -25344,7 +29236,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/volumes">/volumes</a>
+ <a class="json-schema-ref" href="#/getDefinitions/volumes">/volumes</a>
</div>
</div>
</div>
@@ -25621,7 +29513,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/volume">/volume</a>
+ <a class="json-schema-ref" href="#/getDefinitions/volume">/volume</a>
</div>
</div>
</div>
@@ -25668,7 +29560,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>volume object that needs to be created or updated</p>
+ <p><p>volume object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -25803,6 +29695,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--volumes-volume--volume-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--volumes-volume--volume-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing volume</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/volumes/volume/{volume-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing volume</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>volume object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/volume">/volume</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ volume-id
+ </td>
+ <td>
+ <p>Unique ID of block storage volume relative to the vserver.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--volumes-volume--volume-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--volumes-volume--volume-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing volume</div>
@@ -25978,7 +30023,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -26366,7 +30411,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/volume-groups">/volume-groups</a>
+ <a class="json-schema-ref" href="#/getDefinitions/volume-groups">/volume-groups</a>
</div>
</div>
</div>
@@ -26568,7 +30613,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/volume-group">/volume-group</a>
+ <a class="json-schema-ref" href="#/getDefinitions/volume-group">/volume-group</a>
</div>
</div>
</div>
@@ -26615,7 +30660,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>volume-group object that needs to be created or updated</p>
+ <p><p>volume-group object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -26718,6 +30763,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--volume-groups-volume-group--volume-group-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--volume-groups-volume-group--volume-group-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing volume-group</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/volume-groups/volume-group/{volume-group-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing volume-group</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>volume-group object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/volume-group">/volume-group</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ volume-group-id
+ </td>
+ <td>
+ <p>Unique ID of volume-group.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--volume-groups-volume-group--volume-group-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--volume-groups-volume-group--volume-group-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing volume-group</div>
@@ -26861,7 +31027,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -27108,7 +31274,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/complexes">/complexes</a>
+ <a class="json-schema-ref" href="#/getDefinitions/complexes">/complexes</a>
</div>
</div>
</div>
@@ -27248,7 +31414,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/complex">/complex</a>
+ <a class="json-schema-ref" href="#/getDefinitions/complex">/complex</a>
</div>
</div>
</div>
@@ -27295,7 +31461,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>complex object that needs to be created or updated</p>
+ <p><p>complex object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureComplexesComplex.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -27366,6 +31532,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-complexes-complex--physical-location-id--"></span>
+ <div id="operation--cloud-infrastructure-complexes-complex--physical-location-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing complex</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/complexes/complex/{physical-location-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing complex</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>complex object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/complex">/complex</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ physical-location-id
+ </td>
+ <td>
+ <p>Unique identifier for physical location, e.g., CLLI</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-complexes-complex--physical-location-id--"></span>
<div id="operation--cloud-infrastructure-complexes-complex--physical-location-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing complex</div>
@@ -27570,7 +31825,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/ctag-pools">/ctag-pools</a>
+ <a class="json-schema-ref" href="#/getDefinitions/ctag-pools">/ctag-pools</a>
</div>
</div>
</div>
@@ -27742,7 +31997,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/ctag-pool">/ctag-pool</a>
+ <a class="json-schema-ref" href="#/getDefinitions/ctag-pool">/ctag-pool</a>
</div>
</div>
</div>
@@ -27789,7 +32044,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>ctag-pool object that needs to be created or updated</p>
+ <p><p>ctag-pool object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureComplexesComplexCtagPoolsCtagPool.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -27892,6 +32147,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-complexes-complex--physical-location-id--ctag-pools-ctag-pool--target-pe---availability-zone-name--"></span>
+ <div id="operation--cloud-infrastructure-complexes-complex--physical-location-id--ctag-pools-ctag-pool--target-pe---availability-zone-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing ctag-pool</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/complexes/complex/{physical-location-id}/ctag-pools/ctag-pool/{target-pe}/{availability-zone-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing ctag-pool</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>ctag-pool object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/ctag-pool">/ctag-pool</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ physical-location-id
+ </td>
+ <td>
+ <p>Unique identifier for physical location, e.g., CLLI</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ target-pe
+ </td>
+ <td>
+ <p>The Target provider edge router</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ availability-zone-name
+ </td>
+ <td>
+ <p>Name of the availability zone</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-complexes-complex--physical-location-id--ctag-pools-ctag-pool--target-pe---availability-zone-name--"></span>
<div id="operation--cloud-infrastructure-complexes-complex--physical-location-id--ctag-pools-ctag-pool--target-pe---availability-zone-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing ctag-pool</div>
@@ -28035,7 +32411,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureComplexesComplexCtagPoolsCtagPool.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -28265,7 +32641,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureComplexesComplex.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -28448,7 +32824,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/network-profiles">/network-profiles</a>
+ <a class="json-schema-ref" href="#/getDefinitions/network-profiles">/network-profiles</a>
</div>
</div>
</div>
@@ -28543,7 +32919,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/network-profile">/network-profile</a>
+ <a class="json-schema-ref" href="#/getDefinitions/network-profile">/network-profile</a>
</div>
</div>
</div>
@@ -28590,7 +32966,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>network-profile object that needs to be created or updated</p>
+ <p><p>network-profile object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureNetworkProfilesNetworkProfile.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -28661,6 +33037,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-network-profiles-network-profile--nm-profile-name--"></span>
+ <div id="operation--cloud-infrastructure-network-profiles-network-profile--nm-profile-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing network-profile</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/network-profiles/network-profile/{nm-profile-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing network-profile</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>network-profile object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/network-profile">/network-profile</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ nm-profile-name
+ </td>
+ <td>
+ <p>Unique name of network profile.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-network-profiles-network-profile--nm-profile-name--"></span>
<div id="operation--cloud-infrastructure-network-profiles-network-profile--nm-profile-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing network-profile</div>
@@ -28772,7 +33237,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureNetworkProfilesNetworkProfile.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -28955,7 +33420,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/pservers">/pservers</a>
+ <a class="json-schema-ref" href="#/getDefinitions/pservers">/pservers</a>
</div>
</div>
</div>
@@ -29094,7 +33559,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/pserver">/pserver</a>
+ <a class="json-schema-ref" href="#/getDefinitions/pserver">/pserver</a>
</div>
</div>
</div>
@@ -29141,7 +33606,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>pserver object that needs to be created or updated</p>
+ <p><p>pserver object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserver.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -29212,6 +33677,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing pserver</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing pserver</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>pserver object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/pserver">/pserver</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing pserver</div>
@@ -29415,7 +33969,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interfaces">/lag-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interfaces">/lag-interfaces</a>
</div>
</div>
</div>
@@ -29570,7 +34124,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interface">/lag-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interface">/lag-interface</a>
</div>
</div>
</div>
@@ -29617,7 +34171,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>lag-interface object that needs to be created or updated</p>
+ <p><p>lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -29704,6 +34258,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing lag-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing lag-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>lag-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/lag-interface">/lag-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing lag-interface</div>
@@ -29939,7 +34598,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -30155,7 +34814,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -30202,7 +34861,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -30305,6 +34964,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -30678,7 +35458,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -30725,7 +35505,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -30844,6 +35624,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -31003,7 +35920,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -31495,7 +36412,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -31542,7 +36459,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -31661,6 +36578,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -31820,7 +36874,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -32082,7 +37136,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -32481,7 +37535,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -32773,7 +37827,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -32820,7 +37874,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -32939,6 +37993,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -33098,7 +38289,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -33529,7 +38720,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -33791,7 +38982,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -33838,7 +39029,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -33957,6 +39148,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -34392,7 +39720,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -34439,7 +39767,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -34574,6 +39902,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -34749,7 +40230,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -35319,7 +40800,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -35366,7 +40847,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -35501,6 +40982,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -35676,7 +41310,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -35970,7 +41604,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -36232,7 +41866,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -36522,7 +42156,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/p-interfaces">/p-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/p-interfaces">/p-interfaces</a>
</div>
</div>
</div>
@@ -36677,7 +42311,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/p-interface">/p-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/p-interface">/p-interface</a>
</div>
</div>
</div>
@@ -36724,7 +42358,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>p-interface object that needs to be created or updated</p>
+ <p><p>p-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -36811,6 +42445,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing p-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing p-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>p-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/p-interface">/p-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing p-interface</div>
@@ -37046,7 +42785,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -37262,7 +43001,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -37309,7 +43048,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -37412,6 +43151,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -37785,7 +43645,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -37832,7 +43692,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -37951,6 +43811,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -38110,7 +44107,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -38602,7 +44599,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -38649,7 +44646,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -38768,6 +44765,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -38927,7 +45061,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -39189,7 +45323,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -39588,7 +45722,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -39880,7 +46014,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -39927,7 +46061,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -40046,6 +46180,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -40205,7 +46476,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -40636,7 +46907,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -40898,7 +47169,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -40945,7 +47216,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -41064,6 +47335,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -41499,7 +47907,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -41546,7 +47954,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -41681,6 +48089,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -41856,7 +48417,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -42426,7 +48987,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -42473,7 +49034,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -42608,6 +49169,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -42783,7 +49497,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -43077,7 +49791,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -43339,7 +50053,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -43537,7 +50251,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserver.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -43720,7 +50434,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/virtual-data-centers">/virtual-data-centers</a>
+ <a class="json-schema-ref" href="#/getDefinitions/virtual-data-centers">/virtual-data-centers</a>
</div>
</div>
</div>
@@ -43830,7 +50544,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/virtual-data-center">/virtual-data-center</a>
+ <a class="json-schema-ref" href="#/getDefinitions/virtual-data-center">/virtual-data-center</a>
</div>
</div>
</div>
@@ -43877,7 +50591,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>virtual-data-center object that needs to be created or updated</p>
+ <p><p>virtual-data-center object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureVirtualDataCentersVirtualDataCenter.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -43948,6 +50662,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--"></span>
+ <div id="operation--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing virtual-data-center</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing virtual-data-center</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>virtual-data-center object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/virtual-data-center">/virtual-data-center</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vdc-id
+ </td>
+ <td>
+ <p>Unique ID of the vdc</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--"></span>
<div id="operation--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing virtual-data-center</div>
@@ -44059,7 +50862,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureVirtualDataCentersVirtualDataCenter.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -44242,7 +51045,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/generic-vnfs">/generic-vnfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/generic-vnfs">/generic-vnfs</a>
</div>
</div>
</div>
@@ -44530,7 +51333,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/generic-vnf">/generic-vnf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/generic-vnf">/generic-vnf</a>
</div>
</div>
</div>
@@ -44577,7 +51380,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>generic-vnf object that needs to be created or updated</p>
+ <p><p>generic-vnf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -44648,6 +51451,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing generic-vnf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing generic-vnf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>generic-vnf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/generic-vnf">/generic-vnf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing generic-vnf</div>
@@ -45000,7 +51892,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -45349,7 +52241,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -45396,7 +52288,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -45483,6 +52375,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -45973,7 +52970,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -46020,7 +53017,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -46123,6 +53120,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -46266,7 +53384,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -46859,7 +53977,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -46906,7 +54024,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -47009,6 +54127,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -47152,7 +54391,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -47382,7 +54621,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -47882,7 +55121,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -48307,7 +55546,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -48354,7 +55593,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -48457,6 +55696,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -48600,7 +55960,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -49132,7 +56492,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -49527,7 +56887,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -49574,7 +56934,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -49677,6 +57037,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -50229,7 +57710,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -50276,7 +57757,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -50395,6 +57876,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -50554,7 +58172,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -51225,7 +58843,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -51272,7 +58890,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -51391,6 +59009,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -51550,7 +59305,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -51812,7 +59567,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -52283,7 +60038,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interfaces">/lag-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interfaces">/lag-interfaces</a>
</div>
</div>
</div>
@@ -52587,7 +60342,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interface">/lag-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interface">/lag-interface</a>
</div>
</div>
</div>
@@ -52634,7 +60389,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>lag-interface object that needs to be created or updated</p>
+ <p><p>lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -52721,6 +60476,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing lag-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing lag-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>lag-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/lag-interface">/lag-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing lag-interface</div>
@@ -53105,7 +60965,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -53470,7 +61330,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -53517,7 +61377,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -53620,6 +61480,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -54142,7 +62123,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -54189,7 +62170,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -54308,6 +62289,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -54467,7 +62585,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -55108,7 +63226,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -55155,7 +63273,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -55274,6 +63392,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -55433,7 +63688,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -55695,7 +63950,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -56243,7 +64498,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -56684,7 +64939,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -56731,7 +64986,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -56850,6 +65105,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -57009,7 +65401,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -57589,7 +65981,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -58000,7 +66392,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -58047,7 +66439,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -58166,6 +66558,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -58750,7 +67279,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -58797,7 +67326,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -58932,6 +67461,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -59107,7 +67789,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -59826,7 +68508,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -59873,7 +68555,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -60008,6 +68690,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -60183,7 +69018,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -60477,7 +69312,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -60739,7 +69574,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -60937,7 +69772,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -61344,7 +70179,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vf-modules">/vf-modules</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vf-modules">/vf-modules</a>
</div>
</div>
</div>
@@ -61753,7 +70588,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vf-module">/vf-module</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vf-module">/vf-module</a>
</div>
</div>
</div>
@@ -61800,7 +70635,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vf-module object that needs to be created or updated</p>
+ <p><p>vf-module object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfVfModulesVfModule.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -61887,6 +70722,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--vf-modules-vf-module--vf-module-id--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--vf-modules-vf-module--vf-module-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vf-module</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/vf-modules/vf-module/{vf-module-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vf-module</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vf-module object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vf-module">/vf-module</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vf-module-id
+ </td>
+ <td>
+ <p>Unique ID of vf-module.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--vf-modules-vf-module--vf-module-id--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--vf-modules-vf-module--vf-module-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vf-module</div>
@@ -62014,7 +70954,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfVfModulesVfModule.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -62229,7 +71169,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/ipsec-configurations">/ipsec-configurations</a>
+ <a class="json-schema-ref" href="#/getDefinitions/ipsec-configurations">/ipsec-configurations</a>
</div>
</div>
</div>
@@ -62324,7 +71264,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/ipsec-configuration">/ipsec-configuration</a>
+ <a class="json-schema-ref" href="#/getDefinitions/ipsec-configuration">/ipsec-configuration</a>
</div>
</div>
</div>
@@ -62371,7 +71311,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>ipsec-configuration object that needs to be created or updated</p>
+ <p><p>ipsec-configuration object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkIpsecConfigurationsIpsecConfiguration.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -62442,6 +71382,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--"></span>
+ <div id="operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing ipsec-configuration</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing ipsec-configuration</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>ipsec-configuration object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/ipsec-configuration">/ipsec-configuration</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ ipsec-configuration-id
+ </td>
+ <td>
+ <p>UUID of this configuration</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--"></span>
<div id="operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing ipsec-configuration</div>
@@ -62553,7 +71582,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkIpsecConfigurationsIpsecConfiguration.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -62767,7 +71796,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vig-servers">/vig-servers</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vig-servers">/vig-servers</a>
</div>
</div>
</div>
@@ -62878,7 +71907,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vig-server">/vig-server</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vig-server">/vig-server</a>
</div>
</div>
</div>
@@ -62925,7 +71954,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vig-server object that needs to be created or updated</p>
+ <p><p>vig-server object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -63012,6 +72041,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--vig-servers-vig-server--vig-address-type--"></span>
+ <div id="operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--vig-servers-vig-server--vig-address-type--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vig-server</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}/vig-servers/vig-server/{vig-address-type}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vig-server</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vig-server object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vig-server">/vig-server</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ ipsec-configuration-id
+ </td>
+ <td>
+ <p>UUID of this configuration</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vig-address-type
+ </td>
+ <td>
+ <p>indicates whether the VIG is for AVPN or INTERNET</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--vig-servers-vig-server--vig-address-type--"></span>
<div id="operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--vig-servers-vig-server--vig-address-type--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vig-server</div>
@@ -63139,7 +72273,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -63354,7 +72488,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-networks">/l3-networks</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-networks">/l3-networks</a>
</div>
</div>
</div>
@@ -63569,7 +72703,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-network">/l3-network</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-network">/l3-network</a>
</div>
</div>
</div>
@@ -63616,7 +72750,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-network object that needs to be created or updated</p>
+ <p><p>l3-network object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkL3NetworksL3Network.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -63687,6 +72821,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-l3-networks-l3-network--network-id--"></span>
+ <div id="operation--network-l3-networks-l3-network--network-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-network</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/l3-networks/l3-network/{network-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-network</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-network object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-network">/l3-network</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ network-id
+ </td>
+ <td>
+ <p>Network ID, should be uuid. Unique across A&AI.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-l3-networks-l3-network--network-id--"></span>
<div id="operation--network-l3-networks-l3-network--network-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-network</div>
@@ -63966,7 +73189,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/ctag-assignments">/ctag-assignments</a>
+ <a class="json-schema-ref" href="#/getDefinitions/ctag-assignments">/ctag-assignments</a>
</div>
</div>
</div>
@@ -64197,7 +73420,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/ctag-assignment">/ctag-assignment</a>
+ <a class="json-schema-ref" href="#/getDefinitions/ctag-assignment">/ctag-assignment</a>
</div>
</div>
</div>
@@ -64244,7 +73467,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>ctag-assignment object that needs to be created or updated</p>
+ <p><p>ctag-assignment object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -64331,6 +73554,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-l3-networks-l3-network--network-id--ctag-assignments-ctag-assignment--vlan-id-inner--"></span>
+ <div id="operation--network-l3-networks-l3-network--network-id--ctag-assignments-ctag-assignment--vlan-id-inner--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing ctag-assignment</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/l3-networks/l3-network/{network-id}/ctag-assignments/ctag-assignment/{vlan-id-inner}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing ctag-assignment</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>ctag-assignment object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/ctag-assignment">/ctag-assignment</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ network-id
+ </td>
+ <td>
+ <p>Network ID, should be uuid. Unique across A&AI.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-id-inner
+ </td>
+ <td>
+ <p>id.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-l3-networks-l3-network--network-id--ctag-assignments-ctag-assignment--vlan-id-inner--"></span>
<div id="operation--network-l3-networks-l3-network--network-id--ctag-assignments-ctag-assignment--vlan-id-inner--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing ctag-assignment</div>
@@ -64458,7 +73786,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -64656,7 +73984,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkL3NetworksL3Network.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -64990,7 +74318,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/segmentation-assignments">/segmentation-assignments</a>
+ <a class="json-schema-ref" href="#/getDefinitions/segmentation-assignments">/segmentation-assignments</a>
</div>
</div>
</div>
@@ -65221,7 +74549,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/segmentation-assignment">/segmentation-assignment</a>
+ <a class="json-schema-ref" href="#/getDefinitions/segmentation-assignment">/segmentation-assignment</a>
</div>
</div>
</div>
@@ -65268,7 +74596,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>segmentation-assignment object that needs to be created or updated</p>
+ <p><p>segmentation-assignment object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -65355,6 +74683,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-l3-networks-l3-network--network-id--segmentation-assignments-segmentation-assignment--segmentation-id--"></span>
+ <div id="operation--network-l3-networks-l3-network--network-id--segmentation-assignments-segmentation-assignment--segmentation-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing segmentation-assignment</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/l3-networks/l3-network/{network-id}/segmentation-assignments/segmentation-assignment/{segmentation-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing segmentation-assignment</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>segmentation-assignment object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/segmentation-assignment">/segmentation-assignment</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ network-id
+ </td>
+ <td>
+ <p>Network ID, should be uuid. Unique across A&AI.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ segmentation-id
+ </td>
+ <td>
+ <p>Route Table Reference id, UUID assigned to this instance.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-l3-networks-l3-network--network-id--segmentation-assignments-segmentation-assignment--segmentation-id--"></span>
<div id="operation--network-l3-networks-l3-network--network-id--segmentation-assignments-segmentation-assignment--segmentation-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing segmentation-assignment</div>
@@ -65482,7 +74915,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -65848,7 +75281,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/subnets">/subnets</a>
+ <a class="json-schema-ref" href="#/getDefinitions/subnets">/subnets</a>
</div>
</div>
</div>
@@ -66094,7 +75527,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/subnet">/subnet</a>
+ <a class="json-schema-ref" href="#/getDefinitions/subnet">/subnet</a>
</div>
</div>
</div>
@@ -66141,7 +75574,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>subnet object that needs to be created or updated</p>
+ <p><p>subnet object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkL3NetworksL3NetworkSubnetsSubnet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -66228,6 +75661,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-l3-networks-l3-network--network-id--subnets-subnet--subnet-id--"></span>
+ <div id="operation--network-l3-networks-l3-network--network-id--subnets-subnet--subnet-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing subnet</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/l3-networks/l3-network/{network-id}/subnets/subnet/{subnet-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing subnet</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>subnet object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/subnet">/subnet</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ network-id
+ </td>
+ <td>
+ <p>Network ID, should be uuid. Unique across A&AI.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ subnet-id
+ </td>
+ <td>
+ <p>Subnet ID, should be UUID.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-l3-networks-l3-network--network-id--subnets-subnet--subnet-id--"></span>
<div id="operation--network-l3-networks-l3-network--network-id--subnets-subnet--subnet-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing subnet</div>
@@ -66355,7 +75893,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkL3NetworksL3NetworkSubnetsSubnet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -66570,7 +76108,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-links">/lag-links</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-links">/lag-links</a>
</div>
</div>
</div>
@@ -66665,7 +76203,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-link">/lag-link</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-link">/lag-link</a>
</div>
</div>
</div>
@@ -66712,7 +76250,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>lag-link object that needs to be created or updated</p>
+ <p><p>lag-link object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkLagLinksLagLink.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -66783,6 +76321,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-lag-links-lag-link--link-name--"></span>
+ <div id="operation--network-lag-links-lag-link--link-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing lag-link</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/lag-links/lag-link/{link-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing lag-link</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>lag-link object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/lag-link">/lag-link</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ link-name
+ </td>
+ <td>
+ <p>Alphabetical concatenation of lag-interface names</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-lag-links-lag-link--link-name--"></span>
<div id="operation--network-lag-links-lag-link--link-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing lag-link</div>
@@ -66894,7 +76521,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkLagLinksLagLink.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -67077,7 +76704,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/logical-links">/logical-links</a>
+ <a class="json-schema-ref" href="#/getDefinitions/logical-links">/logical-links</a>
</div>
</div>
</div>
@@ -67247,7 +76874,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/logical-link">/logical-link</a>
+ <a class="json-schema-ref" href="#/getDefinitions/logical-link">/logical-link</a>
</div>
</div>
</div>
@@ -67294,7 +76921,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>logical-link object that needs to be created or updated</p>
+ <p><p>logical-link object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkLogicalLinksLogicalLink.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -67365,6 +76992,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-logical-links-logical-link--link-name--"></span>
+ <div id="operation--network-logical-links-logical-link--link-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing logical-link</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/logical-links/logical-link/{link-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing logical-link</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>logical-link object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/logical-link">/logical-link</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ link-name
+ </td>
+ <td>
+ <p>e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-logical-links-logical-link--link-name--"></span>
<div id="operation--network-logical-links-logical-link--link-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing logical-link</div>
@@ -67476,7 +77192,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkLogicalLinksLogicalLink.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -67659,7 +77375,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/multicast-configurations">/multicast-configurations</a>
+ <a class="json-schema-ref" href="#/getDefinitions/multicast-configurations">/multicast-configurations</a>
</div>
</div>
</div>
@@ -67754,7 +77470,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/multicast-configuration">/multicast-configuration</a>
+ <a class="json-schema-ref" href="#/getDefinitions/multicast-configuration">/multicast-configuration</a>
</div>
</div>
</div>
@@ -67801,7 +77517,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>multicast-configuration object that needs to be created or updated</p>
+ <p><p>multicast-configuration object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkMulticastConfigurationsMulticastConfiguration.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -67872,6 +77588,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-multicast-configurations-multicast-configuration--multicast-configuration-id--"></span>
+ <div id="operation--network-multicast-configurations-multicast-configuration--multicast-configuration-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing multicast-configuration</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/multicast-configurations/multicast-configuration/{multicast-configuration-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing multicast-configuration</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>multicast-configuration object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/multicast-configuration">/multicast-configuration</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ multicast-configuration-id
+ </td>
+ <td>
+ <p>Unique id of multicast configuration.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-multicast-configurations-multicast-configuration--multicast-configuration-id--"></span>
<div id="operation--network-multicast-configurations-multicast-configuration--multicast-configuration-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing multicast-configuration</div>
@@ -67983,7 +77788,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkMulticastConfigurationsMulticastConfiguration.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -68166,7 +77971,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/network-policies">/network-policies</a>
+ <a class="json-schema-ref" href="#/getDefinitions/network-policies">/network-policies</a>
</div>
</div>
</div>
@@ -68276,7 +78081,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/network-policy">/network-policy</a>
+ <a class="json-schema-ref" href="#/getDefinitions/network-policy">/network-policy</a>
</div>
</div>
</div>
@@ -68323,7 +78128,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>network-policy object that needs to be created or updated</p>
+ <p><p>network-policy object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNetworkPoliciesNetworkPolicy.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -68394,6 +78199,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-network-policies-network-policy--network-policy-id--"></span>
+ <div id="operation--network-network-policies-network-policy--network-policy-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing network-policy</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/network-policies/network-policy/{network-policy-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing network-policy</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>network-policy object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/network-policy">/network-policy</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ network-policy-id
+ </td>
+ <td>
+ <p>UUID representing unique key to this instance</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-network-policies-network-policy--network-policy-id--"></span>
<div id="operation--network-network-policies-network-policy--network-policy-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing network-policy</div>
@@ -68505,7 +78399,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNetworkPoliciesNetworkPolicy.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -68688,7 +78582,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/newvces">/newvces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/newvces">/newvces</a>
</div>
</div>
</div>
@@ -68858,7 +78752,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/newvce">/newvce</a>
+ <a class="json-schema-ref" href="#/getDefinitions/newvce">/newvce</a>
</div>
</div>
</div>
@@ -68905,7 +78799,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>newvce object that needs to be created or updated</p>
+ <p><p>newvce object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvce.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -68976,6 +78870,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing newvce</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing newvce</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>newvce object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/newvce">/newvce</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing newvce</div>
@@ -69210,7 +79193,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -69441,7 +79424,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -69488,7 +79471,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -69575,6 +79558,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -69947,7 +80035,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -69994,7 +80082,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -70097,6 +80185,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -70240,7 +80449,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -70715,7 +80924,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -70762,7 +80971,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -70865,6 +81074,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -71008,7 +81338,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -71238,7 +81568,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -71620,7 +81950,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -71927,7 +82257,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -71974,7 +82304,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -72077,6 +82407,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -72220,7 +82671,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -72634,7 +83085,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -72911,7 +83362,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -72958,7 +83409,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -73061,6 +83512,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -73495,7 +84067,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -73542,7 +84114,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -73661,6 +84233,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -73820,7 +84529,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -74373,7 +85082,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -74420,7 +85129,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -74539,6 +85248,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -74698,7 +85544,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -74960,7 +85806,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -75190,7 +86036,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvce.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -75373,7 +86219,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/physical-links">/physical-links</a>
+ <a class="json-schema-ref" href="#/getDefinitions/physical-links">/physical-links</a>
</div>
</div>
</div>
@@ -75483,7 +86329,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/physical-link">/physical-link</a>
+ <a class="json-schema-ref" href="#/getDefinitions/physical-link">/physical-link</a>
</div>
</div>
</div>
@@ -75530,7 +86376,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>physical-link object that needs to be created or updated</p>
+ <p><p>physical-link object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPhysicalLinksPhysicalLink.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -75601,6 +86447,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-physical-links-physical-link--link-name--"></span>
+ <div id="operation--network-physical-links-physical-link--link-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing physical-link</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/physical-links/physical-link/{link-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing physical-link</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>physical-link object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/physical-link">/physical-link</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ link-name
+ </td>
+ <td>
+ <p>e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-physical-links-physical-link--link-name--"></span>
<div id="operation--network-physical-links-physical-link--link-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing physical-link</div>
@@ -75712,7 +86647,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPhysicalLinksPhysicalLink.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -75895,7 +86830,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/pnfs">/pnfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/pnfs">/pnfs</a>
</div>
</div>
</div>
@@ -76005,7 +86940,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/pnf">/pnf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/pnf">/pnf</a>
</div>
</div>
</div>
@@ -76052,7 +86987,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>pnf object that needs to be created or updated</p>
+ <p><p>pnf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -76123,6 +87058,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing pnf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing pnf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>pnf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/pnf">/pnf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing pnf</div>
@@ -76297,7 +87321,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interfaces">/lag-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interfaces">/lag-interfaces</a>
</div>
</div>
</div>
@@ -76423,7 +87447,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interface">/lag-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interface">/lag-interface</a>
</div>
</div>
</div>
@@ -76470,7 +87494,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>lag-interface object that needs to be created or updated</p>
+ <p><p>lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -76557,6 +87581,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing lag-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing lag-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>lag-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/lag-interface">/lag-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing lag-interface</div>
@@ -76763,7 +87892,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -76950,7 +88079,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -76997,7 +88126,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -77100,6 +88229,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -77444,7 +88694,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -77491,7 +88741,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -77610,6 +88860,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -77769,7 +89156,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -78232,7 +89619,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -78279,7 +89666,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -78398,6 +89785,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -78557,7 +90081,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -78819,7 +90343,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -79189,7 +90713,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -79452,7 +90976,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -79499,7 +91023,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -79618,6 +91142,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -79777,7 +91438,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -80179,7 +91840,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -80412,7 +92073,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -80459,7 +92120,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -80578,6 +92239,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -80984,7 +92782,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -81031,7 +92829,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -81166,6 +92964,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -81341,7 +93292,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -81882,7 +93833,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -81929,7 +93880,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -82064,6 +94015,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -82239,7 +94343,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -82533,7 +94637,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -82795,7 +94899,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -83056,7 +95160,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/p-interfaces">/p-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/p-interfaces">/p-interfaces</a>
</div>
</div>
</div>
@@ -83182,7 +95286,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/p-interface">/p-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/p-interface">/p-interface</a>
</div>
</div>
</div>
@@ -83229,7 +95333,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>p-interface object that needs to be created or updated</p>
+ <p><p>p-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -83316,6 +95420,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing p-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing p-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>p-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/p-interface">/p-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing p-interface</div>
@@ -83522,7 +95731,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -83709,7 +95918,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -83756,7 +95965,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -83859,6 +96068,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -84203,7 +96533,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -84250,7 +96580,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -84369,6 +96699,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -84528,7 +96995,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -84991,7 +97458,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -85038,7 +97505,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -85157,6 +97624,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -85316,7 +97920,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -85578,7 +98182,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -85948,7 +98552,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -86211,7 +98815,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -86258,7 +98862,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -86377,6 +98981,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -86536,7 +99277,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -86938,7 +99679,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -87171,7 +99912,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -87218,7 +99959,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -87337,6 +100078,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -87743,7 +100621,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -87790,7 +100668,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -87925,6 +100803,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -88100,7 +101131,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -88641,7 +101672,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -88688,7 +101719,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -88823,6 +101854,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -88998,7 +102182,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -89292,7 +102476,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -89554,7 +102738,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -89752,7 +102936,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -89935,7 +103119,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/route-table-references">/route-table-references</a>
+ <a class="json-schema-ref" href="#/getDefinitions/route-table-references">/route-table-references</a>
</div>
</div>
</div>
@@ -90045,7 +103229,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/route-table-reference">/route-table-reference</a>
+ <a class="json-schema-ref" href="#/getDefinitions/route-table-reference">/route-table-reference</a>
</div>
</div>
</div>
@@ -90092,7 +103276,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>route-table-reference object that needs to be created or updated</p>
+ <p><p>route-table-reference object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkRouteTableReferencesRouteTableReference.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -90163,6 +103347,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-route-table-references-route-table-reference--route-table-reference-id--"></span>
+ <div id="operation--network-route-table-references-route-table-reference--route-table-reference-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing route-table-reference</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/route-table-references/route-table-reference/{route-table-reference-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing route-table-reference</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>route-table-reference object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/route-table-reference">/route-table-reference</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ route-table-reference-id
+ </td>
+ <td>
+ <p>Route Table Reference id, UUID assigned to this instance.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-route-table-references-route-table-reference--route-table-reference-id--"></span>
<div id="operation--network-route-table-references-route-table-reference--route-table-reference-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing route-table-reference</div>
@@ -90274,7 +103547,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkRouteTableReferencesRouteTableReference.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -90457,7 +103730,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/site-pair-sets">/site-pair-sets</a>
+ <a class="json-schema-ref" href="#/getDefinitions/site-pair-sets">/site-pair-sets</a>
</div>
</div>
</div>
@@ -90552,7 +103825,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/site-pair-set">/site-pair-set</a>
+ <a class="json-schema-ref" href="#/getDefinitions/site-pair-set">/site-pair-set</a>
</div>
</div>
</div>
@@ -90599,7 +103872,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>site-pair-set object that needs to be created or updated</p>
+ <p><p>site-pair-set object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkSitePairSetsSitePairSet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -90670,6 +103943,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--"></span>
+ <div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing site-pair-set</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/site-pair-sets/site-pair-set/{site-pair-set-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing site-pair-set</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>site-pair-set object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/site-pair-set">/site-pair-set</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ site-pair-set-id
+ </td>
+ <td>
+ <p>Unique id of site pair set.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--"></span>
<div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing site-pair-set</div>
@@ -90781,7 +104143,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkSitePairSetsSitePairSet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -90995,7 +104357,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/routing-instances">/routing-instances</a>
+ <a class="json-schema-ref" href="#/getDefinitions/routing-instances">/routing-instances</a>
</div>
</div>
</div>
@@ -91106,7 +104468,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/routing-instance">/routing-instance</a>
+ <a class="json-schema-ref" href="#/getDefinitions/routing-instance">/routing-instance</a>
</div>
</div>
</div>
@@ -91153,7 +104515,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>routing-instance object that needs to be created or updated</p>
+ <p><p>routing-instance object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -91240,6 +104602,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--"></span>
+ <div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing routing-instance</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing routing-instance</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>routing-instance object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/routing-instance">/routing-instance</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ site-pair-set-id
+ </td>
+ <td>
+ <p>Unique id of site pair set.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ routing-instance-id
+ </td>
+ <td>
+ <p>Unique id of routing instance</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--"></span>
<div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing routing-instance</div>
@@ -91367,7 +104834,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -91629,7 +105096,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/site-pairs">/site-pairs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/site-pairs">/site-pairs</a>
</div>
</div>
</div>
@@ -91756,7 +105223,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/site-pair">/site-pair</a>
+ <a class="json-schema-ref" href="#/getDefinitions/site-pair">/site-pair</a>
</div>
</div>
</div>
@@ -91803,7 +105270,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>site-pair object that needs to be created or updated</p>
+ <p><p>site-pair object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -91906,6 +105373,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--"></span>
+ <div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing site-pair</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing site-pair</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>site-pair object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/site-pair">/site-pair</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ site-pair-set-id
+ </td>
+ <td>
+ <p>Unique id of site pair set.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ routing-instance-id
+ </td>
+ <td>
+ <p>Unique id of routing instance</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ site-pair-id
+ </td>
+ <td>
+ <p>unique identifier of probe</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--"></span>
<div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing site-pair</div>
@@ -92129,7 +105717,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/classes-of-service">/classes-of-service</a>
+ <a class="json-schema-ref" href="#/getDefinitions/classes-of-service">/classes-of-service</a>
</div>
</div>
</div>
@@ -92272,7 +105860,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/class-of-service">/class-of-service</a>
+ <a class="json-schema-ref" href="#/getDefinitions/class-of-service">/class-of-service</a>
</div>
</div>
</div>
@@ -92319,7 +105907,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>class-of-service object that needs to be created or updated</p>
+ <p><p>class-of-service object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -92438,6 +106026,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--classes-of-service-class-of-service--cos--"></span>
+ <div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--classes-of-service-class-of-service--cos--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing class-of-service</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}/classes-of-service/class-of-service/{cos}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing class-of-service</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>class-of-service object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/class-of-service">/class-of-service</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ site-pair-set-id
+ </td>
+ <td>
+ <p>Unique id of site pair set.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ routing-instance-id
+ </td>
+ <td>
+ <p>Unique id of routing instance</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ site-pair-id
+ </td>
+ <td>
+ <p>unique identifier of probe</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cos
+ </td>
+ <td>
+ <p>unique identifier of probe</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--classes-of-service-class-of-service--cos--"></span>
<div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--classes-of-service-class-of-service--cos--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing class-of-service</div>
@@ -92597,7 +106322,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -92859,7 +106584,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -93106,7 +106831,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vces">/vces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vces">/vces</a>
</div>
</div>
</div>
@@ -93321,7 +107046,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vce">/vce</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vce">/vce</a>
</div>
</div>
</div>
@@ -93368,7 +107093,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vce object that needs to be created or updated</p>
+ <p><p>vce object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVcesVce.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -93439,6 +107164,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vces-vce--vnf-id--"></span>
+ <div id="operation--network-vces-vce--vnf-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vce</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vces/vce/{vnf-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vce</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vce object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vce">/vce</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vces-vce--vnf-id--"></span>
<div id="operation--network-vces-vce--vnf-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vce</div>
@@ -93718,7 +107532,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/port-groups">/port-groups</a>
+ <a class="json-schema-ref" href="#/getDefinitions/port-groups">/port-groups</a>
</div>
</div>
</div>
@@ -93994,7 +107808,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/port-group">/port-group</a>
+ <a class="json-schema-ref" href="#/getDefinitions/port-group">/port-group</a>
</div>
</div>
</div>
@@ -94041,7 +107855,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>port-group object that needs to be created or updated</p>
+ <p><p>port-group object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVcesVcePortGroupsPortGroup.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -94128,6 +107942,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vces-vce--vnf-id--port-groups-port-group--interface-id--"></span>
+ <div id="operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing port-group</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing port-group</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>port-group object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/port-group">/port-group</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-id
+ </td>
+ <td>
+ <p>Unique ID of the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vces-vce--vnf-id--port-groups-port-group--interface-id--"></span>
<div id="operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing port-group</div>
@@ -94484,7 +108403,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/cvlan-tags">/cvlan-tags</a>
+ <a class="json-schema-ref" href="#/getDefinitions/cvlan-tags">/cvlan-tags</a>
</div>
</div>
</div>
@@ -94776,7 +108695,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/cvlan-tag-entry">/cvlan-tag-entry</a>
+ <a class="json-schema-ref" href="#/getDefinitions/cvlan-tag-entry">/cvlan-tag-entry</a>
</div>
</div>
</div>
@@ -94823,7 +108742,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>cvlan-tag-entry object that needs to be created or updated</p>
+ <p><p>cvlan-tag-entry object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -94926,6 +108845,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vces-vce--vnf-id--port-groups-port-group--interface-id--cvlan-tags-cvlan-tag-entry--cvlan-tag--"></span>
+ <div id="operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--cvlan-tags-cvlan-tag-entry--cvlan-tag--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing cvlan-tag-entry</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}/cvlan-tags/cvlan-tag-entry/{cvlan-tag}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing cvlan-tag-entry</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>cvlan-tag-entry object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/cvlan-tag-entry">/cvlan-tag-entry</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-id
+ </td>
+ <td>
+ <p>Unique ID of the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cvlan-tag
+ </td>
+ <td>
+ <p>See mis-na-virtualization-platform.yang</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vces-vce--vnf-id--port-groups-port-group--interface-id--cvlan-tags-cvlan-tag-entry--cvlan-tag--"></span>
<div id="operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--cvlan-tags-cvlan-tag-entry--cvlan-tag--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing cvlan-tag-entry</div>
@@ -95069,7 +109109,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -95299,7 +109339,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVcesVcePortGroupsPortGroup.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -95497,7 +109537,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVcesVce.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -95680,7 +109720,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vnfcs">/vnfcs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vnfcs">/vnfcs</a>
</div>
</div>
</div>
@@ -95878,7 +109918,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vnfc">/vnfc</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vnfc">/vnfc</a>
</div>
</div>
</div>
@@ -95925,7 +109965,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vnfc object that needs to be created or updated</p>
+ <p><p>vnfc object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVnfcsVnfc.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -95996,6 +110036,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vnfcs-vnfc--vnfc-name--"></span>
+ <div id="operation--network-vnfcs-vnfc--vnfc-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vnfc</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vnfcs/vnfc/{vnfc-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vnfc</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vnfc object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vnfc">/vnfc</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnfc-name
+ </td>
+ <td>
+ <p>Unique ID of vnfc.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vnfcs-vnfc--vnfc-name--"></span>
<div id="operation--network-vnfcs-vnfc--vnfc-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vnfc</div>
@@ -96107,7 +110236,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVnfcsVnfc.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -96290,7 +110419,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vpls-pes">/vpls-pes</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vpls-pes">/vpls-pes</a>
</div>
</div>
</div>
@@ -96399,7 +110528,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vpls-pe">/vpls-pe</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vpls-pe">/vpls-pe</a>
</div>
</div>
</div>
@@ -96446,7 +110575,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vpls-pe object that needs to be created or updated</p>
+ <p><p>vpls-pe object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPe.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -96516,6 +110645,94 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vpls-pe</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vpls-pe</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vpls-pe object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vpls-pe">/vpls-pe</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vpls-pe</div>
@@ -96688,7 +110905,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interfaces">/lag-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interfaces">/lag-interfaces</a>
</div>
</div>
</div>
@@ -96813,7 +111030,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interface">/lag-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interface">/lag-interface</a>
</div>
</div>
</div>
@@ -96860,7 +111077,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>lag-interface object that needs to be created or updated</p>
+ <p><p>lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -96946,6 +111163,110 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing lag-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing lag-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>lag-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/lag-interface">/lag-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing lag-interface</div>
@@ -97150,7 +111471,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -97336,7 +111657,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -97383,7 +111704,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -97485,6 +111806,126 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -97827,7 +112268,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -97874,7 +112315,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -97992,6 +112433,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -98150,7 +112727,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -98610,7 +113187,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -98657,7 +113234,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -98775,6 +113352,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -98933,7 +113646,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -99193,7 +113906,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -99560,7 +114273,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -99822,7 +114535,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -99869,7 +114582,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -99987,6 +114700,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -100145,7 +114994,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -100544,7 +115393,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -100776,7 +115625,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -100823,7 +115672,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -100941,6 +115790,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -101345,7 +116330,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -101392,7 +116377,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -101526,6 +116511,158 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -101700,7 +116837,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -102238,7 +117375,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -102285,7 +117422,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -102419,6 +117556,158 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -102593,7 +117882,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -102885,7 +118174,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -103145,7 +118434,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -103403,7 +118692,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/p-interfaces">/p-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/p-interfaces">/p-interfaces</a>
</div>
</div>
</div>
@@ -103528,7 +118817,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/p-interface">/p-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/p-interface">/p-interface</a>
</div>
</div>
</div>
@@ -103575,7 +118864,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>p-interface object that needs to be created or updated</p>
+ <p><p>p-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -103661,6 +118950,110 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing p-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing p-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>p-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/p-interface">/p-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing p-interface</div>
@@ -103865,7 +119258,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -104051,7 +119444,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -104098,7 +119491,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -104200,6 +119593,126 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -104542,7 +120055,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -104589,7 +120102,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -104707,6 +120220,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -104865,7 +120514,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -105325,7 +120974,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -105372,7 +121021,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -105490,6 +121139,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -105648,7 +121433,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -105908,7 +121693,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -106275,7 +122060,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -106537,7 +122322,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -106584,7 +122369,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -106702,6 +122487,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -106860,7 +122781,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -107259,7 +123180,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -107491,7 +123412,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -107538,7 +123459,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -107656,6 +123577,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -108060,7 +124117,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -108107,7 +124164,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -108241,6 +124298,158 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -108415,7 +124624,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -108953,7 +125162,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -109000,7 +125209,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -109134,6 +125343,158 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -109308,7 +125669,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -109600,7 +125961,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -109860,7 +126221,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -110056,7 +126417,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPe.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -110237,7 +126598,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vpn-bindings">/vpn-bindings</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vpn-bindings">/vpn-bindings</a>
</div>
</div>
</div>
@@ -110362,7 +126723,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vpn-binding">/vpn-binding</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vpn-binding">/vpn-binding</a>
</div>
</div>
</div>
@@ -110409,7 +126770,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vpn-binding object that needs to be created or updated</p>
+ <p><p>vpn-binding object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVpnBindingsVpnBinding.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -110480,6 +126841,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpn-bindings-vpn-binding--vpn-id--"></span>
+ <div id="operation--network-vpn-bindings-vpn-binding--vpn-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vpn-binding</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpn-bindings/vpn-binding/{vpn-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vpn-binding</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vpn-binding object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vpn-binding">/vpn-binding</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vpn-id
+ </td>
+ <td>
+ <p>VPN ID, globally unique within A&AI</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpn-bindings-vpn-binding--vpn-id--"></span>
<div id="operation--network-vpn-bindings-vpn-binding--vpn-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vpn-binding</div>
@@ -110591,7 +127041,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVpnBindingsVpnBinding.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -110774,7 +127224,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/models">/models</a>
+ <a class="json-schema-ref" href="#/getDefinitions/models">/models</a>
</div>
</div>
</div>
@@ -110929,7 +127379,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/model">/model</a>
+ <a class="json-schema-ref" href="#/getDefinitions/model">/model</a>
</div>
</div>
</div>
@@ -110976,7 +127426,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>model object that needs to be created or updated</p>
+ <p><p>model object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationModelsModel.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -111047,6 +127497,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-models-model--model-name-version-id--"></span>
+ <div id="operation--service-design-and-creation-models-model--model-name-version-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing model</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/models/model/{model-name-version-id}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing model</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>model object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/model">/model</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ model-name-version-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to one version of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-models-model--model-name-version-id--"></span>
<div id="operation--service-design-and-creation-models-model--model-name-version-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing model</div>
@@ -111266,7 +127805,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadata">/metadata</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadata">/metadata</a>
</div>
</div>
</div>
@@ -111436,7 +127975,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadatum">/metadatum</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadatum">/metadatum</a>
</div>
</div>
</div>
@@ -111483,7 +128022,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>metadatum object that needs to be created or updated</p>
+ <p><p>metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationModelsModelMetadataMetadatum.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -111569,6 +128108,110 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-models-model--model-name-version-id--metadata-metadatum--metaname--"></span>
+ <div id="operation--service-design-and-creation-models-model--model-name-version-id--metadata-metadatum--metaname--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing metadatum</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/models/model/{model-name-version-id}/metadata/metadatum/{metaname}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing metadatum</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>metadatum object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/metadatum">/metadatum</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ model-name-version-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to one version of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ metaname
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-models-model--model-name-version-id--metadata-metadatum--metaname--"></span>
<div id="operation--service-design-and-creation-models-model--model-name-version-id--metadata-metadatum--metaname--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing metadatum</div>
@@ -111803,7 +128446,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/model-elements">/model-elements</a>
+ <a class="json-schema-ref" href="#/getDefinitions/model-elements">/model-elements</a>
</div>
</div>
</div>
@@ -111973,7 +128616,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/model-element">/model-element</a>
+ <a class="json-schema-ref" href="#/getDefinitions/model-element">/model-element</a>
</div>
</div>
</div>
@@ -112020,7 +128663,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>model-element object that needs to be created or updated</p>
+ <p><p>model-element object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationModelsModelModelElementsModelElement.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -112106,6 +128749,110 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-models-model--model-name-version-id--model-elements-model-element--model-element-uuid--"></span>
+ <div id="operation--service-design-and-creation-models-model--model-name-version-id--model-elements-model-element--model-element-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing model-element</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/models/model/{model-name-version-id}/model-elements/model-element/{model-element-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing model-element</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>model-element object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/model-element">/model-element</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ model-name-version-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to one version of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-element-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-models-model--model-name-version-id--model-elements-model-element--model-element-uuid--"></span>
<div id="operation--service-design-and-creation-models-model--model-name-version-id--model-elements-model-element--model-element-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing model-element</div>
@@ -112355,7 +129102,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/model-constraints">/model-constraints</a>
+ <a class="json-schema-ref" href="#/getDefinitions/model-constraints">/model-constraints</a>
</div>
</div>
</div>
@@ -112540,7 +129287,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/model-constraint">/model-constraint</a>
+ <a class="json-schema-ref" href="#/getDefinitions/model-constraint">/model-constraint</a>
</div>
</div>
</div>
@@ -112587,7 +129334,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>model-constraint object that needs to be created or updated</p>
+ <p><p>model-constraint object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationModelsModelModelElementsModelElementModelConstraintsModelConstraint.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -112688,6 +129435,125 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-models-model--model-name-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--"></span>
+ <div id="operation--service-design-and-creation-models-model--model-name-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing model-constraint</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/models/model/{model-name-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing model-constraint</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>model-constraint object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/model-constraint">/model-constraint</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ model-name-version-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to one version of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-element-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-constraint-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-models-model--model-name-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--"></span>
<div id="operation--service-design-and-creation-models-model--model-name-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing model-constraint</div>
@@ -112967,7 +129833,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/constrained-element-sets">/constrained-element-sets</a>
+ <a class="json-schema-ref" href="#/getDefinitions/constrained-element-sets">/constrained-element-sets</a>
</div>
</div>
</div>
@@ -113167,7 +130033,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/constrained-element-set">/constrained-element-set</a>
+ <a class="json-schema-ref" href="#/getDefinitions/constrained-element-set">/constrained-element-set</a>
</div>
</div>
</div>
@@ -113214,7 +130080,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>constrained-element-set object that needs to be created or updated</p>
+ <p><p>constrained-element-set object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationModelsModelModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -113330,6 +130196,140 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-models-model--model-name-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--"></span>
+ <div id="operation--service-design-and-creation-models-model--model-name-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing constrained-element-set</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/models/model/{model-name-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing constrained-element-set</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>constrained-element-set object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/constrained-element-set">/constrained-element-set</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ model-name-version-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to one version of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-element-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-constraint-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ constrained-element-set-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-models-model--model-name-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--"></span>
<div id="operation--service-design-and-creation-models-model--model-name-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing constrained-element-set</div>
@@ -113639,7 +130639,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/element-choice-sets">/element-choice-sets</a>
+ <a class="json-schema-ref" href="#/getDefinitions/element-choice-sets">/element-choice-sets</a>
</div>
</div>
</div>
@@ -113854,7 +130854,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/element-choice-set">/element-choice-set</a>
+ <a class="json-schema-ref" href="#/getDefinitions/element-choice-set">/element-choice-set</a>
</div>
</div>
</div>
@@ -113901,7 +130901,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>element-choice-set object that needs to be created or updated</p>
+ <p><p>element-choice-set object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationModelsModelModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -114032,6 +131032,155 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-models-model--model-name-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--element-choice-sets-element-choice-set--element-choice-set-uuid--"></span>
+ <div id="operation--service-design-and-creation-models-model--model-name-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--element-choice-sets-element-choice-set--element-choice-set-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing element-choice-set</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/models/model/{model-name-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}/element-choice-sets/element-choice-set/{element-choice-set-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing element-choice-set</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>element-choice-set object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/element-choice-set">/element-choice-set</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ model-name-version-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to one version of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-element-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-constraint-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ constrained-element-set-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ element-choice-set-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-models-model--model-name-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--element-choice-sets-element-choice-set--element-choice-set-uuid--"></span>
<div id="operation--service-design-and-creation-models-model--model-name-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--element-choice-sets-element-choice-set--element-choice-set-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing element-choice-set</div>
@@ -114203,7 +131352,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationModelsModelModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -114489,7 +131638,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationModelsModelModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -114745,7 +131894,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationModelsModelModelElementsModelElement.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -114941,7 +132090,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationModelsModel.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -115124,7 +132273,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/named-queries">/named-queries</a>
+ <a class="json-schema-ref" href="#/getDefinitions/named-queries">/named-queries</a>
</div>
</div>
</div>
@@ -115232,7 +132381,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/named-query">/named-query</a>
+ <a class="json-schema-ref" href="#/getDefinitions/named-query">/named-query</a>
</div>
</div>
</div>
@@ -115279,7 +132428,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>named-query object that needs to be created or updated</p>
+ <p><p>named-query object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationNamedQueriesNamedQuery.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -115349,6 +132498,94 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--"></span>
+ <div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing named-query</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/named-queries/named-query/{named-query-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing named-query</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>named-query object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/named-query">/named-query</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ named-query-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--"></span>
<div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing named-query</div>
@@ -115520,7 +132757,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/named-query-elements">/named-query-elements</a>
+ <a class="json-schema-ref" href="#/getDefinitions/named-query-elements">/named-query-elements</a>
</div>
</div>
</div>
@@ -115643,7 +132880,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/named-query-element">/named-query-element</a>
+ <a class="json-schema-ref" href="#/getDefinitions/named-query-element">/named-query-element</a>
</div>
</div>
</div>
@@ -115690,7 +132927,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>named-query-element object that needs to be created or updated</p>
+ <p><p>named-query-element object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -115775,6 +133012,109 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--"></span>
+ <div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing named-query-element</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing named-query-element</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>named-query-element object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/named-query-element">/named-query-element</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ named-query-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ named-query-element-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--"></span>
<div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing named-query-element</div>
@@ -115976,7 +133316,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/property-constraints">/property-constraints</a>
+ <a class="json-schema-ref" href="#/getDefinitions/property-constraints">/property-constraints</a>
</div>
</div>
</div>
@@ -116114,7 +133454,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/property-constraint">/property-constraint</a>
+ <a class="json-schema-ref" href="#/getDefinitions/property-constraint">/property-constraint</a>
</div>
</div>
</div>
@@ -116161,7 +133501,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>property-constraint object that needs to be created or updated</p>
+ <p><p>property-constraint object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementPropertyConstraintsPropertyConstraint.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -116261,6 +133601,124 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--property-constraints-property-constraint--property-constraint-uuid--"></span>
+ <div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--property-constraints-property-constraint--property-constraint-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing property-constraint</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/property-constraints/property-constraint/{property-constraint-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing property-constraint</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>property-constraint object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/property-constraint">/property-constraint</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ named-query-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ named-query-element-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ property-constraint-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--property-constraints-property-constraint--property-constraint-uuid--"></span>
<div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--property-constraints-property-constraint--property-constraint-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing property-constraint</div>
@@ -116477,7 +133935,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/related-lookups">/related-lookups</a>
+ <a class="json-schema-ref" href="#/getDefinitions/related-lookups">/related-lookups</a>
</div>
</div>
</div>
@@ -116615,7 +134073,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/related-lookup">/related-lookup</a>
+ <a class="json-schema-ref" href="#/getDefinitions/related-lookup">/related-lookup</a>
</div>
</div>
</div>
@@ -116662,7 +134120,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>related-lookup object that needs to be created or updated</p>
+ <p><p>related-lookup object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -116762,6 +134220,124 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--related-lookups-related-lookup--related-lookup-uuid--"></span>
+ <div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--related-lookups-related-lookup--related-lookup-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing related-lookup</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/related-lookups/related-lookup/{related-lookup-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing related-lookup</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>related-lookup object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/related-lookup">/related-lookup</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ named-query-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ named-query-element-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ related-lookup-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--related-lookups-related-lookup--related-lookup-uuid--"></span>
<div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--related-lookups-related-lookup--related-lookup-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing related-lookup</div>
@@ -116902,7 +134478,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -117126,7 +134702,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -117320,7 +134896,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationNamedQueriesNamedQuery.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -117501,7 +135077,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/service-capabilities">/service-capabilities</a>
+ <a class="json-schema-ref" href="#/getDefinitions/service-capabilities">/service-capabilities</a>
</div>
</div>
</div>
@@ -117612,7 +135188,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/service-capability">/service-capability</a>
+ <a class="json-schema-ref" href="#/getDefinitions/service-capability">/service-capability</a>
</div>
</div>
</div>
@@ -117659,7 +135235,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>service-capability object that needs to be created or updated</p>
+ <p><p>service-capability object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationServiceCapabilitiesServiceCapability.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -117746,6 +135322,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-service-capabilities-service-capability--service-type---vnf-type--"></span>
+ <div id="operation--service-design-and-creation-service-capabilities-service-capability--service-type---vnf-type--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing service-capability</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/service-capabilities/service-capability/{service-type}/{vnf-type}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing service-capability</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>service-capability object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/service-capability">/service-capability</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ service-type
+ </td>
+ <td>
+ <p>This gets defined by others to provide a unique ID for the service, we accept what is sent.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vnf-type
+ </td>
+ <td>
+ <p>String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded and clients should expect changes to occur in the future to this field as ASDC matures.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-service-capabilities-service-capability--service-type---vnf-type--"></span>
<div id="operation--service-design-and-creation-service-capabilities-service-capability--service-type---vnf-type--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing service-capability</div>
@@ -117873,7 +135554,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationServiceCapabilitiesServiceCapability.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -118088,7 +135769,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/services">/services</a>
+ <a class="json-schema-ref" href="#/getDefinitions/services">/services</a>
</div>
</div>
</div>
@@ -118198,7 +135879,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/service">/service</a>
+ <a class="json-schema-ref" href="#/getDefinitions/service">/service</a>
</div>
</div>
</div>
@@ -118245,7 +135926,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>service object that needs to be created or updated</p>
+ <p><p>service object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationServicesService.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -118316,6 +135997,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-services-service--service-id--"></span>
+ <div id="operation--service-design-and-creation-services-service--service-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing service</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/services/service/{service-id}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing service</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>service object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/service">/service</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ service-id
+ </td>
+ <td>
+ <p>This gets defined by others to provide a unique ID for the service, we accept what is sent.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-services-service--service-id--"></span>
<div id="operation--service-design-and-creation-services-service--service-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing service</div>
@@ -118427,7 +136197,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationServicesService.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -118610,7 +136380,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vnf-images">/vnf-images</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vnf-images">/vnf-images</a>
</div>
</div>
</div>
@@ -118750,7 +136520,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vnf-image">/vnf-image</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vnf-image">/vnf-image</a>
</div>
</div>
</div>
@@ -118797,7 +136567,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vnf-image object that needs to be created or updated</p>
+ <p><p>vnf-image object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationVnfImagesVnfImage.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -118868,6 +136638,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-vnf-images-vnf-image--vnf-image-uuid--"></span>
+ <div id="operation--service-design-and-creation-vnf-images-vnf-image--vnf-image-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vnf-image</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/vnf-images/vnf-image/{vnf-image-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vnf-image</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vnf-image object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vnf-image">/vnf-image</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-image-uuid
+ </td>
+ <td>
+ <p>Unique ID of this asset</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-vnf-images-vnf-image--vnf-image-uuid--"></span>
<div id="operation--service-design-and-creation-vnf-images-vnf-image--vnf-image-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vnf-image</div>
@@ -118979,7 +136838,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationVnfImagesVnfImage.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -119129,6 +136988,45 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<h2>Schema definitions</h2>
+ <div id="definition-aai-internal" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/aai-internal"></a>aai-internal:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="property-name">
+ <span class="json-property-name">property-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="property-value">
+ <span class="json-property-name">property-value:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-action" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/action"></a>action:
@@ -119277,6 +137175,215 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-allotted-resource" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/allotted-resource"></a>allotted-resource:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Represents a slice or partial piece of a resource that gets separately allotted</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO generic-vnf( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY)</li>
+<li>TO instance-group( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>TO l3-network( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY)</li>
+<li>TO vlan( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY)</li>
+<li>TO service-instance( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)</li>
+<li>FROM tunnel-xconnect( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY)</li>
+<li>ALLOTTED-RESOURCE is DELETED when these are DELETED TUNNEL-XCONNECT</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="id">
+ <span class="json-property-name">id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Allotted Resource id UUID assigned to this instance.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="description">
+ <span class="json-property-name">description:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>The descriptive information assigned to this allotted resource instance</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="selflink">
+ <span class="json-property-name">selflink:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Link back to more information in the controller</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="persona-model-id">
+ <span class="json-property-name">persona-model-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>the ASDC model id for this resource or service model.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="persona-model-version">
+ <span class="json-property-name">persona-model-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>the ASDC model version for this resource or service model.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="model-version-id">
+ <span class="json-property-name">model-version-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>the ASDC model version for this resource or service model.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="persona-model-customization-id">
+ <span class="json-property-name">persona-model-customization-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>captures the id of all the configuration used to customize the resource for the service.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Concurrency value</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="tunnel-xconnects">
+ <span class="json-property-name">tunnel-xconnects:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/tunnel-xconnect">tunnel-xconnect</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-allotted-resources" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/allotted-resources"></a>allotted-resources:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>This object is used to store slices of services being offered</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="allotted-resource">
+ <span class="json-property-name">allotted-resource:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/allotted-resource">allotted-resource</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-availability-zone" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/availability-zone"></a>availability-zone:
@@ -119289,18 +137396,17 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Availability zone, a collection of compute hosts/pservers</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_IF_ANY_IN_EDGES</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO complex (Many2Many)</li>
-<li>TO service-capability (Many2Many)</li>
-<li>FROM cloud-region (is composed of availability-zone)</li>
-<li>FROM ctag-pool</li>
-<li>FROM dvs-switch</li>
-<li>FROM generic-vnf</li>
-<li>FROM pserver</li>
-<li>FROM vce</li></ul>
+<li>TO complex( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>TO service-capability( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)</li>
+<li>TO cloud-region( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM ctag-pool( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)</li>
+<li>FROM dvs-switch( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)</li>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)</li>
+<li>FROM pserver( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)</li>
+<li>FROM vce( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)</li>
+<li>AVAILABILITY-ZONE cannot be deleted if linked to CTAG-POOL,DVS-SWITCH,GENERIC-VNF,PSERVER,VCE</li></ul>
</section>
@@ -119552,7 +137658,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<section class="json-schema-description">
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM site-pair (is composed of class-of-service)</li></ul>
+<li>TO site-pair( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)</li></ul>
</section>
@@ -119805,22 +137911,22 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>cloud-region designates an installation of a cloud cluster or region or instantiation.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO complex (Many2One)</li>
-<li>TO l3-network (Many2Many)</li>
-<li>TO tenant (comprises cloud-region, One2Many)</li>
-<li>TO image (comprises cloud-region, One2Many)</li>
-<li>TO flavor (comprises cloud-region, One2Many)</li>
-<li>TO availability-zone (comprises cloud-region, One2Many)</li>
-<li>TO oam-network (comprises cloud-region, One2Many)</li>
-<li>TO dvs-switch (comprises cloud-region, One2Many)</li>
-<li>TO volume-group (comprises cloud-region, One2Many)</li>
-<li>TO group-assignment (comprises cloud-region, One2Many)</li>
-<li>TO snapshot (comprises cloud-region, One2Many)</li>
-<li>FROM pserver</li></ul>
+<li>TO complex( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>TO l3-network( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>FROM availability-zone( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM dvs-switch( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM flavor( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM group-assignment( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM image( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM oam-network( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM snapshot( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM tenant( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM volume-group( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM pserver( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)</li>
+<li>CLOUD-REGION cannot be deleted if linked to DVS-SWITCH,FLAVOR,GROUP-ASSIGNMENT,IMAGE,OAM-NETWORK,SNAPSHOT,TENANT,VOLUME-GROUP</li>
+<li>CLOUD-REGION is DELETED when these are DELETED AVAILABILITY-ZONE</li></ul>
</section>
@@ -120191,16 +138297,18 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Collection of physical locations that can house cloud-regions.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO ctag-pool (comprises complex, Many2Many)</li>
-<li>TO l3-network (Many2Many)</li>
-<li>FROM availability-zone</li>
-<li>FROM cloud-region</li>
-<li>FROM oam-network</li>
-<li>FROM pserver</li>
-<li>FROM pnf</li>
-<li>FROM vce</li>
-<li>FROM vpls-pe</li>
-<li>FROM volume-group</li></ul>
+<li>TO l3-network( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>FROM availability-zone( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM ctag-pool( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)</li>
+<li>FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)</li>
+<li>FROM pnf( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM pserver( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM vce( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)</li>
+<li>FROM volume-group( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM vpls-pe( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>COMPLEX cannot be deleted if linked to AVAILABILITY-ZONE,CLOUD-REGION,OAM-NETWORK,PNF,PSERVER,VCE,VOLUME-GROUP,VPLS-PE</li>
+<li>COMPLEX is DELETED when these are DELETED CTAG-POOL</li></ul>
</section>
@@ -120491,6 +138599,268 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-configuration" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/configuration"></a>configuration:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Port Mirror Configuration.</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO allotted-resource( configuration org.onap.relationships.inventory.Uses allotted-resource, ONE2ONE)</li>
+<li>TO logical-link( configuration org.onap.relationships.inventory.Uses logical-link, ONE2MANY)</li>
+<li>FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo configuration, MANY2ONE)</li>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses configuration, ONE2MANY)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.Uses configuration, ONE2MANY)</li>
+<li>CONFIGURATION is DELETED when these are DELETED METADATUM</li>
+<li>CONFIGURATION deletion means associated objects of these types are also DELETED:ALLOTTED-RESOURCE,LOGICAL-LINK</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="configuration-id">
+ <span class="json-property-name">configuration-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>UUID assigned to configuration.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="management-option">
+ <span class="json-property-name">management-option:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Indicates the entity that will manage this feature. Could be an organization or the name of the application as well.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="configuration-name">
+ <span class="json-property-name">configuration-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Name of the configuration.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="configuration-type">
+ <span class="json-property-name">configuration-type:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>port-mirroring-configuration.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="configuration-sub-type">
+ <span class="json-property-name">configuration-sub-type:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>vprobe, pprobe.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="model-invariant-id">
+ <span class="json-property-name">model-invariant-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>the ASDC model id for this resource or service model.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="model-version-id">
+ <span class="json-property-name">model-version-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>the ASDC model version for this resource or service model.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="orchestration-status">
+ <span class="json-property-name">orchestration-status:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Orchestration status of the configuration.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="operational-status">
+ <span class="json-property-name">operational-status:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Indicator for whether the resource is considered operational.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="configuration-selflink">
+ <span class="json-property-name">configuration-selflink:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>URL to endpoint where AAI can get more details from SDN-GC.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="model-customization-id">
+ <span class="json-property-name">model-customization-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>id of the configuration used to customize the resource</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ <dt data-property-name="metadata">
+ <span class="json-property-name">metadata:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/metadatum">metadatum</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-configurations" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/configurations"></a>configurations:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Collection of configurations</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="configuration">
+ <span class="json-property-name">configuration:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/configuration">configuration</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-connector" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/connector"></a>connector:
@@ -120505,9 +138875,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Collection of resource instances used to connect a variety of disparate inventory widgets</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO virtual-data-center (Many2Many)</li>
-<li>TO metadatum (comprises connector, Many2Many)</li>
-<li>FROM service-instance</li></ul>
+<li>TO virtual-data-center( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)</li>
+<li>FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)</li>
+<li>CONNECTOR is DELETED when these are DELETED METADATUM</li></ul>
</section>
@@ -120697,9 +139068,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>This is how we would capture constraints defining allowed sets of elements.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO element-choice-set (comprises constrained-element-set, One2Many)</li>
-<li>FROM model-element (is composed of constrained-element-set)</li>
-<li>FROM model-constraint (is composed of constrained-element-set)</li></ul>
+<li>TO model-constraint( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)</li>
+<li>TO model-element( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)</li>
+<li>FROM element-choice-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)</li>
+<li>CONSTRAINED-ELEMENT-SET is DELETED when these are DELETED ELEMENT-CHOICE-SET</li></ul>
</section>
@@ -120844,11 +139216,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<div class="panel-body">
<section class="json-schema-description">
- <h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
-<h6 id="related-nodes">Related Nodes</h6>
+ <h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM l3-network (is composed of ctag-assignment)</li></ul>
+<li>TO l3-network( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)</li></ul>
</section>
@@ -120954,9 +139324,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>A collection of C tags (vlan tags) grouped for a specific purpose.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO availability-zone (Many2Many)</li>
-<li>FROM complex (is composed of ctag-pool)</li>
-<li>FROM vpls-pe</li></ul>
+<li>TO complex( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)</li>
+<li>TO availability-zone( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)</li>
+<li>FROM vpls-pe( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)</li></ul>
</section>
@@ -121098,11 +139468,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>customer identifiers to provide linkage back to BSS information.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO service-subscription (comprises customer, Many2Many)</li></ul>
+<li>FROM service-subscription( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)</li>
+<li>CUSTOMER is DELETED when these are DELETED SERVICE-SUBSCRIPTION</li></ul>
</section>
@@ -121357,8 +139726,8 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Digital virtual switch metadata, used by SDN-C to configure VCEs. A&AI needs to receive this data from the PO deployment team and administer it using the provisioningTool.sh into A&AI.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO availability-zone (Many2Many)</li>
-<li>FROM cloud-region (is composed of dvs-switch)</li></ul>
+<li>TO cloud-region( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>TO availability-zone( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)</li></ul>
</section>
@@ -121737,8 +140106,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>This is how we would capture constraints defining allowed sets of elements.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO model-element (comprises element-choice-set, One2Many)</li>
-<li>FROM constrained-element-set (is composed of element-choice-set)</li></ul>
+<li>TO constrained-element-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)</li>
+<li>FROM model-element( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)</li>
+<li>ELEMENT-CHOICE-SET is DELETED when these are DELETED MODEL-ELEMENT</li></ul>
</section>
@@ -121871,6 +140241,1235 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-entitlement" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/entitlement"></a>entitlement:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Metadata for entitlement group.</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO generic-vnf( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>TO vce( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="group-uuid">
+ <span class="json-property-name">group-uuid:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Unique ID for the entitlement group the resource comes from, should be uuid.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-uuid">
+ <span class="json-property-name">resource-uuid:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Unique ID of an entitlement resource.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Concurrency value</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-entitlements" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/entitlements"></a>entitlements:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Entitlements, keyed by group-uuid and resource-uuid, related to license management</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="entitlement">
+ <span class="json-property-name">entitlement:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/entitlement">entitlement</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-esr-ems" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/esr-ems"></a>esr-ems:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Persist EMS address information used by EMS driver.</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO esr-system-info (CHILD of esr-ems, esr-ems has esr-system-info, One2Many)</li>
+<li>ESR-EMS deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="ems-id">
+ <span class="json-property-name">ems-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Unique ID of EMS.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="esr-system-info-list">
+ <span class="json-property-name">esr-system-info-list:</span>
+ <span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-system-info-list">esr-system-info-list</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship-list">relationship-list</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-esr-ems-list" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/esr-ems-list"></a>esr-ems-list:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="esr-ems">
+ <span class="json-property-name">esr-ems:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-ems">esr-ems</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-esr-system-info" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/esr-system-info"></a>esr-system-info:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Persist common address information of external systems.</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>FROM esr-ems (PARENT of esr-system-info, esr-ems has esr-system-info)</li>
+<li>FROM esr-vnfm (PARENT of esr-system-info, esr-vnfm has esr-system-info)</li>
+<li>FROM esr-thirdparty-sdnc (PARENT of esr-system-info, esr-thirdparty-sdnc has esr-system-info)</li>
+<li>FROM cloud-region (PARENT of esr-system-info, cloud-region has esr-system-info)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="esr-system-info-id">
+ <span class="json-property-name">esr-system-info-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Unique ID of esr system info.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="system-name">
+ <span class="json-property-name">system-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>name of external system.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="type">
+ <span class="json-property-name">type:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>type of external systems.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="vendor">
+ <span class="json-property-name">vendor:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>vendor of external systems.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="version">
+ <span class="json-property-name">version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>version of external systems.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="service-url">
+ <span class="json-property-name">service-url:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>url used to access external systems.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="user-name">
+ <span class="json-property-name">user-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>username used to access external systems.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="password">
+ <span class="json-property-name">password:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>password used to access external systems.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="system-type">
+ <span class="json-property-name">system-type:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>it could be vim/vnfm/thirdparty-sdnc/ems-resource/ems-performance/ems-alarm.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="protocol">
+ <span class="json-property-name">protocol:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>protocol of third party SDNC, for example netconf/snmp.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="ssl-cacert">
+ <span class="json-property-name">ssl-cacert:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>ca file content if enabled ssl on auth-url.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="ssl-insecure">
+ <span class="json-property-name">ssl-insecure:</span>
+ <span class="json-property-type">boolean</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Whether to verify VIM's certificate.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="ip-address">
+ <span class="json-property-name">ip-address:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>service IP of ftp server.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="port">
+ <span class="json-property-name">port:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>service port of ftp server.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="cloud-domain">
+ <span class="json-property-name">cloud-domain:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>domain info for authentication.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="default-tenant">
+ <span class="json-property-name">default-tenant:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>default tenant of VIM.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="passive">
+ <span class="json-property-name">passive:</span>
+ <span class="json-property-type">boolean</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>ftp passive mode or not.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="remote-path">
+ <span class="json-property-name">remote-path:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>resource or performance data file path.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="system-status">
+ <span class="json-property-name">system-status:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>the status of external system.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-esr-system-info-list" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/esr-system-info-list"></a>esr-system-info-list:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Collection of persistent block-level external system auth info.</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="esr-system-info">
+ <span class="json-property-name">esr-system-info:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-system-info">esr-system-info</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-esr-thirdparty-sdnc" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/esr-thirdparty-sdnc"></a>esr-thirdparty-sdnc:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Persist SDNC address information used by ONAP SDNC.</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO esr-system-info (CHILD of esr-thirdparty-sdnc, esr-thirdparty-sdnc has esr-system-info, One2One)</li>
+<li>TO pnf( esr-thirdparty-sdnc has pnf, One2Many)</li>
+<li>ESR-THIRDPARTY-SDNC deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="thirdparty-sdnc-id">
+ <span class="json-property-name">thirdparty-sdnc-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Unique ID of SDNC.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="location">
+ <span class="json-property-name">location:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>used for DC type to indicate the location of SDNC, such as Core or Edge.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="product-name">
+ <span class="json-property-name">product-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>password used to access SDNC server.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="esr-system-info-list">
+ <span class="json-property-name">esr-system-info-list:</span>
+ <span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-system-info-list">esr-system-info-list</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship-list">relationship-list</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-esr-thirdparty-sdnc-list" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/esr-thirdparty-sdnc-list"></a>esr-thirdparty-sdnc-list:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="esr-thirdparty-sdnc">
+ <span class="json-property-name">esr-thirdparty-sdnc:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-thirdparty-sdnc">esr-thirdparty-sdnc</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-esr-vnfm" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/esr-vnfm"></a>esr-vnfm:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Persist VNFM address information used by VF-C.</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO esr-system-info (CHILD of esr-vnfm, esr-vnfm has esr-system-info, One2One)</li>
+<li>ESR-VNFM deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="vnfm-id">
+ <span class="json-property-name">vnfm-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Unique ID of VNFM.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="vim-id">
+ <span class="json-property-name">vim-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>indecate the VIM to deploy VNF.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="certificate-url">
+ <span class="json-property-name">certificate-url:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>certificate url of VNFM.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="esr-system-info-list">
+ <span class="json-property-name">esr-system-info-list:</span>
+ <span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-system-info-list">esr-system-info-list</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship-list">relationship-list</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-esr-vnfm-list" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/esr-vnfm-list"></a>esr-vnfm-list:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="esr-vnfm">
+ <span class="json-property-name">esr-vnfm:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-vnfm">esr-vnfm</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-evc" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/evc"></a>evc:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>evc object is an optional child object of the Configuration object.</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO configuration( evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="evc-id">
+ <span class="json-property-name">evc-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Unique/key field for the evc object</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="forwarding-path-topology">
+ <span class="json-property-name">forwarding-path-topology:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Point-to-Point, Multi-Point</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="cir-value">
+ <span class="json-property-name">cir-value:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Commited Information Rate</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="cir-units">
+ <span class="json-property-name">cir-units:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>CIR units</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="connection-diversity-group-id">
+ <span class="json-property-name">connection-diversity-group-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Diversity Group ID</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="service-hours">
+ <span class="json-property-name">service-hours:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>formerly Performance Group</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="esp-evc-circuit-id">
+ <span class="json-property-name">esp-evc-circuit-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>EVC Circuit ID of ESP EVC</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="esp-evc-cir-value">
+ <span class="json-property-name">esp-evc-cir-value:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Committed Information Rate (For ESP)</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="esp-evc-cir-units">
+ <span class="json-property-name">esp-evc-cir-units:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>CIR units (For ESP)</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="esp-itu-code">
+ <span class="json-property-name">esp-itu-code:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Identifies ESP</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="collector-pop-clli">
+ <span class="json-property-name">collector-pop-clli:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Collector POP CLLI (from the hostname of the access pnf)</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="inter-connect-type-ingress">
+ <span class="json-property-name">inter-connect-type-ingress:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Interconnect type on ingress side of EVC.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="tagmode-access-ingress">
+ <span class="json-property-name">tagmode-access-ingress:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>tagode for collector side of EVC</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="tagmode-access-egress">
+ <span class="json-property-name">tagmode-access-egress:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>tagMode for network side of EVC</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-evcs" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/evcs"></a>evcs:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="evc">
+ <span class="json-property-name">evc:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/evc">evc</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-external-system" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/external-system"></a>external-system:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Namespace for external system.</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="esr-ems-list">
+ <span class="json-property-name">esr-ems-list:</span>
+ <span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-ems-list">esr-ems-list</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ <dt data-property-name="esr-vnfm-list">
+ <span class="json-property-name">esr-vnfm-list:</span>
+ <span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-vnfm-list">esr-vnfm-list</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ <dt data-property-name="esr-thirdparty-sdnc-list">
+ <span class="json-property-name">esr-thirdparty-sdnc-list:</span>
+ <span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-thirdparty-sdnc-list">esr-thirdparty-sdnc-list</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-extra-properties" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/extra-properties"></a>extra-properties:
@@ -121932,12 +141531,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Openstack flavor.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_IF_ANY_IN_EDGES</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM cloud-region (is composed of flavor)</li>
-<li>FROM vserver</li></ul>
+<li>TO cloud-region( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM vserver( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)</li>
+<li>FLAVOR cannot be deleted if linked to VSERVER</li></ul>
</section>
@@ -122143,6 +141741,438 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-forwarder" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/forwarder"></a>forwarder:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Entity describing a sequenced segment of forwarding path</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO forwarding-path( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)</li>
+<li>TO l-interface( forwarder org.onap.relationships.inventory.ForwardsTo l-interface, MANY2ONE)</li>
+<li>TO configuration( forwarder org.onap.relationships.inventory.Uses configuration, ONE2ONE)</li>
+<li>TO lag-interface( forwarder org.onap.relationships.inventory.ForwardsTo lag-interface, MANY2ONE)</li>
+<li>TO p-interface( forwarder org.onap.relationships.inventory.ForwardsTo p-interface, MANY2ONE)</li>
+<li>FORWARDER deletion means associated objects of these types are also DELETED:CONFIGURATION</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="sequence">
+ <span class="json-property-name">sequence:</span>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Unique ID of this segmentation</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="forwarder-role">
+ <span class="json-property-name">forwarder-role:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>ingress, intermediate, egress</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-forwarder-evc" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/forwarder-evc"></a>forwarder-evc:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>forwarder object is an optional child object of the Configuration object.</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO configuration( forwarder-evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="forwarder-evc-id">
+ <span class="json-property-name">forwarder-evc-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Key for forwarder-evc object</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="circuit-id">
+ <span class="json-property-name">circuit-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Circuit ID from customer/ESP/ingress end of EVC, or reference to beater circuit on gateway/network/egress end of EVC</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="ivlan">
+ <span class="json-property-name">ivlan:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Internal VLAN.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="svlan">
+ <span class="json-property-name">svlan:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>SVLAN value for ingress of egress forwarder.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="cvlan">
+ <span class="json-property-name">cvlan:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>CVLAN value for ingress of egress forwarder.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-forwarder-evcs" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/forwarder-evcs"></a>forwarder-evcs:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="forwarder-evc">
+ <span class="json-property-name">forwarder-evc:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/forwarder-evc">forwarder-evc</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-forwarders" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/forwarders"></a>forwarders:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="forwarder">
+ <span class="json-property-name">forwarder:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/forwarder">forwarder</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-forwarding-path" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/forwarding-path"></a>forwarding-path:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Entity that describes the sequenced forwarding path between interfaces of services or resources</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO service-instance( forwarding-path org.onap.relationships.inventory.AppliesTo service-instance, MANY2ONE)</li>
+<li>TO configuration( forwarding-path org.onap.relationships.inventory.Uses configuration, ONE2ONE)</li>
+<li>FROM forwarder( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)</li>
+<li>FORWARDING-PATH is DELETED when these are DELETED FORWARDER</li>
+<li>FORWARDING-PATH deletion means associated objects of these types are also DELETED:CONFIGURATION</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="forwarding-path-id">
+ <span class="json-property-name">forwarding-path-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Unique ID of this FP</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="forwarding-path-name">
+ <span class="json-property-name">forwarding-path-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Name of the FP</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="selflink">
+ <span class="json-property-name">selflink:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>the self link for this FP</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ <dt data-property-name="forwarders">
+ <span class="json-property-name">forwarders:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/forwarder">forwarder</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-forwarding-paths" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/forwarding-paths"></a>forwarding-paths:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="forwarding-path">
+ <span class="json-property-name">forwarding-path:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/forwarding-path">forwarding-path</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-generic-vnf" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/generic-vnf"></a>generic-vnf:
@@ -122155,27 +142185,26 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>General purpose VNF</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO license-key-resource (Many2Many)</li>
-<li>TO l-interface (comprises generic-vnf, Many2Many)</li>
-<li>TO availability-zone (Many2Many)</li>
-<li>TO lag-interface (comprises generic-vnf, Many2Many)</li>
-<li>TO l3-network (Many2Many)</li>
-<li>TO pserver (Many2Many)</li>
-<li>TO vnf-image (Many2One)</li>
-<li>TO vserver (One2Many)</li>
-<li>TO service-instance (Many2Many)</li>
-<li>TO site-pair-set (Many2Many)</li>
-<li>TO network-profile (Many2Many)</li>
-<li>TO ipsec-configuration (Many2One)</li>
-<li>TO vf-module (comprises generic-vnf, One2Many)</li>
-<li>TO volume-group (One2Many)</li>
-<li>TO vnfc (One2Many)</li>
-<li>FROM virtual-data-center</li>
-<li>FROM logical-link</li></ul>
+<li>TO availability-zone( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)</li>
+<li>TO ipsec-configuration( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)</li>
+<li>TO l3-network( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>TO license-key-resource( generic-vnf org.onap.relationships.inventory.Uses license-key-resource, MANY2MANY)</li>
+<li>TO pserver( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)</li>
+<li>TO vnf-image( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)</li>
+<li>TO volume-group( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)</li>
+<li>TO vserver( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)</li>
+<li>TO virtual-data-center( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)</li>
+<li>FROM vnfc( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>FROM lag-interface( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>FROM network-profile( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)</li>
+<li>FROM site-pair-set( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)</li>
+<li>FROM vf-module( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)</li>
+<li>GENERIC-VNF is DELETED when these are DELETED VNFC,LAG-INTERFACE,L-INTERFACE,VF-MODULE</li></ul>
</section>
@@ -122753,13 +142782,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Openstack group-assignment used to store exclusivity groups (EG).</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO tenant (Many2Many)</li>
-<li>TO pserver (One2Many)</li>
-<li>FROM cloud-region (is composed of group-assignment)</li></ul>
+<li>TO cloud-region( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM pserver( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)</li>
+<li>FROM tenant( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)</li></ul>
</section>
@@ -122893,6 +142920,149 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-host-route" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/host-route"></a>host-route:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO subnet( host-route org.onap.relationships.inventory.BelongsTo subnet, MANY2ONE)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="host-route-id">
+ <span class="json-property-name">host-route-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>host-route id</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="route-prefix">
+ <span class="json-property-name">route-prefix:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>subnet prefix</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="next-hop">
+ <span class="json-property-name">next-hop:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Could be ip-address, hostname, or service-instance</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="next-hop-type">
+ <span class="json-property-name">next-hop-type:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Should be ip-address, hostname, or service-instance to match next-hop</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-host-routes" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/host-routes"></a>host-routes:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="host-route">
+ <span class="json-property-name">host-route:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/host-route">host-route</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-image" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/image"></a>image:
@@ -122905,13 +143075,13 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Openstack image.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_4_IN_EDGES_OR_CASCADE</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO metadatum (comprises image, Many2Many)</li>
-<li>FROM cloud-region (is composed of image)</li>
-<li>FROM vserver</li></ul>
+<li>TO cloud-region( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)</li>
+<li>FROM vserver( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)</li>
+<li>IMAGE cannot be deleted if linked to VSERVER</li>
+<li>IMAGE is DELETED when these are DELETED METADATUM</li></ul>
</section>
@@ -123217,6 +143387,158 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-instance-group" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/instance-group"></a>instance-group:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>General mechanism for grouping instances</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO model( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY)</li>
+<li>FROM allotted-resource( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>FROM pnf( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="id">
+ <span class="json-property-name">id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Instance Group ID, UUID assigned to this instance.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="description">
+ <span class="json-property-name">description:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Descriptive text to help identify the usage of this instance-group</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="type">
+ <span class="json-property-name">type:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Only valid value today is lower case ha for high availability</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="sub-type">
+ <span class="json-property-name">sub-type:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Valid values for ha type are [geo-activeactive, geo-activestandby, local-activeactive, local-activestandby]</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Concurrency value</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-instance-groups" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/instance-groups"></a>instance-groups:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Collection of openstack route table references</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="instance-group">
+ <span class="json-property-name">instance-group:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/instance-group">instance-group</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-inventory" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/inventory"></a>inventory:
@@ -123619,8 +143941,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>IPSec configuration node will contain various configuration data for the NMTE VNF. This node will have an edge to the generic-vnf (vnf type = TE). Starting 1607, this data will be populated by SDN-C</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO vig-server (comprises ipsec-configuration, One2Many)</li>
-<li>FROM generic-vnf</li></ul>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)</li>
+<li>FROM vig-server( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)</li>
+<li>IPSEC-CONFIGURATION is DELETED when these are DELETED VIG-SERVER</li></ul>
</section>
@@ -124023,20 +144346,20 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Logical interfaces, e.g., a vnic.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO l3-interface-ipv4-address-list (comprises l-interface, Many2Many)</li>
-<li>TO l3-interface-ipv6-address-list (comprises l-interface, Many2Many)</li>
-<li>TO logical-link (Many2Many)</li>
-<li>TO vlan (comprises l-interface, Many2Many)</li>
-<li>TO sriov-vf (comprises l-interface, One2One)</li>
-<li>FROM generic-vnf (is composed of l-interface)</li>
-<li>FROM lag-interface (is composed of l-interface)</li>
-<li>FROM newvce (is composed of l-interface)</li>
-<li>FROM p-interface (is composed of l-interface)</li>
-<li>FROM vserver (is composed of l-interface)</li></ul>
+<li>TO generic-vnf( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>TO lag-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)</li>
+<li>TO logical-link( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)</li>
+<li>TO newvce( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)</li>
+<li>TO p-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)</li>
+<li>TO vserver( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)</li>
+<li>FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)</li>
+<li>FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)</li>
+<li>FROM sriov-vf( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)</li>
+<li>FROM vlan( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)</li>
+<li>L-INTERFACE is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST,SRIOV-VF,VLAN</li>
+<li>L-INTERFACE deletion means associated objects of these types are also DELETED:LOGICAL-LINK</li></ul>
</section>
@@ -124308,14 +144631,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>IPv4 Address Range</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO l3-network (Many2Many)</li>
-<li>TO subnet (Many2Many)</li>
-<li>FROM l-interface (is composed of l3-interface-ipv4-address-list)</li>
-<li>FROM vlan (is composed of l3-interface-ipv4-address-list)</li></ul>
+<li>TO l3-network( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)</li>
+<li>TO subnet( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)</li>
+<li>TO l-interface( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)</li>
+<li>TO vlan( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)</li></ul>
</section>
@@ -124454,14 +144775,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>IPv6 Address Range</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO l3-network (Many2Many)</li>
-<li>TO subnet (Many2Many)</li>
-<li>FROM l-interface (is composed of l3-interface-ipv6-address-list)</li>
-<li>FROM vlan (is composed of l3-interface-ipv6-address-list)</li></ul>
+<li>TO l3-network( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)</li>
+<li>TO subnet( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)</li>
+<li>TO l-interface( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)</li>
+<li>TO vlan( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)</li></ul>
</section>
@@ -124600,24 +144919,23 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Generic network definition</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO vpn-binding (Many2Many)</li>
-<li>TO subnet (comprises l3-network, Many2Many)</li>
-<li>TO service-instance (Many2Many)</li>
-<li>TO ctag-assignment (comprises l3-network, Many2Many)</li>
-<li>TO network-policy (Many2Many)</li>
-<li>TO segmentation-assignment (comprises l3-network, One2Many)</li>
-<li>TO route-table-reference (Many2Many)</li>
-<li>FROM cloud-region</li>
-<li>FROM complex</li>
-<li>FROM generic-vnf</li>
-<li>FROM l3-interface-ipv4-address-list</li>
-<li>FROM l3-interface-ipv6-address-list</li>
-<li>FROM tenant</li>
-<li>FROM vf-module</li></ul>
+<li>TO network-policy( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)</li>
+<li>TO route-table-reference( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)</li>
+<li>TO vpn-binding( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)</li>
+<li>FROM cloud-region( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>FROM complex( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)</li>
+<li>FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)</li>
+<li>FROM ctag-assignment( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)</li>
+<li>FROM segmentation-assignment( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)</li>
+<li>FROM subnet( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)</li>
+<li>FROM tenant( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>FROM vf-module( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)</li>
+<li>L3-NETWORK is DELETED when these are DELETED CTAG-ASSIGNMENT,SEGMENTATION-ASSIGNMENT,SUBNET</li></ul>
</section>
@@ -125034,17 +145352,17 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Link aggregate interface</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO lag-link (Many2Many)</li>
-<li>TO p-interface (Many2Many)</li>
-<li>TO l-interface (comprises lag-interface, Many2Many)</li>
-<li>FROM generic-vnf (is composed of lag-interface)</li>
-<li>FROM pserver (is composed of lag-interface)</li>
-<li>FROM pnf (is composed of lag-interface)</li>
-<li>FROM vpls-pe (is composed of lag-interface)</li></ul>
+<li>TO generic-vnf( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>TO lag-link( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)</li>
+<li>TO p-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)</li>
+<li>TO pnf( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)</li>
+<li>TO pserver( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)</li>
+<li>TO vpls-pe( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)</li>
+<li>FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)</li>
+<li>LAG-INTERFACE is DELETED when these are DELETED L-INTERFACE</li>
+<li>LAG-INTERFACE deletion means associated objects of these types are also DELETED:LAG-LINK</li></ul>
</section>
@@ -125198,8 +145516,8 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>LAG links can connect lag-interfaces</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM lag-interface</li>
-<li>FROM logical-link</li></ul>
+<li>FROM lag-interface( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)</li>
+<li>FROM logical-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)</li></ul>
</section>
@@ -125295,6 +145613,240 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-license" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/license"></a>license:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Metadata for license group.</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO generic-vnf( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>TO vce( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="group-uuid">
+ <span class="json-property-name">group-uuid:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Unique ID for the license group the resource belongs to, should be uuid.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-uuid">
+ <span class="json-property-name">resource-uuid:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Unique ID of a license resource.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Concurrency value</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-licenses" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/licenses"></a>licenses:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Licenses to be allocated across resources, keyed by group-uuid and resource-uuid, related to license management</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="license">
+ <span class="json-property-name">license:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/license">license</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-line-of-business" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/line-of-business"></a>line-of-business:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>describes a line-of-business</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO generic-vnf( line-of-business org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="line-of-business-name">
+ <span class="json-property-name">line-of-business-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Name of the line-of-business (product)</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-lines-of-business" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/lines-of-business"></a>lines-of-business:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Collection of lines-of-business</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="line-of-business">
+ <span class="json-property-name">line-of-business:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/line-of-business">line-of-business</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-logical-link" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/logical-link"></a>logical-link:
@@ -125307,21 +145859,19 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Logical links generally connect l-interfaces but are used to express logical connectivity between two points</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO lag-link (Many2Many)</li>
-<li>TO pnf (Many2Many)</li>
-<li>TO logical-link (One2Many)</li>
-<li>TO generic-vnf (Many2Many)</li>
-<li>TO pserver (Many2Many)</li>
-<li>FROM l-interface</li>
-<li>FROM p-interface</li>
-<li>FROM service-instance</li>
-<li>FROM virtual-data-center</li>
-<li>FROM vlan</li>
-<li>FROM logical-link</li></ul>
+<li>TO generic-vnf( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)</li>
+<li>TO lag-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)</li>
+<li>TO logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, ONE2MANY)</li>
+<li>TO pnf( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)</li>
+<li>TO pserver( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)</li>
+<li>TO virtual-data-center( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)</li>
+<li>FROM l-interface( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)</li>
+<li>FROM p-interface( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)</li>
+<li>FROM vlan( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)</li>
+<li>FROM logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, ONE2MANY)</li></ul>
</section>
@@ -125598,8 +146148,6 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Collection of metadatum (key/value pairs)</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
</section>
@@ -125641,14 +146189,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Key/value pairs</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM image (is composed of metadatum)</li>
-<li>FROM model (is composed of metadatum)</li>
-<li>FROM service-instance (is composed of metadatum)</li>
-<li>FROM connector (is composed of metadatum)</li></ul>
+<li>TO connector( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)</li>
+<li>TO image( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)</li>
+<li>TO service-instance( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)</li>
+<li>TO model( metadatum org.onap.relationships.inventory.BelongsTo model, MANY2ONE)</li></ul>
</section>
@@ -125706,16 +146252,17 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Subgraph definition provided by ASDC to describe an inventory asset and its connections related to ASDC models</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_4_IN_EDGES_OR_CASCADE</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO model (Many2One)</li>
-<li>TO model-element (comprises model, One2Many)</li>
-<li>TO metadatum (comprises model, One2Many)</li>
-<li>FROM model-element</li>
-<li>FROM named-query</li>
-<li>FROM named-query-element</li></ul>
+<li>TO model( model-element isA model, MANY2ONE)</li>
+<li>TO model-element (CHILD of model, model startsWith model-element, ONE2MANY)</li>
+<li>FROM named-query( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)</li>
+<li>FROM named-query-element( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)</li>
+<li>FROM model-element( model-element isA model, MANY2ONE)</li>
+<li>FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo model, MANY2ONE)</li>
+<li>MODEL cannot be deleted if linked to NAMED-QUERY,NAMED-QUERY-ELEMENT</li>
+<li>MODEL is DELETED when these are DELETED METADATUM</li>
+<li>MODEL deletion means associated objects of these types are also DELETED:MODEL-ELEMENT</li></ul>
</section>
@@ -125960,8 +146507,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>This is how we would capture constraints defining allowed sets of elements.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO constrained-element-set (comprises model-constraint, One2Many)</li>
-<li>FROM model-element (is composed of model-constraint)</li></ul>
+<li>TO model-element( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)</li>
+<li>FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)</li>
+<li>MODEL-CONSTRAINT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET</li></ul>
</section>
@@ -126064,17 +146612,16 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Defines how other models combine to make up a higher-level model.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO model (Many2One)</li>
-<li>TO model-element (comprises model-element, One2Many)</li>
-<li>TO model-constraint (comprises model-element, One2Many)</li>
-<li>TO constrained-element-set (comprises model-element, One2Many)</li>
-<li>FROM model (is composed of model-element)</li>
-<li>FROM element-choice-set (is composed of model-element)</li>
-<li>FROM model-element (is composed of model-element)</li></ul>
+<li>TO element-choice-set( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)</li>
+<li>TO model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)</li>
+<li>TO model( model-element isA model, MANY2ONE)</li>
+<li>FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)</li>
+<li>FROM model-constraint( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)</li>
+<li>FROM model (PARENT of model-element, model startsWith model-element)</li>
+<li>FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)</li>
+<li>MODEL-ELEMENT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET,MODEL-CONSTRAINT</li></ul>
</section>
@@ -126242,6 +146789,195 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-model-ver" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/model-ver"></a>model-ver:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Subgraph definition provided by ASDC to describe a specific version of an inventory asset and its connections related to ASDC models</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)</li>
+<li>FROM model-element( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE)</li>
+<li>FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)</li>
+<li>FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)</li>
+<li>MODEL-VER cannot be deleted if linked to MODEL-ELEMENT</li>
+<li>MODEL-VER is DELETED when these are DELETED MODEL-ELEMENT,METADATUM</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="model-version-id">
+ <span class="json-property-name">model-version-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Unique identifier corresponding to one version of a model in ASDC</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="model-name">
+ <span class="json-property-name">model-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Name of the model, which can change from version to version.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="model-version">
+ <span class="json-property-name">model-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Version</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="model-description">
+ <span class="json-property-name">model-description:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Description</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="model-elements">
+ <span class="json-property-name">model-elements:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/model-element">model-element</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ <dt data-property-name="metadata">
+ <span class="json-property-name">metadata:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/metadatum">metadatum</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-model-vers" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/model-vers"></a>model-vers:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="model-ver">
+ <span class="json-property-name">model-ver:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/model-ver">model-ver</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-models" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/models"></a>models:
@@ -126296,7 +147032,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<section class="json-schema-description">
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM vlan</li></ul>
+<li>FROM vlan( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)</li></ul>
</section>
@@ -126467,12 +147203,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>TBD</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO model (One2Many)</li>
-<li>TO named-query-element (comprises named-query, One2One)</li></ul>
+<li>TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)</li>
+<li>TO model( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)</li>
+<li>FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)</li>
+<li>NAMED-QUERY is DELETED when these are DELETED NAMED-QUERY-ELEMENT</li></ul>
</section>
@@ -126603,16 +147339,15 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>TBD</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO named-query-element (comprises named-query-element, Many2Many)</li>
-<li>TO model (Many2One)</li>
-<li>TO property-constraint (comprises named-query-element, One2Many)</li>
-<li>TO related-lookup (comprises named-query-element, One2Many)</li>
-<li>FROM named-query (is composed of named-query-element)</li>
-<li>FROM named-query-element (is composed of named-query-element)</li></ul>
+<li>TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)</li>
+<li>TO model( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)</li>
+<li>TO named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)</li>
+<li>FROM property-constraint( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)</li>
+<li>FROM related-lookup( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)</li>
+<li>FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)</li>
+<li>NAMED-QUERY-ELEMENT is DELETED when these are DELETED PROPERTY-CONSTRAINT,RELATED-LOOKUP</li></ul>
</section>
@@ -127186,7 +147921,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<section class="json-schema-description">
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM l3-network</li></ul>
+<li>FROM l3-network( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)</li></ul>
</section>
@@ -127279,7 +148014,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Network profile populated by SDN-GP for SNMP</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM generic-vnf</li></ul>
+<li>TO generic-vnf( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)</li></ul>
</section>
@@ -127401,7 +148136,8 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO l-interface (comprises newvce, Many2Many)</li></ul>
+<li>FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)</li>
+<li>NEWVCE is DELETED when these are DELETED L-INTERFACE</li></ul>
</section>
@@ -127967,9 +148703,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>OAM network, to be deprecated shortly. Do not use for new purposes.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO complex (Many2Many)</li>
-<li>TO service-capability (Many2Many)</li>
-<li>FROM cloud-region (is composed of oam-network)</li></ul>
+<li>TO cloud-region( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>TO complex( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)</li>
+<li>TO service-capability( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)</li></ul>
</section>
@@ -128115,6 +148851,468 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-operational-environment" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/operational-environment"></a>operational-environment:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>It is a logical partition of the cloud which allows to have multiple environments in the production AIC.</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)</li>
+<li>FROM operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="operational-environment-id">
+ <span class="json-property-name">operational-environment-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>UUID of an operational environment</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="operational-environment-name">
+ <span class="json-property-name">operational-environment-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Operational Environment name</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="operational-environment-type">
+ <span class="json-property-name">operational-environment-type:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Operational Environment Type.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="operational-environment-status">
+ <span class="json-property-name">operational-environment-status:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Status</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="tenant-context">
+ <span class="json-property-name">tenant-context:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Tenant Context.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="workload-context">
+ <span class="json-property-name">workload-context:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Workload Context.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-operational-environments" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/operational-environments"></a>operational-environments:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>a logical partition of the cloud which allows to have multiple environments in the production AIC.</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="operational-environment">
+ <span class="json-property-name">operational-environment:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/operational-environment">operational-environment</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-overloaded-model" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/overloaded-model"></a>overloaded-model:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Allows for legacy POST of old-style and new-style models</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="model-invariant-id">
+ <span class="json-property-name">model-invariant-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Unique identifier corresponding to the main definition of a model in ASDC</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="model-name-version-id">
+ <span class="json-property-name">model-name-version-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Unique identifier corresponding to one version of a model in ASDC</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="model-type">
+ <span class="json-property-name">model-type:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Type of the model, e.g., service, resource, widget, etc.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="model-name">
+ <span class="json-property-name">model-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Name of the model, which can change from version to version.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="model-id">
+ <span class="json-property-name">model-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Invariant unique ID which does not change from version to version</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="model-version">
+ <span class="json-property-name">model-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Version</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="model-description">
+ <span class="json-property-name">model-description:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Description</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="model-vers">
+ <span class="json-property-name">model-vers:</span>
+ <span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/model-vers">model-vers</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship-list">relationship-list</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-owning-entities" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/owning-entities"></a>owning-entities:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Collection of owning-entities</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="owning-entity">
+ <span class="json-property-name">owning-entity:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/owning-entity">owning-entity</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-owning-entity" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/owning-entity"></a>owning-entity:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>describes an owning-entity</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo owning-entity, MANY2ONE)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="owning-entity-id">
+ <span class="json-property-name">owning-entity-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>UUID of an owning entity</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="owning-entity-name">
+ <span class="json-property-name">owning-entity-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Owning entity name</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-p-interface" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/p-interface"></a>p-interface:
@@ -128127,17 +149325,17 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Physical interface (e.g., nic)</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO l-interface (comprises p-interface, Many2Many)</li>
-<li>TO physical-link (Many2Many)</li>
-<li>TO logical-link (Many2One)</li>
-<li>FROM lag-interface</li>
-<li>FROM pserver (is composed of p-interface)</li>
-<li>FROM pnf (is composed of p-interface)</li>
-<li>FROM vpls-pe (is composed of p-interface)</li></ul>
+<li>TO logical-link( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)</li>
+<li>TO physical-link( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)</li>
+<li>TO pnf( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)</li>
+<li>TO pserver( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)</li>
+<li>TO vpls-pe( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)</li>
+<li>FROM lag-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)</li>
+<li>FROM l-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)</li>
+<li>P-INTERFACE is DELETED when these are DELETED L-INTERFACE</li>
+<li>P-INTERFACE deletion means associated objects of these types are also DELETED:PHYSICAL-LINK</li></ul>
</section>
@@ -128337,11 +149535,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Collection of physical connections, typically between p-interfaces</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM p-interface</li></ul>
+<li>FROM p-interface( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)</li></ul>
</section>
@@ -128509,6 +149705,116 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-platform" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/platform"></a>platform:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>describes a platform</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO generic-vnf( platform org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="platform-name">
+ <span class="json-property-name">platform-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Name of the platform</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-platforms" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/platforms"></a>platforms:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Collection of platforms</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="platform">
+ <span class="json-property-name">platform:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/platform">platform</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-pnf" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/pnf"></a>pnf:
@@ -128521,14 +149827,13 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>PNF represents a physical network function. typically equipment used in the D1 world.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO p-interface (comprises pnf, Many2Many)</li>
-<li>TO lag-interface (comprises pnf, One2Many)</li>
-<li>TO complex (Many2One)</li>
-<li>FROM logical-link</li></ul>
+<li>TO complex( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)</li>
+<li>FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)</li>
+<li>FROM p-interface( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)</li>
+<li>PNF is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE</li></ul>
</section>
@@ -128822,8 +150127,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Used to capture the network interfaces of this VCE</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO cvlan-tag (comprises port-group, Many2Many)</li>
-<li>FROM vce (is composed of port-group)</li></ul>
+<li>TO vce( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)</li>
+<li>FROM cvlan-tag( cvlan-tag org.onap.relationships.inventory.BelongsTo port-group, MANY2ONE)</li>
+<li>PORT-GROUP is DELETED when these are DELETED CVLAN-TAG</li></ul>
</section>
@@ -129044,6 +150350,116 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-project" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/project"></a>project:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>describes the project</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO service-instance( project org.onap.relationships.inventory.Uses service-instance, ONE2MANY)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="project-name">
+ <span class="json-property-name">project-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Name of the project deploying a service</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-projects" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/projects"></a>projects:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Collection of projects</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="project">
+ <span class="json-property-name">project:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/project">project</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-properties" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/properties"></a>properties:
@@ -129101,7 +150517,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>TBD</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM named-query-element (is composed of property-constraint)</li></ul>
+<li>TO named-query-element( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)</li></ul>
</section>
@@ -129219,19 +150635,20 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Compute host whose hostname must be unique and must exactly match what is sent as a relationship to a vserver.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_4_IN_EDGES_OR_CASCADE</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO complex (Many2One)</li>
-<li>TO cloud-region (Many2One)</li>
-<li>TO availability-zone (Many2One)</li>
-<li>TO lag-interface (comprises pserver, Many2Many)</li>
-<li>TO p-interface (comprises pserver, Many2Many)</li>
-<li>FROM generic-vnf</li>
-<li>FROM group-assignment</li>
-<li>FROM vserver</li>
-<li>FROM logical-link</li></ul>
+<li>TO group-assignment( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)</li>
+<li>TO availability-zone( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)</li>
+<li>TO cloud-region( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)</li>
+<li>TO complex( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM generic-vnf( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)</li>
+<li>FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)</li>
+<li>FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)</li>
+<li>FROM p-interface( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)</li>
+<li>FROM vserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)</li>
+<li>PSERVER cannot be deleted if linked to GENERIC-VNF,LOGICAL-LINK,VSERVER</li>
+<li>PSERVER is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE</li>
+<li>PSERVER cannot be deleted if linked to GROUP-ASSIGNMENT</li></ul>
</section>
@@ -129634,7 +151051,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>TBD</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM named-query-element (is composed of related-lookup)</li></ul>
+<li>TO named-query-element( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)</li></ul>
</section>
@@ -129881,26 +151298,6 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</section> </div>
</dd>
- <dt data-property-name="related-to-property">
- <span class="json-property-name">related-to-property:</span>
- <span class="json-property-type">object[]</span>
- <span class="json-property-range" title="Value limits"></span>
-
- </dt>
- <dd>
-
- <div class="json-inner-schema">
-
- <section class="json-schema-array-items">
- <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/related-to-property">related-to-property</a>
- </span>
- <span class="json-property-range" title="Value limits"></span>
-
- <div class="json-inner-schema">
-
- </div>
- </section> </div>
- </dd>
</dl>
</section>
</div>
@@ -130168,7 +151565,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Openstack route table reference.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM l3-network</li></ul>
+<li>FROM l3-network( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)</li></ul>
</section>
@@ -130277,6 +151674,129 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-route-target" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/route-target"></a>route-target:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Route target information</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO vpn-binding( route-target org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2ONE)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="global-route-target">
+ <span class="json-property-name">global-route-target:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Number used to identify an RT, globally unique in the network</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="route-target-role">
+ <span class="json-property-name">route-target-role:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Role assigned to this route target</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-route-targets" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/route-targets"></a>route-targets:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Collection of route target information</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="route-target">
+ <span class="json-property-name">route-target:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/route-target">route-target</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-routing-instance" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/routing-instance"></a>routing-instance:
@@ -130290,8 +151810,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<section class="json-schema-description">
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO site-pair (comprises routing-instance, Many2Many)</li>
-<li>FROM site-pair-set (is composed of routing-instance)</li></ul>
+<li>TO site-pair-set( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)</li>
+<li>FROM site-pair( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)</li>
+<li>ROUTING-INSTANCE is DELETED when these are DELETED SITE-PAIR</li></ul>
</section>
@@ -130610,6 +152131,27 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-secondary-filt" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/secondary-filt"></a>secondary-filt:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>SecondaryFilt for performing a named-query or model query</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-secondary-filter" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/secondary-filter"></a>secondary-filter:
@@ -130660,6 +152202,47 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-secondary-filts" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/secondary-filts"></a>secondary-filts:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>SecondaryFilts for performing a named-query or model query</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="secondary-filt">
+ <span class="json-property-name">secondary-filt:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/secondary-filt">secondary-filt</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-segmentation-assignment" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/segmentation-assignment"></a>segmentation-assignment:
@@ -130672,11 +152255,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Openstack segmentation assignment.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM l3-network (is composed of segmentation-assignment)</li></ul>
+<li>TO l3-network( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)</li></ul>
</section>
@@ -130784,8 +152365,6 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Stand-in for service model definitions. Likely to be deprecated in favor of models from ASDC.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_IF_ANY_IN_EDGES</p>
</section>
@@ -130932,8 +152511,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Early definition of server/resource pairings, likely to be replaced by models. No new use should be made of this.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM availability-zone</li>
-<li>FROM oam-network</li></ul>
+<li>FROM availability-zone( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)</li>
+<li>FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)</li>
+<li>SERVICE-CAPABILITY cannot be deleted if linked to AVAILABILITY-ZONE,OAM-NETWORK</li></ul>
</section>
@@ -131134,21 +152714,21 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Instance of a service</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO cvlan-tag (Many2Many)</li>
-<li>TO connector (Many2Many)</li>
-<li>TO metadatum (comprises service-instance, Many2Many)</li>
-<li>TO logical-link (Many2Many)</li>
-<li>TO vlan (One2Many)</li>
-<li>TO service-instance (One2Many)</li>
-<li>FROM generic-vnf</li>
-<li>FROM l3-network</li>
-<li>FROM service-subscription (is composed of service-instance)</li>
-<li>FROM vce</li>
-<li>FROM service-instance</li></ul>
+<li>TO generic-vnf( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)</li>
+<li>TO l3-network( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)</li>
+<li>TO connector( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)</li>
+<li>TO cvlan-tag( service-instance org.onap.relationships.inventory.ComposedOf cvlan-tag, MANY2MANY)</li>
+<li>TO logical-link( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)</li>
+<li>TO service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)</li>
+<li>TO vlan( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)</li>
+<li>TO service-subscription( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)</li>
+<li>TO vce( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)</li>
+<li>FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)</li>
+<li>SERVICE-INSTANCE is DELETED when these are DELETED METADATUM</li>
+<li>SERVICE-INSTANCE deletion means associated objects of these types are also DELETED:LOGICAL-LINK</li></ul>
</section>
@@ -131432,13 +153012,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Object that group service instances.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO service-instance (comprises service-subscription, Many2Many)</li>
-<li>FROM customer (is composed of service-subscription)</li>
-<li>FROM tenant</li></ul>
+<li>TO customer( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)</li>
+<li>TO tenant( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)</li>
+<li>SERVICE-SUBSCRIPTION is DELETED when these are DELETED SERVICE-INSTANCE</li></ul>
</section>
@@ -131620,8 +153199,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<section class="json-schema-description">
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO class-of-service (comprises site-pair, Many2Many)</li>
-<li>FROM routing-instance (is composed of site-pair)</li></ul>
+<li>TO routing-instance( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)</li>
+<li>FROM class-of-service( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)</li>
+<li>SITE-PAIR is DELETED when these are DELETED CLASS-OF-SERVICE</li></ul>
</section>
@@ -131770,8 +153350,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Set of instances for probes used to measure service level agreements</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO routing-instance (comprises site-pair-set, Many2Many)</li>
-<li>FROM generic-vnf</li></ul>
+<li>TO generic-vnf( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)</li>
+<li>FROM routing-instance( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)</li>
+<li>SITE-PAIR-SET is DELETED when these are DELETED ROUTING-INSTANCE</li></ul>
</section>
@@ -131940,12 +153521,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Openstack snapshot</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM cloud-region (is composed of snapshot)</li>
-<li>FROM vserver</li></ul>
+<li>TO cloud-region( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM vserver( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)</li></ul>
</section>
@@ -132149,6 +153728,117 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-sriov-pf" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/sriov-pf"></a>sriov-pf:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>SR-IOV Physical Function</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO p-interface( sriov-pf org.onap.relationships.inventory.BelongsTo p-interface, ONE2ONE)</li>
+<li>FROM sriov-vf( sriov-vf org.onap.relationships.inventory.Uses sriov-pf, MANY2ONE)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="pf-pci-id">
+ <span class="json-property-name">pf-pci-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Identifier for the sriov-pf</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-sriov-pfs" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/sriov-pfs"></a>sriov-pfs:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Collection of SR-IOV Physical Functions.</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="sriov-pf">
+ <span class="json-property-name">sriov-pf:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/sriov-pf">sriov-pf</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-sriov-vf" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/sriov-vf"></a>sriov-vf:
@@ -132163,7 +153853,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>SR-IOV Virtual Function (not to be confused with virtual network function)</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM l-interface (is composed of sriov-vf)</li></ul>
+<li>TO l-interface( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)</li></ul>
</section>
@@ -132453,13 +154143,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<div class="panel-body">
<section class="json-schema-description">
- <h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_IF_ANY_IN_EDGES</p>
-<h6 id="related-nodes">Related Nodes</h6>
+ <h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM l3-interface-ipv4-address-list</li>
-<li>FROM l3-interface-ipv6-address-list</li>
-<li>FROM l3-network (is composed of subnet)</li></ul>
+<li>TO l3-network( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)</li>
+<li>FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)</li>
+<li>FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)</li>
+<li>SUBNET cannot be deleted if linked to L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST</li></ul>
</section>
@@ -132720,16 +154409,15 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Openstack tenant</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO l3-network (Many2Many)</li>
-<li>TO service-subscription (Many2Many)</li>
-<li>TO vserver (comprises tenant, One2Many)</li>
-<li>FROM cloud-region (is composed of tenant)</li>
-<li>FROM group-assignment</li>
-<li>FROM volume-group</li></ul>
+<li>TO cloud-region( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>TO group-assignment( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)</li>
+<li>TO l3-network( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>TO volume-group( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)</li>
+<li>FROM service-subscription( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)</li>
+<li>FROM vserver( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)</li>
+<li>TENANT cannot be deleted if linked to VSERVER</li></ul>
</section>
@@ -132858,6 +154546,168 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-tunnel-xconnect" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/tunnel-xconnect"></a>tunnel-xconnect:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Represents the specifics of a tunnel cross connect piece of a resource that gets separately allotted</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO allotted-resource( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="id">
+ <span class="json-property-name">id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Allotted Resource id UUID assigned to this instance.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="bandwidth-up-wan1">
+ <span class="json-property-name">bandwidth-up-wan1:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>The WAN uplink bandwidth for WAN1</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="bandwidth-down-wan1">
+ <span class="json-property-name">bandwidth-down-wan1:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>The WAN downlink bandwidth for WAN1</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="bandwidth-up-wan2">
+ <span class="json-property-name">bandwidth-up-wan2:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>The WAN uplink bandwidth for WAN2</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="bandwidth-down-wan2">
+ <span class="json-property-name">bandwidth-down-wan2:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>The WAN downlink bandwidth for WAN2</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Concurrency value</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-tunnel-xconnects" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/tunnel-xconnects"></a>tunnel-xconnects:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>This object is used to store the specific tunnel cross connect aspects of an allotted resource</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="tunnel-xconnect">
+ <span class="json-property-name">tunnel-xconnect:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/tunnel-xconnect">tunnel-xconnect</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-update" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/update"></a>update:
@@ -132995,11 +154845,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Virtual Customer Edge Router, used specifically for Gamma. This object is deprecated.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO availability-zone (Many2Many)</li>
-<li>TO complex (Many2Many)</li>
-<li>TO port-group (comprises vce, Many2Many)</li>
-<li>TO vserver (Many2Many)</li>
-<li>TO service-instance (Many2Many)</li></ul>
+<li>TO availability-zone( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)</li>
+<li>TO complex( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)</li>
+<li>TO vserver( vce tosca.relationships.HostedOn vserver, ONE2MANY)</li>
+<li>FROM port-group( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)</li>
+<li>VCE is DELETED when these are DELETED PORT-GROUP</li></ul>
</section>
@@ -133333,15 +155184,14 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>a deployment unit of VNFCs</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO volume-group (One2One)</li>
-<li>TO l3-network (Many2Many)</li>
-<li>TO vnfc (One2Many)</li>
-<li>FROM vserver</li>
-<li>FROM generic-vnf (is composed of vf-module)</li></ul>
+<li>TO generic-vnf( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>TO l3-network( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)</li>
+<li>TO vnfc( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)</li>
+<li>TO volume-group( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)</li>
+<li>TO vserver( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)</li>
+<li>VF-MODULE cannot be deleted if linked to VNFC</li></ul>
</section>
@@ -133571,7 +155421,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>vig-server contains information about a vig server used for IPSec-configuration. Populated by SDN-C from 1607</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM ipsec-configuration (is composed of vig-server)</li></ul>
+<li>TO ipsec-configuration( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)</li></ul>
</section>
@@ -133687,6 +155537,294 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-vip-ipv4-address-list" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/vip-ipv4-address-list"></a>vip-ipv4-address-list:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>IPv4 Address Range</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO cloud-region( vip-ipv4-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>TO instance-group( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>TO subnet( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)</li>
+<li>FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv4-address-list, MANY2MANY)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="vip-ipv4-address">
+ <span class="json-property-name">vip-ipv4-address:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>IP address</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="vip-ipv4-prefix-length">
+ <span class="json-property-name">vip-ipv4-prefix-length:</span>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Prefix length, 32 for single address</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="vlan-id-inner">
+ <span class="json-property-name">vlan-id-inner:</span>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Inner VLAN tag</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="vlan-id-outer">
+ <span class="json-property-name">vlan-id-outer:</span>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Outer VLAN tag</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="is-floating">
+ <span class="json-property-name">is-floating:</span>
+ <span class="json-property-type">boolean</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Indicator of fixed or floating address</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="neutron-network-id">
+ <span class="json-property-name">neutron-network-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Neutron network id of the interface that address belongs to</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="neutron-subnet-id">
+ <span class="json-property-name">neutron-subnet-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Neutron id of subnet that address belongs to</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-vip-ipv6-address-list" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/vip-ipv6-address-list"></a>vip-ipv6-address-list:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>IPv6 Address Range</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO cloud-region( vip-ipv6-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>TO instance-group( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>TO subnet( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)</li>
+<li>FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv6-address-list, MANY2MANY)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="vip-ipv6-address">
+ <span class="json-property-name">vip-ipv6-address:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>IP address</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="vip-ipv6-prefix-length">
+ <span class="json-property-name">vip-ipv6-prefix-length:</span>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Prefix length, 128 for single address</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="vlan-id-inner">
+ <span class="json-property-name">vlan-id-inner:</span>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Inner VLAN tag</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="vlan-id-outer">
+ <span class="json-property-name">vlan-id-outer:</span>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Outer VLAN tag</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="is-floating">
+ <span class="json-property-name">is-floating:</span>
+ <span class="json-property-type">boolean</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Indicator of fixed or floating address</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="neutron-network-id">
+ <span class="json-property-name">neutron-network-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Neutron network id of the interface that address belongs to</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="neutron-subnet-id">
+ <span class="json-property-name">neutron-subnet-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Neutron id of subnet that address belongs to</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-virtual-data-center" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/virtual-data-center"></a>virtual-data-center:
@@ -133701,9 +155839,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Virtual organization of cloud infrastructure elements in a data center context</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO generic-vnf (Many2Many)</li>
-<li>TO logical-link (Many2Many)</li>
-<li>FROM connector</li></ul>
+<li>FROM connector( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)</li>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)</li>
+<li>FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)</li></ul>
</section>
@@ -133824,16 +155962,16 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Definition of vlan</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO l3-interface-ipv4-address-list (comprises vlan, Many2Many)</li>
-<li>TO l3-interface-ipv6-address-list (comprises vlan, Many2Many)</li>
-<li>TO multicast-configuration (Many2Many)</li>
-<li>TO logical-link (One2One)</li>
-<li>FROM l-interface (is composed of vlan)</li>
-<li>FROM service-instance</li></ul>
+<li>TO l-interface( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)</li>
+<li>TO logical-link( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)</li>
+<li>TO multicast-configuration( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)</li>
+<li>FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)</li>
+<li>FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)</li>
+<li>VLAN is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST</li>
+<li>VLAN deletion means associated objects of these types are also DELETED:LOGICAL-LINK</li></ul>
</section>
@@ -134097,7 +156235,8 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>Image object that pertain to a VNF that doesn't have associated vservers. This is a kludge.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM generic-vnf</li></ul>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)</li>
+<li>VNF-IMAGE cannot be deleted if linked to GENERIC-VNF</li></ul>
</section>
@@ -134254,13 +156393,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<div class="panel-body">
<section class="json-schema-description">
- <h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
-<h6 id="related-nodes">Related Nodes</h6>
+ <h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM vserver</li>
-<li>FROM vf-module</li>
-<li>FROM generic-vnf</li></ul>
+<li>TO generic-vnf( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>TO vserver( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)</li>
+<li>FROM vf-module( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)</li></ul>
</section>
@@ -134466,11 +156603,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Ephemeral Block storage volume.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM vserver (is composed of volume)</li></ul>
+<li>FROM vserver (PARENT of volume, vserver tosca.relationships.AttachesTo volume)</li></ul>
</section>
@@ -134550,15 +156685,13 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Persistent block-level storage.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO complex (Many2Many)</li>
-<li>TO tenant (Many2Many)</li>
-<li>FROM cloud-region (is composed of volume-group)</li>
-<li>FROM vf-module</li>
-<li>FROM generic-vnf</li></ul>
+<li>TO cloud-region( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>TO complex( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)</li>
+<li>FROM vf-module( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)</li>
+<li>FROM tenant( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)</li></ul>
</section>
@@ -134759,10 +156892,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>VPLS Provider Edge routers.</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO complex (Many2Many)</li>
-<li>TO ctag-pool (Many2Many)</li>
-<li>TO p-interface (comprises vpls-pe, Many2Many)</li>
-<li>TO lag-interface (comprises vpls-pe, Many2Many)</li></ul>
+<li>TO complex( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>TO ctag-pool( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)</li>
+<li>FROM lag-interface( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)</li>
+<li>FROM p-interface( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)</li>
+<li>VPLS-PE is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE</li></ul>
</section>
@@ -134959,7 +157093,8 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<p>VPN binding</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM l3-network</li></ul>
+<li>FROM l3-network( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)</li>
+<li>VPN-BINDING cannot be deleted if linked to L3-NETWORK</li></ul>
</section>
@@ -135101,21 +157236,21 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Virtual Servers, aka virtual machine or VM.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO flavor (Many2One)</li>
-<li>TO image (Many2One)</li>
-<li>TO l-interface (comprises vserver, Many2Many)</li>
-<li>TO pserver (Many2One)</li>
-<li>TO volume (comprises vserver, Many2Many)</li>
-<li>TO vnfc (Many2Many)</li>
-<li>TO snapshot (One2One)</li>
-<li>TO vf-module (Many2One)</li>
-<li>FROM generic-vnf</li>
-<li>FROM tenant (is composed of vserver)</li>
-<li>FROM vce</li></ul>
+<li>TO tenant( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)</li>
+<li>TO flavor( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)</li>
+<li>TO image( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)</li>
+<li>TO pserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)</li>
+<li>TO snapshot( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)</li>
+<li>TO volume (CHILD of vserver, vserver tosca.relationships.AttachesTo volume, ONE2MANY)</li>
+<li>FROM generic-vnf( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)</li>
+<li>FROM vce( vce tosca.relationships.HostedOn vserver, ONE2MANY)</li>
+<li>FROM l-interface( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)</li>
+<li>FROM vf-module( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)</li>
+<li>FROM vnfc( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)</li>
+<li>VSERVER is DELETED when these are DELETED L-INTERFACE</li>
+<li>VSERVER deletion means associated objects of these types are also DELETED:VOLUME</li></ul>
</section>
@@ -135325,6 +157460,170 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-zone" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/zone"></a>zone:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>A zone is a grouping of assets in a location homing to the same connections into the CBB</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO complex( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)</li>
+<li>FROM pnf( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)</li>
+<li>FROM pserver( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="zone-id">
+ <span class="json-property-name">zone-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Code assigned by AIC to the zone</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="zone-name">
+ <span class="json-property-name">zone-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>English name associated with the zone</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="design-type">
+ <span class="json-property-name">design-type:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Design of zone [Medium/Large?]</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="zone-context">
+ <span class="json-property-name">zone-context:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Context of zone [production/test]</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="status">
+ <span class="json-property-name">status:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Status of a zone.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Concurrency value</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-zones" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/zones"></a>zones:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Collection of zones</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="zone">
+ <span class="json-property-name">zone:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/zone">zone</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
</div>
</body>
</html>
diff --git a/aai-schema/src/main/resources/aai_swagger_html/aai_swagger_v9.html b/aai-schema/src/main/resources/aai_swagger_html/aai_swagger_v9.html
index 95cffc24..e8dae82f 100644
--- a/aai-schema/src/main/resources/aai_swagger_html/aai_swagger_v9.html
+++ b/aai-schema/src/main/resources/aai_swagger_html/aai_swagger_v9.html
@@ -1,4 +1,3 @@
-
<!DOCTYPE html>
<html>
<head>
@@ -15,8 +14,11 @@
<body>
<div class="container">
<h1>Active and Available Inventory REST API.</h1>
- <p class="sw-info-version">Version: <span>v11</span></p>
- <p><p>Copyright &copy; 2017 AT&amp;T Intellectual Property. All rights reserved.<br/>
+ <p class="sw-info-version">Version: <span>v12</span></p>
+ <p><p><br/>
+[Differences versus the previous schema version](apidocs/aai_swagger_v9.diff)<br/>
+<br/>
+Copyright &copy; 2017 AT&amp;T Intellectual Property. All rights reserved.<br/>
<br/>
Licensed under the Creative Commons License, Attribution 4.0 Intl. (the &quot;License&quot;); you may not use this documentation except in compliance with the License.<br/>
<br/>
@@ -65,6 +67,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}</a></td>
+ <td><p>update an existing cloud-region</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}</a></td>
<td><p>delete an existing cloud-region</p>
</td>
@@ -85,6 +92,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--availability-zones-availability-zone--availability-zone-name--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/availability-zones/availability-zone/{availability-zone-name}</a></td>
+ <td><p>update an existing availability-zone</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--availability-zones-availability-zone--availability-zone-name--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/availability-zones/availability-zone/{availability-zone-name}</a></td>
<td><p>delete an existing availability-zone</p>
</td>
@@ -115,6 +127,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--dvs-switches-dvs-switch--switch-name--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/dvs-switches/dvs-switch/{switch-name}</a></td>
+ <td><p>update an existing dvs-switch</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--dvs-switches-dvs-switch--switch-name--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/dvs-switches/dvs-switch/{switch-name}</a></td>
<td><p>delete an existing dvs-switch</p>
</td>
@@ -145,6 +162,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--flavors-flavor--flavor-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/flavors/flavor/{flavor-id}</a></td>
+ <td><p>update an existing flavor</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--flavors-flavor--flavor-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/flavors/flavor/{flavor-id}</a></td>
<td><p>delete an existing flavor</p>
</td>
@@ -175,6 +197,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--group-assignments-group-assignment--group-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/group-assignments/group-assignment/{group-id}</a></td>
+ <td><p>update an existing group-assignment</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--group-assignments-group-assignment--group-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/group-assignments/group-assignment/{group-id}</a></td>
<td><p>delete an existing group-assignment</p>
</td>
@@ -205,6 +232,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}</a></td>
+ <td><p>update an existing image</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}</a></td>
<td><p>delete an existing image</p>
</td>
@@ -225,6 +257,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--metadata-metadatum--metaname--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}/metadata/metadatum/{metaname}</a></td>
+ <td><p>update an existing metadatum</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--metadata-metadatum--metaname--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}/metadata/metadatum/{metaname}</a></td>
<td><p>delete an existing metadatum</p>
</td>
@@ -255,6 +292,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--oam-networks-oam-network--network-uuid--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/oam-networks/oam-network/{network-uuid}</a></td>
+ <td><p>update an existing oam-network</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--oam-networks-oam-network--network-uuid--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/oam-networks/oam-network/{network-uuid}</a></td>
<td><p>delete an existing oam-network</p>
</td>
@@ -295,6 +337,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--snapshots-snapshot--snapshot-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/snapshots/snapshot/{snapshot-id}</a></td>
+ <td><p>update an existing snapshot</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--snapshots-snapshot--snapshot-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/snapshots/snapshot/{snapshot-id}</a></td>
<td><p>delete an existing snapshot</p>
</td>
@@ -325,6 +372,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}</a></td>
+ <td><p>update an existing tenant</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}</a></td>
<td><p>delete an existing tenant</p>
</td>
@@ -355,6 +407,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}</a></td>
+ <td><p>update an existing vserver</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}</a></td>
<td><p>delete an existing vserver</p>
</td>
@@ -375,6 +432,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -390,6 +452,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -415,6 +482,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -455,6 +527,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -485,6 +562,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -500,6 +582,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -525,6 +612,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -575,6 +667,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--volumes-volume--volume-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/volumes/volume/{volume-id}</a></td>
+ <td><p>update an existing volume</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--volumes-volume--volume-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/volumes/volume/{volume-id}</a></td>
<td><p>delete an existing volume</p>
</td>
@@ -605,6 +702,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--volume-groups-volume-group--volume-group-id--patch">PATCH /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/volume-groups/volume-group/{volume-group-id}</a></td>
+ <td><p>update an existing volume-group</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--volume-groups-volume-group--volume-group-id--delete">DELETE /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/volume-groups/volume-group/{volume-group-id}</a></td>
<td><p>delete an existing volume-group</p>
</td>
@@ -635,6 +737,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-complexes-complex--physical-location-id--patch">PATCH /cloud-infrastructure/complexes/complex/{physical-location-id}</a></td>
+ <td><p>update an existing complex</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-complexes-complex--physical-location-id--delete">DELETE /cloud-infrastructure/complexes/complex/{physical-location-id}</a></td>
<td><p>delete an existing complex</p>
</td>
@@ -655,6 +762,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-complexes-complex--physical-location-id--ctag-pools-ctag-pool--target-pe---availability-zone-name--patch">PATCH /cloud-infrastructure/complexes/complex/{physical-location-id}/ctag-pools/ctag-pool/{target-pe}/{availability-zone-name}</a></td>
+ <td><p>update an existing ctag-pool</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-complexes-complex--physical-location-id--ctag-pools-ctag-pool--target-pe---availability-zone-name--delete">DELETE /cloud-infrastructure/complexes/complex/{physical-location-id}/ctag-pools/ctag-pool/{target-pe}/{availability-zone-name}</a></td>
<td><p>delete an existing ctag-pool</p>
</td>
@@ -695,6 +807,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-network-profiles-network-profile--nm-profile-name--patch">PATCH /cloud-infrastructure/network-profiles/network-profile/{nm-profile-name}</a></td>
+ <td><p>update an existing network-profile</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-network-profiles-network-profile--nm-profile-name--delete">DELETE /cloud-infrastructure/network-profiles/network-profile/{nm-profile-name}</a></td>
<td><p>delete an existing network-profile</p>
</td>
@@ -725,6 +842,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}</a></td>
+ <td><p>update an existing pserver</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}</a></td>
<td><p>delete an existing pserver</p>
</td>
@@ -745,6 +867,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}</a></td>
+ <td><p>update an existing lag-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}</a></td>
<td><p>delete an existing lag-interface</p>
</td>
@@ -765,6 +892,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -780,6 +912,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -805,6 +942,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -845,6 +987,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -875,6 +1022,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -890,6 +1042,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -915,6 +1072,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -965,6 +1127,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}</a></td>
+ <td><p>update an existing p-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}</a></td>
<td><p>delete an existing p-interface</p>
</td>
@@ -985,6 +1152,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -1000,6 +1172,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -1025,6 +1202,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -1065,6 +1247,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -1095,6 +1282,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -1110,6 +1302,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -1135,6 +1332,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -1195,6 +1397,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--patch">PATCH /cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}</a></td>
+ <td><p>update an existing virtual-data-center</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--delete">DELETE /cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}</a></td>
<td><p>delete an existing virtual-data-center</p>
</td>
@@ -1239,6 +1446,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-connectors-connector--resource-instance-id--patch">PATCH /business/connectors/connector/{resource-instance-id}</a></td>
+ <td><p>update an existing connector</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-connectors-connector--resource-instance-id--delete">DELETE /business/connectors/connector/{resource-instance-id}</a></td>
<td><p>delete an existing connector</p>
</td>
@@ -1259,6 +1471,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-connectors-connector--resource-instance-id--metadata-metadatum--metaname--patch">PATCH /business/connectors/connector/{resource-instance-id}/metadata/metadatum/{metaname}</a></td>
+ <td><p>update an existing metadatum</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-connectors-connector--resource-instance-id--metadata-metadatum--metaname--delete">DELETE /business/connectors/connector/{resource-instance-id}/metadata/metadatum/{metaname}</a></td>
<td><p>delete an existing metadatum</p>
</td>
@@ -1289,6 +1506,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-customers-customer--global-customer-id--patch">PATCH /business/customers/customer/{global-customer-id}</a></td>
+ <td><p>update an existing customer</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-customers-customer--global-customer-id--delete">DELETE /business/customers/customer/{global-customer-id}</a></td>
<td><p>delete an existing customer</p>
</td>
@@ -1319,6 +1541,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--patch">PATCH /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}</a></td>
+ <td><p>update an existing service-subscription</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--delete">DELETE /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}</a></td>
<td><p>delete an existing service-subscription</p>
</td>
@@ -1349,6 +1576,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--patch">PATCH /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}</a></td>
+ <td><p>update an existing service-instance</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--delete">DELETE /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}</a></td>
<td><p>delete an existing service-instance</p>
</td>
@@ -1369,6 +1601,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--patch">PATCH /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/allotted-resources/allotted-resource/{id}</a></td>
+ <td><p>update an existing allotted-resource</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--delete">DELETE /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/allotted-resources/allotted-resource/{id}</a></td>
<td><p>delete an existing allotted-resource</p>
</td>
@@ -1399,6 +1636,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--tunnel-xconnects-tunnel-xconnect--id--patch">PATCH /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/allotted-resources/allotted-resource/{id}/tunnel-xconnects/tunnel-xconnect/{id}</a></td>
+ <td><p>update an existing tunnel-xconnect</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--tunnel-xconnects-tunnel-xconnect--id--delete">DELETE /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/allotted-resources/allotted-resource/{id}/tunnel-xconnects/tunnel-xconnect/{id}</a></td>
<td><p>delete an existing tunnel-xconnect</p>
</td>
@@ -1429,6 +1671,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--metadata-metadatum--metaname--patch">PATCH /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/metadata/metadatum/{metaname}</a></td>
+ <td><p>update an existing metadatum</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--metadata-metadatum--metaname--delete">DELETE /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/metadata/metadatum/{metaname}</a></td>
<td><p>delete an existing metadatum</p>
</td>
@@ -1473,6 +1720,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--patch">PATCH /service-design-and-creation/models/model/{model-invariant-id}</a></td>
+ <td><p>update an existing model</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--delete">DELETE /service-design-and-creation/models/model/{model-invariant-id}</a></td>
<td><p>delete an existing model</p>
</td>
@@ -1493,6 +1745,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--patch">PATCH /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}</a></td>
+ <td><p>update an existing model-ver</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--delete">DELETE /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}</a></td>
<td><p>delete an existing model-ver</p>
</td>
@@ -1513,6 +1770,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--metadata-metadatum--metaname--patch">PATCH /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/metadata/metadatum/{metaname}</a></td>
+ <td><p>update an existing metadatum</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--metadata-metadatum--metaname--delete">DELETE /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/metadata/metadatum/{metaname}</a></td>
<td><p>delete an existing metadatum</p>
</td>
@@ -1533,6 +1795,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--patch">PATCH /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}</a></td>
+ <td><p>update an existing model-element</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--delete">DELETE /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}</a></td>
<td><p>delete an existing model-element</p>
</td>
@@ -1553,6 +1820,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--patch">PATCH /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}</a></td>
+ <td><p>update an existing model-constraint</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--delete">DELETE /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}</a></td>
<td><p>delete an existing model-constraint</p>
</td>
@@ -1573,6 +1845,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--patch">PATCH /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}</a></td>
+ <td><p>update an existing constrained-element-set</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--delete">DELETE /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}</a></td>
<td><p>delete an existing constrained-element-set</p>
</td>
@@ -1593,6 +1870,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--element-choice-sets-element-choice-set--element-choice-set-uuid--patch">PATCH /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}/element-choice-sets/element-choice-set/{element-choice-set-uuid}</a></td>
+ <td><p>update an existing element-choice-set</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--element-choice-sets-element-choice-set--element-choice-set-uuid--delete">DELETE /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}/element-choice-sets/element-choice-set/{element-choice-set-uuid}</a></td>
<td><p>delete an existing element-choice-set</p>
</td>
@@ -1663,6 +1945,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--patch">PATCH /service-design-and-creation/named-queries/named-query/{named-query-uuid}</a></td>
+ <td><p>update an existing named-query</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--delete">DELETE /service-design-and-creation/named-queries/named-query/{named-query-uuid}</a></td>
<td><p>delete an existing named-query</p>
</td>
@@ -1683,6 +1970,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--patch">PATCH /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}</a></td>
+ <td><p>update an existing named-query-element</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--delete">DELETE /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}</a></td>
<td><p>delete an existing named-query-element</p>
</td>
@@ -1703,6 +1995,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--property-constraints-property-constraint--property-constraint-uuid--patch">PATCH /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/property-constraints/property-constraint/{property-constraint-uuid}</a></td>
+ <td><p>update an existing property-constraint</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--property-constraints-property-constraint--property-constraint-uuid--delete">DELETE /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/property-constraints/property-constraint/{property-constraint-uuid}</a></td>
<td><p>delete an existing property-constraint</p>
</td>
@@ -1723,6 +2020,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--related-lookups-related-lookup--related-lookup-uuid--patch">PATCH /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/related-lookups/related-lookup/{related-lookup-uuid}</a></td>
+ <td><p>update an existing related-lookup</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--related-lookups-related-lookup--related-lookup-uuid--delete">DELETE /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/related-lookups/related-lookup/{related-lookup-uuid}</a></td>
<td><p>delete an existing related-lookup</p>
</td>
@@ -1773,6 +2075,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-service-capabilities-service-capability--service-type---vnf-type--patch">PATCH /service-design-and-creation/service-capabilities/service-capability/{service-type}/{vnf-type}</a></td>
+ <td><p>update an existing service-capability</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-service-capabilities-service-capability--service-type---vnf-type--delete">DELETE /service-design-and-creation/service-capabilities/service-capability/{service-type}/{vnf-type}</a></td>
<td><p>delete an existing service-capability</p>
</td>
@@ -1803,6 +2110,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-services-service--service-id--patch">PATCH /service-design-and-creation/services/service/{service-id}</a></td>
+ <td><p>update an existing service</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-services-service--service-id--delete">DELETE /service-design-and-creation/services/service/{service-id}</a></td>
<td><p>delete an existing service</p>
</td>
@@ -1833,6 +2145,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--service-design-and-creation-vnf-images-vnf-image--vnf-image-uuid--patch">PATCH /service-design-and-creation/vnf-images/vnf-image/{vnf-image-uuid}</a></td>
+ <td><p>update an existing vnf-image</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--service-design-and-creation-vnf-images-vnf-image--vnf-image-uuid--delete">DELETE /service-design-and-creation/vnf-images/vnf-image/{vnf-image-uuid}</a></td>
<td><p>delete an existing vnf-image</p>
</td>
@@ -1877,6 +2194,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}</a></td>
+ <td><p>update an existing generic-vnf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}</a></td>
<td><p>delete an existing generic-vnf</p>
</td>
@@ -1897,6 +2219,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/entitlements/entitlement/{group-uuid}/{resource-uuid}</a></td>
+ <td><p>update an existing entitlement</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/entitlements/entitlement/{group-uuid}/{resource-uuid}</a></td>
<td><p>delete an existing entitlement</p>
</td>
@@ -1927,6 +2254,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -1942,6 +2274,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -1967,6 +2304,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -2007,6 +2349,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -2037,6 +2384,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -2052,6 +2404,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -2077,6 +2434,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -2117,6 +2479,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}</a></td>
+ <td><p>update an existing lag-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}</a></td>
<td><p>delete an existing lag-interface</p>
</td>
@@ -2137,6 +2504,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -2152,6 +2524,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -2177,6 +2554,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -2217,6 +2599,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -2247,6 +2634,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -2262,6 +2654,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -2287,6 +2684,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -2337,6 +2739,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--licenses-license--group-uuid---resource-uuid--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/licenses/license/{group-uuid}/{resource-uuid}</a></td>
+ <td><p>update an existing license</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--licenses-license--group-uuid---resource-uuid--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/licenses/license/{group-uuid}/{resource-uuid}</a></td>
<td><p>delete an existing license</p>
</td>
@@ -2377,6 +2784,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--vf-modules-vf-module--vf-module-id--patch">PATCH /network/generic-vnfs/generic-vnf/{vnf-id}/vf-modules/vf-module/{vf-module-id}</a></td>
+ <td><p>update an existing vf-module</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-generic-vnfs-generic-vnf--vnf-id--vf-modules-vf-module--vf-module-id--delete">DELETE /network/generic-vnfs/generic-vnf/{vnf-id}/vf-modules/vf-module/{vf-module-id}</a></td>
<td><p>delete an existing vf-module</p>
</td>
@@ -2407,6 +2819,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-instance-groups-instance-group--id--patch">PATCH /network/instance-groups/instance-group/{id}</a></td>
+ <td><p>update an existing instance-group</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-instance-groups-instance-group--id--delete">DELETE /network/instance-groups/instance-group/{id}</a></td>
<td><p>delete an existing instance-group</p>
</td>
@@ -2437,6 +2854,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--patch">PATCH /network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}</a></td>
+ <td><p>update an existing ipsec-configuration</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--delete">DELETE /network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}</a></td>
<td><p>delete an existing ipsec-configuration</p>
</td>
@@ -2467,6 +2889,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--vig-servers-vig-server--vig-address-type--patch">PATCH /network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}/vig-servers/vig-server/{vig-address-type}</a></td>
+ <td><p>update an existing vig-server</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--vig-servers-vig-server--vig-address-type--delete">DELETE /network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}/vig-servers/vig-server/{vig-address-type}</a></td>
<td><p>delete an existing vig-server</p>
</td>
@@ -2497,6 +2924,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-l3-networks-l3-network--network-id--patch">PATCH /network/l3-networks/l3-network/{network-id}</a></td>
+ <td><p>update an existing l3-network</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-l3-networks-l3-network--network-id--delete">DELETE /network/l3-networks/l3-network/{network-id}</a></td>
<td><p>delete an existing l3-network</p>
</td>
@@ -2517,6 +2949,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-l3-networks-l3-network--network-id--ctag-assignments-ctag-assignment--vlan-id-inner--patch">PATCH /network/l3-networks/l3-network/{network-id}/ctag-assignments/ctag-assignment/{vlan-id-inner}</a></td>
+ <td><p>update an existing ctag-assignment</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-l3-networks-l3-network--network-id--ctag-assignments-ctag-assignment--vlan-id-inner--delete">DELETE /network/l3-networks/l3-network/{network-id}/ctag-assignments/ctag-assignment/{vlan-id-inner}</a></td>
<td><p>delete an existing ctag-assignment</p>
</td>
@@ -2557,6 +2994,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-l3-networks-l3-network--network-id--segmentation-assignments-segmentation-assignment--segmentation-id--patch">PATCH /network/l3-networks/l3-network/{network-id}/segmentation-assignments/segmentation-assignment/{segmentation-id}</a></td>
+ <td><p>update an existing segmentation-assignment</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-l3-networks-l3-network--network-id--segmentation-assignments-segmentation-assignment--segmentation-id--delete">DELETE /network/l3-networks/l3-network/{network-id}/segmentation-assignments/segmentation-assignment/{segmentation-id}</a></td>
<td><p>delete an existing segmentation-assignment</p>
</td>
@@ -2587,6 +3029,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-l3-networks-l3-network--network-id--subnets-subnet--subnet-id--patch">PATCH /network/l3-networks/l3-network/{network-id}/subnets/subnet/{subnet-id}</a></td>
+ <td><p>update an existing subnet</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-l3-networks-l3-network--network-id--subnets-subnet--subnet-id--delete">DELETE /network/l3-networks/l3-network/{network-id}/subnets/subnet/{subnet-id}</a></td>
<td><p>delete an existing subnet</p>
</td>
@@ -2617,6 +3064,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-lag-links-lag-link--link-name--patch">PATCH /network/lag-links/lag-link/{link-name}</a></td>
+ <td><p>update an existing lag-link</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-lag-links-lag-link--link-name--delete">DELETE /network/lag-links/lag-link/{link-name}</a></td>
<td><p>delete an existing lag-link</p>
</td>
@@ -2647,6 +3099,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-logical-links-logical-link--link-name--patch">PATCH /network/logical-links/logical-link/{link-name}</a></td>
+ <td><p>update an existing logical-link</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-logical-links-logical-link--link-name--delete">DELETE /network/logical-links/logical-link/{link-name}</a></td>
<td><p>delete an existing logical-link</p>
</td>
@@ -2677,6 +3134,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-multicast-configurations-multicast-configuration--multicast-configuration-id--patch">PATCH /network/multicast-configurations/multicast-configuration/{multicast-configuration-id}</a></td>
+ <td><p>update an existing multicast-configuration</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-multicast-configurations-multicast-configuration--multicast-configuration-id--delete">DELETE /network/multicast-configurations/multicast-configuration/{multicast-configuration-id}</a></td>
<td><p>delete an existing multicast-configuration</p>
</td>
@@ -2707,6 +3169,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-network-policies-network-policy--network-policy-id--patch">PATCH /network/network-policies/network-policy/{network-policy-id}</a></td>
+ <td><p>update an existing network-policy</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-network-policies-network-policy--network-policy-id--delete">DELETE /network/network-policies/network-policy/{network-policy-id}</a></td>
<td><p>delete an existing network-policy</p>
</td>
@@ -2737,6 +3204,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--patch">PATCH /network/newvces/newvce/{vnf-id2}</a></td>
+ <td><p>update an existing newvce</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--delete">DELETE /network/newvces/newvce/{vnf-id2}</a></td>
<td><p>delete an existing newvce</p>
</td>
@@ -2757,6 +3229,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--patch">PATCH /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--delete">DELETE /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -2772,6 +3249,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -2797,6 +3279,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -2837,6 +3324,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -2867,6 +3359,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -2882,6 +3379,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -2907,6 +3409,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -2957,6 +3464,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-physical-links-physical-link--link-name--patch">PATCH /network/physical-links/physical-link/{link-name}</a></td>
+ <td><p>update an existing physical-link</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-physical-links-physical-link--link-name--delete">DELETE /network/physical-links/physical-link/{link-name}</a></td>
<td><p>delete an existing physical-link</p>
</td>
@@ -2987,6 +3499,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--patch">PATCH /network/pnfs/pnf/{pnf-name}</a></td>
+ <td><p>update an existing pnf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--delete">DELETE /network/pnfs/pnf/{pnf-name}</a></td>
<td><p>delete an existing pnf</p>
</td>
@@ -3007,6 +3524,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}</a></td>
+ <td><p>update an existing lag-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}</a></td>
<td><p>delete an existing lag-interface</p>
</td>
@@ -3027,6 +3549,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -3042,6 +3569,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -3067,6 +3599,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -3107,6 +3644,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -3137,6 +3679,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -3152,6 +3699,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -3177,6 +3729,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -3227,6 +3784,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}</a></td>
+ <td><p>update an existing p-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}</a></td>
<td><p>delete an existing p-interface</p>
</td>
@@ -3247,6 +3809,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -3262,6 +3829,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -3287,6 +3859,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -3327,6 +3904,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -3357,6 +3939,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -3372,6 +3959,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -3397,6 +3989,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -3457,6 +4054,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-route-table-references-route-table-reference--route-table-reference-id--patch">PATCH /network/route-table-references/route-table-reference/{route-table-reference-id}</a></td>
+ <td><p>update an existing route-table-reference</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-route-table-references-route-table-reference--route-table-reference-id--delete">DELETE /network/route-table-references/route-table-reference/{route-table-reference-id}</a></td>
<td><p>delete an existing route-table-reference</p>
</td>
@@ -3487,6 +4089,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--patch">PATCH /network/site-pair-sets/site-pair-set/{site-pair-set-id}</a></td>
+ <td><p>update an existing site-pair-set</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--delete">DELETE /network/site-pair-sets/site-pair-set/{site-pair-set-id}</a></td>
<td><p>delete an existing site-pair-set</p>
</td>
@@ -3517,6 +4124,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--patch">PATCH /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}</a></td>
+ <td><p>update an existing routing-instance</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--delete">DELETE /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}</a></td>
<td><p>delete an existing routing-instance</p>
</td>
@@ -3547,6 +4159,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--patch">PATCH /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}</a></td>
+ <td><p>update an existing site-pair</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--delete">DELETE /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}</a></td>
<td><p>delete an existing site-pair</p>
</td>
@@ -3567,6 +4184,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--classes-of-service-class-of-service--cos--patch">PATCH /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}/classes-of-service/class-of-service/{cos}</a></td>
+ <td><p>update an existing class-of-service</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--classes-of-service-class-of-service--cos--delete">DELETE /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}/classes-of-service/class-of-service/{cos}</a></td>
<td><p>delete an existing class-of-service</p>
</td>
@@ -3607,6 +4229,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vces-vce--vnf-id--patch">PATCH /network/vces/vce/{vnf-id}</a></td>
+ <td><p>update an existing vce</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vces-vce--vnf-id--delete">DELETE /network/vces/vce/{vnf-id}</a></td>
<td><p>delete an existing vce</p>
</td>
@@ -3627,6 +4254,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vces-vce--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--patch">PATCH /network/vces/vce/{vnf-id}/entitlements/entitlement/{group-uuid}/{resource-uuid}</a></td>
+ <td><p>update an existing entitlement</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vces-vce--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--delete">DELETE /network/vces/vce/{vnf-id}/entitlements/entitlement/{group-uuid}/{resource-uuid}</a></td>
<td><p>delete an existing entitlement</p>
</td>
@@ -3657,6 +4289,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vces-vce--vnf-id--licenses-license--group-uuid---resource-uuid--patch">PATCH /network/vces/vce/{vnf-id}/licenses/license/{group-uuid}/{resource-uuid}</a></td>
+ <td><p>update an existing license</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vces-vce--vnf-id--licenses-license--group-uuid---resource-uuid--delete">DELETE /network/vces/vce/{vnf-id}/licenses/license/{group-uuid}/{resource-uuid}</a></td>
<td><p>delete an existing license</p>
</td>
@@ -3687,6 +4324,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--patch">PATCH /network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}</a></td>
+ <td><p>update an existing port-group</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--delete">DELETE /network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}</a></td>
<td><p>delete an existing port-group</p>
</td>
@@ -3707,6 +4349,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--cvlan-tags-cvlan-tag-entry--cvlan-tag--patch">PATCH /network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}/cvlan-tags/cvlan-tag-entry/{cvlan-tag}</a></td>
+ <td><p>update an existing cvlan-tag-entry</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--cvlan-tags-cvlan-tag-entry--cvlan-tag--delete">DELETE /network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}/cvlan-tags/cvlan-tag-entry/{cvlan-tag}</a></td>
<td><p>delete an existing cvlan-tag-entry</p>
</td>
@@ -3757,6 +4404,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vnfcs-vnfc--vnfc-name--patch">PATCH /network/vnfcs/vnfc/{vnfc-name}</a></td>
+ <td><p>update an existing vnfc</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vnfcs-vnfc--vnfc-name--delete">DELETE /network/vnfcs/vnfc/{vnfc-name}</a></td>
<td><p>delete an existing vnfc</p>
</td>
@@ -3787,6 +4439,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}</a></td>
+ <td><p>update an existing vpls-pe</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}</a></td>
<td><p>delete an existing vpls-pe</p>
</td>
@@ -3807,6 +4464,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}</a></td>
+ <td><p>update an existing lag-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}</a></td>
<td><p>delete an existing lag-interface</p>
</td>
@@ -3827,6 +4489,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -3842,6 +4509,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -3867,6 +4539,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -3907,6 +4584,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -3937,6 +4619,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -3952,6 +4639,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -3977,6 +4669,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -4027,6 +4724,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}</a></td>
+ <td><p>update an existing p-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}</a></td>
<td><p>delete an existing p-interface</p>
</td>
@@ -4047,6 +4749,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
+ <td><p>update an existing l-interface</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</a></td>
<td><p>delete an existing l-interface</p>
</td>
@@ -4062,6 +4769,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -4087,6 +4799,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -4127,6 +4844,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
+ <td><p>update an existing sriov-vf</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</a></td>
<td><p>delete an existing sriov-vf</p>
</td>
@@ -4157,6 +4879,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
+ <td><p>update an existing vlan</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</a></td>
<td><p>delete an existing vlan</p>
</td>
@@ -4172,6 +4899,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
+ <td><p>update an existing l3-interface-ipv4-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</a></td>
<td><p>delete an existing l3-interface-ipv4-address-list</p>
</td>
@@ -4197,6 +4929,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch">PATCH /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
+ <td><p>update an existing l3-interface-ipv6-address-list</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete">DELETE /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</a></td>
<td><p>delete an existing l3-interface-ipv6-address-list</p>
</td>
@@ -4257,6 +4994,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-vpn-bindings-vpn-binding--vpn-id--patch">PATCH /network/vpn-bindings/vpn-binding/{vpn-id}</a></td>
+ <td><p>update an existing vpn-binding</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-vpn-bindings-vpn-binding--vpn-id--delete">DELETE /network/vpn-bindings/vpn-binding/{vpn-id}</a></td>
<td><p>delete an existing vpn-binding</p>
</td>
@@ -4287,6 +5029,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</td>
</tr>
<tr>
+ <td><a href="#operation--network-zones-zone--zone-id--patch">PATCH /network/zones/zone/{zone-id}</a></td>
+ <td><p>update an existing zone</p>
+ </td>
+ </tr>
+ <tr>
<td><a href="#operation--network-zones-zone--zone-id--delete">DELETE /network/zones/zone/{zone-id}</a></td>
<td><p>delete an existing zone</p>
</td>
@@ -4346,7 +5093,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/connectors">/connectors</a>
+ <a class="json-schema-ref" href="#/getDefinitions/connectors">/connectors</a>
</div>
</div>
</div>
@@ -4501,7 +5248,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/connector">/connector</a>
+ <a class="json-schema-ref" href="#/getDefinitions/connector">/connector</a>
</div>
</div>
</div>
@@ -4548,7 +5295,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>connector object that needs to be created or updated</p>
+ <p><p>connector object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/BusinessConnectorsConnector.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -4619,6 +5366,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-connectors-connector--resource-instance-id--"></span>
+ <div id="operation--business-connectors-connector--resource-instance-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing connector</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/connectors/connector/{resource-instance-id}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing connector</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>connector object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/connector">/connector</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ resource-instance-id
+ </td>
+ <td>
+ <p>Unique id of resource instance.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-connectors-connector--resource-instance-id--"></span>
<div id="operation--business-connectors-connector--resource-instance-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing connector</div>
@@ -4838,7 +5674,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadata">/metadata</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadata">/metadata</a>
</div>
</div>
</div>
@@ -5008,7 +5844,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadatum">/metadatum</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadatum">/metadatum</a>
</div>
</div>
</div>
@@ -5055,7 +5891,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>metadatum object that needs to be created or updated</p>
+ <p><p>metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/BusinessConnectorsConnectorMetadataMetadatum.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -5141,6 +5977,110 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-connectors-connector--resource-instance-id--metadata-metadatum--metaname--"></span>
+ <div id="operation--business-connectors-connector--resource-instance-id--metadata-metadatum--metaname--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing metadatum</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/connectors/connector/{resource-instance-id}/metadata/metadatum/{metaname}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing metadatum</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>metadatum object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/metadatum">/metadatum</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ resource-instance-id
+ </td>
+ <td>
+ <p>Unique id of resource instance.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ metaname
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-connectors-connector--resource-instance-id--metadata-metadatum--metaname--"></span>
<div id="operation--business-connectors-connector--resource-instance-id--metadata-metadatum--metaname--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing metadatum</div>
@@ -5267,7 +6207,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/BusinessConnectorsConnector.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -5450,7 +6390,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/customers">/customers</a>
+ <a class="json-schema-ref" href="#/getDefinitions/customers">/customers</a>
</div>
</div>
</div>
@@ -5575,7 +6515,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/customer">/customer</a>
+ <a class="json-schema-ref" href="#/getDefinitions/customer">/customer</a>
</div>
</div>
</div>
@@ -5622,7 +6562,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>customer object that needs to be created or updated</p>
+ <p><p>customer object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/BusinessCustomersCustomer.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -5693,6 +6633,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-customers-customer--global-customer-id--"></span>
+ <div id="operation--business-customers-customer--global-customer-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing customer</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/customers/customer/{global-customer-id}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing customer</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>customer object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/customer">/customer</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ global-customer-id
+ </td>
+ <td>
+ <p>Global customer id used across ECOMP to uniquely identify customer.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-customers-customer--global-customer-id--"></span>
<div id="operation--business-customers-customer--global-customer-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing customer</div>
@@ -5804,7 +6833,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/BusinessCustomersCustomer.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -6048,7 +7077,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/service-subscriptions">/service-subscriptions</a>
+ <a class="json-schema-ref" href="#/getDefinitions/service-subscriptions">/service-subscriptions</a>
</div>
</div>
</div>
@@ -6189,7 +7218,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/service-subscription">/service-subscription</a>
+ <a class="json-schema-ref" href="#/getDefinitions/service-subscription">/service-subscription</a>
</div>
</div>
</div>
@@ -6236,7 +7265,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>service-subscription object that needs to be created or updated</p>
+ <p><p>service-subscription object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/BusinessCustomersCustomerServiceSubscriptionsServiceSubscription.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -6323,6 +7352,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--"></span>
+ <div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing service-subscription</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing service-subscription</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>service-subscription object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/service-subscription">/service-subscription</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ global-customer-id
+ </td>
+ <td>
+ <p>Global customer id used across ECOMP to uniquely identify customer.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-type
+ </td>
+ <td>
+ <p>Value defined by orchestration to identify this service across ECOMP.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--"></span>
<div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing service-subscription</div>
@@ -6450,7 +7584,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/BusinessCustomersCustomerServiceSubscriptionsServiceSubscription.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -6742,7 +7876,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/service-instances">/service-instances</a>
+ <a class="json-schema-ref" href="#/getDefinitions/service-instances">/service-instances</a>
</div>
</div>
</div>
@@ -7004,7 +8138,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/service-instance">/service-instance</a>
+ <a class="json-schema-ref" href="#/getDefinitions/service-instance">/service-instance</a>
</div>
</div>
</div>
@@ -7051,7 +8185,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>service-instance object that needs to be created or updated</p>
+ <p><p>service-instance object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -7154,6 +8288,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--"></span>
+ <div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing service-instance</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing service-instance</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>service-instance object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/service-instance">/service-instance</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ global-customer-id
+ </td>
+ <td>
+ <p>Global customer id used across ECOMP to uniquely identify customer.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-type
+ </td>
+ <td>
+ <p>Value defined by orchestration to identify this service across ECOMP.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-instance-id
+ </td>
+ <td>
+ <p>Uniquely identifies this instance of a service</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--"></span>
<div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing service-instance</div>
@@ -7512,7 +8767,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/allotted-resources">/allotted-resources</a>
+ <a class="json-schema-ref" href="#/getDefinitions/allotted-resources">/allotted-resources</a>
</div>
</div>
</div>
@@ -7820,7 +9075,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/allotted-resource">/allotted-resource</a>
+ <a class="json-schema-ref" href="#/getDefinitions/allotted-resource">/allotted-resource</a>
</div>
</div>
</div>
@@ -7867,7 +9122,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>allotted-resource object that needs to be created or updated</p>
+ <p><p>allotted-resource object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResource.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -7986,6 +9241,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--"></span>
+ <div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing allotted-resource</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/allotted-resources/allotted-resource/{id}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing allotted-resource</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>allotted-resource object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/allotted-resource">/allotted-resource</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ global-customer-id
+ </td>
+ <td>
+ <p>Global customer id used across ECOMP to uniquely identify customer.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-type
+ </td>
+ <td>
+ <p>Value defined by orchestration to identify this service across ECOMP.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-instance-id
+ </td>
+ <td>
+ <p>Uniquely identifies this instance of a service</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ id
+ </td>
+ <td>
+ <p>Allotted Resource id UUID assigned to this instance.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--"></span>
<div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing allotted-resource</div>
@@ -8145,7 +9537,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResource.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -8668,7 +10060,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/tunnel-xconnects">/tunnel-xconnects</a>
+ <a class="json-schema-ref" href="#/getDefinitions/tunnel-xconnects">/tunnel-xconnects</a>
</div>
</div>
</div>
@@ -8992,7 +10384,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/tunnel-xconnect">/tunnel-xconnect</a>
+ <a class="json-schema-ref" href="#/getDefinitions/tunnel-xconnect">/tunnel-xconnect</a>
</div>
</div>
</div>
@@ -9039,7 +10431,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>tunnel-xconnect object that needs to be created or updated</p>
+ <p><p>tunnel-xconnect object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResourceTunnelXconnectsTunnelXconnect.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -9174,6 +10566,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--tunnel-xconnects-tunnel-xconnect--id--"></span>
+ <div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--tunnel-xconnects-tunnel-xconnect--id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing tunnel-xconnect</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/allotted-resources/allotted-resource/{id}/tunnel-xconnects/tunnel-xconnect/{id}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing tunnel-xconnect</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>tunnel-xconnect object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/tunnel-xconnect">/tunnel-xconnect</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ global-customer-id
+ </td>
+ <td>
+ <p>Global customer id used across ECOMP to uniquely identify customer.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-type
+ </td>
+ <td>
+ <p>Value defined by orchestration to identify this service across ECOMP.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-instance-id
+ </td>
+ <td>
+ <p>Uniquely identifies this instance of a service</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ id
+ </td>
+ <td>
+ <p>Allotted Resource id UUID assigned to this instance.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ id
+ </td>
+ <td>
+ <p>Allotted Resource id UUID assigned to this instance.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--tunnel-xconnects-tunnel-xconnect--id--"></span>
<div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--allotted-resources-allotted-resource--id--tunnel-xconnects-tunnel-xconnect--id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing tunnel-xconnect</div>
@@ -9349,7 +10894,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResourceTunnelXconnectsTunnelXconnect.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -9858,7 +11403,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadata">/metadata</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadata">/metadata</a>
</div>
</div>
</div>
@@ -10135,7 +11680,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadatum">/metadatum</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadatum">/metadatum</a>
</div>
</div>
</div>
@@ -10182,7 +11727,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>metadatum object that needs to be created or updated</p>
+ <p><p>metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceMetadataMetadatum.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -10300,6 +11845,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--metadata-metadatum--metaname--"></span>
+ <div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--metadata-metadatum--metaname--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing metadatum</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/metadata/metadatum/{metaname}</strong></h3>
+ Tags:
+ <a href="#tag-Business">Business</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing metadatum</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>metadatum object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/metadatum">/metadatum</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ global-customer-id
+ </td>
+ <td>
+ <p>Global customer id used across ECOMP to uniquely identify customer.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-type
+ </td>
+ <td>
+ <p>Value defined by orchestration to identify this service across ECOMP.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ service-instance-id
+ </td>
+ <td>
+ <p>Uniquely identifies this instance of a service</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ metaname
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--metadata-metadatum--metaname--"></span>
<div id="operation--business-customers-customer--global-customer-id--service-subscriptions-service-subscription--service-type--service-instances-service-instance--service-instance-id--metadata-metadatum--metaname--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing metadatum</div>
@@ -10458,7 +12139,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -10705,7 +12386,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/cloud-regions">/cloud-regions</a>
+ <a class="json-schema-ref" href="#/getDefinitions/cloud-regions">/cloud-regions</a>
</div>
</div>
</div>
@@ -10846,7 +12527,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/cloud-region">/cloud-region</a>
+ <a class="json-schema-ref" href="#/getDefinitions/cloud-region">/cloud-region</a>
</div>
</div>
</div>
@@ -10893,7 +12574,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>cloud-region object that needs to be created or updated</p>
+ <p><p>cloud-region object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegion.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -10980,6 +12661,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing cloud-region</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing cloud-region</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>cloud-region object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/cloud-region">/cloud-region</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing cloud-region</div>
@@ -11201,7 +12987,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/availability-zones">/availability-zones</a>
+ <a class="json-schema-ref" href="#/getDefinitions/availability-zones">/availability-zones</a>
</div>
</div>
</div>
@@ -11358,7 +13144,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/availability-zone">/availability-zone</a>
+ <a class="json-schema-ref" href="#/getDefinitions/availability-zone">/availability-zone</a>
</div>
</div>
</div>
@@ -11405,7 +13191,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>availability-zone object that needs to be created or updated</p>
+ <p><p>availability-zone object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -11508,6 +13294,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--availability-zones-availability-zone--availability-zone-name--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--availability-zones-availability-zone--availability-zone-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing availability-zone</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/availability-zones/availability-zone/{availability-zone-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing availability-zone</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>availability-zone object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/availability-zone">/availability-zone</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ availability-zone-name
+ </td>
+ <td>
+ <p>Name of the availability zone. Unique across a cloud region</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--availability-zones-availability-zone--availability-zone-name--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--availability-zones-availability-zone--availability-zone-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing availability-zone</div>
@@ -11651,7 +13558,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -11975,7 +13882,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/dvs-switches">/dvs-switches</a>
+ <a class="json-schema-ref" href="#/getDefinitions/dvs-switches">/dvs-switches</a>
</div>
</div>
</div>
@@ -12147,7 +14054,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/dvs-switch">/dvs-switch</a>
+ <a class="json-schema-ref" href="#/getDefinitions/dvs-switch">/dvs-switch</a>
</div>
</div>
</div>
@@ -12194,7 +14101,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>dvs-switch object that needs to be created or updated</p>
+ <p><p>dvs-switch object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -12297,6 +14204,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--dvs-switches-dvs-switch--switch-name--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--dvs-switches-dvs-switch--switch-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing dvs-switch</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/dvs-switches/dvs-switch/{switch-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing dvs-switch</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>dvs-switch object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/dvs-switch">/dvs-switch</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ switch-name
+ </td>
+ <td>
+ <p>DVS switch name</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--dvs-switches-dvs-switch--switch-name--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--dvs-switches-dvs-switch--switch-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing dvs-switch</div>
@@ -12440,7 +14468,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -12764,7 +14792,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/flavors">/flavors</a>
+ <a class="json-schema-ref" href="#/getDefinitions/flavors">/flavors</a>
</div>
</div>
</div>
@@ -12936,7 +14964,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/flavor">/flavor</a>
+ <a class="json-schema-ref" href="#/getDefinitions/flavor">/flavor</a>
</div>
</div>
</div>
@@ -12983,7 +15011,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>flavor object that needs to be created or updated</p>
+ <p><p>flavor object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -13086,6 +15114,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--flavors-flavor--flavor-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--flavors-flavor--flavor-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing flavor</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/flavors/flavor/{flavor-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing flavor</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>flavor object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/flavor">/flavor</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ flavor-id
+ </td>
+ <td>
+ <p>Flavor id, expected to be unique across cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--flavors-flavor--flavor-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--flavors-flavor--flavor-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing flavor</div>
@@ -13229,7 +15378,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -13553,7 +15702,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/group-assignments">/group-assignments</a>
+ <a class="json-schema-ref" href="#/getDefinitions/group-assignments">/group-assignments</a>
</div>
</div>
</div>
@@ -13740,7 +15889,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/group-assignment">/group-assignment</a>
+ <a class="json-schema-ref" href="#/getDefinitions/group-assignment">/group-assignment</a>
</div>
</div>
</div>
@@ -13787,7 +15936,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>group-assignment object that needs to be created or updated</p>
+ <p><p>group-assignment object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -13890,6 +16039,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--group-assignments-group-assignment--group-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--group-assignments-group-assignment--group-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing group-assignment</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/group-assignments/group-assignment/{group-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing group-assignment</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>group-assignment object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/group-assignment">/group-assignment</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ group-id
+ </td>
+ <td>
+ <p>Group id, expected to be unique across cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--group-assignments-group-assignment--group-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--group-assignments-group-assignment--group-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing group-assignment</div>
@@ -14033,7 +16303,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -14357,7 +16627,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/images">/images</a>
+ <a class="json-schema-ref" href="#/getDefinitions/images">/images</a>
</div>
</div>
</div>
@@ -14574,7 +16844,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/image">/image</a>
+ <a class="json-schema-ref" href="#/getDefinitions/image">/image</a>
</div>
</div>
</div>
@@ -14621,7 +16891,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>image object that needs to be created or updated</p>
+ <p><p>image object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionImagesImage.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -14724,6 +16994,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing image</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing image</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>image object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/image">/image</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ image-id
+ </td>
+ <td>
+ <p>Image id, expected to be unique across cloud region</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing image</div>
@@ -15037,7 +17428,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadata">/metadata</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadata">/metadata</a>
</div>
</div>
</div>
@@ -15269,7 +17660,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadatum">/metadatum</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadatum">/metadatum</a>
</div>
</div>
</div>
@@ -15316,7 +17707,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>metadatum object that needs to be created or updated</p>
+ <p><p>metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionImagesImageMetadataMetadatum.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -15434,6 +17825,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--metadata-metadatum--metaname--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--metadata-metadatum--metaname--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing metadatum</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}/metadata/metadatum/{metaname}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing metadatum</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>metadatum object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/metadatum">/metadatum</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ image-id
+ </td>
+ <td>
+ <p>Image id, expected to be unique across cloud region</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ metaname
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--metadata-metadatum--metaname--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--images-image--image-id--metadata-metadatum--metaname--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing metadatum</div>
@@ -15592,7 +18119,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionImagesImage.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -15916,7 +18443,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/oam-networks">/oam-networks</a>
+ <a class="json-schema-ref" href="#/getDefinitions/oam-networks">/oam-networks</a>
</div>
</div>
</div>
@@ -16103,7 +18630,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/oam-network">/oam-network</a>
+ <a class="json-schema-ref" href="#/getDefinitions/oam-network">/oam-network</a>
</div>
</div>
</div>
@@ -16150,7 +18677,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>oam-network object that needs to be created or updated</p>
+ <p><p>oam-network object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -16253,6 +18780,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--oam-networks-oam-network--network-uuid--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--oam-networks-oam-network--network-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing oam-network</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/oam-networks/oam-network/{network-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing oam-network</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>oam-network object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/oam-network">/oam-network</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ network-uuid
+ </td>
+ <td>
+ <p>UUID of the network. Unique across a cloud-region</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--oam-networks-oam-network--network-uuid--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--oam-networks-oam-network--network-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing oam-network</div>
@@ -16396,7 +19044,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -16626,7 +19274,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegion.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -16918,7 +19566,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/snapshots">/snapshots</a>
+ <a class="json-schema-ref" href="#/getDefinitions/snapshots">/snapshots</a>
</div>
</div>
</div>
@@ -17150,7 +19798,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/snapshot">/snapshot</a>
+ <a class="json-schema-ref" href="#/getDefinitions/snapshot">/snapshot</a>
</div>
</div>
</div>
@@ -17197,7 +19845,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>snapshot object that needs to be created or updated</p>
+ <p><p>snapshot object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -17300,6 +19948,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--snapshots-snapshot--snapshot-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--snapshots-snapshot--snapshot-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing snapshot</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/snapshots/snapshot/{snapshot-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing snapshot</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>snapshot object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/snapshot">/snapshot</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ snapshot-id
+ </td>
+ <td>
+ <p>Snapshot id, this is the key UUID assoc associated in glance with the snapshots.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--snapshots-snapshot--snapshot-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--snapshots-snapshot--snapshot-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing snapshot</div>
@@ -17443,7 +20212,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -17767,7 +20536,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/tenants">/tenants</a>
+ <a class="json-schema-ref" href="#/getDefinitions/tenants">/tenants</a>
</div>
</div>
</div>
@@ -17939,7 +20708,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/tenant">/tenant</a>
+ <a class="json-schema-ref" href="#/getDefinitions/tenant">/tenant</a>
</div>
</div>
</div>
@@ -17986,7 +20755,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>tenant object that needs to be created or updated</p>
+ <p><p>tenant object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenant.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -18089,6 +20858,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing tenant</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing tenant</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>tenant object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/tenant">/tenant</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing tenant</div>
@@ -18232,7 +21122,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenant.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -18587,7 +21477,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vservers">/vservers</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vservers">/vservers</a>
</div>
</div>
</div>
@@ -18848,7 +21738,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vserver">/vserver</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vserver">/vserver</a>
</div>
</div>
</div>
@@ -18895,7 +21785,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vserver object that needs to be created or updated</p>
+ <p><p>vserver object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -19014,6 +21904,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vserver</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vserver</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vserver object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vserver">/vserver</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vserver</div>
@@ -19387,7 +22414,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -19709,7 +22736,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -19756,7 +22783,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -19891,6 +22918,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -20402,7 +23582,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -20449,7 +23629,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -20600,6 +23780,175 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -20791,7 +24140,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -21453,7 +24802,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -21500,7 +24849,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -21651,6 +25000,175 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -21842,7 +25360,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -22168,7 +25686,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -22737,7 +26255,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -23135,7 +26653,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -23182,7 +26700,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -23333,6 +26851,175 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -23524,7 +27211,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -24125,7 +27812,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -24493,7 +28180,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -24540,7 +28227,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -24691,6 +28378,175 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -25264,7 +29120,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -25311,7 +29167,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -25478,6 +29334,191 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -25685,7 +29726,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -26425,7 +30466,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -26472,7 +30513,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -26639,6 +30680,191 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -26846,7 +31072,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -27204,7 +31430,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -27530,7 +31756,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -28006,7 +32232,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/volumes">/volumes</a>
+ <a class="json-schema-ref" href="#/getDefinitions/volumes">/volumes</a>
</div>
</div>
</div>
@@ -28283,7 +32509,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/volume">/volume</a>
+ <a class="json-schema-ref" href="#/getDefinitions/volume">/volume</a>
</div>
</div>
</div>
@@ -28330,7 +32556,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>volume object that needs to be created or updated</p>
+ <p><p>volume object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -28465,6 +32691,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--volumes-volume--volume-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--volumes-volume--volume-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing volume</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/volumes/volume/{volume-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing volume</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>volume object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/volume">/volume</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ tenant-id
+ </td>
+ <td>
+ <p>Unique id relative to the cloud-region.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vserver-id
+ </td>
+ <td>
+ <p>Unique identifier for this vserver relative to its tenant</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ volume-id
+ </td>
+ <td>
+ <p>Unique ID of block storage volume relative to the vserver.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--volumes-volume--volume-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--tenants-tenant--tenant-id--vservers-vserver--vserver-id--volumes-volume--volume-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing volume</div>
@@ -28640,7 +33019,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -29028,7 +33407,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/volume-groups">/volume-groups</a>
+ <a class="json-schema-ref" href="#/getDefinitions/volume-groups">/volume-groups</a>
</div>
</div>
</div>
@@ -29230,7 +33609,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/volume-group">/volume-group</a>
+ <a class="json-schema-ref" href="#/getDefinitions/volume-group">/volume-group</a>
</div>
</div>
</div>
@@ -29277,7 +33656,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>volume-group object that needs to be created or updated</p>
+ <p><p>volume-group object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -29380,6 +33759,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--volume-groups-volume-group--volume-group-id--"></span>
+ <div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--volume-groups-volume-group--volume-group-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing volume-group</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/volume-groups/volume-group/{volume-group-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing volume-group</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>volume-group object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/volume-group">/volume-group</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ cloud-owner
+ </td>
+ <td>
+ <p>Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cloud-region-id
+ </td>
+ <td>
+ <p>Identifier used by the vendor for the region. Second part of composite key</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ volume-group-id
+ </td>
+ <td>
+ <p>Unique ID of volume-group.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--volume-groups-volume-group--volume-group-id--"></span>
<div id="operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--volume-groups-volume-group--volume-group-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing volume-group</div>
@@ -29523,7 +34023,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -29770,7 +34270,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/complexes">/complexes</a>
+ <a class="json-schema-ref" href="#/getDefinitions/complexes">/complexes</a>
</div>
</div>
</div>
@@ -29910,7 +34410,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/complex">/complex</a>
+ <a class="json-schema-ref" href="#/getDefinitions/complex">/complex</a>
</div>
</div>
</div>
@@ -29957,7 +34457,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>complex object that needs to be created or updated</p>
+ <p><p>complex object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureComplexesComplex.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -30028,6 +34528,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-complexes-complex--physical-location-id--"></span>
+ <div id="operation--cloud-infrastructure-complexes-complex--physical-location-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing complex</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/complexes/complex/{physical-location-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing complex</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>complex object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/complex">/complex</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ physical-location-id
+ </td>
+ <td>
+ <p>Unique identifier for physical location, e.g., CLLI</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-complexes-complex--physical-location-id--"></span>
<div id="operation--cloud-infrastructure-complexes-complex--physical-location-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing complex</div>
@@ -30232,7 +34821,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/ctag-pools">/ctag-pools</a>
+ <a class="json-schema-ref" href="#/getDefinitions/ctag-pools">/ctag-pools</a>
</div>
</div>
</div>
@@ -30404,7 +34993,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/ctag-pool">/ctag-pool</a>
+ <a class="json-schema-ref" href="#/getDefinitions/ctag-pool">/ctag-pool</a>
</div>
</div>
</div>
@@ -30451,7 +35040,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>ctag-pool object that needs to be created or updated</p>
+ <p><p>ctag-pool object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureComplexesComplexCtagPoolsCtagPool.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -30554,6 +35143,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-complexes-complex--physical-location-id--ctag-pools-ctag-pool--target-pe---availability-zone-name--"></span>
+ <div id="operation--cloud-infrastructure-complexes-complex--physical-location-id--ctag-pools-ctag-pool--target-pe---availability-zone-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing ctag-pool</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/complexes/complex/{physical-location-id}/ctag-pools/ctag-pool/{target-pe}/{availability-zone-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing ctag-pool</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>ctag-pool object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/ctag-pool">/ctag-pool</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ physical-location-id
+ </td>
+ <td>
+ <p>Unique identifier for physical location, e.g., CLLI</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ target-pe
+ </td>
+ <td>
+ <p>The Target provider edge router</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ availability-zone-name
+ </td>
+ <td>
+ <p>Name of the availability zone</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-complexes-complex--physical-location-id--ctag-pools-ctag-pool--target-pe---availability-zone-name--"></span>
<div id="operation--cloud-infrastructure-complexes-complex--physical-location-id--ctag-pools-ctag-pool--target-pe---availability-zone-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing ctag-pool</div>
@@ -30697,7 +35407,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureComplexesComplexCtagPoolsCtagPool.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -30927,7 +35637,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureComplexesComplex.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -31110,7 +35820,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/network-profiles">/network-profiles</a>
+ <a class="json-schema-ref" href="#/getDefinitions/network-profiles">/network-profiles</a>
</div>
</div>
</div>
@@ -31205,7 +35915,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/network-profile">/network-profile</a>
+ <a class="json-schema-ref" href="#/getDefinitions/network-profile">/network-profile</a>
</div>
</div>
</div>
@@ -31252,7 +35962,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>network-profile object that needs to be created or updated</p>
+ <p><p>network-profile object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureNetworkProfilesNetworkProfile.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -31323,6 +36033,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-network-profiles-network-profile--nm-profile-name--"></span>
+ <div id="operation--cloud-infrastructure-network-profiles-network-profile--nm-profile-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing network-profile</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/network-profiles/network-profile/{nm-profile-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing network-profile</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>network-profile object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/network-profile">/network-profile</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ nm-profile-name
+ </td>
+ <td>
+ <p>Unique name of network profile.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-network-profiles-network-profile--nm-profile-name--"></span>
<div id="operation--cloud-infrastructure-network-profiles-network-profile--nm-profile-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing network-profile</div>
@@ -31434,7 +36233,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureNetworkProfilesNetworkProfile.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -31617,7 +36416,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/pservers">/pservers</a>
+ <a class="json-schema-ref" href="#/getDefinitions/pservers">/pservers</a>
</div>
</div>
</div>
@@ -31771,7 +36570,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/pserver">/pserver</a>
+ <a class="json-schema-ref" href="#/getDefinitions/pserver">/pserver</a>
</div>
</div>
</div>
@@ -31818,7 +36617,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>pserver object that needs to be created or updated</p>
+ <p><p>pserver object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserver.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -31889,6 +36688,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing pserver</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing pserver</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>pserver object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/pserver">/pserver</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing pserver</div>
@@ -32107,7 +36995,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interfaces">/lag-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interfaces">/lag-interfaces</a>
</div>
</div>
</div>
@@ -32307,7 +37195,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interface">/lag-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interface">/lag-interface</a>
</div>
</div>
</div>
@@ -32354,7 +37242,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>lag-interface object that needs to be created or updated</p>
+ <p><p>lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -32441,6 +37329,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing lag-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing lag-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>lag-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/lag-interface">/lag-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing lag-interface</div>
@@ -32721,7 +37714,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -32982,7 +37975,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -33029,7 +38022,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -33132,6 +38125,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -33550,7 +38664,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -33597,7 +38711,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -33716,6 +38830,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -33875,7 +39126,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -34412,7 +39663,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -34459,7 +39710,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -34578,6 +39829,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -34737,7 +40125,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -34999,7 +40387,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -35443,7 +40831,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -35780,7 +41168,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -35827,7 +41215,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -35946,6 +41334,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -36105,7 +41630,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -36581,7 +42106,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -36888,7 +42413,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -36935,7 +42460,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -37054,6 +42579,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -37534,7 +43196,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -37581,7 +43243,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -37716,6 +43378,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -37891,7 +43706,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -38506,7 +44321,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -38553,7 +44368,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -38688,6 +44503,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -38863,7 +44831,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -39157,7 +45125,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -39419,7 +45387,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -39724,7 +45692,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/p-interfaces">/p-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/p-interfaces">/p-interfaces</a>
</div>
</div>
</div>
@@ -39909,7 +45877,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/p-interface">/p-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/p-interface">/p-interface</a>
</div>
</div>
</div>
@@ -39956,7 +45924,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>p-interface object that needs to be created or updated</p>
+ <p><p>p-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -40043,6 +46011,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing p-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing p-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>p-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/p-interface">/p-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing p-interface</div>
@@ -40308,7 +46381,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -40554,7 +46627,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -40601,7 +46674,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -40704,6 +46777,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -41107,7 +47301,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -41154,7 +47348,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -41273,6 +47467,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -41432,7 +47763,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -41954,7 +48285,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -42001,7 +48332,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -42120,6 +48451,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -42279,7 +48747,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -42541,7 +49009,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -42970,7 +49438,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -43292,7 +49760,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -43339,7 +49807,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -43458,6 +49926,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -43617,7 +50222,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -44078,7 +50683,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -44370,7 +50975,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -44417,7 +51022,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -44536,6 +51141,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -45001,7 +51743,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -45048,7 +51790,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -45183,6 +51925,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -45358,7 +52253,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -45958,7 +52853,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -46005,7 +52900,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -46140,6 +53035,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ hostname
+ </td>
+ <td>
+ <p>Value from executing hostname on the compute node.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--cloud-infrastructure-pservers-pserver--hostname--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -46315,7 +53363,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -46609,7 +53657,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -46871,7 +53919,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -47069,7 +54117,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserver.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -47252,7 +54300,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/virtual-data-centers">/virtual-data-centers</a>
+ <a class="json-schema-ref" href="#/getDefinitions/virtual-data-centers">/virtual-data-centers</a>
</div>
</div>
</div>
@@ -47362,7 +54410,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/virtual-data-center">/virtual-data-center</a>
+ <a class="json-schema-ref" href="#/getDefinitions/virtual-data-center">/virtual-data-center</a>
</div>
</div>
</div>
@@ -47409,7 +54457,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>virtual-data-center object that needs to be created or updated</p>
+ <p><p>virtual-data-center object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureVirtualDataCentersVirtualDataCenter.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -47480,6 +54528,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--"></span>
+ <div id="operation--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing virtual-data-center</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}</strong></h3>
+ Tags:
+ <a href="#tag-CloudInfrastructure">CloudInfrastructure</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing virtual-data-center</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>virtual-data-center object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/virtual-data-center">/virtual-data-center</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vdc-id
+ </td>
+ <td>
+ <p>Unique ID of the vdc</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--"></span>
<div id="operation--cloud-infrastructure-virtual-data-centers-virtual-data-center--vdc-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing virtual-data-center</div>
@@ -47591,7 +54728,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureVirtualDataCentersVirtualDataCenter.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -47774,7 +54911,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/generic-vnfs">/generic-vnfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/generic-vnfs">/generic-vnfs</a>
</div>
</div>
</div>
@@ -48062,7 +55199,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/generic-vnf">/generic-vnf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/generic-vnf">/generic-vnf</a>
</div>
</div>
</div>
@@ -48109,7 +55246,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>generic-vnf object that needs to be created or updated</p>
+ <p><p>generic-vnf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -48180,6 +55317,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing generic-vnf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing generic-vnf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>generic-vnf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/generic-vnf">/generic-vnf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing generic-vnf</div>
@@ -48532,7 +55758,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/entitlements">/entitlements</a>
+ <a class="json-schema-ref" href="#/getDefinitions/entitlements">/entitlements</a>
</div>
</div>
</div>
@@ -48852,7 +56078,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/entitlement">/entitlement</a>
+ <a class="json-schema-ref" href="#/getDefinitions/entitlement">/entitlement</a>
</div>
</div>
</div>
@@ -48899,7 +56125,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>entitlement object that needs to be created or updated</p>
+ <p><p>entitlement object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfEntitlementsEntitlement.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -49002,6 +56228,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing entitlement</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/entitlements/entitlement/{group-uuid}/{resource-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing entitlement</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>entitlement object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/entitlement">/entitlement</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ group-uuid
+ </td>
+ <td>
+ <p>Unique ID for the entitlement group the resource comes from, should be uuid.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ resource-uuid
+ </td>
+ <td>
+ <p>Unique ID of an entitlement resource.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing entitlement</div>
@@ -49145,7 +56492,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfEntitlementsEntitlement.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -49616,7 +56963,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -49965,7 +57312,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -50012,7 +57359,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -50099,6 +57446,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -50589,7 +58041,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -50636,7 +58088,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -50739,6 +58191,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -50882,7 +58455,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -51475,7 +59048,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -51522,7 +59095,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -51625,6 +59198,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -51768,7 +59462,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -51998,7 +59692,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -52498,7 +60192,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -52923,7 +60617,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -52970,7 +60664,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -53073,6 +60767,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -53216,7 +61031,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -53748,7 +61563,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -54143,7 +61958,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -54190,7 +62005,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -54293,6 +62108,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -54845,7 +62781,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -54892,7 +62828,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -55011,6 +62947,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -55170,7 +63243,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -55841,7 +63914,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -55888,7 +63961,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -56007,6 +64080,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -56166,7 +64376,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -56428,7 +64638,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -56899,7 +65109,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interfaces">/lag-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interfaces">/lag-interfaces</a>
</div>
</div>
</div>
@@ -57233,7 +65443,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interface">/lag-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interface">/lag-interface</a>
</div>
</div>
</div>
@@ -57280,7 +65490,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>lag-interface object that needs to be created or updated</p>
+ <p><p>lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -57367,6 +65577,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing lag-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing lag-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>lag-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/lag-interface">/lag-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing lag-interface</div>
@@ -57781,7 +66096,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -58176,7 +66491,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -58223,7 +66538,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -58326,6 +66641,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -58878,7 +67314,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -58925,7 +67361,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -59044,6 +67480,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -59203,7 +67776,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -59874,7 +68447,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -59921,7 +68494,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -60040,6 +68613,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -60199,7 +68909,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -60461,7 +69171,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -61039,7 +69749,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -61510,7 +70220,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -61557,7 +70267,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -61676,6 +70386,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -61835,7 +70682,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -62445,7 +71292,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -62886,7 +71733,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -62933,7 +71780,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -63052,6 +71899,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -63666,7 +72650,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -63713,7 +72697,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -63848,6 +72832,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -64023,7 +73160,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -64772,7 +73909,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -64819,7 +73956,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -64954,6 +74091,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -65129,7 +74419,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -65423,7 +74713,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -65685,7 +74975,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -66124,7 +75414,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/licenses">/licenses</a>
+ <a class="json-schema-ref" href="#/getDefinitions/licenses">/licenses</a>
</div>
</div>
</div>
@@ -66444,7 +75734,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/license">/license</a>
+ <a class="json-schema-ref" href="#/getDefinitions/license">/license</a>
</div>
</div>
</div>
@@ -66491,7 +75781,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>license object that needs to be created or updated</p>
+ <p><p>license object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLicensesLicense.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -66594,6 +75884,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--licenses-license--group-uuid---resource-uuid--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--licenses-license--group-uuid---resource-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing license</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/licenses/license/{group-uuid}/{resource-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing license</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>license object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/license">/license</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ group-uuid
+ </td>
+ <td>
+ <p>Unique ID for the license group the resource belongs to, should be uuid.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ resource-uuid
+ </td>
+ <td>
+ <p>Unique ID of a license resource.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--licenses-license--group-uuid---resource-uuid--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--licenses-license--group-uuid---resource-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing license</div>
@@ -66737,7 +76148,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLicensesLicense.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -66967,7 +76378,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -67374,7 +76785,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vf-modules">/vf-modules</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vf-modules">/vf-modules</a>
</div>
</div>
</div>
@@ -67783,7 +77194,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vf-module">/vf-module</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vf-module">/vf-module</a>
</div>
</div>
</div>
@@ -67830,7 +77241,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vf-module object that needs to be created or updated</p>
+ <p><p>vf-module object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfVfModulesVfModule.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -67917,6 +77328,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-generic-vnfs-generic-vnf--vnf-id--vf-modules-vf-module--vf-module-id--"></span>
+ <div id="operation--network-generic-vnfs-generic-vnf--vnf-id--vf-modules-vf-module--vf-module-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vf-module</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/generic-vnfs/generic-vnf/{vnf-id}/vf-modules/vf-module/{vf-module-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vf-module</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vf-module object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vf-module">/vf-module</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vf-module-id
+ </td>
+ <td>
+ <p>Unique ID of vf-module.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-generic-vnfs-generic-vnf--vnf-id--vf-modules-vf-module--vf-module-id--"></span>
<div id="operation--network-generic-vnfs-generic-vnf--vnf-id--vf-modules-vf-module--vf-module-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vf-module</div>
@@ -68044,7 +77560,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfVfModulesVfModule.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -68259,7 +77775,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/instance-groups">/instance-groups</a>
+ <a class="json-schema-ref" href="#/getDefinitions/instance-groups">/instance-groups</a>
</div>
</div>
</div>
@@ -68399,7 +77915,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/instance-group">/instance-group</a>
+ <a class="json-schema-ref" href="#/getDefinitions/instance-group">/instance-group</a>
</div>
</div>
</div>
@@ -68446,7 +77962,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>instance-group object that needs to be created or updated</p>
+ <p><p>instance-group object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkInstanceGroupsInstanceGroup.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -68517,6 +78033,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-instance-groups-instance-group--id--"></span>
+ <div id="operation--network-instance-groups-instance-group--id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing instance-group</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/instance-groups/instance-group/{id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing instance-group</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>instance-group object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/instance-group">/instance-group</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ id
+ </td>
+ <td>
+ <p>Instance Group ID, UUID assigned to this instance.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-instance-groups-instance-group--id--"></span>
<div id="operation--network-instance-groups-instance-group--id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing instance-group</div>
@@ -68628,7 +78233,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkInstanceGroupsInstanceGroup.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -68811,7 +78416,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/ipsec-configurations">/ipsec-configurations</a>
+ <a class="json-schema-ref" href="#/getDefinitions/ipsec-configurations">/ipsec-configurations</a>
</div>
</div>
</div>
@@ -68906,7 +78511,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/ipsec-configuration">/ipsec-configuration</a>
+ <a class="json-schema-ref" href="#/getDefinitions/ipsec-configuration">/ipsec-configuration</a>
</div>
</div>
</div>
@@ -68953,7 +78558,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>ipsec-configuration object that needs to be created or updated</p>
+ <p><p>ipsec-configuration object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkIpsecConfigurationsIpsecConfiguration.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -69024,6 +78629,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--"></span>
+ <div id="operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing ipsec-configuration</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing ipsec-configuration</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>ipsec-configuration object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/ipsec-configuration">/ipsec-configuration</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ ipsec-configuration-id
+ </td>
+ <td>
+ <p>UUID of this configuration</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--"></span>
<div id="operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing ipsec-configuration</div>
@@ -69135,7 +78829,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkIpsecConfigurationsIpsecConfiguration.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -69349,7 +79043,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vig-servers">/vig-servers</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vig-servers">/vig-servers</a>
</div>
</div>
</div>
@@ -69460,7 +79154,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vig-server">/vig-server</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vig-server">/vig-server</a>
</div>
</div>
</div>
@@ -69507,7 +79201,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vig-server object that needs to be created or updated</p>
+ <p><p>vig-server object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -69594,6 +79288,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--vig-servers-vig-server--vig-address-type--"></span>
+ <div id="operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--vig-servers-vig-server--vig-address-type--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vig-server</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}/vig-servers/vig-server/{vig-address-type}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vig-server</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vig-server object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vig-server">/vig-server</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ ipsec-configuration-id
+ </td>
+ <td>
+ <p>UUID of this configuration</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vig-address-type
+ </td>
+ <td>
+ <p>indicates whether the VIG is for AVPN or INTERNET</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--vig-servers-vig-server--vig-address-type--"></span>
<div id="operation--network-ipsec-configurations-ipsec-configuration--ipsec-configuration-id--vig-servers-vig-server--vig-address-type--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vig-server</div>
@@ -69721,7 +79520,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -69936,7 +79735,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-networks">/l3-networks</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-networks">/l3-networks</a>
</div>
</div>
</div>
@@ -70166,7 +79965,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-network">/l3-network</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-network">/l3-network</a>
</div>
</div>
</div>
@@ -70213,7 +80012,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-network object that needs to be created or updated</p>
+ <p><p>l3-network object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkL3NetworksL3Network.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -70284,6 +80083,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-l3-networks-l3-network--network-id--"></span>
+ <div id="operation--network-l3-networks-l3-network--network-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-network</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/l3-networks/l3-network/{network-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-network</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-network object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-network">/l3-network</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ network-id
+ </td>
+ <td>
+ <p>Network ID, should be uuid. Unique across A&AI.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-l3-networks-l3-network--network-id--"></span>
<div id="operation--network-l3-networks-l3-network--network-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-network</div>
@@ -70578,7 +80466,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/ctag-assignments">/ctag-assignments</a>
+ <a class="json-schema-ref" href="#/getDefinitions/ctag-assignments">/ctag-assignments</a>
</div>
</div>
</div>
@@ -70824,7 +80712,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/ctag-assignment">/ctag-assignment</a>
+ <a class="json-schema-ref" href="#/getDefinitions/ctag-assignment">/ctag-assignment</a>
</div>
</div>
</div>
@@ -70871,7 +80759,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>ctag-assignment object that needs to be created or updated</p>
+ <p><p>ctag-assignment object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -70958,6 +80846,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-l3-networks-l3-network--network-id--ctag-assignments-ctag-assignment--vlan-id-inner--"></span>
+ <div id="operation--network-l3-networks-l3-network--network-id--ctag-assignments-ctag-assignment--vlan-id-inner--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing ctag-assignment</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/l3-networks/l3-network/{network-id}/ctag-assignments/ctag-assignment/{vlan-id-inner}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing ctag-assignment</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>ctag-assignment object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/ctag-assignment">/ctag-assignment</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ network-id
+ </td>
+ <td>
+ <p>Network ID, should be uuid. Unique across A&AI.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-id-inner
+ </td>
+ <td>
+ <p>id.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-l3-networks-l3-network--network-id--ctag-assignments-ctag-assignment--vlan-id-inner--"></span>
<div id="operation--network-l3-networks-l3-network--network-id--ctag-assignments-ctag-assignment--vlan-id-inner--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing ctag-assignment</div>
@@ -71085,7 +81078,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -71283,7 +81276,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkL3NetworksL3Network.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -71632,7 +81625,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/segmentation-assignments">/segmentation-assignments</a>
+ <a class="json-schema-ref" href="#/getDefinitions/segmentation-assignments">/segmentation-assignments</a>
</div>
</div>
</div>
@@ -71878,7 +81871,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/segmentation-assignment">/segmentation-assignment</a>
+ <a class="json-schema-ref" href="#/getDefinitions/segmentation-assignment">/segmentation-assignment</a>
</div>
</div>
</div>
@@ -71925,7 +81918,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>segmentation-assignment object that needs to be created or updated</p>
+ <p><p>segmentation-assignment object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -72012,6 +82005,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-l3-networks-l3-network--network-id--segmentation-assignments-segmentation-assignment--segmentation-id--"></span>
+ <div id="operation--network-l3-networks-l3-network--network-id--segmentation-assignments-segmentation-assignment--segmentation-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing segmentation-assignment</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/l3-networks/l3-network/{network-id}/segmentation-assignments/segmentation-assignment/{segmentation-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing segmentation-assignment</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>segmentation-assignment object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/segmentation-assignment">/segmentation-assignment</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ network-id
+ </td>
+ <td>
+ <p>Network ID, should be uuid. Unique across A&AI.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ segmentation-id
+ </td>
+ <td>
+ <p>Route Table Reference id, UUID assigned to this instance.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-l3-networks-l3-network--network-id--segmentation-assignments-segmentation-assignment--segmentation-id--"></span>
<div id="operation--network-l3-networks-l3-network--network-id--segmentation-assignments-segmentation-assignment--segmentation-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing segmentation-assignment</div>
@@ -72139,7 +82237,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -72520,7 +82618,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/subnets">/subnets</a>
+ <a class="json-schema-ref" href="#/getDefinitions/subnets">/subnets</a>
</div>
</div>
</div>
@@ -72781,7 +82879,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/subnet">/subnet</a>
+ <a class="json-schema-ref" href="#/getDefinitions/subnet">/subnet</a>
</div>
</div>
</div>
@@ -72828,7 +82926,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>subnet object that needs to be created or updated</p>
+ <p><p>subnet object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkL3NetworksL3NetworkSubnetsSubnet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -72915,6 +83013,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-l3-networks-l3-network--network-id--subnets-subnet--subnet-id--"></span>
+ <div id="operation--network-l3-networks-l3-network--network-id--subnets-subnet--subnet-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing subnet</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/l3-networks/l3-network/{network-id}/subnets/subnet/{subnet-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing subnet</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>subnet object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/subnet">/subnet</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ network-id
+ </td>
+ <td>
+ <p>Network ID, should be uuid. Unique across A&AI.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ subnet-id
+ </td>
+ <td>
+ <p>Subnet ID, should be UUID.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-l3-networks-l3-network--network-id--subnets-subnet--subnet-id--"></span>
<div id="operation--network-l3-networks-l3-network--network-id--subnets-subnet--subnet-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing subnet</div>
@@ -73042,7 +83245,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkL3NetworksL3NetworkSubnetsSubnet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -73257,7 +83460,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-links">/lag-links</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-links">/lag-links</a>
</div>
</div>
</div>
@@ -73352,7 +83555,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-link">/lag-link</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-link">/lag-link</a>
</div>
</div>
</div>
@@ -73399,7 +83602,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>lag-link object that needs to be created or updated</p>
+ <p><p>lag-link object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkLagLinksLagLink.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -73470,6 +83673,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-lag-links-lag-link--link-name--"></span>
+ <div id="operation--network-lag-links-lag-link--link-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing lag-link</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/lag-links/lag-link/{link-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing lag-link</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>lag-link object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/lag-link">/lag-link</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ link-name
+ </td>
+ <td>
+ <p>Alphabetical concatenation of lag-interface names</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-lag-links-lag-link--link-name--"></span>
<div id="operation--network-lag-links-lag-link--link-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing lag-link</div>
@@ -73581,7 +83873,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkLagLinksLagLink.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -73764,7 +84056,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/logical-links">/logical-links</a>
+ <a class="json-schema-ref" href="#/getDefinitions/logical-links">/logical-links</a>
</div>
</div>
</div>
@@ -73979,7 +84271,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/logical-link">/logical-link</a>
+ <a class="json-schema-ref" href="#/getDefinitions/logical-link">/logical-link</a>
</div>
</div>
</div>
@@ -74026,7 +84318,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>logical-link object that needs to be created or updated</p>
+ <p><p>logical-link object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkLogicalLinksLogicalLink.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -74097,6 +84389,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-logical-links-logical-link--link-name--"></span>
+ <div id="operation--network-logical-links-logical-link--link-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing logical-link</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/logical-links/logical-link/{link-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing logical-link</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>logical-link object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/logical-link">/logical-link</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ link-name
+ </td>
+ <td>
+ <p>e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-logical-links-logical-link--link-name--"></span>
<div id="operation--network-logical-links-logical-link--link-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing logical-link</div>
@@ -74208,7 +84589,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkLogicalLinksLogicalLink.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -74391,7 +84772,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/multicast-configurations">/multicast-configurations</a>
+ <a class="json-schema-ref" href="#/getDefinitions/multicast-configurations">/multicast-configurations</a>
</div>
</div>
</div>
@@ -74486,7 +84867,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/multicast-configuration">/multicast-configuration</a>
+ <a class="json-schema-ref" href="#/getDefinitions/multicast-configuration">/multicast-configuration</a>
</div>
</div>
</div>
@@ -74533,7 +84914,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>multicast-configuration object that needs to be created or updated</p>
+ <p><p>multicast-configuration object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkMulticastConfigurationsMulticastConfiguration.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -74604,6 +84985,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-multicast-configurations-multicast-configuration--multicast-configuration-id--"></span>
+ <div id="operation--network-multicast-configurations-multicast-configuration--multicast-configuration-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing multicast-configuration</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/multicast-configurations/multicast-configuration/{multicast-configuration-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing multicast-configuration</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>multicast-configuration object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/multicast-configuration">/multicast-configuration</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ multicast-configuration-id
+ </td>
+ <td>
+ <p>Unique id of multicast configuration.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-multicast-configurations-multicast-configuration--multicast-configuration-id--"></span>
<div id="operation--network-multicast-configurations-multicast-configuration--multicast-configuration-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing multicast-configuration</div>
@@ -74715,7 +85185,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkMulticastConfigurationsMulticastConfiguration.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -74898,7 +85368,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/network-policies">/network-policies</a>
+ <a class="json-schema-ref" href="#/getDefinitions/network-policies">/network-policies</a>
</div>
</div>
</div>
@@ -75008,7 +85478,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/network-policy">/network-policy</a>
+ <a class="json-schema-ref" href="#/getDefinitions/network-policy">/network-policy</a>
</div>
</div>
</div>
@@ -75055,7 +85525,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>network-policy object that needs to be created or updated</p>
+ <p><p>network-policy object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNetworkPoliciesNetworkPolicy.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -75126,6 +85596,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-network-policies-network-policy--network-policy-id--"></span>
+ <div id="operation--network-network-policies-network-policy--network-policy-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing network-policy</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/network-policies/network-policy/{network-policy-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing network-policy</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>network-policy object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/network-policy">/network-policy</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ network-policy-id
+ </td>
+ <td>
+ <p>UUID representing unique key to this instance</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-network-policies-network-policy--network-policy-id--"></span>
<div id="operation--network-network-policies-network-policy--network-policy-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing network-policy</div>
@@ -75237,7 +85796,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNetworkPoliciesNetworkPolicy.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -75420,7 +85979,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/newvces">/newvces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/newvces">/newvces</a>
</div>
</div>
</div>
@@ -75590,7 +86149,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/newvce">/newvce</a>
+ <a class="json-schema-ref" href="#/getDefinitions/newvce">/newvce</a>
</div>
</div>
</div>
@@ -75637,7 +86196,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>newvce object that needs to be created or updated</p>
+ <p><p>newvce object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvce.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -75708,6 +86267,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing newvce</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing newvce</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>newvce object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/newvce">/newvce</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing newvce</div>
@@ -75942,7 +86590,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -76173,7 +86821,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -76220,7 +86868,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -76307,6 +86955,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -76679,7 +87432,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -76726,7 +87479,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -76829,6 +87582,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -76972,7 +87846,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -77447,7 +88321,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -77494,7 +88368,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -77597,6 +88471,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -77740,7 +88735,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -77970,7 +88965,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -78352,7 +89347,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -78659,7 +89654,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -78706,7 +89701,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -78809,6 +89804,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -78952,7 +90068,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -79366,7 +90482,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -79643,7 +90759,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -79690,7 +90806,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -79793,6 +90909,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -80227,7 +91464,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -80274,7 +91511,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -80393,6 +91630,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -80552,7 +91926,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -81105,7 +92479,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -81152,7 +92526,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -81271,6 +92645,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id2
+ </td>
+ <td>
+ <p>Unique id of VNF, can't use same attribute name right now until we promote this new object</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-newvces-newvce--vnf-id2--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -81430,7 +92941,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -81692,7 +93203,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -81922,7 +93433,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvce.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -82105,7 +93616,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/physical-links">/physical-links</a>
+ <a class="json-schema-ref" href="#/getDefinitions/physical-links">/physical-links</a>
</div>
</div>
</div>
@@ -82215,7 +93726,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/physical-link">/physical-link</a>
+ <a class="json-schema-ref" href="#/getDefinitions/physical-link">/physical-link</a>
</div>
</div>
</div>
@@ -82262,7 +93773,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>physical-link object that needs to be created or updated</p>
+ <p><p>physical-link object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPhysicalLinksPhysicalLink.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -82333,6 +93844,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-physical-links-physical-link--link-name--"></span>
+ <div id="operation--network-physical-links-physical-link--link-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing physical-link</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/physical-links/physical-link/{link-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing physical-link</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>physical-link object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/physical-link">/physical-link</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ link-name
+ </td>
+ <td>
+ <p>e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-physical-links-physical-link--link-name--"></span>
<div id="operation--network-physical-links-physical-link--link-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing physical-link</div>
@@ -82444,7 +94044,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPhysicalLinksPhysicalLink.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -82627,7 +94227,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/pnfs">/pnfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/pnfs">/pnfs</a>
</div>
</div>
</div>
@@ -82737,7 +94337,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/pnf">/pnf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/pnf">/pnf</a>
</div>
</div>
</div>
@@ -82784,7 +94384,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>pnf object that needs to be created or updated</p>
+ <p><p>pnf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -82855,6 +94455,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing pnf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing pnf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>pnf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/pnf">/pnf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing pnf</div>
@@ -83029,7 +94718,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interfaces">/lag-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interfaces">/lag-interfaces</a>
</div>
</div>
</div>
@@ -83185,7 +94874,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interface">/lag-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interface">/lag-interface</a>
</div>
</div>
</div>
@@ -83232,7 +94921,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>lag-interface object that needs to be created or updated</p>
+ <p><p>lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -83319,6 +95008,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing lag-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing lag-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>lag-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/lag-interface">/lag-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing lag-interface</div>
@@ -83555,7 +95349,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -83772,7 +95566,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -83819,7 +95613,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -83922,6 +95716,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -84296,7 +96211,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -84343,7 +96258,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -84462,6 +96377,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -84621,7 +96673,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -85114,7 +97166,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -85161,7 +97213,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -85280,6 +97332,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -85439,7 +97628,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -85701,7 +97890,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -86101,7 +98290,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -86394,7 +98583,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -86441,7 +98630,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -86560,6 +98749,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -86719,7 +99045,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -87151,7 +99477,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -87414,7 +99740,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -87461,7 +99787,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -87580,6 +99906,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -88016,7 +100479,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -88063,7 +100526,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -88198,6 +100661,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -88373,7 +100989,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -88944,7 +101560,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -88991,7 +101607,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -89126,6 +101742,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -89301,7 +102070,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -89595,7 +102364,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -89857,7 +102626,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -90118,7 +102887,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/p-interfaces">/p-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/p-interfaces">/p-interfaces</a>
</div>
</div>
</div>
@@ -90259,7 +103028,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/p-interface">/p-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/p-interface">/p-interface</a>
</div>
</div>
</div>
@@ -90306,7 +103075,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>p-interface object that needs to be created or updated</p>
+ <p><p>p-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -90393,6 +103162,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing p-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing p-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>p-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/p-interface">/p-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing p-interface</div>
@@ -90614,7 +103488,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -90816,7 +103690,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -90863,7 +103737,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -90966,6 +103840,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -91325,7 +104320,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -91372,7 +104367,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -91491,6 +104486,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -91650,7 +104782,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -92128,7 +105260,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -92175,7 +105307,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -92294,6 +105426,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -92453,7 +105722,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -92715,7 +105984,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -93100,7 +106369,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -93378,7 +106647,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -93425,7 +106694,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -93544,6 +106813,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -93703,7 +107109,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -94120,7 +107526,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -94368,7 +107774,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -94415,7 +107821,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -94534,6 +107940,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -94955,7 +108498,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -95002,7 +108545,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -95137,6 +108680,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -95312,7 +109008,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -95868,7 +109564,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -95915,7 +109611,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -96050,6 +109746,159 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ pnf-name
+ </td>
+ <td>
+ <p>unique name of Physical Network Function.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-pnfs-pnf--pnf-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -96225,7 +110074,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -96519,7 +110368,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -96781,7 +110630,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -96979,7 +110828,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -97162,7 +111011,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/route-table-references">/route-table-references</a>
+ <a class="json-schema-ref" href="#/getDefinitions/route-table-references">/route-table-references</a>
</div>
</div>
</div>
@@ -97272,7 +111121,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/route-table-reference">/route-table-reference</a>
+ <a class="json-schema-ref" href="#/getDefinitions/route-table-reference">/route-table-reference</a>
</div>
</div>
</div>
@@ -97319,7 +111168,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>route-table-reference object that needs to be created or updated</p>
+ <p><p>route-table-reference object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkRouteTableReferencesRouteTableReference.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -97390,6 +111239,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-route-table-references-route-table-reference--route-table-reference-id--"></span>
+ <div id="operation--network-route-table-references-route-table-reference--route-table-reference-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing route-table-reference</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/route-table-references/route-table-reference/{route-table-reference-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing route-table-reference</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>route-table-reference object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/route-table-reference">/route-table-reference</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ route-table-reference-id
+ </td>
+ <td>
+ <p>Route Table Reference id, UUID assigned to this instance.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-route-table-references-route-table-reference--route-table-reference-id--"></span>
<div id="operation--network-route-table-references-route-table-reference--route-table-reference-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing route-table-reference</div>
@@ -97501,7 +111439,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkRouteTableReferencesRouteTableReference.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -97684,7 +111622,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/site-pair-sets">/site-pair-sets</a>
+ <a class="json-schema-ref" href="#/getDefinitions/site-pair-sets">/site-pair-sets</a>
</div>
</div>
</div>
@@ -97779,7 +111717,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/site-pair-set">/site-pair-set</a>
+ <a class="json-schema-ref" href="#/getDefinitions/site-pair-set">/site-pair-set</a>
</div>
</div>
</div>
@@ -97826,7 +111764,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>site-pair-set object that needs to be created or updated</p>
+ <p><p>site-pair-set object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkSitePairSetsSitePairSet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -97897,6 +111835,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--"></span>
+ <div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing site-pair-set</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/site-pair-sets/site-pair-set/{site-pair-set-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing site-pair-set</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>site-pair-set object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/site-pair-set">/site-pair-set</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ site-pair-set-id
+ </td>
+ <td>
+ <p>Unique id of site pair set.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--"></span>
<div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing site-pair-set</div>
@@ -98008,7 +112035,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkSitePairSetsSitePairSet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -98222,7 +112249,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/routing-instances">/routing-instances</a>
+ <a class="json-schema-ref" href="#/getDefinitions/routing-instances">/routing-instances</a>
</div>
</div>
</div>
@@ -98333,7 +112360,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/routing-instance">/routing-instance</a>
+ <a class="json-schema-ref" href="#/getDefinitions/routing-instance">/routing-instance</a>
</div>
</div>
</div>
@@ -98380,7 +112407,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>routing-instance object that needs to be created or updated</p>
+ <p><p>routing-instance object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -98467,6 +112494,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--"></span>
+ <div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing routing-instance</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing routing-instance</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>routing-instance object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/routing-instance">/routing-instance</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ site-pair-set-id
+ </td>
+ <td>
+ <p>Unique id of site pair set.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ routing-instance-id
+ </td>
+ <td>
+ <p>Unique id of routing instance</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--"></span>
<div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing routing-instance</div>
@@ -98594,7 +112726,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -98856,7 +112988,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/site-pairs">/site-pairs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/site-pairs">/site-pairs</a>
</div>
</div>
</div>
@@ -98983,7 +113115,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/site-pair">/site-pair</a>
+ <a class="json-schema-ref" href="#/getDefinitions/site-pair">/site-pair</a>
</div>
</div>
</div>
@@ -99030,7 +113162,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>site-pair object that needs to be created or updated</p>
+ <p><p>site-pair object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -99133,6 +113265,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--"></span>
+ <div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing site-pair</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing site-pair</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>site-pair object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/site-pair">/site-pair</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ site-pair-set-id
+ </td>
+ <td>
+ <p>Unique id of site pair set.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ routing-instance-id
+ </td>
+ <td>
+ <p>Unique id of routing instance</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ site-pair-id
+ </td>
+ <td>
+ <p>unique identifier of probe</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--"></span>
<div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing site-pair</div>
@@ -99356,7 +113609,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/classes-of-service">/classes-of-service</a>
+ <a class="json-schema-ref" href="#/getDefinitions/classes-of-service">/classes-of-service</a>
</div>
</div>
</div>
@@ -99499,7 +113752,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/class-of-service">/class-of-service</a>
+ <a class="json-schema-ref" href="#/getDefinitions/class-of-service">/class-of-service</a>
</div>
</div>
</div>
@@ -99546,7 +113799,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>class-of-service object that needs to be created or updated</p>
+ <p><p>class-of-service object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -99665,6 +113918,143 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--classes-of-service-class-of-service--cos--"></span>
+ <div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--classes-of-service-class-of-service--cos--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing class-of-service</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}/classes-of-service/class-of-service/{cos}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing class-of-service</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>class-of-service object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/class-of-service">/class-of-service</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ site-pair-set-id
+ </td>
+ <td>
+ <p>Unique id of site pair set.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ routing-instance-id
+ </td>
+ <td>
+ <p>Unique id of routing instance</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ site-pair-id
+ </td>
+ <td>
+ <p>unique identifier of probe</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cos
+ </td>
+ <td>
+ <p>unique identifier of probe</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--classes-of-service-class-of-service--cos--"></span>
<div id="operation--network-site-pair-sets-site-pair-set--site-pair-set-id--routing-instances-routing-instance--routing-instance-id--site-pairs-site-pair--site-pair-id--classes-of-service-class-of-service--cos--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing class-of-service</div>
@@ -99824,7 +114214,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -100086,7 +114476,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -100333,7 +114723,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vces">/vces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vces">/vces</a>
</div>
</div>
</div>
@@ -100548,7 +114938,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vce">/vce</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vce">/vce</a>
</div>
</div>
</div>
@@ -100595,7 +114985,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vce object that needs to be created or updated</p>
+ <p><p>vce object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVcesVce.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -100666,6 +115056,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vces-vce--vnf-id--"></span>
+ <div id="operation--network-vces-vce--vnf-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vce</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vces/vce/{vnf-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vce</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vce object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vce">/vce</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vces-vce--vnf-id--"></span>
<div id="operation--network-vces-vce--vnf-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vce</div>
@@ -100945,7 +115424,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/entitlements">/entitlements</a>
+ <a class="json-schema-ref" href="#/getDefinitions/entitlements">/entitlements</a>
</div>
</div>
</div>
@@ -101192,7 +115671,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/entitlement">/entitlement</a>
+ <a class="json-schema-ref" href="#/getDefinitions/entitlement">/entitlement</a>
</div>
</div>
</div>
@@ -101239,7 +115718,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>entitlement object that needs to be created or updated</p>
+ <p><p>entitlement object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVcesVceEntitlementsEntitlement.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -101342,6 +115821,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vces-vce--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--"></span>
+ <div id="operation--network-vces-vce--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing entitlement</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vces/vce/{vnf-id}/entitlements/entitlement/{group-uuid}/{resource-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing entitlement</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>entitlement object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/entitlement">/entitlement</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ group-uuid
+ </td>
+ <td>
+ <p>Unique ID for the entitlement group the resource comes from, should be uuid.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ resource-uuid
+ </td>
+ <td>
+ <p>Unique ID of an entitlement resource.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vces-vce--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--"></span>
<div id="operation--network-vces-vce--vnf-id--entitlements-entitlement--group-uuid---resource-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing entitlement</div>
@@ -101485,7 +116085,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVcesVceEntitlementsEntitlement.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -101883,7 +116483,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/licenses">/licenses</a>
+ <a class="json-schema-ref" href="#/getDefinitions/licenses">/licenses</a>
</div>
</div>
</div>
@@ -102130,7 +116730,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/license">/license</a>
+ <a class="json-schema-ref" href="#/getDefinitions/license">/license</a>
</div>
</div>
</div>
@@ -102177,7 +116777,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>license object that needs to be created or updated</p>
+ <p><p>license object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVcesVceLicensesLicense.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -102280,6 +116880,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vces-vce--vnf-id--licenses-license--group-uuid---resource-uuid--"></span>
+ <div id="operation--network-vces-vce--vnf-id--licenses-license--group-uuid---resource-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing license</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vces/vce/{vnf-id}/licenses/license/{group-uuid}/{resource-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing license</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>license object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/license">/license</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ group-uuid
+ </td>
+ <td>
+ <p>Unique ID for the license group the resource belongs to, should be uuid.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ resource-uuid
+ </td>
+ <td>
+ <p>Unique ID of a license resource.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vces-vce--vnf-id--licenses-license--group-uuid---resource-uuid--"></span>
<div id="operation--network-vces-vce--vnf-id--licenses-license--group-uuid---resource-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing license</div>
@@ -102423,7 +117144,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVcesVceLicensesLicense.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -102821,7 +117542,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/port-groups">/port-groups</a>
+ <a class="json-schema-ref" href="#/getDefinitions/port-groups">/port-groups</a>
</div>
</div>
</div>
@@ -103097,7 +117818,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/port-group">/port-group</a>
+ <a class="json-schema-ref" href="#/getDefinitions/port-group">/port-group</a>
</div>
</div>
</div>
@@ -103144,7 +117865,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>port-group object that needs to be created or updated</p>
+ <p><p>port-group object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVcesVcePortGroupsPortGroup.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -103231,6 +117952,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vces-vce--vnf-id--port-groups-port-group--interface-id--"></span>
+ <div id="operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing port-group</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing port-group</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>port-group object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/port-group">/port-group</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-id
+ </td>
+ <td>
+ <p>Unique ID of the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vces-vce--vnf-id--port-groups-port-group--interface-id--"></span>
<div id="operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing port-group</div>
@@ -103587,7 +118413,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/cvlan-tags">/cvlan-tags</a>
+ <a class="json-schema-ref" href="#/getDefinitions/cvlan-tags">/cvlan-tags</a>
</div>
</div>
</div>
@@ -103879,7 +118705,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/cvlan-tag-entry">/cvlan-tag-entry</a>
+ <a class="json-schema-ref" href="#/getDefinitions/cvlan-tag-entry">/cvlan-tag-entry</a>
</div>
</div>
</div>
@@ -103926,7 +118752,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>cvlan-tag-entry object that needs to be created or updated</p>
+ <p><p>cvlan-tag-entry object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -104029,6 +118855,127 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vces-vce--vnf-id--port-groups-port-group--interface-id--cvlan-tags-cvlan-tag-entry--cvlan-tag--"></span>
+ <div id="operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--cvlan-tags-cvlan-tag-entry--cvlan-tag--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing cvlan-tag-entry</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}/cvlan-tags/cvlan-tag-entry/{cvlan-tag}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing cvlan-tag-entry</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>cvlan-tag-entry object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/cvlan-tag-entry">/cvlan-tag-entry</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-id
+ </td>
+ <td>
+ <p>Unique id of VNF. This is unique across the graph.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-id
+ </td>
+ <td>
+ <p>Unique ID of the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ cvlan-tag
+ </td>
+ <td>
+ <p>See mis-na-virtualization-platform.yang</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vces-vce--vnf-id--port-groups-port-group--interface-id--cvlan-tags-cvlan-tag-entry--cvlan-tag--"></span>
<div id="operation--network-vces-vce--vnf-id--port-groups-port-group--interface-id--cvlan-tags-cvlan-tag-entry--cvlan-tag--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing cvlan-tag-entry</div>
@@ -104172,7 +119119,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -104402,7 +119349,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVcesVcePortGroupsPortGroup.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -104600,7 +119547,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVcesVce.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -104783,7 +119730,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vnfcs">/vnfcs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vnfcs">/vnfcs</a>
</div>
</div>
</div>
@@ -104981,7 +119928,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vnfc">/vnfc</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vnfc">/vnfc</a>
</div>
</div>
</div>
@@ -105028,7 +119975,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vnfc object that needs to be created or updated</p>
+ <p><p>vnfc object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVnfcsVnfc.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -105099,6 +120046,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vnfcs-vnfc--vnfc-name--"></span>
+ <div id="operation--network-vnfcs-vnfc--vnfc-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vnfc</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vnfcs/vnfc/{vnfc-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vnfc</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vnfc object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vnfc">/vnfc</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnfc-name
+ </td>
+ <td>
+ <p>Unique ID of vnfc.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vnfcs-vnfc--vnfc-name--"></span>
<div id="operation--network-vnfcs-vnfc--vnfc-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vnfc</div>
@@ -105210,7 +120246,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVnfcsVnfc.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -105393,7 +120429,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vpls-pes">/vpls-pes</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vpls-pes">/vpls-pes</a>
</div>
</div>
</div>
@@ -105502,7 +120538,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vpls-pe">/vpls-pe</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vpls-pe">/vpls-pe</a>
</div>
</div>
</div>
@@ -105549,7 +120585,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vpls-pe object that needs to be created or updated</p>
+ <p><p>vpls-pe object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPe.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -105619,6 +120655,94 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vpls-pe</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vpls-pe</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vpls-pe object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vpls-pe">/vpls-pe</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vpls-pe</div>
@@ -105791,7 +120915,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interfaces">/lag-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interfaces">/lag-interfaces</a>
</div>
</div>
</div>
@@ -105946,7 +121070,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/lag-interface">/lag-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/lag-interface">/lag-interface</a>
</div>
</div>
</div>
@@ -105993,7 +121117,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>lag-interface object that needs to be created or updated</p>
+ <p><p>lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -106079,6 +121203,110 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing lag-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing lag-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>lag-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/lag-interface">/lag-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing lag-interface</div>
@@ -106313,7 +121541,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -106529,7 +121757,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -106576,7 +121804,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -106678,6 +121906,126 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -107050,7 +122398,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -107097,7 +122445,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -107215,6 +122563,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -107373,7 +122857,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -107863,7 +123347,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -107910,7 +123394,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -108028,6 +123512,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -108186,7 +123806,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -108446,7 +124066,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -108843,7 +124463,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -109135,7 +124755,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -109182,7 +124802,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -109300,6 +124920,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -109458,7 +125214,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -109887,7 +125643,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -110149,7 +125905,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -110196,7 +125952,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -110314,6 +126070,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -110748,7 +126640,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -110795,7 +126687,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -110929,6 +126821,158 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -111103,7 +127147,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -111671,7 +127715,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -111718,7 +127762,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -111852,6 +127896,158 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the link aggregate interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--lag-interfaces-lag-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -112026,7 +128222,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -112318,7 +128514,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -112578,7 +128774,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -112836,7 +129032,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/p-interfaces">/p-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/p-interfaces">/p-interfaces</a>
</div>
</div>
</div>
@@ -112976,7 +129172,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/p-interface">/p-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/p-interface">/p-interface</a>
</div>
</div>
</div>
@@ -113023,7 +129219,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>p-interface object that needs to be created or updated</p>
+ <p><p>p-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -113109,6 +129305,110 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing p-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing p-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>p-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/p-interface">/p-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing p-interface</div>
@@ -113328,7 +129628,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interfaces">/l-interfaces</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interfaces">/l-interfaces</a>
</div>
</div>
</div>
@@ -113529,7 +129829,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l-interface">/l-interface</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l-interface">/l-interface</a>
</div>
</div>
</div>
@@ -113576,7 +129876,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l-interface object that needs to be created or updated</p>
+ <p><p>l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -113678,6 +129978,126 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l-interface</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l-interface</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l-interface object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l-interface">/l-interface</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l-interface</div>
@@ -114035,7 +130455,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -114082,7 +130502,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -114200,6 +130620,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -114358,7 +130914,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -114833,7 +131389,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -114880,7 +131436,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -114998,6 +131554,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -115156,7 +131848,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -115416,7 +132108,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -115798,7 +132490,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vfs">/sriov-vfs</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vfs">/sriov-vfs</a>
</div>
</div>
</div>
@@ -116075,7 +132767,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/sriov-vf">/sriov-vf</a>
+ <a class="json-schema-ref" href="#/getDefinitions/sriov-vf">/sriov-vf</a>
</div>
</div>
</div>
@@ -116122,7 +132814,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>sriov-vf object that needs to be created or updated</p>
+ <p><p>sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -116240,6 +132932,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing sriov-vf</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing sriov-vf</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>sriov-vf object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/sriov-vf">/sriov-vf</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ pci-id
+ </td>
+ <td>
+ <p>PCI ID used to identify the sriov-vf</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--sriov-vfs-sriov-vf--pci-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing sriov-vf</div>
@@ -116398,7 +133226,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -116812,7 +133640,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlans">/vlans</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlans">/vlans</a>
</div>
</div>
</div>
@@ -117059,7 +133887,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vlan">/vlan</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vlan">/vlan</a>
</div>
</div>
</div>
@@ -117106,7 +133934,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vlan object that needs to be created or updated</p>
+ <p><p>vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -117224,6 +134052,142 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vlan</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vlan</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vlan object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vlan">/vlan</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vlan</div>
@@ -117643,7 +134607,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
</div>
</div>
</div>
@@ -117690,7 +134654,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv4-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -117824,6 +134788,158 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv4-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv4-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv4-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv4-address-list">/l3-interface-ipv4-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv4-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv4-address-list--l3-interface-ipv4-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv4-address-list</div>
@@ -117998,7 +135114,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -118551,7 +135667,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ <a class="json-schema-ref" href="#/getDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
</div>
</div>
</div>
@@ -118598,7 +135714,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>l3-interface-ipv6-address-list object that needs to be created or updated</p>
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -118732,6 +135848,158 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
+ <div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing l3-interface-ipv6-address-list</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing l3-interface-ipv6-address-list</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>l3-interface-ipv6-address-list object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/l3-interface-ipv6-address-list">/l3-interface-ipv6-address-list</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ equipment-name
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name that identifies the physical interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ interface-name
+ </td>
+ <td>
+ <p>Name given to the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vlan-interface
+ </td>
+ <td>
+ <p>String that identifies the interface</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ l3-interface-ipv6-address
+ </td>
+ <td>
+ <p>IP address</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--"></span>
<div id="operation--network-vpls-pes-vpls-pe--equipment-name--p-interfaces-p-interface--interface-name--l-interfaces-l-interface--interface-name--vlans-vlan--vlan-interface--l3-interface-ipv6-address-list--l3-interface-ipv6-address--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing l3-interface-ipv6-address-list</div>
@@ -118906,7 +136174,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -119198,7 +136466,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -119458,7 +136726,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterface.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -119654,7 +136922,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPe.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -119835,7 +137103,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vpn-bindings">/vpn-bindings</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vpn-bindings">/vpn-bindings</a>
</div>
</div>
</div>
@@ -119975,7 +137243,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vpn-binding">/vpn-binding</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vpn-binding">/vpn-binding</a>
</div>
</div>
</div>
@@ -120022,7 +137290,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vpn-binding object that needs to be created or updated</p>
+ <p><p>vpn-binding object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVpnBindingsVpnBinding.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -120093,6 +137361,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-vpn-bindings-vpn-binding--vpn-id--"></span>
+ <div id="operation--network-vpn-bindings-vpn-binding--vpn-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vpn-binding</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/vpn-bindings/vpn-binding/{vpn-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vpn-binding</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vpn-binding object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vpn-binding">/vpn-binding</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vpn-id
+ </td>
+ <td>
+ <p>VPN ID, globally unique within A&AI</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-vpn-bindings-vpn-binding--vpn-id--"></span>
<div id="operation--network-vpn-bindings-vpn-binding--vpn-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vpn-binding</div>
@@ -120204,7 +137561,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVpnBindingsVpnBinding.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -120387,7 +137744,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/zones">/zones</a>
+ <a class="json-schema-ref" href="#/getDefinitions/zones">/zones</a>
</div>
</div>
</div>
@@ -120512,7 +137869,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/zone">/zone</a>
+ <a class="json-schema-ref" href="#/getDefinitions/zone">/zone</a>
</div>
</div>
</div>
@@ -120559,7 +137916,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>zone object that needs to be created or updated</p>
+ <p><p>zone object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkZonesZone.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -120630,6 +137987,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--network-zones-zone--zone-id--"></span>
+ <div id="operation--network-zones-zone--zone-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing zone</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/network/zones/zone/{zone-id}</strong></h3>
+ Tags:
+ <a href="#tag-Network">Network</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing zone</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>zone object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/zone">/zone</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ zone-id
+ </td>
+ <td>
+ <p>Code assigned by AIC to the zone</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--network-zones-zone--zone-id--"></span>
<div id="operation--network-zones-zone--zone-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing zone</div>
@@ -120741,7 +138187,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkZonesZone.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -120924,7 +138370,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/models">/models</a>
+ <a class="json-schema-ref" href="#/getDefinitions/models">/models</a>
</div>
</div>
</div>
@@ -121034,7 +138480,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/model">/model</a>
+ <a class="json-schema-ref" href="#/getDefinitions/model">/model</a>
</div>
</div>
</div>
@@ -121081,7 +138527,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>model object that needs to be created or updated</p>
+ <p><p>model object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationModelsModel.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -121152,6 +138598,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-models-model--model-invariant-id--"></span>
+ <div id="operation--service-design-and-creation-models-model--model-invariant-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing model</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/models/model/{model-invariant-id}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing model</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>model object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/model">/model</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ model-invariant-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to the main definition of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-models-model--model-invariant-id--"></span>
<div id="operation--service-design-and-creation-models-model--model-invariant-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing model</div>
@@ -121326,7 +138861,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/model-vers">/model-vers</a>
+ <a class="json-schema-ref" href="#/getDefinitions/model-vers">/model-vers</a>
</div>
</div>
</div>
@@ -121482,7 +139017,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/model-ver">/model-ver</a>
+ <a class="json-schema-ref" href="#/getDefinitions/model-ver">/model-ver</a>
</div>
</div>
</div>
@@ -121529,7 +139064,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>model-ver object that needs to be created or updated</p>
+ <p><p>model-ver object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationModelsModelModelVersModelVer.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -121616,6 +139151,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--"></span>
+ <div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing model-ver</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing model-ver</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>model-ver object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/model-ver">/model-ver</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ model-invariant-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to the main definition of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-version-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to one version of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--"></span>
<div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing model-ver</div>
@@ -121852,7 +139492,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadata">/metadata</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadata">/metadata</a>
</div>
</div>
</div>
@@ -122023,7 +139663,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/metadatum">/metadatum</a>
+ <a class="json-schema-ref" href="#/getDefinitions/metadatum">/metadatum</a>
</div>
</div>
</div>
@@ -122070,7 +139710,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>metadatum object that needs to be created or updated</p>
+ <p><p>metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationModelsModelModelVersModelVerMetadataMetadatum.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -122172,6 +139812,126 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--metadata-metadatum--metaname--"></span>
+ <div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--metadata-metadatum--metaname--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing metadatum</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/metadata/metadatum/{metaname}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing metadatum</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>metadatum object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/metadatum">/metadatum</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ model-invariant-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to the main definition of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-version-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to one version of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ metaname
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--metadata-metadatum--metaname--"></span>
<div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--metadata-metadatum--metaname--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing metadatum</div>
@@ -122423,7 +140183,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/model-elements">/model-elements</a>
+ <a class="json-schema-ref" href="#/getDefinitions/model-elements">/model-elements</a>
</div>
</div>
</div>
@@ -122594,7 +140354,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/model-element">/model-element</a>
+ <a class="json-schema-ref" href="#/getDefinitions/model-element">/model-element</a>
</div>
</div>
</div>
@@ -122641,7 +140401,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>model-element object that needs to be created or updated</p>
+ <p><p>model-element object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElement.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -122743,6 +140503,126 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--"></span>
+ <div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing model-element</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing model-element</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>model-element object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/model-element">/model-element</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ model-invariant-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to the main definition of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-version-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to one version of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-element-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--"></span>
<div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing model-element</div>
@@ -123009,7 +140889,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/model-constraints">/model-constraints</a>
+ <a class="json-schema-ref" href="#/getDefinitions/model-constraints">/model-constraints</a>
</div>
</div>
</div>
@@ -123195,7 +141075,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/model-constraint">/model-constraint</a>
+ <a class="json-schema-ref" href="#/getDefinitions/model-constraint">/model-constraint</a>
</div>
</div>
</div>
@@ -123242,7 +141122,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>model-constraint object that needs to be created or updated</p>
+ <p><p>model-constraint object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraint.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -123359,6 +141239,141 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--"></span>
+ <div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing model-constraint</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing model-constraint</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>model-constraint object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/model-constraint">/model-constraint</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ model-invariant-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to the main definition of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-version-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to one version of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-element-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-constraint-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--"></span>
<div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing model-constraint</div>
@@ -123655,7 +141670,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/constrained-element-sets">/constrained-element-sets</a>
+ <a class="json-schema-ref" href="#/getDefinitions/constrained-element-sets">/constrained-element-sets</a>
</div>
</div>
</div>
@@ -123856,7 +141871,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/constrained-element-set">/constrained-element-set</a>
+ <a class="json-schema-ref" href="#/getDefinitions/constrained-element-set">/constrained-element-set</a>
</div>
</div>
</div>
@@ -123903,7 +141918,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>constrained-element-set object that needs to be created or updated</p>
+ <p><p>constrained-element-set object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -124035,6 +142050,156 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--"></span>
+ <div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing constrained-element-set</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing constrained-element-set</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>constrained-element-set object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/constrained-element-set">/constrained-element-set</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ model-invariant-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to the main definition of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-version-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to one version of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-element-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-constraint-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ constrained-element-set-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--"></span>
<div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing constrained-element-set</div>
@@ -124361,7 +142526,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/element-choice-sets">/element-choice-sets</a>
+ <a class="json-schema-ref" href="#/getDefinitions/element-choice-sets">/element-choice-sets</a>
</div>
</div>
</div>
@@ -124577,7 +142742,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/element-choice-set">/element-choice-set</a>
+ <a class="json-schema-ref" href="#/getDefinitions/element-choice-set">/element-choice-set</a>
</div>
</div>
</div>
@@ -124624,7 +142789,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>element-choice-set object that needs to be created or updated</p>
+ <p><p>element-choice-set object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -124771,6 +142936,171 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--element-choice-sets-element-choice-set--element-choice-set-uuid--"></span>
+ <div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--element-choice-sets-element-choice-set--element-choice-set-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing element-choice-set</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}/element-choice-sets/element-choice-set/{element-choice-set-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing element-choice-set</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>element-choice-set object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/element-choice-set">/element-choice-set</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ model-invariant-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to the main definition of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-version-id
+ </td>
+ <td>
+ <p>Unique identifier corresponding to one version of a model in ASDC</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-element-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ model-constraint-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ constrained-element-set-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ element-choice-set-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--element-choice-sets-element-choice-set--element-choice-set-uuid--"></span>
<div id="operation--service-design-and-creation-models-model--model-invariant-id--model-vers-model-ver--model-version-id--model-elements-model-element--model-element-uuid--model-constraints-model-constraint--model-constraint-uuid--constrained-element-sets-constrained-element-set--constrained-element-set-uuid--element-choice-sets-element-choice-set--element-choice-set-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing element-choice-set</div>
@@ -124958,7 +143288,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -125276,7 +143606,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -125564,7 +143894,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElement.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -125792,7 +144122,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationModelsModelModelVersModelVer.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -125990,7 +144320,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationModelsModel.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -126173,7 +144503,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/named-queries">/named-queries</a>
+ <a class="json-schema-ref" href="#/getDefinitions/named-queries">/named-queries</a>
</div>
</div>
</div>
@@ -126281,7 +144611,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/named-query">/named-query</a>
+ <a class="json-schema-ref" href="#/getDefinitions/named-query">/named-query</a>
</div>
</div>
</div>
@@ -126328,7 +144658,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>named-query object that needs to be created or updated</p>
+ <p><p>named-query object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationNamedQueriesNamedQuery.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -126398,6 +144728,94 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--"></span>
+ <div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing named-query</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/named-queries/named-query/{named-query-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing named-query</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>named-query object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/named-query">/named-query</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ named-query-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--"></span>
<div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing named-query</div>
@@ -126569,7 +144987,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/named-query-elements">/named-query-elements</a>
+ <a class="json-schema-ref" href="#/getDefinitions/named-query-elements">/named-query-elements</a>
</div>
</div>
</div>
@@ -126692,7 +145110,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/named-query-element">/named-query-element</a>
+ <a class="json-schema-ref" href="#/getDefinitions/named-query-element">/named-query-element</a>
</div>
</div>
</div>
@@ -126739,7 +145157,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>named-query-element object that needs to be created or updated</p>
+ <p><p>named-query-element object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -126824,6 +145242,109 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--"></span>
+ <div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing named-query-element</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing named-query-element</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>named-query-element object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/named-query-element">/named-query-element</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ named-query-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ named-query-element-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--"></span>
<div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing named-query-element</div>
@@ -127025,7 +145546,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/property-constraints">/property-constraints</a>
+ <a class="json-schema-ref" href="#/getDefinitions/property-constraints">/property-constraints</a>
</div>
</div>
</div>
@@ -127163,7 +145684,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/property-constraint">/property-constraint</a>
+ <a class="json-schema-ref" href="#/getDefinitions/property-constraint">/property-constraint</a>
</div>
</div>
</div>
@@ -127210,7 +145731,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>property-constraint object that needs to be created or updated</p>
+ <p><p>property-constraint object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementPropertyConstraintsPropertyConstraint.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -127310,6 +145831,124 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--property-constraints-property-constraint--property-constraint-uuid--"></span>
+ <div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--property-constraints-property-constraint--property-constraint-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing property-constraint</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/property-constraints/property-constraint/{property-constraint-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing property-constraint</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>property-constraint object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/property-constraint">/property-constraint</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ named-query-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ named-query-element-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ property-constraint-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--property-constraints-property-constraint--property-constraint-uuid--"></span>
<div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--property-constraints-property-constraint--property-constraint-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing property-constraint</div>
@@ -127526,7 +146165,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/related-lookups">/related-lookups</a>
+ <a class="json-schema-ref" href="#/getDefinitions/related-lookups">/related-lookups</a>
</div>
</div>
</div>
@@ -127664,7 +146303,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/related-lookup">/related-lookup</a>
+ <a class="json-schema-ref" href="#/getDefinitions/related-lookup">/related-lookup</a>
</div>
</div>
</div>
@@ -127711,7 +146350,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>related-lookup object that needs to be created or updated</p>
+ <p><p>related-lookup object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -127811,6 +146450,124 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--related-lookups-related-lookup--related-lookup-uuid--"></span>
+ <div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--related-lookups-related-lookup--related-lookup-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing related-lookup</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/related-lookups/related-lookup/{related-lookup-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing related-lookup</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>related-lookup object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/related-lookup">/related-lookup</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ named-query-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ named-query-element-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ related-lookup-uuid
+ </td>
+ <td>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--related-lookups-related-lookup--related-lookup-uuid--"></span>
<div id="operation--service-design-and-creation-named-queries-named-query--named-query-uuid--named-query-elements-named-query-element--named-query-element-uuid--related-lookups-related-lookup--related-lookup-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing related-lookup</div>
@@ -127951,7 +146708,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -128175,7 +146932,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -128369,7 +147126,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationNamedQueriesNamedQuery.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -128550,7 +147307,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/service-capabilities">/service-capabilities</a>
+ <a class="json-schema-ref" href="#/getDefinitions/service-capabilities">/service-capabilities</a>
</div>
</div>
</div>
@@ -128661,7 +147418,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/service-capability">/service-capability</a>
+ <a class="json-schema-ref" href="#/getDefinitions/service-capability">/service-capability</a>
</div>
</div>
</div>
@@ -128708,7 +147465,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>service-capability object that needs to be created or updated</p>
+ <p><p>service-capability object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationServiceCapabilitiesServiceCapability.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -128795,6 +147552,111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-service-capabilities-service-capability--service-type---vnf-type--"></span>
+ <div id="operation--service-design-and-creation-service-capabilities-service-capability--service-type---vnf-type--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing service-capability</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/service-capabilities/service-capability/{service-type}/{vnf-type}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing service-capability</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>service-capability object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/service-capability">/service-capability</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ service-type
+ </td>
+ <td>
+ <p>This gets defined by others to provide a unique ID for the service, we accept what is sent.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ vnf-type
+ </td>
+ <td>
+ <p>String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-service-capabilities-service-capability--service-type---vnf-type--"></span>
<div id="operation--service-design-and-creation-service-capabilities-service-capability--service-type---vnf-type--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing service-capability</div>
@@ -128922,7 +147784,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationServiceCapabilitiesServiceCapability.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -129137,7 +147999,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/services">/services</a>
+ <a class="json-schema-ref" href="#/getDefinitions/services">/services</a>
</div>
</div>
</div>
@@ -129247,7 +148109,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/service">/service</a>
+ <a class="json-schema-ref" href="#/getDefinitions/service">/service</a>
</div>
</div>
</div>
@@ -129294,7 +148156,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>service object that needs to be created or updated</p>
+ <p><p>service object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationServicesService.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -129365,6 +148227,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-services-service--service-id--"></span>
+ <div id="operation--service-design-and-creation-services-service--service-id--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing service</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/services/service/{service-id}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing service</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>service object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/service">/service</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ service-id
+ </td>
+ <td>
+ <p>This gets defined by others to provide a unique ID for the service, we accept what is sent.</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-services-service--service-id--"></span>
<div id="operation--service-design-and-creation-services-service--service-id--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing service</div>
@@ -129476,7 +148427,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationServicesService.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -129659,7 +148610,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vnf-images">/vnf-images</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vnf-images">/vnf-images</a>
</div>
</div>
</div>
@@ -129799,7 +148750,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel panel-definition">
<div class="panel-body">
- <a class="json-schema-ref" href="#/definitions/vnf-image">/vnf-image</a>
+ <a class="json-schema-ref" href="#/getDefinitions/vnf-image">/vnf-image</a>
</div>
</div>
</div>
@@ -129846,7 +148797,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>vnf-image object that needs to be created or updated</p>
+ <p><p>vnf-image object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationVnfImagesVnfImage.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -129917,6 +148868,95 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<span id="path--service-design-and-creation-vnf-images-vnf-image--vnf-image-uuid--"></span>
+ <div id="operation--service-design-and-creation-vnf-images-vnf-image--vnf-image-uuid--patch" class="swagger--panel-operation-patch panel">
+ <div class="panel-heading">
+ <div class="operation-summary">update an existing vnf-image</div>
+ <h3 class="panel-title"><span class="operation-name">PATCH</span> <strong>/service-design-and-creation/vnf-images/vnf-image/{vnf-image-uuid}</strong></h3>
+ Tags:
+ <a href="#tag-ServiceDesignAndCreation">ServiceDesignAndCreation</a>
+ </div>
+ <div class="panel-body">
+ <section class="sw-operation-description">
+ <p>update an existing vnf-image</p>
+
+ </section>
+ <section class="sw-request-body">
+
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+ <div class="row">
+ <div class="col-md-6">
+ <p><p>vnf-image object that needs to be created or updated.</p>
+ </p>
+ </div>
+ <div class="col-md-6 sw-request-model">
+ <div class="panel panel-definition">
+ <div class="panel-body">
+ <a class="json-schema-ref" href="#/patchDefinitions/vnf-image">/vnf-image</a>
+ </div>
+ </div></div>
+ </div>
+ </section>
+ <section class="sw-request-params">
+ <table class="table">
+ <thead>
+ <tr>
+ <th class="sw-param-name"></th>
+ <th class="sw-param-description"></th>
+ <th class="sw-param-type"></th>
+ <th class="sw-param-data-type"></th>
+ <th class="sw-param-annotation"></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ vnf-image-uuid
+ </td>
+ <td>
+ <p>Unique ID of this asset</p>
+ </td>
+ <td>path</td>
+ <td>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+ </td>
+ <td>
+ <span class="json-property-required"></span>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+
+ <section class="sw-responses">
+ <p><span class="label label-default">application/json</span> <span class="label label-default">application/xml</span>
+ </p>
+
+ <dl>
+ <dt class="sw-response-default">
+ default
+
+ </dt>
+ <dd class="sw-response-default">
+ <div class="row">
+ <div class="col-md-12">
+ <p>Response codes found in <a href="https://wiki.onap.org/">response codes</a>.</p>
+
+ </div>
+ </div>
+ <div class="row">
+
+ <div class="col-md-6 sw-response-model">
+ </div>
+
+ </div> </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+
+ <span id="path--service-design-and-creation-vnf-images-vnf-image--vnf-image-uuid--"></span>
<div id="operation--service-design-and-creation-vnf-images-vnf-image--vnf-image-uuid--delete" class="swagger--panel-operation-delete panel">
<div class="panel-heading">
<div class="operation-summary">delete an existing vnf-image</div>
@@ -130028,7 +149068,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</p>
<div class="row">
<div class="col-md-6">
- <p><p>relationship object that needs to be created or updated</p>
+ <p><p>relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationVnfImagesVnfImage.json)</p>
</p>
</div>
<div class="col-md-6 sw-request-model">
@@ -130178,6 +149218,45 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<h2>Schema definitions</h2>
+ <div id="definition-aai-internal" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/aai-internal"></a>aai-internal:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="property-name">
+ <span class="json-property-name">property-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="property-value">
+ <span class="json-property-name">property-value:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-action" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/action"></a>action:
@@ -130338,17 +149417,16 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Represents a slice or partial piece of a resource that gets separately allotted</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO generic-vnf (Many2Many)</li>
-<li>TO l3-network (Many2Many)</li>
-<li>TO instance-group (Many2Many)</li>
-<li>TO vlan (Many2Many)</li>
-<li>TO tunnel-xconnect (comprises allotted-resource, One2One)</li>
-<li>FROM service-instance (is composed of allotted-resource)</li>
-<li>FROM service-instance</li></ul>
+<li>TO generic-vnf( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY)</li>
+<li>TO instance-group( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>TO l3-network( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY)</li>
+<li>TO vlan( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY)</li>
+<li>TO service-instance( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)</li>
+<li>FROM tunnel-xconnect( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY)</li>
+<li>ALLOTTED-RESOURCE is DELETED when these are DELETED TUNNEL-XCONNECT</li></ul>
</section>
@@ -130548,18 +149626,17 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Availability zone, a collection of compute hosts/pservers</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_IF_ANY_IN_EDGES</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO complex (Many2Many)</li>
-<li>TO service-capability (Many2Many)</li>
-<li>FROM cloud-region (is composed of availability-zone)</li>
-<li>FROM ctag-pool</li>
-<li>FROM dvs-switch</li>
-<li>FROM generic-vnf</li>
-<li>FROM pserver</li>
-<li>FROM vce</li></ul>
+<li>TO complex( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>TO service-capability( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)</li>
+<li>TO cloud-region( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM ctag-pool( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)</li>
+<li>FROM dvs-switch( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)</li>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)</li>
+<li>FROM pserver( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)</li>
+<li>FROM vce( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)</li>
+<li>AVAILABILITY-ZONE cannot be deleted if linked to CTAG-POOL,DVS-SWITCH,GENERIC-VNF,PSERVER,VCE</li></ul>
</section>
@@ -130809,11 +149886,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<div class="panel-body">
<section class="json-schema-description">
- <h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
-<h6 id="related-nodes">Related Nodes</h6>
+ <h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM site-pair (is composed of class-of-service)</li></ul>
+<li>TO site-pair( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)</li></ul>
</section>
@@ -131066,24 +150141,24 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>cloud-region designates an installation of a cloud cluster or region or instantiation.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO complex (Many2One)</li>
-<li>TO l3-network (Many2Many)</li>
-<li>TO tenant (comprises cloud-region, One2Many)</li>
-<li>TO image (comprises cloud-region, One2Many)</li>
-<li>TO flavor (comprises cloud-region, One2Many)</li>
-<li>TO availability-zone (comprises cloud-region, One2Many)</li>
-<li>TO oam-network (comprises cloud-region, One2Many)</li>
-<li>TO dvs-switch (comprises cloud-region, One2Many)</li>
-<li>TO volume-group (comprises cloud-region, One2Many)</li>
-<li>TO group-assignment (comprises cloud-region, One2Many)</li>
-<li>TO snapshot (comprises cloud-region, One2Many)</li>
-<li>TO zone (Many2One)</li>
-<li>FROM pserver</li>
-<li>FROM logical-link</li></ul>
+<li>TO complex( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>TO l3-network( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>TO zone( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)</li>
+<li>FROM availability-zone( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM dvs-switch( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM flavor( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM group-assignment( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM image( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM oam-network( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM snapshot( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM tenant( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM volume-group( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn cloud-region, MANY2MANY)</li>
+<li>FROM pserver( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)</li>
+<li>CLOUD-REGION cannot be deleted if linked to DVS-SWITCH,FLAVOR,GROUP-ASSIGNMENT,IMAGE,OAM-NETWORK,SNAPSHOT,TENANT,VOLUME-GROUP</li>
+<li>CLOUD-REGION is DELETED when these are DELETED AVAILABILITY-ZONE</li></ul>
</section>
@@ -131452,21 +150527,21 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Collection of physical locations that can house cloud-regions.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_4_IN_EDGES_OR_CASCADE</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO ctag-pool (comprises complex, Many2Many)</li>
-<li>TO l3-network (Many2Many)</li>
-<li>FROM availability-zone</li>
-<li>FROM cloud-region</li>
-<li>FROM oam-network</li>
-<li>FROM pserver</li>
-<li>FROM pnf</li>
-<li>FROM vce</li>
-<li>FROM vpls-pe</li>
-<li>FROM volume-group</li>
-<li>FROM zone</li></ul>
+<li>TO l3-network( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>FROM availability-zone( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM ctag-pool( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)</li>
+<li>FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)</li>
+<li>FROM pnf( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM pserver( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM vce( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)</li>
+<li>FROM volume-group( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM vpls-pe( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM zone( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>COMPLEX cannot be deleted if linked to AVAILABILITY-ZONE,CLOUD-REGION,OAM-NETWORK,PNF,PSERVER,VCE,VOLUME-GROUP,VPLS-PE,ZONE</li>
+<li>COMPLEX is DELETED when these are DELETED CTAG-POOL</li></ul>
</section>
@@ -131757,6 +150832,268 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-configuration" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/configuration"></a>configuration:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Port Mirror Configuration.</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO allotted-resource( configuration org.onap.relationships.inventory.Uses allotted-resource, ONE2ONE)</li>
+<li>TO logical-link( configuration org.onap.relationships.inventory.Uses logical-link, ONE2MANY)</li>
+<li>FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo configuration, MANY2ONE)</li>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses configuration, ONE2MANY)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.Uses configuration, ONE2MANY)</li>
+<li>CONFIGURATION is DELETED when these are DELETED METADATUM</li>
+<li>CONFIGURATION deletion means associated objects of these types are also DELETED:ALLOTTED-RESOURCE,LOGICAL-LINK</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="configuration-id">
+ <span class="json-property-name">configuration-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>UUID assigned to configuration.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="management-option">
+ <span class="json-property-name">management-option:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Indicates the entity that will manage this feature. Could be an organization or the name of the application as well.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="configuration-name">
+ <span class="json-property-name">configuration-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Name of the configuration.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="configuration-type">
+ <span class="json-property-name">configuration-type:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>port-mirroring-configuration.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="configuration-sub-type">
+ <span class="json-property-name">configuration-sub-type:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>vprobe, pprobe.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="model-invariant-id">
+ <span class="json-property-name">model-invariant-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>the ASDC model id for this resource or service model.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="model-version-id">
+ <span class="json-property-name">model-version-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>the ASDC model version for this resource or service model.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="orchestration-status">
+ <span class="json-property-name">orchestration-status:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Orchestration status of the configuration.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="operational-status">
+ <span class="json-property-name">operational-status:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Indicator for whether the resource is considered operational.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="configuration-selflink">
+ <span class="json-property-name">configuration-selflink:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>URL to endpoint where AAI can get more details from SDN-GC.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="model-customization-id">
+ <span class="json-property-name">model-customization-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>id of the configuration used to customize the resource</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ <dt data-property-name="metadata">
+ <span class="json-property-name">metadata:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/metadatum">metadatum</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-configurations" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/configurations"></a>configurations:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Collection of configurations</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="configuration">
+ <span class="json-property-name">configuration:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/configuration">configuration</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-connector" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/connector"></a>connector:
@@ -131769,13 +151106,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Collection of resource instances used to connect a variety of disparate inventory widgets</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO virtual-data-center (Many2Many)</li>
-<li>TO metadatum (comprises connector, Many2Many)</li>
-<li>FROM service-instance</li></ul>
+<li>TO virtual-data-center( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)</li>
+<li>FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)</li>
+<li>CONNECTOR is DELETED when these are DELETED METADATUM</li></ul>
</section>
@@ -131963,13 +151299,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>This is how we would capture constraints defining allowed sets of elements.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO element-choice-set (comprises constrained-element-set, One2Many)</li>
-<li>FROM model-element (is composed of constrained-element-set)</li>
-<li>FROM model-constraint (is composed of constrained-element-set)</li></ul>
+<li>TO model-constraint( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)</li>
+<li>TO model-element( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)</li>
+<li>FROM element-choice-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)</li>
+<li>CONSTRAINED-ELEMENT-SET is DELETED when these are DELETED ELEMENT-CHOICE-SET</li></ul>
</section>
@@ -132114,12 +151449,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<div class="panel-body">
<section class="json-schema-description">
- <h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
-<h6 id="related-nodes">Related Nodes</h6>
+ <h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM l3-network (is composed of ctag-assignment)</li>
-<li>FROM service-instance</li></ul>
+<li>TO l3-network( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.Uses ctag-assignment, ONE2MANY)</li></ul>
</section>
@@ -132223,13 +151556,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>A collection of C tags (vlan tags) grouped for a specific purpose.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO availability-zone (Many2Many)</li>
-<li>FROM complex (is composed of ctag-pool)</li>
-<li>FROM vpls-pe</li></ul>
+<li>TO complex( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)</li>
+<li>TO availability-zone( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)</li>
+<li>FROM vpls-pe( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)</li></ul>
</section>
@@ -132371,11 +151702,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>customer identifiers to provide linkage back to BSS information.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO service-subscription (comprises customer, Many2Many)</li></ul>
+<li>FROM service-subscription( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)</li>
+<li>CUSTOMER is DELETED when these are DELETED SERVICE-SUBSCRIPTION</li></ul>
</section>
@@ -132628,12 +151958,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Digital virtual switch metadata, used by SDN-C to configure VCEs. A&AI needs to receive this data from the PO deployment team and administer it using the provisioningTool.sh into A&AI.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO availability-zone (Many2Many)</li>
-<li>FROM cloud-region (is composed of dvs-switch)</li></ul>
+<li>TO cloud-region( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>TO availability-zone( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)</li></ul>
</section>
@@ -133010,12 +152338,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>This is how we would capture constraints defining allowed sets of elements.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO model-element (comprises element-choice-set, One2Many)</li>
-<li>FROM constrained-element-set (is composed of element-choice-set)</li></ul>
+<li>TO constrained-element-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)</li>
+<li>FROM model-element( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)</li>
+<li>ELEMENT-CHOICE-SET is DELETED when these are DELETED MODEL-ELEMENT</li></ul>
</section>
@@ -133160,12 +152487,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Metadata for entitlement group.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM generic-vnf (is composed of entitlement)</li>
-<li>FROM vce (is composed of entitlement)</li></ul>
+<li>TO generic-vnf( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>TO vce( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)</li></ul>
</section>
@@ -133274,6 +152599,1111 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-esr-ems" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/esr-ems"></a>esr-ems:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Persist EMS address information used by EMS driver.</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO esr-system-info (CHILD of esr-ems, esr-ems has esr-system-info, One2Many)</li>
+<li>ESR-EMS deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="ems-id">
+ <span class="json-property-name">ems-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Unique ID of EMS.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="esr-system-info-list">
+ <span class="json-property-name">esr-system-info-list:</span>
+ <span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-system-info-list">esr-system-info-list</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship-list">relationship-list</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-esr-ems-list" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/esr-ems-list"></a>esr-ems-list:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="esr-ems">
+ <span class="json-property-name">esr-ems:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-ems">esr-ems</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-esr-system-info" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/esr-system-info"></a>esr-system-info:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Persist common address information of external systems.</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>FROM esr-ems (PARENT of esr-system-info, esr-ems has esr-system-info)</li>
+<li>FROM esr-vnfm (PARENT of esr-system-info, esr-vnfm has esr-system-info)</li>
+<li>FROM esr-thirdparty-sdnc (PARENT of esr-system-info, esr-thirdparty-sdnc has esr-system-info)</li>
+<li>FROM cloud-region (PARENT of esr-system-info, cloud-region has esr-system-info)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="esr-system-info-id">
+ <span class="json-property-name">esr-system-info-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Unique ID of esr system info.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="system-name">
+ <span class="json-property-name">system-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>name of external system.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="type">
+ <span class="json-property-name">type:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>type of external systems.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="vendor">
+ <span class="json-property-name">vendor:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>vendor of external systems.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="version">
+ <span class="json-property-name">version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>version of external systems.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="service-url">
+ <span class="json-property-name">service-url:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>url used to access external systems.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="user-name">
+ <span class="json-property-name">user-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>username used to access external systems.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="password">
+ <span class="json-property-name">password:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>password used to access external systems.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="system-type">
+ <span class="json-property-name">system-type:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>it could be vim/vnfm/thirdparty-sdnc/ems-resource/ems-performance/ems-alarm.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="protocol">
+ <span class="json-property-name">protocol:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>protocol of third party SDNC, for example netconf/snmp.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="ssl-cacert">
+ <span class="json-property-name">ssl-cacert:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>ca file content if enabled ssl on auth-url.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="ssl-insecure">
+ <span class="json-property-name">ssl-insecure:</span>
+ <span class="json-property-type">boolean</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Whether to verify VIM's certificate.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="ip-address">
+ <span class="json-property-name">ip-address:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>service IP of ftp server.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="port">
+ <span class="json-property-name">port:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>service port of ftp server.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="cloud-domain">
+ <span class="json-property-name">cloud-domain:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>domain info for authentication.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="default-tenant">
+ <span class="json-property-name">default-tenant:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>default tenant of VIM.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="passive">
+ <span class="json-property-name">passive:</span>
+ <span class="json-property-type">boolean</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>ftp passive mode or not.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="remote-path">
+ <span class="json-property-name">remote-path:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>resource or performance data file path.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="system-status">
+ <span class="json-property-name">system-status:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>the status of external system.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-esr-system-info-list" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/esr-system-info-list"></a>esr-system-info-list:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Collection of persistent block-level external system auth info.</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="esr-system-info">
+ <span class="json-property-name">esr-system-info:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-system-info">esr-system-info</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-esr-thirdparty-sdnc" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/esr-thirdparty-sdnc"></a>esr-thirdparty-sdnc:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Persist SDNC address information used by ONAP SDNC.</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO esr-system-info (CHILD of esr-thirdparty-sdnc, esr-thirdparty-sdnc has esr-system-info, One2One)</li>
+<li>TO pnf( esr-thirdparty-sdnc has pnf, One2Many)</li>
+<li>ESR-THIRDPARTY-SDNC deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="thirdparty-sdnc-id">
+ <span class="json-property-name">thirdparty-sdnc-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Unique ID of SDNC.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="location">
+ <span class="json-property-name">location:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>used for DC type to indicate the location of SDNC, such as Core or Edge.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="product-name">
+ <span class="json-property-name">product-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>password used to access SDNC server.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="esr-system-info-list">
+ <span class="json-property-name">esr-system-info-list:</span>
+ <span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-system-info-list">esr-system-info-list</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship-list">relationship-list</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-esr-thirdparty-sdnc-list" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/esr-thirdparty-sdnc-list"></a>esr-thirdparty-sdnc-list:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="esr-thirdparty-sdnc">
+ <span class="json-property-name">esr-thirdparty-sdnc:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-thirdparty-sdnc">esr-thirdparty-sdnc</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-esr-vnfm" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/esr-vnfm"></a>esr-vnfm:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Persist VNFM address information used by VF-C.</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO esr-system-info (CHILD of esr-vnfm, esr-vnfm has esr-system-info, One2One)</li>
+<li>ESR-VNFM deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="vnfm-id">
+ <span class="json-property-name">vnfm-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Unique ID of VNFM.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="vim-id">
+ <span class="json-property-name">vim-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>indecate the VIM to deploy VNF.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="certificate-url">
+ <span class="json-property-name">certificate-url:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>certificate url of VNFM.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="esr-system-info-list">
+ <span class="json-property-name">esr-system-info-list:</span>
+ <span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-system-info-list">esr-system-info-list</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship-list">relationship-list</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-esr-vnfm-list" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/esr-vnfm-list"></a>esr-vnfm-list:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="esr-vnfm">
+ <span class="json-property-name">esr-vnfm:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-vnfm">esr-vnfm</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-evc" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/evc"></a>evc:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>evc object is an optional child object of the Configuration object.</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO configuration( evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="evc-id">
+ <span class="json-property-name">evc-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Unique/key field for the evc object</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="forwarding-path-topology">
+ <span class="json-property-name">forwarding-path-topology:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Point-to-Point, Multi-Point</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="cir-value">
+ <span class="json-property-name">cir-value:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Commited Information Rate</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="cir-units">
+ <span class="json-property-name">cir-units:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>CIR units</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="connection-diversity-group-id">
+ <span class="json-property-name">connection-diversity-group-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Diversity Group ID</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="service-hours">
+ <span class="json-property-name">service-hours:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>formerly Performance Group</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="esp-evc-circuit-id">
+ <span class="json-property-name">esp-evc-circuit-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>EVC Circuit ID of ESP EVC</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="esp-evc-cir-value">
+ <span class="json-property-name">esp-evc-cir-value:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Committed Information Rate (For ESP)</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="esp-evc-cir-units">
+ <span class="json-property-name">esp-evc-cir-units:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>CIR units (For ESP)</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="esp-itu-code">
+ <span class="json-property-name">esp-itu-code:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Identifies ESP</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="collector-pop-clli">
+ <span class="json-property-name">collector-pop-clli:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Collector POP CLLI (from the hostname of the access pnf)</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="inter-connect-type-ingress">
+ <span class="json-property-name">inter-connect-type-ingress:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Interconnect type on ingress side of EVC.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="tagmode-access-ingress">
+ <span class="json-property-name">tagmode-access-ingress:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>tagode for collector side of EVC</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="tagmode-access-egress">
+ <span class="json-property-name">tagmode-access-egress:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>tagMode for network side of EVC</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-evcs" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/evcs"></a>evcs:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="evc">
+ <span class="json-property-name">evc:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/evc">evc</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-external-system" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/external-system"></a>external-system:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Namespace for external system.</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="esr-ems-list">
+ <span class="json-property-name">esr-ems-list:</span>
+ <span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-ems-list">esr-ems-list</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ <dt data-property-name="esr-vnfm-list">
+ <span class="json-property-name">esr-vnfm-list:</span>
+ <span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-vnfm-list">esr-vnfm-list</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ <dt data-property-name="esr-thirdparty-sdnc-list">
+ <span class="json-property-name">esr-thirdparty-sdnc-list:</span>
+ <span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/esr-thirdparty-sdnc-list">esr-thirdparty-sdnc-list</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-extra-properties" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/extra-properties"></a>extra-properties:
@@ -133335,12 +153765,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Openstack flavor.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_IF_ANY_IN_EDGES</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM cloud-region (is composed of flavor)</li>
-<li>FROM vserver</li></ul>
+<li>TO cloud-region( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM vserver( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)</li>
+<li>FLAVOR cannot be deleted if linked to VSERVER</li></ul>
</section>
@@ -133546,6 +153975,438 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-forwarder" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/forwarder"></a>forwarder:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Entity describing a sequenced segment of forwarding path</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO forwarding-path( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)</li>
+<li>TO l-interface( forwarder org.onap.relationships.inventory.ForwardsTo l-interface, MANY2ONE)</li>
+<li>TO configuration( forwarder org.onap.relationships.inventory.Uses configuration, ONE2ONE)</li>
+<li>TO lag-interface( forwarder org.onap.relationships.inventory.ForwardsTo lag-interface, MANY2ONE)</li>
+<li>TO p-interface( forwarder org.onap.relationships.inventory.ForwardsTo p-interface, MANY2ONE)</li>
+<li>FORWARDER deletion means associated objects of these types are also DELETED:CONFIGURATION</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="sequence">
+ <span class="json-property-name">sequence:</span>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Unique ID of this segmentation</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="forwarder-role">
+ <span class="json-property-name">forwarder-role:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>ingress, intermediate, egress</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-forwarder-evc" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/forwarder-evc"></a>forwarder-evc:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>forwarder object is an optional child object of the Configuration object.</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO configuration( forwarder-evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="forwarder-evc-id">
+ <span class="json-property-name">forwarder-evc-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Key for forwarder-evc object</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="circuit-id">
+ <span class="json-property-name">circuit-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Circuit ID from customer/ESP/ingress end of EVC, or reference to beater circuit on gateway/network/egress end of EVC</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="ivlan">
+ <span class="json-property-name">ivlan:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Internal VLAN.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="svlan">
+ <span class="json-property-name">svlan:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>SVLAN value for ingress of egress forwarder.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="cvlan">
+ <span class="json-property-name">cvlan:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>CVLAN value for ingress of egress forwarder.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-forwarder-evcs" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/forwarder-evcs"></a>forwarder-evcs:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="forwarder-evc">
+ <span class="json-property-name">forwarder-evc:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/forwarder-evc">forwarder-evc</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-forwarders" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/forwarders"></a>forwarders:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="forwarder">
+ <span class="json-property-name">forwarder:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/forwarder">forwarder</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-forwarding-path" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/forwarding-path"></a>forwarding-path:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Entity that describes the sequenced forwarding path between interfaces of services or resources</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO service-instance( forwarding-path org.onap.relationships.inventory.AppliesTo service-instance, MANY2ONE)</li>
+<li>TO configuration( forwarding-path org.onap.relationships.inventory.Uses configuration, ONE2ONE)</li>
+<li>FROM forwarder( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)</li>
+<li>FORWARDING-PATH is DELETED when these are DELETED FORWARDER</li>
+<li>FORWARDING-PATH deletion means associated objects of these types are also DELETED:CONFIGURATION</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="forwarding-path-id">
+ <span class="json-property-name">forwarding-path-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Unique ID of this FP</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="forwarding-path-name">
+ <span class="json-property-name">forwarding-path-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Name of the FP</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="selflink">
+ <span class="json-property-name">selflink:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>the self link for this FP</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ <dt data-property-name="forwarders">
+ <span class="json-property-name">forwarders:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/forwarder">forwarder</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-forwarding-paths" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/forwarding-paths"></a>forwarding-paths:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="forwarding-path">
+ <span class="json-property-name">forwarding-path:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/forwarding-path">forwarding-path</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-generic-vnf" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/generic-vnf"></a>generic-vnf:
@@ -133558,31 +154419,30 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>General purpose VNF</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO license-key-resource (Many2Many)</li>
-<li>TO l-interface (comprises generic-vnf, Many2Many)</li>
-<li>TO availability-zone (Many2Many)</li>
-<li>TO lag-interface (comprises generic-vnf, Many2Many)</li>
-<li>TO l3-network (Many2Many)</li>
-<li>TO pserver (Many2Many)</li>
-<li>TO vnf-image (Many2One)</li>
-<li>TO vserver (One2Many)</li>
-<li>TO service-instance (Many2Many)</li>
-<li>TO site-pair-set (Many2Many)</li>
-<li>TO network-profile (Many2Many)</li>
-<li>TO ipsec-configuration (Many2One)</li>
-<li>TO vf-module (comprises generic-vnf, One2Many)</li>
-<li>TO volume-group (One2Many)</li>
-<li>TO vnfc (One2Many)</li>
-<li>TO instance-group (Many2Many)</li>
-<li>TO entitlement (comprises generic-vnf, One2Many)</li>
-<li>TO license (comprises generic-vnf, One2Many)</li>
-<li>FROM virtual-data-center</li>
-<li>FROM logical-link</li>
-<li>FROM allotted-resource</li></ul>
+<li>TO availability-zone( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)</li>
+<li>TO instance-group( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>TO ipsec-configuration( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)</li>
+<li>TO l3-network( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>TO license-key-resource( generic-vnf org.onap.relationships.inventory.Uses license-key-resource, MANY2MANY)</li>
+<li>TO pserver( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)</li>
+<li>TO vnf-image( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)</li>
+<li>TO volume-group( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)</li>
+<li>TO vserver( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)</li>
+<li>TO virtual-data-center( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)</li>
+<li>FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY)</li>
+<li>FROM entitlement( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>FROM vnfc( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>FROM lag-interface( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>FROM license( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>FROM network-profile( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)</li>
+<li>FROM site-pair-set( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)</li>
+<li>FROM vf-module( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)</li>
+<li>GENERIC-VNF is DELETED when these are DELETED ENTITLEMENT,VNFC,LAG-INTERFACE,LICENSE,L-INTERFACE,VF-MODULE</li></ul>
</section>
@@ -134224,13 +155084,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Openstack group-assignment used to store exclusivity groups (EG).</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO tenant (Many2Many)</li>
-<li>TO pserver (One2Many)</li>
-<li>FROM cloud-region (is composed of group-assignment)</li></ul>
+<li>TO cloud-region( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM pserver( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)</li>
+<li>FROM tenant( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)</li></ul>
</section>
@@ -134364,6 +155222,149 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-host-route" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/host-route"></a>host-route:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO subnet( host-route org.onap.relationships.inventory.BelongsTo subnet, MANY2ONE)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="host-route-id">
+ <span class="json-property-name">host-route-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>host-route id</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="route-prefix">
+ <span class="json-property-name">route-prefix:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>subnet prefix</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="next-hop">
+ <span class="json-property-name">next-hop:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Could be ip-address, hostname, or service-instance</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="next-hop-type">
+ <span class="json-property-name">next-hop-type:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Should be ip-address, hostname, or service-instance to match next-hop</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-host-routes" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/host-routes"></a>host-routes:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="host-route">
+ <span class="json-property-name">host-route:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/host-route">host-route</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-image" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/image"></a>image:
@@ -134376,13 +155377,13 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Openstack image.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_4_IN_EDGES_OR_CASCADE</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO metadatum (comprises image, Many2Many)</li>
-<li>FROM cloud-region (is composed of image)</li>
-<li>FROM vserver</li></ul>
+<li>TO cloud-region( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)</li>
+<li>FROM vserver( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)</li>
+<li>IMAGE cannot be deleted if linked to VSERVER</li>
+<li>IMAGE is DELETED when these are DELETED METADATUM</li></ul>
</section>
@@ -134700,15 +155701,13 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>General mechanism for grouping instances</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO model (Many2Many)</li>
-<li>FROM pnf</li>
-<li>FROM allotted-resource</li>
-<li>FROM generic-vnf</li>
-<li>FROM service-instance</li></ul>
+<li>TO model( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY)</li>
+<li>FROM allotted-resource( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>FROM pnf( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li></ul>
</section>
@@ -135006,7 +156005,7 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="json-inner-schema">
<section class="json-schema-array-items">
- <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/"></a>
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/aai-internal">aai-internal</a>
</span>
<span class="json-property-range" title="Value limits"></span>
@@ -135262,12 +156261,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>IPSec configuration node will contain various configuration data for the NMTE VNF. This node will have an edge to the generic-vnf (vnf type = TE). Starting 1607, this data will be populated by SDN-C</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO vig-server (comprises ipsec-configuration, One2Many)</li>
-<li>FROM generic-vnf</li></ul>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)</li>
+<li>FROM vig-server( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)</li>
+<li>IPSEC-CONFIGURATION is DELETED when these are DELETED VIG-SERVER</li></ul>
</section>
@@ -135670,20 +156668,20 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Logical interfaces, e.g., a vnic.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO l3-interface-ipv4-address-list (comprises l-interface, Many2Many)</li>
-<li>TO l3-interface-ipv6-address-list (comprises l-interface, Many2Many)</li>
-<li>TO logical-link (Many2Many)</li>
-<li>TO vlan (comprises l-interface, Many2Many)</li>
-<li>TO sriov-vf (comprises l-interface, One2One)</li>
-<li>FROM generic-vnf (is composed of l-interface)</li>
-<li>FROM lag-interface (is composed of l-interface)</li>
-<li>FROM newvce (is composed of l-interface)</li>
-<li>FROM p-interface (is composed of l-interface)</li>
-<li>FROM vserver (is composed of l-interface)</li></ul>
+<li>TO generic-vnf( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>TO lag-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)</li>
+<li>TO logical-link( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)</li>
+<li>TO newvce( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)</li>
+<li>TO p-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)</li>
+<li>TO vserver( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)</li>
+<li>FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)</li>
+<li>FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)</li>
+<li>FROM sriov-vf( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)</li>
+<li>FROM vlan( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)</li>
+<li>L-INTERFACE is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST,SRIOV-VF,VLAN</li>
+<li>L-INTERFACE deletion means associated objects of these types are also DELETED:LOGICAL-LINK</li></ul>
</section>
@@ -135967,14 +156965,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>IPv4 Address Range</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO l3-network (Many2Many)</li>
-<li>TO subnet (Many2Many)</li>
-<li>FROM l-interface (is composed of l3-interface-ipv4-address-list)</li>
-<li>FROM vlan (is composed of l3-interface-ipv4-address-list)</li></ul>
+<li>TO l3-network( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)</li>
+<li>TO subnet( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)</li>
+<li>TO l-interface( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)</li>
+<li>TO vlan( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)</li></ul>
</section>
@@ -136113,14 +157109,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>IPv6 Address Range</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO l3-network (Many2Many)</li>
-<li>TO subnet (Many2Many)</li>
-<li>FROM l-interface (is composed of l3-interface-ipv6-address-list)</li>
-<li>FROM vlan (is composed of l3-interface-ipv6-address-list)</li></ul>
+<li>TO l3-network( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)</li>
+<li>TO subnet( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)</li>
+<li>TO l-interface( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)</li>
+<li>TO vlan( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)</li></ul>
</section>
@@ -136259,25 +157253,24 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Generic network definition</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO vpn-binding (Many2Many)</li>
-<li>TO subnet (comprises l3-network, Many2Many)</li>
-<li>TO service-instance (Many2Many)</li>
-<li>TO ctag-assignment (comprises l3-network, Many2Many)</li>
-<li>TO network-policy (Many2Many)</li>
-<li>TO segmentation-assignment (comprises l3-network, One2Many)</li>
-<li>TO route-table-reference (Many2Many)</li>
-<li>FROM cloud-region</li>
-<li>FROM complex</li>
-<li>FROM generic-vnf</li>
-<li>FROM l3-interface-ipv4-address-list</li>
-<li>FROM l3-interface-ipv6-address-list</li>
-<li>FROM tenant</li>
-<li>FROM vf-module</li>
-<li>FROM allotted-resource</li></ul>
+<li>TO network-policy( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)</li>
+<li>TO route-table-reference( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)</li>
+<li>TO vpn-binding( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)</li>
+<li>FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY)</li>
+<li>FROM cloud-region( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>FROM complex( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)</li>
+<li>FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)</li>
+<li>FROM ctag-assignment( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)</li>
+<li>FROM segmentation-assignment( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)</li>
+<li>FROM subnet( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)</li>
+<li>FROM tenant( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>FROM vf-module( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)</li>
+<li>L3-NETWORK is DELETED when these are DELETED CTAG-ASSIGNMENT,SEGMENTATION-ASSIGNMENT,SUBNET</li></ul>
</section>
@@ -136718,17 +157711,17 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Link aggregate interface</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO lag-link (Many2Many)</li>
-<li>TO p-interface (Many2Many)</li>
-<li>TO l-interface (comprises lag-interface, Many2Many)</li>
-<li>FROM generic-vnf (is composed of lag-interface)</li>
-<li>FROM pserver (is composed of lag-interface)</li>
-<li>FROM pnf (is composed of lag-interface)</li>
-<li>FROM vpls-pe (is composed of lag-interface)</li></ul>
+<li>TO generic-vnf( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>TO lag-link( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)</li>
+<li>TO p-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)</li>
+<li>TO pnf( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)</li>
+<li>TO pserver( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)</li>
+<li>TO vpls-pe( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)</li>
+<li>FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)</li>
+<li>LAG-INTERFACE is DELETED when these are DELETED L-INTERFACE</li>
+<li>LAG-INTERFACE deletion means associated objects of these types are also DELETED:LAG-LINK</li></ul>
</section>
@@ -136928,12 +157921,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>LAG links can connect lag-interfaces</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM lag-interface</li>
-<li>FROM logical-link</li></ul>
+<li>FROM lag-interface( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)</li>
+<li>FROM logical-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)</li></ul>
</section>
@@ -137041,12 +158032,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Metadata for license group.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM generic-vnf (is composed of license)</li>
-<li>FROM vce (is composed of license)</li></ul>
+<li>TO generic-vnf( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>TO vce( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)</li></ul>
</section>
@@ -137155,6 +158144,116 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-line-of-business" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/line-of-business"></a>line-of-business:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>describes a line-of-business</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO generic-vnf( line-of-business org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="line-of-business-name">
+ <span class="json-property-name">line-of-business-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Name of the line-of-business (product)</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-lines-of-business" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/lines-of-business"></a>lines-of-business:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Collection of lines-of-business</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="line-of-business">
+ <span class="json-property-name">line-of-business:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/line-of-business">line-of-business</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-logical-link" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/logical-link"></a>logical-link:
@@ -137167,23 +158266,21 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Logical links generally connect l-interfaces but are used to express logical connectivity between two points</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO lag-link (Many2Many)</li>
-<li>TO pnf (Many2Many)</li>
-<li>TO logical-link (One2Many)</li>
-<li>TO generic-vnf (Many2Many)</li>
-<li>TO pserver (Many2Many)</li>
-<li>TO cloud-region (Many2Many)</li>
-<li>TO vpn-binding (Many2Many)</li>
-<li>FROM l-interface</li>
-<li>FROM p-interface</li>
-<li>FROM service-instance</li>
-<li>FROM virtual-data-center</li>
-<li>FROM vlan</li>
-<li>FROM logical-link</li></ul>
+<li>TO cloud-region( logical-link org.onap.relationships.inventory.LocatedIn cloud-region, MANY2MANY)</li>
+<li>TO generic-vnf( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)</li>
+<li>TO lag-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)</li>
+<li>TO logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, ONE2MANY)</li>
+<li>TO pnf( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)</li>
+<li>TO pserver( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)</li>
+<li>TO vpn-binding( logical-link org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)</li>
+<li>TO virtual-data-center( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)</li>
+<li>FROM l-interface( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)</li>
+<li>FROM p-interface( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)</li>
+<li>FROM vlan( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)</li>
+<li>FROM logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, ONE2MANY)</li></ul>
</section>
@@ -137496,8 +158593,6 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Collection of metadatum (key/value pairs)</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
</section>
@@ -137539,14 +158634,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Key/value pairs</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM image (is composed of metadatum)</li>
-<li>FROM model-ver (is composed of metadatum)</li>
-<li>FROM service-instance (is composed of metadatum)</li>
-<li>FROM connector (is composed of metadatum)</li></ul>
+<li>TO connector( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)</li>
+<li>TO image( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)</li>
+<li>TO service-instance( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)</li>
+<li>TO model-ver( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)</li></ul>
</section>
@@ -137604,14 +158697,15 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Subgraph definition provided by ASDC to describe an inventory asset and its connections related to ASDC models, independent of version</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_4_IN_EDGES_OR_CASCADE</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO model-ver (comprises model, One2Many)</li>
-<li>FROM named-query</li>
-<li>FROM named-query-element</li>
-<li>FROM instance-group</li></ul>
+<li>TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)</li>
+<li>FROM instance-group( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY)</li>
+<li>FROM model-ver( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)</li>
+<li>FROM named-query( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)</li>
+<li>FROM named-query-element( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)</li>
+<li>MODEL cannot be deleted if linked to INSTANCE-GROUP,NAMED-QUERY,NAMED-QUERY-ELEMENT</li>
+<li>MODEL is DELETED when these are DELETED MODEL-VER</li></ul>
</section>
@@ -137814,12 +158908,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>This is how we would capture constraints defining allowed sets of elements.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO constrained-element-set (comprises model-constraint, One2Many)</li>
-<li>FROM model-element (is composed of model-constraint)</li></ul>
+<li>TO model-element( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)</li>
+<li>FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)</li>
+<li>MODEL-CONSTRAINT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET</li></ul>
</section>
@@ -137934,17 +159027,16 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Defines how other models combine to make up a higher-level model.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO model-ver (Many2One)</li>
-<li>TO model-element (comprises model-element, One2Many)</li>
-<li>TO model-constraint (comprises model-element, One2Many)</li>
-<li>TO constrained-element-set (comprises model-element, One2Many)</li>
-<li>FROM model-ver (is composed of model-element)</li>
-<li>FROM element-choice-set (is composed of model-element)</li>
-<li>FROM model-element (is composed of model-element)</li></ul>
+<li>TO element-choice-set( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)</li>
+<li>TO model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)</li>
+<li>TO model-ver( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE)</li>
+<li>TO model-ver( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)</li>
+<li>FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)</li>
+<li>FROM model-constraint( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)</li>
+<li>FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)</li>
+<li>MODEL-ELEMENT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET,MODEL-CONSTRAINT</li></ul>
</section>
@@ -138124,14 +159216,14 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Subgraph definition provided by ASDC to describe a specific version of an inventory asset and its connections related to ASDC models</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_4_IN_EDGES_OR_CASCADE</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO model-element (comprises model-ver, One2Many)</li>
-<li>TO metadatum (comprises model-ver, One2Many)</li>
-<li>FROM model (is composed of model-ver)</li>
-<li>FROM model-element</li></ul>
+<li>TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)</li>
+<li>FROM model-element( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE)</li>
+<li>FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)</li>
+<li>FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)</li>
+<li>MODEL-VER cannot be deleted if linked to MODEL-ELEMENT</li>
+<li>MODEL-VER is DELETED when these are DELETED MODEL-ELEMENT,METADATUM</li></ul>
</section>
@@ -138353,11 +159445,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<div class="panel-body">
<section class="json-schema-description">
- <h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
-<h6 id="related-nodes">Related Nodes</h6>
+ <h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM vlan</li></ul>
+<li>FROM vlan( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)</li></ul>
</section>
@@ -138528,12 +159618,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>TBD</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO model (One2Many)</li>
-<li>TO named-query-element (comprises named-query, One2One)</li></ul>
+<li>TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)</li>
+<li>TO model( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)</li>
+<li>FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)</li>
+<li>NAMED-QUERY is DELETED when these are DELETED NAMED-QUERY-ELEMENT</li></ul>
</section>
@@ -138664,16 +159754,15 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>TBD</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO named-query-element (comprises named-query-element, Many2Many)</li>
-<li>TO model (Many2One)</li>
-<li>TO property-constraint (comprises named-query-element, One2Many)</li>
-<li>TO related-lookup (comprises named-query-element, One2Many)</li>
-<li>FROM named-query (is composed of named-query-element)</li>
-<li>FROM named-query-element (is composed of named-query-element)</li></ul>
+<li>TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)</li>
+<li>TO model( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)</li>
+<li>TO named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)</li>
+<li>FROM property-constraint( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)</li>
+<li>FROM related-lookup( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)</li>
+<li>FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)</li>
+<li>NAMED-QUERY-ELEMENT is DELETED when these are DELETED PROPERTY-CONSTRAINT,RELATED-LOOKUP</li></ul>
</section>
@@ -139285,11 +160374,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<div class="panel-body">
<section class="json-schema-description">
- <h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
-<h6 id="related-nodes">Related Nodes</h6>
+ <h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM l3-network</li></ul>
+<li>FROM l3-network( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)</li></ul>
</section>
@@ -139380,11 +160467,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Network profile populated by SDN-GP for SNMP</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM generic-vnf</li></ul>
+<li>TO generic-vnf( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)</li></ul>
</section>
@@ -139504,11 +160589,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO l-interface (comprises newvce, Many2Many)</li></ul>
+<li>FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)</li>
+<li>NEWVCE is DELETED when these are DELETED L-INTERFACE</li></ul>
</section>
@@ -140072,13 +161156,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>OAM network, to be deprecated shortly. Do not use for new purposes.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_IF_ANY_IN_EDGES</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO complex (Many2Many)</li>
-<li>TO service-capability (Many2Many)</li>
-<li>FROM cloud-region (is composed of oam-network)</li></ul>
+<li>TO cloud-region( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>TO complex( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)</li>
+<li>TO service-capability( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)</li></ul>
</section>
@@ -140224,6 +161306,182 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-operational-environment" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/operational-environment"></a>operational-environment:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>It is a logical partition of the cloud which allows to have multiple environments in the production AIC.</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)</li>
+<li>FROM operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="operational-environment-id">
+ <span class="json-property-name">operational-environment-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>UUID of an operational environment</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="operational-environment-name">
+ <span class="json-property-name">operational-environment-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Operational Environment name</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="operational-environment-type">
+ <span class="json-property-name">operational-environment-type:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Operational Environment Type.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="operational-environment-status">
+ <span class="json-property-name">operational-environment-status:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Status</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="tenant-context">
+ <span class="json-property-name">tenant-context:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Tenant Context.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="workload-context">
+ <span class="json-property-name">workload-context:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Workload Context.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-operational-environments" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/operational-environments"></a>operational-environments:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>a logical partition of the cloud which allows to have multiple environments in the production AIC.</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="operational-environment">
+ <span class="json-property-name">operational-environment:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/operational-environment">operational-environment</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-overloaded-model" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/overloaded-model"></a>overloaded-model:
@@ -140387,6 +161645,129 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-owning-entities" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/owning-entities"></a>owning-entities:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Collection of owning-entities</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="owning-entity">
+ <span class="json-property-name">owning-entity:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/owning-entity">owning-entity</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-owning-entity" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/owning-entity"></a>owning-entity:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>describes an owning-entity</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo owning-entity, MANY2ONE)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="owning-entity-id">
+ <span class="json-property-name">owning-entity-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>UUID of an owning entity</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="owning-entity-name">
+ <span class="json-property-name">owning-entity-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Owning entity name</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-p-interface" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/p-interface"></a>p-interface:
@@ -140399,17 +161780,17 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Physical interface (e.g., nic)</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO l-interface (comprises p-interface, Many2Many)</li>
-<li>TO physical-link (Many2Many)</li>
-<li>TO logical-link (Many2One)</li>
-<li>FROM lag-interface</li>
-<li>FROM pserver (is composed of p-interface)</li>
-<li>FROM pnf (is composed of p-interface)</li>
-<li>FROM vpls-pe (is composed of p-interface)</li></ul>
+<li>TO logical-link( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)</li>
+<li>TO physical-link( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)</li>
+<li>TO pnf( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)</li>
+<li>TO pserver( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)</li>
+<li>TO vpls-pe( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)</li>
+<li>FROM lag-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)</li>
+<li>FROM l-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)</li>
+<li>P-INTERFACE is DELETED when these are DELETED L-INTERFACE</li>
+<li>P-INTERFACE deletion means associated objects of these types are also DELETED:PHYSICAL-LINK</li></ul>
</section>
@@ -140621,11 +162002,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Collection of physical connections, typically between p-interfaces</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM p-interface</li></ul>
+<li>FROM p-interface( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)</li></ul>
</section>
@@ -140793,6 +162172,116 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-platform" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/platform"></a>platform:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>describes a platform</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO generic-vnf( platform org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="platform-name">
+ <span class="json-property-name">platform-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Name of the platform</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-platforms" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/platforms"></a>platforms:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Collection of platforms</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="platform">
+ <span class="json-property-name">platform:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/platform">platform</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-pnf" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/pnf"></a>pnf:
@@ -140805,17 +162294,16 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>PNF represents a physical network function. typically equipment used in the D1 world.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO p-interface (comprises pnf, Many2Many)</li>
-<li>TO lag-interface (comprises pnf, One2Many)</li>
-<li>TO complex (Many2One)</li>
-<li>TO instance-group (Many2Many)</li>
-<li>TO zone (Many2One)</li>
-<li>FROM logical-link</li>
-<li>FROM service-instance</li></ul>
+<li>TO complex( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>TO instance-group( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>TO zone( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)</li>
+<li>FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)</li>
+<li>FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)</li>
+<li>FROM p-interface( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf pnf, ONE2MANY)</li>
+<li>PNF is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE</li></ul>
</section>
@@ -141203,12 +162691,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Used to capture the network interfaces of this VCE</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO cvlan-tag (comprises port-group, Many2Many)</li>
-<li>FROM vce (is composed of port-group)</li></ul>
+<li>TO vce( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)</li>
+<li>FROM cvlan-tag( cvlan-tag org.onap.relationships.inventory.BelongsTo port-group, MANY2ONE)</li>
+<li>PORT-GROUP is DELETED when these are DELETED CVLAN-TAG</li></ul>
</section>
@@ -141429,6 +162916,116 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-project" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/project"></a>project:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>describes the project</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO service-instance( project org.onap.relationships.inventory.Uses service-instance, ONE2MANY)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="project-name">
+ <span class="json-property-name">project-name:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Name of the project deploying a service</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-projects" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/projects"></a>projects:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Collection of projects</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="project">
+ <span class="json-property-name">project:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/project">project</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-properties" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/properties"></a>properties:
@@ -141484,11 +163081,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>TBD</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM named-query-element (is composed of property-constraint)</li></ul>
+<li>TO named-query-element( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)</li></ul>
</section>
@@ -141606,20 +163201,21 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Compute host whose hostname must be unique and must exactly match what is sent as a relationship to a vserver.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_4_IN_EDGES_OR_CASCADE</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO complex (Many2One)</li>
-<li>TO cloud-region (Many2One)</li>
-<li>TO availability-zone (Many2One)</li>
-<li>TO lag-interface (comprises pserver, Many2Many)</li>
-<li>TO p-interface (comprises pserver, Many2Many)</li>
-<li>TO zone (Many2One)</li>
-<li>FROM generic-vnf</li>
-<li>FROM group-assignment</li>
-<li>FROM vserver</li>
-<li>FROM logical-link</li></ul>
+<li>TO group-assignment( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)</li>
+<li>TO availability-zone( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)</li>
+<li>TO cloud-region( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)</li>
+<li>TO complex( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>TO zone( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)</li>
+<li>FROM generic-vnf( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)</li>
+<li>FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)</li>
+<li>FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)</li>
+<li>FROM p-interface( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)</li>
+<li>FROM vserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)</li>
+<li>PSERVER cannot be deleted if linked to GENERIC-VNF,LOGICAL-LINK,VSERVER</li>
+<li>PSERVER is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE</li>
+<li>PSERVER cannot be deleted if linked to GROUP-ASSIGNMENT</li></ul>
</section>
@@ -142104,11 +163700,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>TBD</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM named-query-element (is composed of related-lookup)</li></ul>
+<li>TO named-query-element( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)</li></ul>
</section>
@@ -142355,26 +163949,6 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
</section> </div>
</dd>
- <dt data-property-name="related-to-property">
- <span class="json-property-name">related-to-property:</span>
- <span class="json-property-type">object[]</span>
- <span class="json-property-range" title="Value limits"></span>
-
- </dt>
- <dd>
-
- <div class="json-inner-schema">
-
- <section class="json-schema-array-items">
- <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/related-to-property">related-to-property</a>
- </span>
- <span class="json-property-range" title="Value limits"></span>
-
- <div class="json-inner-schema">
-
- </div>
- </section> </div>
- </dd>
</dl>
</section>
</div>
@@ -142651,11 +164225,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Openstack route table reference.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM l3-network</li></ul>
+<li>FROM l3-network( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)</li></ul>
</section>
@@ -142764,6 +164336,129 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-route-target" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/route-target"></a>route-target:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Route target information</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO vpn-binding( route-target org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2ONE)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="global-route-target">
+ <span class="json-property-name">global-route-target:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Number used to identify an RT, globally unique in the network</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="route-target-role">
+ <span class="json-property-name">route-target-role:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Role assigned to this route target</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-route-targets" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/route-targets"></a>route-targets:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Collection of route target information</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="route-target">
+ <span class="json-property-name">route-target:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/route-target">route-target</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-routing-instance" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/routing-instance"></a>routing-instance:
@@ -142775,12 +164470,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<div class="panel-body">
<section class="json-schema-description">
- <h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
-<h6 id="related-nodes">Related Nodes</h6>
+ <h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO site-pair (comprises routing-instance, Many2Many)</li>
-<li>FROM site-pair-set (is composed of routing-instance)</li></ul>
+<li>TO site-pair-set( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)</li>
+<li>FROM site-pair( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)</li>
+<li>ROUTING-INSTANCE is DELETED when these are DELETED SITE-PAIR</li></ul>
</section>
@@ -143223,11 +164917,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Openstack segmentation assignment.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM l3-network (is composed of segmentation-assignment)</li></ul>
+<li>TO l3-network( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)</li></ul>
</section>
@@ -143335,8 +165027,6 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Stand-in for service model definitions. Likely to be deprecated in favor of models from ASDC. Does not strictly map to ASDC services.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_IF_ANY_IN_EDGES</p>
</section>
@@ -143481,12 +165171,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Early definition of server/resource pairings, likely to be replaced by models. No new use should be made of this.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_IF_ANY_IN_EDGES</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM availability-zone</li>
-<li>FROM oam-network</li></ul>
+<li>FROM availability-zone( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)</li>
+<li>FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)</li>
+<li>SERVICE-CAPABILITY cannot be deleted if linked to AVAILABILITY-ZONE,OAM-NETWORK</li></ul>
</section>
@@ -143687,26 +165376,26 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Instance of a service</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO cvlan-tag (Many2Many)</li>
-<li>TO pnf (One2Many)</li>
-<li>TO connector (Many2Many)</li>
-<li>TO metadatum (comprises service-instance, Many2Many)</li>
-<li>TO logical-link (Many2Many)</li>
-<li>TO vlan (One2Many)</li>
-<li>TO service-instance (One2Many)</li>
-<li>TO ctag-assignment (One2Many)</li>
-<li>TO instance-group (Many2Many)</li>
-<li>TO allotted-resource (comprises service-instance, Many2Many)</li>
-<li>TO allotted-resource (Many2Many)</li>
-<li>FROM generic-vnf</li>
-<li>FROM l3-network</li>
-<li>FROM service-subscription (is composed of service-instance)</li>
-<li>FROM vce</li>
-<li>FROM service-instance</li></ul>
+<li>TO generic-vnf( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)</li>
+<li>TO l3-network( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)</li>
+<li>TO allotted-resource( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY)</li>
+<li>TO connector( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)</li>
+<li>TO ctag-assignment( service-instance org.onap.relationships.inventory.Uses ctag-assignment, ONE2MANY)</li>
+<li>TO cvlan-tag( service-instance org.onap.relationships.inventory.ComposedOf cvlan-tag, MANY2MANY)</li>
+<li>TO instance-group( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>TO logical-link( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)</li>
+<li>TO pnf( service-instance org.onap.relationships.inventory.ComposedOf pnf, ONE2MANY)</li>
+<li>TO service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)</li>
+<li>TO vlan( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)</li>
+<li>TO service-subscription( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)</li>
+<li>TO vce( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)</li>
+<li>FROM allotted-resource( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)</li>
+<li>FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)</li>
+<li>SERVICE-INSTANCE is DELETED when these are DELETED ALLOTTED-RESOURCE,METADATUM</li>
+<li>SERVICE-INSTANCE deletion means associated objects of these types are also DELETED:LOGICAL-LINK</li></ul>
</section>
@@ -144034,13 +165723,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Object that group service instances.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO service-instance (comprises service-subscription, Many2Many)</li>
-<li>FROM customer (is composed of service-subscription)</li>
-<li>FROM tenant</li></ul>
+<li>TO customer( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)</li>
+<li>TO tenant( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)</li>
+<li>SERVICE-SUBSCRIPTION is DELETED when these are DELETED SERVICE-INSTANCE</li></ul>
</section>
@@ -144220,12 +165908,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<div class="panel-body">
<section class="json-schema-description">
- <h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
-<h6 id="related-nodes">Related Nodes</h6>
+ <h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO class-of-service (comprises site-pair, Many2Many)</li>
-<li>FROM routing-instance (is composed of site-pair)</li></ul>
+<li>TO routing-instance( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)</li>
+<li>FROM class-of-service( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)</li>
+<li>SITE-PAIR is DELETED when these are DELETED CLASS-OF-SERVICE</li></ul>
</section>
@@ -144372,12 +166059,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Set of instances for probes used to measure service level agreements</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO routing-instance (comprises site-pair-set, Many2Many)</li>
-<li>FROM generic-vnf</li></ul>
+<li>TO generic-vnf( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)</li>
+<li>FROM routing-instance( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)</li>
+<li>SITE-PAIR-SET is DELETED when these are DELETED ROUTING-INSTANCE</li></ul>
</section>
@@ -144546,12 +166232,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Openstack snapshot</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM cloud-region (is composed of snapshot)</li>
-<li>FROM vserver</li></ul>
+<li>TO cloud-region( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>FROM vserver( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)</li></ul>
</section>
@@ -144755,6 +166439,117 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-sriov-pf" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/sriov-pf"></a>sriov-pf:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>SR-IOV Physical Function</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO p-interface( sriov-pf org.onap.relationships.inventory.BelongsTo p-interface, ONE2ONE)</li>
+<li>FROM sriov-vf( sriov-vf org.onap.relationships.inventory.Uses sriov-pf, MANY2ONE)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="pf-pci-id">
+ <span class="json-property-name">pf-pci-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>Identifier for the sriov-pf</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-sriov-pfs" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/sriov-pfs"></a>sriov-pfs:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>Collection of SR-IOV Physical Functions.</p>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="sriov-pf">
+ <span class="json-property-name">sriov-pf:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/sriov-pf">sriov-pf</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-sriov-vf" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/sriov-vf"></a>sriov-vf:
@@ -144767,11 +166562,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>SR-IOV Virtual Function (not to be confused with virtual network function)</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM l-interface (is composed of sriov-vf)</li></ul>
+<li>TO l-interface( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)</li></ul>
</section>
@@ -145061,13 +166854,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<div class="panel-body">
<section class="json-schema-description">
- <h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_IF_ANY_IN_EDGES</p>
-<h6 id="related-nodes">Related Nodes</h6>
+ <h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM l3-interface-ipv4-address-list</li>
-<li>FROM l3-interface-ipv6-address-list</li>
-<li>FROM l3-network (is composed of subnet)</li></ul>
+<li>TO l3-network( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)</li>
+<li>FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)</li>
+<li>FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)</li>
+<li>SUBNET cannot be deleted if linked to L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST</li></ul>
</section>
@@ -145328,16 +167120,15 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Openstack tenant</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO l3-network (Many2Many)</li>
-<li>TO service-subscription (Many2Many)</li>
-<li>TO vserver (comprises tenant, One2Many)</li>
-<li>FROM cloud-region (is composed of tenant)</li>
-<li>FROM group-assignment</li>
-<li>FROM volume-group</li></ul>
+<li>TO cloud-region( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>TO group-assignment( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)</li>
+<li>TO l3-network( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)</li>
+<li>TO volume-group( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)</li>
+<li>FROM service-subscription( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)</li>
+<li>FROM vserver( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)</li>
+<li>TENANT cannot be deleted if linked to VSERVER</li></ul>
</section>
@@ -145478,11 +167269,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Represents the specifics of a tunnel cross connect piece of a resource that gets separately allotted</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM allotted-resource (is composed of tunnel-xconnect)</li></ul>
+<li>TO allotted-resource( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)</li></ul>
</section>
@@ -145765,17 +167554,16 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Virtual Customer Edge Router, used specifically for Gamma. This object is deprecated.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO availability-zone (Many2Many)</li>
-<li>TO complex (Many2Many)</li>
-<li>TO port-group (comprises vce, Many2Many)</li>
-<li>TO vserver (Many2Many)</li>
-<li>TO service-instance (Many2Many)</li>
-<li>TO entitlement (comprises vce, One2Many)</li>
-<li>TO license (comprises vce, One2Many)</li></ul>
+<li>TO availability-zone( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)</li>
+<li>TO complex( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)</li>
+<li>TO vserver( vce tosca.relationships.HostedOn vserver, ONE2MANY)</li>
+<li>FROM entitlement( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)</li>
+<li>FROM license( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)</li>
+<li>FROM port-group( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)</li>
+<li>VCE is DELETED when these are DELETED ENTITLEMENT,LICENSE,PORT-GROUP</li></ul>
</section>
@@ -146149,15 +167937,14 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>a deployment unit of VNFCs</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO volume-group (One2One)</li>
-<li>TO l3-network (Many2Many)</li>
-<li>TO vnfc (One2Many)</li>
-<li>FROM vserver</li>
-<li>FROM generic-vnf (is composed of vf-module)</li></ul>
+<li>TO generic-vnf( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>TO l3-network( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)</li>
+<li>TO vnfc( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)</li>
+<li>TO volume-group( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)</li>
+<li>TO vserver( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)</li>
+<li>VF-MODULE cannot be deleted if linked to VNFC</li></ul>
</section>
@@ -146421,11 +168208,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>vig-server contains information about a vig server used for IPSec-configuration. Populated by SDN-C from 1607</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM ipsec-configuration (is composed of vig-server)</li></ul>
+<li>TO ipsec-configuration( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)</li></ul>
</section>
@@ -146541,6 +168326,294 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</section>
</div>
</div>
+ <div id="definition-vip-ipv4-address-list" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/vip-ipv4-address-list"></a>vip-ipv4-address-list:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>IPv4 Address Range</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO cloud-region( vip-ipv4-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>TO instance-group( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>TO subnet( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)</li>
+<li>FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv4-address-list, MANY2MANY)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="vip-ipv4-address">
+ <span class="json-property-name">vip-ipv4-address:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>IP address</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="vip-ipv4-prefix-length">
+ <span class="json-property-name">vip-ipv4-prefix-length:</span>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Prefix length, 32 for single address</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="vlan-id-inner">
+ <span class="json-property-name">vlan-id-inner:</span>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Inner VLAN tag</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="vlan-id-outer">
+ <span class="json-property-name">vlan-id-outer:</span>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Outer VLAN tag</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="is-floating">
+ <span class="json-property-name">is-floating:</span>
+ <span class="json-property-type">boolean</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Indicator of fixed or floating address</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="neutron-network-id">
+ <span class="json-property-name">neutron-network-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Neutron network id of the interface that address belongs to</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="neutron-subnet-id">
+ <span class="json-property-name">neutron-subnet-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Neutron id of subnet that address belongs to</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
+ <div id="definition-vip-ipv6-address-list" class="panel panel-definition">
+ <div class="panel-heading">
+ <h3 class="panel-title"><a name="/definitions/vip-ipv6-address-list"></a>vip-ipv6-address-list:
+ <span class="json-property-type"><span class="json-property-type">object</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </span>
+ </h3>
+ </div>
+ <div class="panel-body">
+ <section class="json-schema-description">
+ <p>IPv6 Address Range</p>
+<h6 id="related-nodes">Related Nodes</h6>
+<ul>
+<li>TO cloud-region( vip-ipv6-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>TO instance-group( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)</li>
+<li>TO subnet( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)</li>
+<li>FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv6-address-list, MANY2MANY)</li></ul>
+
+ </section>
+
+ <section class="json-schema-properties">
+ <dl>
+ <dt data-property-name="vip-ipv6-address">
+ <span class="json-property-name">vip-ipv6-address:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <span class="json-property-required"></span>
+ </dt>
+ <dd>
+ <p>IP address</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="vip-ipv6-prefix-length">
+ <span class="json-property-name">vip-ipv6-prefix-length:</span>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Prefix length, 128 for single address</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="vlan-id-inner">
+ <span class="json-property-name">vlan-id-inner:</span>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Inner VLAN tag</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="vlan-id-outer">
+ <span class="json-property-name">vlan-id-outer:</span>
+ <span class="json-property-type">integer</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Outer VLAN tag</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="is-floating">
+ <span class="json-property-name">is-floating:</span>
+ <span class="json-property-type">boolean</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Indicator of fixed or floating address</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="resource-version">
+ <span class="json-property-name">resource-version:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Used for optimistic concurrency. Must be empty on create, valid on update and delete.</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="neutron-network-id">
+ <span class="json-property-name">neutron-network-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Neutron network id of the interface that address belongs to</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="neutron-subnet-id">
+ <span class="json-property-name">neutron-subnet-id:</span>
+ <span class="json-property-type">string</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+ <p>Neutron id of subnet that address belongs to</p>
+ <div class="json-inner-schema">
+
+ </div>
+ </dd>
+ <dt data-property-name="relationship-list">
+ <span class="json-property-name">relationship-list:</span>
+ <span class="json-property-type">object[]</span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ </dt>
+ <dd>
+
+ <div class="json-inner-schema">
+
+ <section class="json-schema-array-items">
+ <span class="json-property-type"> <a class="json-schema-ref" href="#/definitions/relationship">relationship</a>
+ </span>
+ <span class="json-property-range" title="Value limits"></span>
+
+ <div class="json-inner-schema">
+
+ </div>
+ </section> </div>
+ </dd>
+ </dl>
+ </section>
+ </div>
+ </div>
<div id="definition-virtual-data-center" class="panel panel-definition">
<div class="panel-heading">
<h3 class="panel-title"><a name="/definitions/virtual-data-center"></a>virtual-data-center:
@@ -146553,13 +168626,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Virtual organization of cloud infrastructure elements in a data center context</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO generic-vnf (Many2Many)</li>
-<li>TO logical-link (Many2Many)</li>
-<li>FROM connector</li></ul>
+<li>FROM connector( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)</li>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)</li>
+<li>FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)</li></ul>
</section>
@@ -146680,17 +168751,17 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Definition of vlan</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO l3-interface-ipv4-address-list (comprises vlan, Many2Many)</li>
-<li>TO l3-interface-ipv6-address-list (comprises vlan, Many2Many)</li>
-<li>TO multicast-configuration (Many2Many)</li>
-<li>TO logical-link (Many2Many)</li>
-<li>FROM l-interface (is composed of vlan)</li>
-<li>FROM service-instance</li>
-<li>FROM allotted-resource</li></ul>
+<li>TO l-interface( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)</li>
+<li>TO logical-link( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)</li>
+<li>TO multicast-configuration( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)</li>
+<li>FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY)</li>
+<li>FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)</li>
+<li>FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)</li>
+<li>FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)</li>
+<li>VLAN is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST</li>
+<li>VLAN deletion means associated objects of these types are also DELETED:LOGICAL-LINK</li></ul>
</section>
@@ -146964,11 +169035,10 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Image object that pertain to a VNF that doesn't have associated vservers. This is a kludge.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_IF_ANY_IN_EDGES</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM generic-vnf</li></ul>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)</li>
+<li>VNF-IMAGE cannot be deleted if linked to GENERIC-VNF</li></ul>
</section>
@@ -147125,13 +169195,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
</div>
<div class="panel-body">
<section class="json-schema-description">
- <h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
-<h6 id="related-nodes">Related Nodes</h6>
+ <h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM vserver</li>
-<li>FROM vf-module</li>
-<li>FROM generic-vnf</li></ul>
+<li>TO generic-vnf( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)</li>
+<li>TO vserver( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)</li>
+<li>FROM vf-module( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)</li></ul>
</section>
@@ -147337,11 +169405,9 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Ephemeral Block storage volume.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM vserver (is composed of volume)</li></ul>
+<li>FROM vserver (PARENT of volume, vserver tosca.relationships.AttachesTo volume)</li></ul>
</section>
@@ -147421,15 +169487,13 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Persistent block-level storage.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO complex (Many2Many)</li>
-<li>TO tenant (Many2Many)</li>
-<li>FROM cloud-region (is composed of volume-group)</li>
-<li>FROM vf-module</li>
-<li>FROM generic-vnf</li></ul>
+<li>TO cloud-region( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)</li>
+<li>TO complex( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM generic-vnf( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)</li>
+<li>FROM vf-module( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)</li>
+<li>FROM tenant( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)</li></ul>
</section>
@@ -147652,14 +169716,13 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>VPLS Provider Edge routers.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO complex (Many2Many)</li>
-<li>TO ctag-pool (Many2Many)</li>
-<li>TO p-interface (comprises vpls-pe, Many2Many)</li>
-<li>TO lag-interface (comprises vpls-pe, Many2Many)</li></ul>
+<li>TO complex( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>TO ctag-pool( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)</li>
+<li>FROM lag-interface( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)</li>
+<li>FROM p-interface( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)</li>
+<li>VPLS-PE is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE</li></ul>
</section>
@@ -147854,12 +169917,11 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>VPN binding</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>ERROR_4_IN_EDGES_OR_CASCADE</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>FROM l3-network</li>
-<li>FROM logical-link</li></ul>
+<li>FROM l3-network( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)</li>
+<li>FROM logical-link( logical-link org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)</li>
+<li>VPN-BINDING cannot be deleted if linked to L3-NETWORK,LOGICAL-LINK</li></ul>
</section>
@@ -148038,21 +170100,21 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>Virtual Servers, aka virtual machine or VM.</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>CASCADE_TO_CHILDREN</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO flavor (Many2One)</li>
-<li>TO image (Many2One)</li>
-<li>TO l-interface (comprises vserver, Many2Many)</li>
-<li>TO pserver (Many2One)</li>
-<li>TO volume (comprises vserver, Many2Many)</li>
-<li>TO vnfc (Many2Many)</li>
-<li>TO snapshot (One2One)</li>
-<li>TO vf-module (Many2One)</li>
-<li>FROM generic-vnf</li>
-<li>FROM tenant (is composed of vserver)</li>
-<li>FROM vce</li></ul>
+<li>TO tenant( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)</li>
+<li>TO flavor( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)</li>
+<li>TO image( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)</li>
+<li>TO pserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)</li>
+<li>TO snapshot( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)</li>
+<li>TO volume (CHILD of vserver, vserver tosca.relationships.AttachesTo volume, ONE2MANY)</li>
+<li>FROM generic-vnf( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)</li>
+<li>FROM vce( vce tosca.relationships.HostedOn vserver, ONE2MANY)</li>
+<li>FROM l-interface( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)</li>
+<li>FROM vf-module( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)</li>
+<li>FROM vnfc( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)</li>
+<li>VSERVER is DELETED when these are DELETED L-INTERFACE</li>
+<li>VSERVER deletion means associated objects of these types are also DELETED:VOLUME</li></ul>
</section>
@@ -148274,14 +170336,12 @@ This document is best viewed with Firefox or Chrome. Nodes can be found by appen
<div class="panel-body">
<section class="json-schema-description">
<p>A zone is a grouping of assets in a location homing to the same connections into the CBB</p>
-<h6 id="default-delete-scope">Default Delete Scope</h6>
-<p>THIS_NODE_ONLY</p>
<h6 id="related-nodes">Related Nodes</h6>
<ul>
-<li>TO complex (Many2One)</li>
-<li>FROM cloud-region</li>
-<li>FROM pserver</li>
-<li>FROM pnf</li></ul>
+<li>TO complex( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)</li>
+<li>FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)</li>
+<li>FROM pnf( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)</li>
+<li>FROM pserver( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)</li></ul>
</section>
diff --git a/aai-schema/src/main/resources/aai_swagger_yaml/aai_swagger_v10.yaml b/aai-schema/src/main/resources/aai_swagger_yaml/aai_swagger_v10.yaml
index b5d83e21..aaa008d4 100644
--- a/aai-schema/src/main/resources/aai_swagger_yaml/aai_swagger_v10.yaml
+++ b/aai-schema/src/main/resources/aai_swagger_yaml/aai_swagger_v10.yaml
@@ -1,28 +1,9 @@
-#
-# ============LICENSE_START=======================================================
-# org.onap.aai
-# ================================================================================
-# Copyright © 2017 AT&T Intellectual Property. All rights reserved.
-# ================================================================================
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-# http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-# ============LICENSE_END=========================================================
-#
-# ECOMP is a trademark and service mark of AT&T Intellectual Property.
-#
-
swagger: "2.0"
info:
description: |
+
+ [Differences versus the previous schema version](apidocs/aai_swagger_v10.diff)
+
Copyright &copy; 2017 AT&amp;T Intellectual Property. All rights reserved.
Licensed under the Creative Commons License, Attribution 4.0 Intl. (the &quot;License&quot;); you may not use this documentation except in compliance with the License.
@@ -71,19 +52,22 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: target-pe
in: path
description: The Target provider edge router
required: true
type: string
+ example: __TARGET-PE__
- name: availability-zone-name
in: path
description: Name of the availability zone
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureComplexesComplexCtagPoolsCtagPool.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -108,16 +92,19 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: target-pe
in: path
description: The Target provider edge router
required: true
type: string
+ example: __TARGET-PE__
- name: availability-zone-name
in: path
description: Name of the availability zone
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
/cloud-infrastructure/complexes/complex/{physical-location-id}/ctag-pools/ctag-pool/{target-pe}/{availability-zone-name}:
get:
tags:
@@ -132,7 +119,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/ctag-pool"
+ $ref: "#/getDefinitions/ctag-pool"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -141,16 +128,19 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: target-pe
in: path
description: The Target provider edge router
required: true
type: string
+ example: __TARGET-PE__
- name: availability-zone-name
in: path
description: Name of the availability zone
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: data-center-code
in: query
description: Data center code which can be an alternate way to identify a complex
@@ -170,7 +160,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing ctag-pool
- description: create or update an existing ctag-pool
+ description: |
+ Create or update an existing ctag-pool.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureComplexesComplexCtagPoolsCtagPool
consumes:
- application/json
@@ -187,22 +180,76 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: target-pe
in: path
description: The Target provider edge router
required: true
type: string
+ example: __TARGET-PE__
- name: availability-zone-name
in: path
description: Name of the availability zone
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: body
in: body
- description: ctag-pool object that needs to be created or updated
+ description: ctag-pool object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureComplexesComplexCtagPoolsCtagPool.json)
required: true
schema:
$ref: "#/definitions/ctag-pool"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing ctag-pool
+ description: |
+ Update an existing ctag-pool
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureComplexesComplexCtagPoolsCtagPool
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: physical-location-id
+ in: path
+ description: Unique identifier for physical location, e.g., CLLI
+ required: true
+ type: string
+ example: __PHYSICAL-LOCATION-ID__
+ - name: target-pe
+ in: path
+ description: The Target provider edge router
+ required: true
+ type: string
+ example: __TARGET-PE__
+ - name: availability-zone-name
+ in: path
+ description: Name of the availability zone
+ required: true
+ type: string
+ example: __AVAILABILITY-ZONE-NAME__
+ - name: body
+ in: body
+ description: ctag-pool object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/ctag-pool"
delete:
tags:
- CloudInfrastructure
@@ -224,16 +271,19 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: target-pe
in: path
description: The Target provider edge router
required: true
type: string
+ example: __TARGET-PE__
- name: availability-zone-name
in: path
description: Name of the availability zone
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -253,7 +303,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/ctag-pools"
+ $ref: "#/getDefinitions/ctag-pools"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -262,6 +312,7 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: data-center-code
in: query
description: Data center code which can be an alternate way to identify a complex
@@ -298,9 +349,10 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureComplexesComplex.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -325,6 +377,7 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
/cloud-infrastructure/complexes/complex/{physical-location-id}:
get:
tags:
@@ -339,7 +392,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/complex"
+ $ref: "#/getDefinitions/complex"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -348,6 +401,7 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: data-center-code
in: query
description: Data center code which can be an alternate way to identify a complex
@@ -367,7 +421,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing complex
- description: create or update an existing complex
+ description: |
+ Create or update an existing complex.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureComplexesComplex
consumes:
- application/json
@@ -384,12 +441,52 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: body
in: body
- description: complex object that needs to be created or updated
+ description: complex object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureComplexesComplex.json)
required: true
schema:
$ref: "#/definitions/complex"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing complex
+ description: |
+ Update an existing complex
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureComplexesComplex
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: physical-location-id
+ in: path
+ description: Unique identifier for physical location, e.g., CLLI
+ required: true
+ type: string
+ example: __PHYSICAL-LOCATION-ID__
+ - name: body
+ in: body
+ description: complex object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/complex"
delete:
tags:
- CloudInfrastructure
@@ -411,6 +508,7 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -430,7 +528,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/complexes"
+ $ref: "#/getDefinitions/complexes"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/volume-groups/volume-group/{volume-group-id}/relationship-list/relationship:
@@ -454,19 +552,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: volume-group-id
in: path
description: Unique ID of volume-group.
required: true
type: string
+ example: __VOLUME-GROUP-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -491,16 +592,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: volume-group-id
in: path
description: Unique ID of volume-group.
required: true
type: string
+ example: __VOLUME-GROUP-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/volume-groups/volume-group/{volume-group-id}:
get:
tags:
@@ -515,7 +619,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/volume-group"
+ $ref: "#/getDefinitions/volume-group"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -524,16 +628,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: volume-group-id
in: path
description: Unique ID of volume-group.
required: true
type: string
+ example: __VOLUME-GROUP-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -563,7 +670,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing volume-group
- description: create or update an existing volume-group
+ description: |
+ Create or update an existing volume-group.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup
consumes:
- application/json
@@ -580,22 +690,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: volume-group-id
in: path
description: Unique ID of volume-group.
required: true
type: string
+ example: __VOLUME-GROUP-ID__
- name: body
in: body
- description: volume-group object that needs to be created or updated
+ description: volume-group object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup.json)
required: true
schema:
$ref: "#/definitions/volume-group"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing volume-group
+ description: |
+ Update an existing volume-group
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: volume-group-id
+ in: path
+ description: Unique ID of volume-group.
+ required: true
+ type: string
+ example: __VOLUME-GROUP-ID__
+ - name: body
+ in: body
+ description: volume-group object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/volume-group"
delete:
tags:
- CloudInfrastructure
@@ -617,16 +781,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: volume-group-id
in: path
description: Unique ID of volume-group.
required: true
type: string
+ example: __VOLUME-GROUP-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -646,7 +813,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/volume-groups"
+ $ref: "#/getDefinitions/volume-groups"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -655,11 +822,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -691,29 +860,34 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: volume-id
in: path
description: Unique ID of block storage volume relative to the vserver.
required: true
type: string
+ example: __VOLUME-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -738,26 +912,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: volume-id
in: path
description: Unique ID of block storage volume relative to the vserver.
required: true
type: string
+ example: __VOLUME-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/volumes/volume/{volume-id}:
get:
tags:
@@ -772,7 +951,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/volume"
+ $ref: "#/getDefinitions/volume"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -781,26 +960,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: volume-id
in: path
description: Unique ID of block storage volume relative to the vserver.
required: true
type: string
+ example: __VOLUME-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -843,7 +1027,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing volume
- description: create or update an existing volume
+ description: |
+ Create or update an existing volume.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume
consumes:
- application/json
@@ -860,32 +1047,100 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: volume-id
in: path
description: Unique ID of block storage volume relative to the vserver.
required: true
type: string
+ example: __VOLUME-ID__
- name: body
in: body
- description: volume object that needs to be created or updated
+ description: volume object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume.json)
required: true
schema:
$ref: "#/definitions/volume"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing volume
+ description: |
+ Update an existing volume
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: volume-id
+ in: path
+ description: Unique ID of block storage volume relative to the vserver.
+ required: true
+ type: string
+ example: __VOLUME-ID__
+ - name: body
+ in: body
+ description: volume object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/volume"
delete:
tags:
- CloudInfrastructure
@@ -907,26 +1162,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: volume-id
in: path
description: Unique ID of block storage volume relative to the vserver.
required: true
type: string
+ example: __VOLUME-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -946,7 +1206,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/volumes"
+ $ref: "#/getDefinitions/volumes"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -955,21 +1215,25 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -1029,24 +1293,28 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -1071,21 +1339,25 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -1107,34 +1379,40 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -1159,31 +1437,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -1205,39 +1489,46 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -1262,36 +1553,43 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -1306,7 +1604,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -1315,36 +1613,43 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -1429,7 +1734,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -1446,42 +1754,124 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- CloudInfrastructure
@@ -1503,36 +1893,43 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -1559,39 +1956,46 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -1616,36 +2020,43 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -1660,7 +2071,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -1669,36 +2080,43 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -1783,7 +2201,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -1800,42 +2221,124 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- CloudInfrastructure
@@ -1857,36 +2360,43 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -1906,7 +2416,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -1915,31 +2425,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -2008,7 +2524,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -2025,37 +2544,112 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- CloudInfrastructure
@@ -2077,31 +2671,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -2121,7 +2721,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -2130,26 +2730,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -2224,34 +2829,40 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -2276,31 +2887,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -2315,7 +2932,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -2324,31 +2941,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -2426,7 +3049,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -2443,37 +3069,112 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- CloudInfrastructure
@@ -2495,31 +3196,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -2539,7 +3246,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -2548,26 +3255,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -2642,29 +3354,34 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -2689,26 +3406,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -2730,34 +3452,40 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -2782,31 +3510,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -2821,7 +3555,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -2830,31 +3564,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -2928,7 +3668,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -2945,37 +3688,112 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- CloudInfrastructure
@@ -2997,31 +3815,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -3048,34 +3872,40 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -3100,31 +3930,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -3139,7 +3975,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -3148,31 +3984,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -3246,7 +4088,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -3263,37 +4108,112 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- CloudInfrastructure
@@ -3315,31 +4235,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -3359,7 +4285,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -3368,26 +4294,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -3445,7 +4376,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface
consumes:
- application/json
@@ -3462,32 +4396,100 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- CloudInfrastructure
@@ -3509,26 +4511,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -3548,7 +4555,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -3557,21 +4564,25 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -3624,7 +4635,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vserver"
+ $ref: "#/getDefinitions/vserver"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -3633,21 +4644,25 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -3690,7 +4705,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing vserver
- description: create or update an existing vserver
+ description: |
+ Create or update an existing vserver.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver
consumes:
- application/json
@@ -3707,27 +4725,88 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: body
in: body
- description: vserver object that needs to be created or updated
+ description: vserver object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver.json)
required: true
schema:
$ref: "#/definitions/vserver"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing vserver
+ description: |
+ Update an existing vserver
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: body
+ in: body
+ description: vserver object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vserver"
delete:
tags:
- CloudInfrastructure
@@ -3749,21 +4828,25 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -3783,7 +4866,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vservers"
+ $ref: "#/getDefinitions/vservers"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -3792,16 +4875,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -3838,19 +4924,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenant.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -3875,16 +4964,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}:
get:
tags:
@@ -3899,7 +4991,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/tenant"
+ $ref: "#/getDefinitions/tenant"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -3908,16 +5000,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -3937,7 +5032,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing tenant
- description: create or update an existing tenant
+ description: |
+ Create or update an existing tenant.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenant
consumes:
- application/json
@@ -3954,22 +5052,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: body
in: body
- description: tenant object that needs to be created or updated
+ description: tenant object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenant.json)
required: true
schema:
$ref: "#/definitions/tenant"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing tenant
+ description: |
+ Update an existing tenant
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenant
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: body
+ in: body
+ description: tenant object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/tenant"
delete:
tags:
- CloudInfrastructure
@@ -3991,16 +5143,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -4020,7 +5175,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/tenants"
+ $ref: "#/getDefinitions/tenants"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4029,11 +5184,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4065,19 +5222,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: flavor-id
in: path
description: Flavor id, expected to be unique across cloud-region.
required: true
type: string
+ example: __FLAVOR-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -4102,16 +5262,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: flavor-id
in: path
description: Flavor id, expected to be unique across cloud-region.
required: true
type: string
+ example: __FLAVOR-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/flavors/flavor/{flavor-id}:
get:
tags:
@@ -4126,7 +5289,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/flavor"
+ $ref: "#/getDefinitions/flavor"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4135,16 +5298,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: flavor-id
in: path
description: Flavor id, expected to be unique across cloud-region.
required: true
type: string
+ example: __FLAVOR-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4164,7 +5330,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing flavor
- description: create or update an existing flavor
+ description: |
+ Create or update an existing flavor.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor
consumes:
- application/json
@@ -4181,22 +5350,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: flavor-id
in: path
description: Flavor id, expected to be unique across cloud-region.
required: true
type: string
+ example: __FLAVOR-ID__
- name: body
in: body
- description: flavor object that needs to be created or updated
+ description: flavor object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor.json)
required: true
schema:
$ref: "#/definitions/flavor"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing flavor
+ description: |
+ Update an existing flavor
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: flavor-id
+ in: path
+ description: Flavor id, expected to be unique across cloud-region.
+ required: true
+ type: string
+ example: __FLAVOR-ID__
+ - name: body
+ in: body
+ description: flavor object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/flavor"
delete:
tags:
- CloudInfrastructure
@@ -4218,16 +5441,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: flavor-id
in: path
description: Flavor id, expected to be unique across cloud-region.
required: true
type: string
+ example: __FLAVOR-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -4247,7 +5473,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/flavors"
+ $ref: "#/getDefinitions/flavors"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4256,11 +5482,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4292,19 +5520,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: group-id
in: path
description: Group id, expected to be unique across cloud-region.
required: true
type: string
+ example: __GROUP-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -4329,16 +5560,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: group-id
in: path
description: Group id, expected to be unique across cloud-region.
required: true
type: string
+ example: __GROUP-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/group-assignments/group-assignment/{group-id}:
get:
tags:
@@ -4353,7 +5587,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/group-assignment"
+ $ref: "#/getDefinitions/group-assignment"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4362,16 +5596,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: group-id
in: path
description: Group id, expected to be unique across cloud-region.
required: true
type: string
+ example: __GROUP-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4396,7 +5633,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing group-assignment
- description: create or update an existing group-assignment
+ description: |
+ Create or update an existing group-assignment.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment
consumes:
- application/json
@@ -4413,22 +5653,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: group-id
in: path
description: Group id, expected to be unique across cloud-region.
required: true
type: string
+ example: __GROUP-ID__
- name: body
in: body
- description: group-assignment object that needs to be created or updated
+ description: group-assignment object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment.json)
required: true
schema:
$ref: "#/definitions/group-assignment"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing group-assignment
+ description: |
+ Update an existing group-assignment
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: group-id
+ in: path
+ description: Group id, expected to be unique across cloud-region.
+ required: true
+ type: string
+ example: __GROUP-ID__
+ - name: body
+ in: body
+ description: group-assignment object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/group-assignment"
delete:
tags:
- CloudInfrastructure
@@ -4450,16 +5744,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: group-id
in: path
description: Group id, expected to be unique across cloud-region.
required: true
type: string
+ example: __GROUP-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -4479,7 +5776,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/group-assignments"
+ $ref: "#/getDefinitions/group-assignments"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4488,11 +5785,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4524,19 +5823,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: snapshot-id
in: path
description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
required: true
type: string
+ example: __SNAPSHOT-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -4561,16 +5863,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: snapshot-id
in: path
description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
required: true
type: string
+ example: __SNAPSHOT-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/snapshots/snapshot/{snapshot-id}:
get:
tags:
@@ -4585,7 +5890,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/snapshot"
+ $ref: "#/getDefinitions/snapshot"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4594,16 +5899,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: snapshot-id
in: path
description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
required: true
type: string
+ example: __SNAPSHOT-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4643,7 +5951,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing snapshot
- description: create or update an existing snapshot
+ description: |
+ Create or update an existing snapshot.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot
consumes:
- application/json
@@ -4660,22 +5971,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: snapshot-id
in: path
description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
required: true
type: string
+ example: __SNAPSHOT-ID__
- name: body
in: body
- description: snapshot object that needs to be created or updated
+ description: snapshot object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot.json)
required: true
schema:
$ref: "#/definitions/snapshot"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing snapshot
+ description: |
+ Update an existing snapshot
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: snapshot-id
+ in: path
+ description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
+ required: true
+ type: string
+ example: __SNAPSHOT-ID__
+ - name: body
+ in: body
+ description: snapshot object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/snapshot"
delete:
tags:
- CloudInfrastructure
@@ -4697,16 +6062,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: snapshot-id
in: path
description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
required: true
type: string
+ example: __SNAPSHOT-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -4726,7 +6094,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/snapshots"
+ $ref: "#/getDefinitions/snapshots"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4735,11 +6103,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4771,19 +6141,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionImagesImage.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -4808,16 +6181,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}/metadata/metadatum/{metaname}:
get:
tags:
@@ -4832,7 +6208,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadatum"
+ $ref: "#/getDefinitions/metadatum"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4841,20 +6217,24 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4889,7 +6269,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing metadatum
- description: create or update an existing metadatum
+ description: |
+ Create or update an existing metadatum.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionImagesImageMetadataMetadatum
consumes:
- application/json
@@ -4906,26 +6289,86 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: body
in: body
- description: metadatum object that needs to be created or updated
+ description: metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionImagesImageMetadataMetadatum.json)
required: true
schema:
$ref: "#/definitions/metadatum"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing metadatum
+ description: |
+ Update an existing metadatum
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionImagesImageMetadataMetadatum
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: image-id
+ in: path
+ description: Image id, expected to be unique across cloud region
+ required: true
+ type: string
+ example: __IMAGE-ID__
+ - name: metaname
+ in: path
+ required: true
+ type: string
+ example: __METANAME__
+ - name: body
+ in: body
+ description: metadatum object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/metadatum"
delete:
tags:
- CloudInfrastructure
@@ -4947,20 +6390,24 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -4980,7 +6427,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadata"
+ $ref: "#/getDefinitions/metadata"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4989,16 +6436,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5043,7 +6493,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/image"
+ $ref: "#/getDefinitions/image"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5052,16 +6502,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5096,7 +6549,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing image
- description: create or update an existing image
+ description: |
+ Create or update an existing image.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionImagesImage
consumes:
- application/json
@@ -5113,22 +6569,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: body
in: body
- description: image object that needs to be created or updated
+ description: image object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionImagesImage.json)
required: true
schema:
$ref: "#/definitions/image"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing image
+ description: |
+ Update an existing image
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionImagesImage
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: image-id
+ in: path
+ description: Image id, expected to be unique across cloud region
+ required: true
+ type: string
+ example: __IMAGE-ID__
+ - name: body
+ in: body
+ description: image object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/image"
delete:
tags:
- CloudInfrastructure
@@ -5150,16 +6660,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -5179,7 +6692,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/images"
+ $ref: "#/getDefinitions/images"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5188,11 +6701,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5224,19 +6739,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: switch-name
in: path
description: DVS switch name
required: true
type: string
+ example: __SWITCH-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -5261,16 +6779,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: switch-name
in: path
description: DVS switch name
required: true
type: string
+ example: __SWITCH-NAME__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/dvs-switches/dvs-switch/{switch-name}:
get:
tags:
@@ -5285,7 +6806,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/dvs-switch"
+ $ref: "#/getDefinitions/dvs-switch"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5294,16 +6815,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: switch-name
in: path
description: DVS switch name
required: true
type: string
+ example: __SWITCH-NAME__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5323,7 +6847,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing dvs-switch
- description: create or update an existing dvs-switch
+ description: |
+ Create or update an existing dvs-switch.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch
consumes:
- application/json
@@ -5340,22 +6867,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: switch-name
in: path
description: DVS switch name
required: true
type: string
+ example: __SWITCH-NAME__
- name: body
in: body
- description: dvs-switch object that needs to be created or updated
+ description: dvs-switch object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch.json)
required: true
schema:
$ref: "#/definitions/dvs-switch"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing dvs-switch
+ description: |
+ Update an existing dvs-switch
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: switch-name
+ in: path
+ description: DVS switch name
+ required: true
+ type: string
+ example: __SWITCH-NAME__
+ - name: body
+ in: body
+ description: dvs-switch object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/dvs-switch"
delete:
tags:
- CloudInfrastructure
@@ -5377,16 +6958,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: switch-name
in: path
description: DVS switch name
required: true
type: string
+ example: __SWITCH-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -5406,7 +6990,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/dvs-switches"
+ $ref: "#/getDefinitions/dvs-switches"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5415,11 +6999,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5451,19 +7037,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: network-uuid
in: path
description: UUID of the network. Unique across a cloud-region
required: true
type: string
+ example: __NETWORK-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -5488,16 +7077,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: network-uuid
in: path
description: UUID of the network. Unique across a cloud-region
required: true
type: string
+ example: __NETWORK-UUID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/oam-networks/oam-network/{network-uuid}:
get:
tags:
@@ -5512,7 +7104,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/oam-network"
+ $ref: "#/getDefinitions/oam-network"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5521,16 +7113,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: network-uuid
in: path
description: UUID of the network. Unique across a cloud-region
required: true
type: string
+ example: __NETWORK-UUID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5556,7 +7151,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing oam-network
- description: create or update an existing oam-network
+ description: |
+ Create or update an existing oam-network.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork
consumes:
- application/json
@@ -5573,22 +7171,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: network-uuid
in: path
description: UUID of the network. Unique across a cloud-region
required: true
type: string
+ example: __NETWORK-UUID__
- name: body
in: body
- description: oam-network object that needs to be created or updated
+ description: oam-network object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork.json)
required: true
schema:
$ref: "#/definitions/oam-network"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing oam-network
+ description: |
+ Update an existing oam-network
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: network-uuid
+ in: path
+ description: UUID of the network. Unique across a cloud-region
+ required: true
+ type: string
+ example: __NETWORK-UUID__
+ - name: body
+ in: body
+ description: oam-network object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/oam-network"
delete:
tags:
- CloudInfrastructure
@@ -5610,16 +7262,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: network-uuid
in: path
description: UUID of the network. Unique across a cloud-region
required: true
type: string
+ example: __NETWORK-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -5639,7 +7294,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/oam-networks"
+ $ref: "#/getDefinitions/oam-networks"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5648,11 +7303,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5684,19 +7341,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: availability-zone-name
in: path
description: Name of the availability zone. Unique across a cloud region
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -5721,16 +7381,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: availability-zone-name
in: path
description: Name of the availability zone. Unique across a cloud region
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/availability-zones/availability-zone/{availability-zone-name}:
get:
tags:
@@ -5745,7 +7408,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/availability-zone"
+ $ref: "#/getDefinitions/availability-zone"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5754,16 +7417,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: availability-zone-name
in: path
description: Name of the availability zone. Unique across a cloud region
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5778,7 +7444,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing availability-zone
- description: create or update an existing availability-zone
+ description: |
+ Create or update an existing availability-zone.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone
consumes:
- application/json
@@ -5795,22 +7464,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: availability-zone-name
in: path
description: Name of the availability zone. Unique across a cloud region
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: body
in: body
- description: availability-zone object that needs to be created or updated
+ description: availability-zone object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone.json)
required: true
schema:
$ref: "#/definitions/availability-zone"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing availability-zone
+ description: |
+ Update an existing availability-zone
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: availability-zone-name
+ in: path
+ description: Name of the availability zone. Unique across a cloud region
+ required: true
+ type: string
+ example: __AVAILABILITY-ZONE-NAME__
+ - name: body
+ in: body
+ description: availability-zone object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/availability-zone"
delete:
tags:
- CloudInfrastructure
@@ -5832,16 +7555,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: availability-zone-name
in: path
description: Name of the availability zone. Unique across a cloud region
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -5861,7 +7587,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/availability-zones"
+ $ref: "#/getDefinitions/availability-zones"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5870,11 +7596,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5906,14 +7634,16 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegion.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -5938,11 +7668,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}:
get:
tags:
@@ -5957,7 +7689,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/cloud-region"
+ $ref: "#/getDefinitions/cloud-region"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5966,11 +7698,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5985,7 +7719,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing cloud-region
- description: create or update an existing cloud-region
+ description: |
+ Create or update an existing cloud-region.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegion
consumes:
- application/json
@@ -6002,17 +7739,64 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: body
in: body
- description: cloud-region object that needs to be created or updated
+ description: cloud-region object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegion.json)
required: true
schema:
$ref: "#/definitions/cloud-region"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing cloud-region
+ description: |
+ Update an existing cloud-region
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegion
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: body
+ in: body
+ description: cloud-region object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/cloud-region"
delete:
tags:
- CloudInfrastructure
@@ -6034,11 +7818,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -6058,7 +7844,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/cloud-regions"
+ $ref: "#/getDefinitions/cloud-regions"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/cloud-infrastructure/network-profiles/network-profile/{nm-profile-name}/relationship-list/relationship:
@@ -6082,9 +7868,10 @@ paths:
description: Unique name of network profile.
required: true
type: string
+ example: __NM-PROFILE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureNetworkProfilesNetworkProfile.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -6109,6 +7896,7 @@ paths:
description: Unique name of network profile.
required: true
type: string
+ example: __NM-PROFILE-NAME__
/cloud-infrastructure/network-profiles/network-profile/{nm-profile-name}:
get:
tags:
@@ -6123,7 +7911,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/network-profile"
+ $ref: "#/getDefinitions/network-profile"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -6132,11 +7920,15 @@ paths:
description: Unique name of network profile.
required: true
type: string
+ example: __NM-PROFILE-NAME__
put:
tags:
- CloudInfrastructure
summary: create or update an existing network-profile
- description: create or update an existing network-profile
+ description: |
+ Create or update an existing network-profile.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureNetworkProfilesNetworkProfile
consumes:
- application/json
@@ -6153,12 +7945,52 @@ paths:
description: Unique name of network profile.
required: true
type: string
+ example: __NM-PROFILE-NAME__
- name: body
in: body
- description: network-profile object that needs to be created or updated
+ description: network-profile object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureNetworkProfilesNetworkProfile.json)
required: true
schema:
$ref: "#/definitions/network-profile"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing network-profile
+ description: |
+ Update an existing network-profile
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureNetworkProfilesNetworkProfile
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: nm-profile-name
+ in: path
+ description: Unique name of network profile.
+ required: true
+ type: string
+ example: __NM-PROFILE-NAME__
+ - name: body
+ in: body
+ description: network-profile object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/network-profile"
delete:
tags:
- CloudInfrastructure
@@ -6180,6 +8012,7 @@ paths:
description: Unique name of network profile.
required: true
type: string
+ example: __NM-PROFILE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -6199,7 +8032,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/network-profiles"
+ $ref: "#/getDefinitions/network-profiles"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/cloud-infrastructure/pservers/pserver/{hostname}/relationship-list/relationship:
@@ -6223,9 +8056,10 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserver.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -6250,6 +8084,7 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/relationship-list/relationship:
put:
tags:
@@ -6271,14 +8106,16 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -6303,11 +8140,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -6329,24 +8168,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -6371,21 +8214,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -6407,29 +8254,34 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -6454,26 +8306,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -6488,7 +8345,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -6497,26 +8354,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -6587,7 +8449,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -6604,32 +8469,100 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- CloudInfrastructure
@@ -6651,26 +8584,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -6697,29 +8635,34 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -6744,26 +8687,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -6778,7 +8726,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -6787,26 +8735,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -6877,7 +8830,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -6894,32 +8850,100 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- CloudInfrastructure
@@ -6941,26 +8965,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -6980,7 +9009,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -6989,21 +9018,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -7058,7 +9091,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -7075,27 +9111,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- CloudInfrastructure
@@ -7117,21 +9214,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -7151,7 +9252,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -7160,16 +9261,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -7230,24 +9334,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -7272,21 +9380,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -7301,7 +9413,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -7310,21 +9422,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -7388,7 +9504,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -7405,27 +9524,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- CloudInfrastructure
@@ -7447,21 +9627,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -7481,7 +9665,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -7490,16 +9674,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -7560,19 +9747,22 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -7597,16 +9787,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -7628,24 +9821,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -7670,21 +9867,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -7699,7 +9900,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -7708,21 +9909,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -7782,7 +9987,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -7799,27 +10007,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- CloudInfrastructure
@@ -7841,21 +10110,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -7882,24 +10155,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -7924,21 +10201,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -7953,7 +10234,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -7962,21 +10243,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -8036,7 +10321,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -8053,27 +10341,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- CloudInfrastructure
@@ -8095,21 +10444,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -8129,7 +10482,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -8138,16 +10491,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -8191,7 +10547,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface
consumes:
- application/json
@@ -8208,22 +10567,76 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- CloudInfrastructure
@@ -8245,16 +10658,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -8274,7 +10690,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -8283,11 +10699,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -8326,7 +10744,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/p-interface"
+ $ref: "#/getDefinitions/p-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -8335,11 +10753,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -8368,7 +10788,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing p-interface
- description: create or update an existing p-interface
+ description: |
+ Create or update an existing p-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterface
consumes:
- application/json
@@ -8385,17 +10808,64 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: p-interface object that needs to be created or updated
+ description: p-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterface.json)
required: true
schema:
$ref: "#/definitions/p-interface"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing p-interface
+ description: |
+ Update an existing p-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: p-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/p-interface"
delete:
tags:
- CloudInfrastructure
@@ -8417,11 +10887,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -8441,7 +10913,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/p-interfaces"
+ $ref: "#/getDefinitions/p-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -8450,6 +10922,7 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -8490,14 +10963,16 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -8522,11 +10997,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -8548,24 +11025,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -8590,21 +11071,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -8626,29 +11111,34 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -8673,26 +11163,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -8707,7 +11202,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -8716,26 +11211,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -8811,7 +11311,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -8828,32 +11331,100 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- CloudInfrastructure
@@ -8875,26 +11446,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -8921,29 +11497,34 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -8968,26 +11549,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -9002,7 +11588,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -9011,26 +11597,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -9106,7 +11697,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -9123,32 +11717,100 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- CloudInfrastructure
@@ -9170,26 +11832,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -9209,7 +11876,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -9218,21 +11885,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -9292,7 +11963,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -9309,27 +11983,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- CloudInfrastructure
@@ -9351,21 +12086,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -9385,7 +12124,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -9394,16 +12133,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -9469,24 +12211,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -9511,21 +12257,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -9540,7 +12290,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -9549,21 +12299,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -9632,7 +12386,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -9649,27 +12406,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- CloudInfrastructure
@@ -9691,21 +12509,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -9725,7 +12547,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -9734,16 +12556,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -9809,19 +12634,22 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -9846,16 +12674,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -9877,24 +12708,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -9919,21 +12754,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -9948,7 +12787,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -9957,21 +12796,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -10036,7 +12879,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -10053,27 +12899,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- CloudInfrastructure
@@ -10095,21 +13002,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -10136,24 +13047,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -10178,21 +13093,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -10207,7 +13126,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -10216,21 +13135,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -10295,7 +13218,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -10312,27 +13238,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- CloudInfrastructure
@@ -10354,21 +13341,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -10388,7 +13379,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -10397,16 +13388,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -10455,7 +13449,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface
consumes:
- application/json
@@ -10472,22 +13469,76 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- CloudInfrastructure
@@ -10509,16 +13560,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -10538,7 +13592,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -10547,11 +13601,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -10595,7 +13651,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interface"
+ $ref: "#/getDefinitions/lag-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -10604,11 +13660,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -10642,7 +13700,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing lag-interface
- description: create or update an existing lag-interface
+ description: |
+ Create or update an existing lag-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterface
consumes:
- application/json
@@ -10659,17 +13720,64 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: lag-interface object that needs to be created or updated
+ description: lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/lag-interface"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing lag-interface
+ description: |
+ Update an existing lag-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: lag-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/lag-interface"
delete:
tags:
- CloudInfrastructure
@@ -10691,11 +13799,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -10715,7 +13825,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interfaces"
+ $ref: "#/getDefinitions/lag-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -10724,6 +13834,7 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -10757,7 +13868,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/pserver"
+ $ref: "#/getDefinitions/pserver"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -10766,6 +13877,7 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -10789,7 +13901,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing pserver
- description: create or update an existing pserver
+ description: |
+ Create or update an existing pserver.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserver
consumes:
- application/json
@@ -10806,12 +13921,52 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: body
in: body
- description: pserver object that needs to be created or updated
+ description: pserver object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserver.json)
required: true
schema:
$ref: "#/definitions/pserver"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing pserver
+ description: |
+ Update an existing pserver
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserver
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: body
+ in: body
+ description: pserver object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/pserver"
delete:
tags:
- CloudInfrastructure
@@ -10833,6 +13988,7 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -10852,7 +14008,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/pservers"
+ $ref: "#/getDefinitions/pservers"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}/relationship-list/relationship:
@@ -10876,9 +14032,10 @@ paths:
description: Unique ID of the vdc
required: true
type: string
+ example: __VDC-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureVirtualDataCentersVirtualDataCenter.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -10903,6 +14060,7 @@ paths:
description: Unique ID of the vdc
required: true
type: string
+ example: __VDC-ID__
/cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}:
get:
tags:
@@ -10917,7 +14075,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/virtual-data-center"
+ $ref: "#/getDefinitions/virtual-data-center"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -10926,6 +14084,7 @@ paths:
description: Unique ID of the vdc
required: true
type: string
+ example: __VDC-ID__
- name: vdc-name
in: query
description: Name of the virtual data center
@@ -10935,7 +14094,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing virtual-data-center
- description: create or update an existing virtual-data-center
+ description: |
+ Create or update an existing virtual-data-center.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureVirtualDataCentersVirtualDataCenter
consumes:
- application/json
@@ -10952,12 +14114,52 @@ paths:
description: Unique ID of the vdc
required: true
type: string
+ example: __VDC-ID__
- name: body
in: body
- description: virtual-data-center object that needs to be created or updated
+ description: virtual-data-center object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureVirtualDataCentersVirtualDataCenter.json)
required: true
schema:
$ref: "#/definitions/virtual-data-center"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing virtual-data-center
+ description: |
+ Update an existing virtual-data-center
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureVirtualDataCentersVirtualDataCenter
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vdc-id
+ in: path
+ description: Unique ID of the vdc
+ required: true
+ type: string
+ example: __VDC-ID__
+ - name: body
+ in: body
+ description: virtual-data-center object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/virtual-data-center"
delete:
tags:
- CloudInfrastructure
@@ -10979,6 +14181,7 @@ paths:
description: Unique ID of the vdc
required: true
type: string
+ example: __VDC-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -10998,7 +14201,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/virtual-data-centers"
+ $ref: "#/getDefinitions/virtual-data-centers"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/business/connectors/connector/{resource-instance-id}/relationship-list/relationship:
@@ -11022,9 +14225,10 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessConnectorsConnector.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -11049,6 +14253,7 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
/business/connectors/connector/{resource-instance-id}/metadata/metadatum/{metaname}:
get:
tags:
@@ -11063,7 +14268,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadatum"
+ $ref: "#/getDefinitions/metadatum"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -11072,10 +14277,12 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: model-invariant-id
in: query
description: the ASDC model id for this resource or service model.
@@ -11100,7 +14307,10 @@ paths:
tags:
- Business
summary: create or update an existing metadatum
- description: create or update an existing metadatum
+ description: |
+ Create or update an existing metadatum.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessConnectorsConnectorMetadataMetadatum
consumes:
- application/json
@@ -11117,16 +14327,62 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: body
in: body
- description: metadatum object that needs to be created or updated
+ description: metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessConnectorsConnectorMetadataMetadatum.json)
required: true
schema:
$ref: "#/definitions/metadatum"
+ patch:
+ tags:
+ - Business
+ summary: update an existing metadatum
+ description: |
+ Update an existing metadatum
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessConnectorsConnectorMetadataMetadatum
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: resource-instance-id
+ in: path
+ description: Unique id of resource instance.
+ required: true
+ type: string
+ example: __RESOURCE-INSTANCE-ID__
+ - name: metaname
+ in: path
+ required: true
+ type: string
+ example: __METANAME__
+ - name: body
+ in: body
+ description: metadatum object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/metadatum"
delete:
tags:
- Business
@@ -11148,10 +14404,12 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -11171,7 +14429,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadata"
+ $ref: "#/getDefinitions/metadata"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -11180,6 +14438,7 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: model-invariant-id
in: query
description: the ASDC model id for this resource or service model.
@@ -11214,7 +14473,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/connector"
+ $ref: "#/getDefinitions/connector"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -11223,6 +14482,7 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: model-invariant-id
in: query
description: the ASDC model id for this resource or service model.
@@ -11247,7 +14507,10 @@ paths:
tags:
- Business
summary: create or update an existing connector
- description: create or update an existing connector
+ description: |
+ Create or update an existing connector.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessConnectorsConnector
consumes:
- application/json
@@ -11264,12 +14527,52 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: body
in: body
- description: connector object that needs to be created or updated
+ description: connector object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessConnectorsConnector.json)
required: true
schema:
$ref: "#/definitions/connector"
+ patch:
+ tags:
+ - Business
+ summary: update an existing connector
+ description: |
+ Update an existing connector
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessConnectorsConnector
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: resource-instance-id
+ in: path
+ description: Unique id of resource instance.
+ required: true
+ type: string
+ example: __RESOURCE-INSTANCE-ID__
+ - name: body
+ in: body
+ description: connector object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/connector"
delete:
tags:
- Business
@@ -11291,6 +14594,7 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -11310,7 +14614,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/connectors"
+ $ref: "#/getDefinitions/connectors"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/relationship-list/relationship:
@@ -11334,19 +14638,22 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -11371,16 +14678,19 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/metadata/metadatum/{metaname}:
get:
tags:
@@ -11395,7 +14705,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadatum"
+ $ref: "#/getDefinitions/metadatum"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -11404,20 +14714,24 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -11467,7 +14781,10 @@ paths:
tags:
- Business
summary: create or update an existing metadatum
- description: create or update an existing metadatum
+ description: |
+ Create or update an existing metadatum.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceMetadataMetadatum
consumes:
- application/json
@@ -11484,26 +14801,86 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: body
in: body
- description: metadatum object that needs to be created or updated
+ description: metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceMetadataMetadatum.json)
required: true
schema:
$ref: "#/definitions/metadatum"
+ patch:
+ tags:
+ - Business
+ summary: update an existing metadatum
+ description: |
+ Update an existing metadatum
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceMetadataMetadatum
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: global-customer-id
+ in: path
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ required: true
+ type: string
+ example: __GLOBAL-CUSTOMER-ID__
+ - name: service-type
+ in: path
+ description: Value defined by orchestration to identify this service across ECOMP.
+ required: true
+ type: string
+ example: __SERVICE-TYPE__
+ - name: service-instance-id
+ in: path
+ description: Uniquely identifies this instance of a service
+ required: true
+ type: string
+ example: __SERVICE-INSTANCE-ID__
+ - name: metaname
+ in: path
+ required: true
+ type: string
+ example: __METANAME__
+ - name: body
+ in: body
+ description: metadatum object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/metadatum"
delete:
tags:
- Business
@@ -11525,20 +14902,24 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -11558,7 +14939,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadata"
+ $ref: "#/getDefinitions/metadata"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -11567,16 +14948,19 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -11643,29 +15027,34 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResourceTunnelXconnectsTunnelXconnect.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -11690,26 +15079,31 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/allotted-resources/allotted-resource/{id}/tunnel-xconnects/tunnel-xconnect/{id}:
get:
tags:
@@ -11724,7 +15118,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/tunnel-xconnect"
+ $ref: "#/getDefinitions/tunnel-xconnect"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -11733,26 +15127,31 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -11822,7 +15221,10 @@ paths:
tags:
- Business
summary: create or update an existing tunnel-xconnect
- description: create or update an existing tunnel-xconnect
+ description: |
+ Create or update an existing tunnel-xconnect.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResourceTunnelXconnectsTunnelXconnect
consumes:
- application/json
@@ -11839,32 +15241,100 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: body
in: body
- description: tunnel-xconnect object that needs to be created or updated
+ description: tunnel-xconnect object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResourceTunnelXconnectsTunnelXconnect.json)
required: true
schema:
$ref: "#/definitions/tunnel-xconnect"
+ patch:
+ tags:
+ - Business
+ summary: update an existing tunnel-xconnect
+ description: |
+ Update an existing tunnel-xconnect
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResourceTunnelXconnectsTunnelXconnect
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: global-customer-id
+ in: path
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ required: true
+ type: string
+ example: __GLOBAL-CUSTOMER-ID__
+ - name: service-type
+ in: path
+ description: Value defined by orchestration to identify this service across ECOMP.
+ required: true
+ type: string
+ example: __SERVICE-TYPE__
+ - name: service-instance-id
+ in: path
+ description: Uniquely identifies this instance of a service
+ required: true
+ type: string
+ example: __SERVICE-INSTANCE-ID__
+ - name: id
+ in: path
+ description: Allotted Resource id UUID assigned to this instance.
+ required: true
+ type: string
+ example: __ID__
+ - name: id
+ in: path
+ description: Allotted Resource id UUID assigned to this instance.
+ required: true
+ type: string
+ example: __ID__
+ - name: body
+ in: body
+ description: tunnel-xconnect object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/tunnel-xconnect"
delete:
tags:
- Business
@@ -11886,26 +15356,31 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -11925,7 +15400,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/tunnel-xconnects"
+ $ref: "#/getDefinitions/tunnel-xconnects"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -11934,21 +15409,25 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -12035,24 +15514,28 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResource.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -12077,21 +15560,25 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/allotted-resources/allotted-resource/{id}:
get:
tags:
@@ -12106,7 +15593,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/allotted-resource"
+ $ref: "#/getDefinitions/allotted-resource"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -12115,21 +15602,25 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -12199,7 +15690,10 @@ paths:
tags:
- Business
summary: create or update an existing allotted-resource
- description: create or update an existing allotted-resource
+ description: |
+ Create or update an existing allotted-resource.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResource
consumes:
- application/json
@@ -12216,27 +15710,88 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: body
in: body
- description: allotted-resource object that needs to be created or updated
+ description: allotted-resource object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResource.json)
required: true
schema:
$ref: "#/definitions/allotted-resource"
+ patch:
+ tags:
+ - Business
+ summary: update an existing allotted-resource
+ description: |
+ Update an existing allotted-resource
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResource
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: global-customer-id
+ in: path
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ required: true
+ type: string
+ example: __GLOBAL-CUSTOMER-ID__
+ - name: service-type
+ in: path
+ description: Value defined by orchestration to identify this service across ECOMP.
+ required: true
+ type: string
+ example: __SERVICE-TYPE__
+ - name: service-instance-id
+ in: path
+ description: Uniquely identifies this instance of a service
+ required: true
+ type: string
+ example: __SERVICE-INSTANCE-ID__
+ - name: id
+ in: path
+ description: Allotted Resource id UUID assigned to this instance.
+ required: true
+ type: string
+ example: __ID__
+ - name: body
+ in: body
+ description: allotted-resource object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/allotted-resource"
delete:
tags:
- Business
@@ -12258,21 +15813,25 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -12292,7 +15851,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/allotted-resources"
+ $ref: "#/getDefinitions/allotted-resources"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -12301,16 +15860,19 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -12370,7 +15932,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/service-instance"
+ $ref: "#/getDefinitions/service-instance"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -12379,16 +15941,19 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -12438,7 +16003,10 @@ paths:
tags:
- Business
summary: create or update an existing service-instance
- description: create or update an existing service-instance
+ description: |
+ Create or update an existing service-instance.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance
consumes:
- application/json
@@ -12455,22 +16023,76 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: body
in: body
- description: service-instance object that needs to be created or updated
+ description: service-instance object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance.json)
required: true
schema:
$ref: "#/definitions/service-instance"
+ patch:
+ tags:
+ - Business
+ summary: update an existing service-instance
+ description: |
+ Update an existing service-instance
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: global-customer-id
+ in: path
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ required: true
+ type: string
+ example: __GLOBAL-CUSTOMER-ID__
+ - name: service-type
+ in: path
+ description: Value defined by orchestration to identify this service across ECOMP.
+ required: true
+ type: string
+ example: __SERVICE-TYPE__
+ - name: service-instance-id
+ in: path
+ description: Uniquely identifies this instance of a service
+ required: true
+ type: string
+ example: __SERVICE-INSTANCE-ID__
+ - name: body
+ in: body
+ description: service-instance object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/service-instance"
delete:
tags:
- Business
@@ -12492,16 +16114,19 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -12521,7 +16146,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/service-instances"
+ $ref: "#/getDefinitions/service-instances"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -12530,11 +16155,13 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -12566,14 +16193,16 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscription.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -12598,11 +16227,13 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}:
get:
tags:
@@ -12617,7 +16248,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/service-subscription"
+ $ref: "#/getDefinitions/service-subscription"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -12626,11 +16257,13 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -12645,7 +16278,10 @@ paths:
tags:
- Business
summary: create or update an existing service-subscription
- description: create or update an existing service-subscription
+ description: |
+ Create or update an existing service-subscription.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscription
consumes:
- application/json
@@ -12662,17 +16298,64 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: body
in: body
- description: service-subscription object that needs to be created or updated
+ description: service-subscription object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscription.json)
required: true
schema:
$ref: "#/definitions/service-subscription"
+ patch:
+ tags:
+ - Business
+ summary: update an existing service-subscription
+ description: |
+ Update an existing service-subscription
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscription
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: global-customer-id
+ in: path
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ required: true
+ type: string
+ example: __GLOBAL-CUSTOMER-ID__
+ - name: service-type
+ in: path
+ description: Value defined by orchestration to identify this service across ECOMP.
+ required: true
+ type: string
+ example: __SERVICE-TYPE__
+ - name: body
+ in: body
+ description: service-subscription object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/service-subscription"
delete:
tags:
- Business
@@ -12694,11 +16377,13 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -12718,7 +16403,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/service-subscriptions"
+ $ref: "#/getDefinitions/service-subscriptions"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -12727,6 +16412,7 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -12758,9 +16444,10 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomer.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -12785,6 +16472,7 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
/business/customers/customer/{global-customer-id}:
get:
tags:
@@ -12799,7 +16487,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/customer"
+ $ref: "#/getDefinitions/customer"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -12808,6 +16496,7 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -12822,7 +16511,10 @@ paths:
tags:
- Business
summary: create or update an existing customer
- description: create or update an existing customer
+ description: |
+ Create or update an existing customer.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessCustomersCustomer
consumes:
- application/json
@@ -12839,12 +16531,52 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: body
in: body
- description: customer object that needs to be created or updated
+ description: customer object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomer.json)
required: true
schema:
$ref: "#/definitions/customer"
+ patch:
+ tags:
+ - Business
+ summary: update an existing customer
+ description: |
+ Update an existing customer
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessCustomersCustomer
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: global-customer-id
+ in: path
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ required: true
+ type: string
+ example: __GLOBAL-CUSTOMER-ID__
+ - name: body
+ in: body
+ description: customer object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/customer"
delete:
tags:
- Business
@@ -12866,6 +16598,7 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -12885,7 +16618,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/customers"
+ $ref: "#/getDefinitions/customers"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/service-design-and-creation/vnf-images/vnf-image/{vnf-image-uuid}/relationship-list/relationship:
@@ -12909,9 +16642,10 @@ paths:
description: Unique ID of this asset
required: true
type: string
+ example: __VNF-IMAGE-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationVnfImagesVnfImage.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -12936,6 +16670,7 @@ paths:
description: Unique ID of this asset
required: true
type: string
+ example: __VNF-IMAGE-UUID__
/service-design-and-creation/vnf-images/vnf-image/{vnf-image-uuid}:
get:
tags:
@@ -12950,7 +16685,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vnf-image"
+ $ref: "#/getDefinitions/vnf-image"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -12959,6 +16694,7 @@ paths:
description: Unique ID of this asset
required: true
type: string
+ example: __VNF-IMAGE-UUID__
- name: application
in: query
description: The application that the image instantiates.
@@ -12978,7 +16714,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing vnf-image
- description: create or update an existing vnf-image
+ description: |
+ Create or update an existing vnf-image.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationVnfImagesVnfImage
consumes:
- application/json
@@ -12995,12 +16734,52 @@ paths:
description: Unique ID of this asset
required: true
type: string
+ example: __VNF-IMAGE-UUID__
- name: body
in: body
- description: vnf-image object that needs to be created or updated
+ description: vnf-image object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationVnfImagesVnfImage.json)
required: true
schema:
$ref: "#/definitions/vnf-image"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing vnf-image
+ description: |
+ Update an existing vnf-image
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationVnfImagesVnfImage
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-image-uuid
+ in: path
+ description: Unique ID of this asset
+ required: true
+ type: string
+ example: __VNF-IMAGE-UUID__
+ - name: body
+ in: body
+ description: vnf-image object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vnf-image"
delete:
tags:
- ServiceDesignAndCreation
@@ -13022,6 +16801,7 @@ paths:
description: Unique ID of this asset
required: true
type: string
+ example: __VNF-IMAGE-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -13041,7 +16821,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vnf-images"
+ $ref: "#/getDefinitions/vnf-images"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/service-design-and-creation/services/service/{service-id}/relationship-list/relationship:
@@ -13065,9 +16845,10 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationServicesService.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -13092,6 +16873,7 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-ID__
/service-design-and-creation/services/service/{service-id}:
get:
tags:
@@ -13106,7 +16888,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/service"
+ $ref: "#/getDefinitions/service"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -13115,6 +16897,7 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-ID__
- name: service-description
in: query
description: Description of the service
@@ -13124,7 +16907,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing service
- description: create or update an existing service
+ description: |
+ Create or update an existing service.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationServicesService
consumes:
- application/json
@@ -13141,12 +16927,52 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-ID__
- name: body
in: body
- description: service object that needs to be created or updated
+ description: service object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationServicesService.json)
required: true
schema:
$ref: "#/definitions/service"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing service
+ description: |
+ Update an existing service
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationServicesService
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: service-id
+ in: path
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ required: true
+ type: string
+ example: __SERVICE-ID__
+ - name: body
+ in: body
+ description: service object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/service"
delete:
tags:
- ServiceDesignAndCreation
@@ -13168,6 +16994,7 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -13187,7 +17014,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/services"
+ $ref: "#/getDefinitions/services"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/service-design-and-creation/service-capabilities/service-capability/{service-type}/{vnf-type}/relationship-list/relationship:
@@ -13211,14 +17038,16 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: vnf-type
in: path
description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
required: true
type: string
+ example: __VNF-TYPE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationServiceCapabilitiesServiceCapability.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -13243,11 +17072,13 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: vnf-type
in: path
description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
required: true
type: string
+ example: __VNF-TYPE__
/service-design-and-creation/service-capabilities/service-capability/{service-type}/{vnf-type}:
get:
tags:
@@ -13262,7 +17093,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/service-capability"
+ $ref: "#/getDefinitions/service-capability"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -13271,16 +17102,21 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: vnf-type
in: path
description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
required: true
type: string
+ example: __VNF-TYPE__
put:
tags:
- ServiceDesignAndCreation
summary: create or update an existing service-capability
- description: create or update an existing service-capability
+ description: |
+ Create or update an existing service-capability.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationServiceCapabilitiesServiceCapability
consumes:
- application/json
@@ -13297,17 +17133,64 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: vnf-type
in: path
description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
required: true
type: string
+ example: __VNF-TYPE__
- name: body
in: body
- description: service-capability object that needs to be created or updated
+ description: service-capability object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationServiceCapabilitiesServiceCapability.json)
required: true
schema:
$ref: "#/definitions/service-capability"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing service-capability
+ description: |
+ Update an existing service-capability
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationServiceCapabilitiesServiceCapability
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: service-type
+ in: path
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ required: true
+ type: string
+ example: __SERVICE-TYPE__
+ - name: vnf-type
+ in: path
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ required: true
+ type: string
+ example: __VNF-TYPE__
+ - name: body
+ in: body
+ description: service-capability object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/service-capability"
delete:
tags:
- ServiceDesignAndCreation
@@ -13329,11 +17212,13 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: vnf-type
in: path
description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
required: true
type: string
+ example: __VNF-TYPE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -13353,7 +17238,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/service-capabilities"
+ $ref: "#/getDefinitions/service-capabilities"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}/element-choice-sets/element-choice-set/{element-choice-set-uuid}/relationship-list/relationship:
@@ -13377,30 +17262,36 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: element-choice-set-uuid
in: path
required: true
type: string
+ example: __ELEMENT-CHOICE-SET-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -13425,27 +17316,33 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: element-choice-set-uuid
in: path
required: true
type: string
+ example: __ELEMENT-CHOICE-SET-UUID__
/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}/element-choice-sets/element-choice-set/{element-choice-set-uuid}:
get:
tags:
@@ -13460,7 +17357,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/element-choice-set"
+ $ref: "#/getDefinitions/element-choice-set"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -13469,27 +17366,33 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: element-choice-set-uuid
in: path
required: true
type: string
+ example: __ELEMENT-CHOICE-SET-UUID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -13509,7 +17412,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing element-choice-set
- description: create or update an existing element-choice-set
+ description: |
+ Create or update an existing element-choice-set.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet
consumes:
- application/json
@@ -13526,33 +17432,104 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: element-choice-set-uuid
in: path
required: true
type: string
+ example: __ELEMENT-CHOICE-SET-UUID__
- name: body
in: body
- description: element-choice-set object that needs to be created or updated
+ description: element-choice-set object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet.json)
required: true
schema:
$ref: "#/definitions/element-choice-set"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing element-choice-set
+ description: |
+ Update an existing element-choice-set
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: model-invariant-id
+ in: path
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-INVARIANT-ID__
+ - name: model-version-id
+ in: path
+ description: Unique identifier corresponding to one version of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-VERSION-ID__
+ - name: model-element-uuid
+ in: path
+ required: true
+ type: string
+ example: __MODEL-ELEMENT-UUID__
+ - name: model-constraint-uuid
+ in: path
+ required: true
+ type: string
+ example: __MODEL-CONSTRAINT-UUID__
+ - name: constrained-element-set-uuid
+ in: path
+ required: true
+ type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
+ - name: element-choice-set-uuid
+ in: path
+ required: true
+ type: string
+ example: __ELEMENT-CHOICE-SET-UUID__
+ - name: body
+ in: body
+ description: element-choice-set object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/element-choice-set"
delete:
tags:
- ServiceDesignAndCreation
@@ -13574,27 +17551,33 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: element-choice-set-uuid
in: path
required: true
type: string
+ example: __ELEMENT-CHOICE-SET-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -13614,7 +17597,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/element-choice-sets"
+ $ref: "#/getDefinitions/element-choice-sets"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -13623,23 +17606,28 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -13676,26 +17664,31 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -13720,23 +17713,28 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}:
get:
tags:
@@ -13751,7 +17749,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/constrained-element-set"
+ $ref: "#/getDefinitions/constrained-element-set"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -13760,23 +17758,28 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -13796,7 +17799,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing constrained-element-set
- description: create or update an existing constrained-element-set
+ description: |
+ Create or update an existing constrained-element-set.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet
consumes:
- application/json
@@ -13813,29 +17819,94 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: body
in: body
- description: constrained-element-set object that needs to be created or updated
+ description: constrained-element-set object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet.json)
required: true
schema:
$ref: "#/definitions/constrained-element-set"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing constrained-element-set
+ description: |
+ Update an existing constrained-element-set
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: model-invariant-id
+ in: path
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-INVARIANT-ID__
+ - name: model-version-id
+ in: path
+ description: Unique identifier corresponding to one version of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-VERSION-ID__
+ - name: model-element-uuid
+ in: path
+ required: true
+ type: string
+ example: __MODEL-ELEMENT-UUID__
+ - name: model-constraint-uuid
+ in: path
+ required: true
+ type: string
+ example: __MODEL-CONSTRAINT-UUID__
+ - name: constrained-element-set-uuid
+ in: path
+ required: true
+ type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
+ - name: body
+ in: body
+ description: constrained-element-set object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/constrained-element-set"
delete:
tags:
- ServiceDesignAndCreation
@@ -13857,23 +17928,28 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -13893,7 +17969,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/constrained-element-sets"
+ $ref: "#/getDefinitions/constrained-element-sets"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -13902,19 +17978,23 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -13944,7 +18024,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/model-constraint"
+ $ref: "#/getDefinitions/model-constraint"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -13953,19 +18033,23 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -13985,7 +18069,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing model-constraint
- description: create or update an existing model-constraint
+ description: |
+ Create or update an existing model-constraint.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraint
consumes:
- application/json
@@ -14002,25 +18089,84 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: body
in: body
- description: model-constraint object that needs to be created or updated
+ description: model-constraint object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraint.json)
required: true
schema:
$ref: "#/definitions/model-constraint"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing model-constraint
+ description: |
+ Update an existing model-constraint
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraint
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: model-invariant-id
+ in: path
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-INVARIANT-ID__
+ - name: model-version-id
+ in: path
+ description: Unique identifier corresponding to one version of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-VERSION-ID__
+ - name: model-element-uuid
+ in: path
+ required: true
+ type: string
+ example: __MODEL-ELEMENT-UUID__
+ - name: model-constraint-uuid
+ in: path
+ required: true
+ type: string
+ example: __MODEL-CONSTRAINT-UUID__
+ - name: body
+ in: body
+ description: model-constraint object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/model-constraint"
delete:
tags:
- ServiceDesignAndCreation
@@ -14042,19 +18188,23 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -14074,7 +18224,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/model-constraints"
+ $ref: "#/getDefinitions/model-constraints"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14083,15 +18233,18 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -14128,18 +18281,21 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElement.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -14164,15 +18320,18 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}:
get:
tags:
@@ -14187,7 +18346,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/model-element"
+ $ref: "#/getDefinitions/model-element"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14196,15 +18355,18 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -14224,7 +18386,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing model-element
- description: create or update an existing model-element
+ description: |
+ Create or update an existing model-element.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElement
consumes:
- application/json
@@ -14241,21 +18406,74 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: body
in: body
- description: model-element object that needs to be created or updated
+ description: model-element object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElement.json)
required: true
schema:
$ref: "#/definitions/model-element"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing model-element
+ description: |
+ Update an existing model-element
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElement
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: model-invariant-id
+ in: path
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-INVARIANT-ID__
+ - name: model-version-id
+ in: path
+ description: Unique identifier corresponding to one version of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-VERSION-ID__
+ - name: model-element-uuid
+ in: path
+ required: true
+ type: string
+ example: __MODEL-ELEMENT-UUID__
+ - name: body
+ in: body
+ description: model-element object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/model-element"
delete:
tags:
- ServiceDesignAndCreation
@@ -14277,15 +18495,18 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -14305,7 +18526,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/model-elements"
+ $ref: "#/getDefinitions/model-elements"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14314,11 +18535,13 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -14348,7 +18571,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadatum"
+ $ref: "#/getDefinitions/metadatum"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14357,15 +18580,18 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -14385,7 +18611,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing metadatum
- description: create or update an existing metadatum
+ description: |
+ Create or update an existing metadatum.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationModelsModelModelVersModelVerMetadataMetadatum
consumes:
- application/json
@@ -14402,21 +18631,74 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: body
in: body
- description: metadatum object that needs to be created or updated
+ description: metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerMetadataMetadatum.json)
required: true
schema:
$ref: "#/definitions/metadatum"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing metadatum
+ description: |
+ Update an existing metadatum
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationModelsModelModelVersModelVerMetadataMetadatum
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: model-invariant-id
+ in: path
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-INVARIANT-ID__
+ - name: model-version-id
+ in: path
+ description: Unique identifier corresponding to one version of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-VERSION-ID__
+ - name: metaname
+ in: path
+ required: true
+ type: string
+ example: __METANAME__
+ - name: body
+ in: body
+ description: metadatum object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/metadatum"
delete:
tags:
- ServiceDesignAndCreation
@@ -14438,15 +18720,18 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -14466,7 +18751,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadata"
+ $ref: "#/getDefinitions/metadata"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14475,11 +18760,13 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -14516,14 +18803,16 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVer.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -14548,11 +18837,13 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}:
get:
tags:
@@ -14567,7 +18858,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/model-ver"
+ $ref: "#/getDefinitions/model-ver"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14576,11 +18867,13 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -14600,7 +18893,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing model-ver
- description: create or update an existing model-ver
+ description: |
+ Create or update an existing model-ver.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationModelsModelModelVersModelVer
consumes:
- application/json
@@ -14617,17 +18913,64 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: body
in: body
- description: model-ver object that needs to be created or updated
+ description: model-ver object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVer.json)
required: true
schema:
$ref: "#/definitions/model-ver"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing model-ver
+ description: |
+ Update an existing model-ver
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationModelsModelModelVersModelVer
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: model-invariant-id
+ in: path
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-INVARIANT-ID__
+ - name: model-version-id
+ in: path
+ description: Unique identifier corresponding to one version of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-VERSION-ID__
+ - name: body
+ in: body
+ description: model-ver object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/model-ver"
delete:
tags:
- ServiceDesignAndCreation
@@ -14649,11 +18992,13 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -14673,7 +19018,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/model-vers"
+ $ref: "#/getDefinitions/model-vers"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14682,6 +19027,7 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -14708,9 +19054,10 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModel.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -14735,6 +19082,7 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
/service-design-and-creation/models/model/{model-invariant-id}:
get:
tags:
@@ -14749,7 +19097,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/model"
+ $ref: "#/getDefinitions/model"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14758,6 +19106,7 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -14767,7 +19116,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing model
- description: create or update an existing model
+ description: |
+ Create or update an existing model.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationModelsModel
consumes:
- application/json
@@ -14784,12 +19136,52 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: body
in: body
- description: model object that needs to be created or updated
+ description: model object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModel.json)
required: true
schema:
$ref: "#/definitions/model"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing model
+ description: |
+ Update an existing model
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationModelsModel
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: model-invariant-id
+ in: path
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-INVARIANT-ID__
+ - name: body
+ in: body
+ description: model object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/model"
delete:
tags:
- ServiceDesignAndCreation
@@ -14811,6 +19203,7 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -14830,7 +19223,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/models"
+ $ref: "#/getDefinitions/models"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/related-lookups/related-lookup/{related-lookup-uuid}/relationship-list/relationship:
@@ -14853,17 +19246,20 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: related-lookup-uuid
in: path
required: true
type: string
+ example: __RELATED-LOOKUP-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -14887,14 +19283,17 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: related-lookup-uuid
in: path
required: true
type: string
+ example: __RELATED-LOOKUP-UUID__
/service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/related-lookups/related-lookup/{related-lookup-uuid}:
get:
tags:
@@ -14909,7 +19308,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/related-lookup"
+ $ref: "#/getDefinitions/related-lookup"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14917,14 +19316,17 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: related-lookup-uuid
in: path
required: true
type: string
+ example: __RELATED-LOOKUP-UUID__
- name: named-query-name
in: query
required: false
@@ -14933,7 +19335,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing related-lookup
- description: create or update an existing related-lookup
+ description: |
+ Create or update an existing related-lookup.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup
consumes:
- application/json
@@ -14949,20 +19354,71 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: related-lookup-uuid
in: path
required: true
type: string
+ example: __RELATED-LOOKUP-UUID__
- name: body
in: body
- description: related-lookup object that needs to be created or updated
+ description: related-lookup object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup.json)
required: true
schema:
$ref: "#/definitions/related-lookup"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing related-lookup
+ description: |
+ Update an existing related-lookup
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: named-query-uuid
+ in: path
+ required: true
+ type: string
+ example: __NAMED-QUERY-UUID__
+ - name: named-query-element-uuid
+ in: path
+ required: true
+ type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
+ - name: related-lookup-uuid
+ in: path
+ required: true
+ type: string
+ example: __RELATED-LOOKUP-UUID__
+ - name: body
+ in: body
+ description: related-lookup object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/related-lookup"
delete:
tags:
- ServiceDesignAndCreation
@@ -14983,14 +19439,17 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: related-lookup-uuid
in: path
required: true
type: string
+ example: __RELATED-LOOKUP-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -15010,7 +19469,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/related-lookups"
+ $ref: "#/getDefinitions/related-lookups"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -15018,10 +19477,12 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: named-query-name
in: query
required: false
@@ -15040,7 +19501,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/property-constraint"
+ $ref: "#/getDefinitions/property-constraint"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -15048,14 +19509,17 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: property-constraint-uuid
in: path
required: true
type: string
+ example: __PROPERTY-CONSTRAINT-UUID__
- name: named-query-name
in: query
required: false
@@ -15064,7 +19528,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing property-constraint
- description: create or update an existing property-constraint
+ description: |
+ Create or update an existing property-constraint.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementPropertyConstraintsPropertyConstraint
consumes:
- application/json
@@ -15080,20 +19547,71 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: property-constraint-uuid
in: path
required: true
type: string
+ example: __PROPERTY-CONSTRAINT-UUID__
- name: body
in: body
- description: property-constraint object that needs to be created or updated
+ description: property-constraint object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementPropertyConstraintsPropertyConstraint.json)
required: true
schema:
$ref: "#/definitions/property-constraint"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing property-constraint
+ description: |
+ Update an existing property-constraint
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementPropertyConstraintsPropertyConstraint
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: named-query-uuid
+ in: path
+ required: true
+ type: string
+ example: __NAMED-QUERY-UUID__
+ - name: named-query-element-uuid
+ in: path
+ required: true
+ type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
+ - name: property-constraint-uuid
+ in: path
+ required: true
+ type: string
+ example: __PROPERTY-CONSTRAINT-UUID__
+ - name: body
+ in: body
+ description: property-constraint object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/property-constraint"
delete:
tags:
- ServiceDesignAndCreation
@@ -15114,14 +19632,17 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: property-constraint-uuid
in: path
required: true
type: string
+ example: __PROPERTY-CONSTRAINT-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -15141,7 +19662,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/property-constraints"
+ $ref: "#/getDefinitions/property-constraints"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -15149,10 +19670,12 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: named-query-name
in: query
required: false
@@ -15177,13 +19700,15 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -15207,10 +19732,12 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
/service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}:
get:
tags:
@@ -15225,7 +19752,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/named-query-element"
+ $ref: "#/getDefinitions/named-query-element"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -15233,10 +19760,12 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: named-query-name
in: query
required: false
@@ -15245,7 +19774,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing named-query-element
- description: create or update an existing named-query-element
+ description: |
+ Create or update an existing named-query-element.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement
consumes:
- application/json
@@ -15261,16 +19793,61 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: body
in: body
- description: named-query-element object that needs to be created or updated
+ description: named-query-element object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement.json)
required: true
schema:
$ref: "#/definitions/named-query-element"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing named-query-element
+ description: |
+ Update an existing named-query-element
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: named-query-uuid
+ in: path
+ required: true
+ type: string
+ example: __NAMED-QUERY-UUID__
+ - name: named-query-element-uuid
+ in: path
+ required: true
+ type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
+ - name: body
+ in: body
+ description: named-query-element object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/named-query-element"
delete:
tags:
- ServiceDesignAndCreation
@@ -15291,10 +19868,12 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -15314,7 +19893,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/named-query-elements"
+ $ref: "#/getDefinitions/named-query-elements"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -15322,6 +19901,7 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-name
in: query
required: false
@@ -15346,9 +19926,10 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationNamedQueriesNamedQuery.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -15372,6 +19953,7 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
/service-design-and-creation/named-queries/named-query/{named-query-uuid}:
get:
tags:
@@ -15386,7 +19968,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/named-query"
+ $ref: "#/getDefinitions/named-query"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -15394,6 +19976,7 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-name
in: query
required: false
@@ -15402,7 +19985,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing named-query
- description: create or update an existing named-query
+ description: |
+ Create or update an existing named-query.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationNamedQueriesNamedQuery
consumes:
- application/json
@@ -15418,12 +20004,51 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: body
in: body
- description: named-query object that needs to be created or updated
+ description: named-query object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationNamedQueriesNamedQuery.json)
required: true
schema:
$ref: "#/definitions/named-query"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing named-query
+ description: |
+ Update an existing named-query
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationNamedQueriesNamedQuery
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: named-query-uuid
+ in: path
+ required: true
+ type: string
+ example: __NAMED-QUERY-UUID__
+ - name: body
+ in: body
+ description: named-query object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/named-query"
delete:
tags:
- ServiceDesignAndCreation
@@ -15444,6 +20069,7 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -15463,7 +20089,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/named-queries"
+ $ref: "#/getDefinitions/named-queries"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/logical-links/logical-link/{link-name}/relationship-list/relationship:
@@ -15487,9 +20113,10 @@ paths:
description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkLogicalLinksLogicalLink.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -15514,6 +20141,7 @@ paths:
description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
required: true
type: string
+ example: __LINK-NAME__
/network/logical-links/logical-link/{link-name}:
get:
tags:
@@ -15528,7 +20156,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/logical-link"
+ $ref: "#/getDefinitions/logical-link"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -15537,6 +20165,7 @@ paths:
description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: model-invariant-id
in: query
description: the ASDC model id for this resource or service model.
@@ -15581,7 +20210,10 @@ paths:
tags:
- Network
summary: create or update an existing logical-link
- description: create or update an existing logical-link
+ description: |
+ Create or update an existing logical-link.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkLogicalLinksLogicalLink
consumes:
- application/json
@@ -15598,12 +20230,52 @@ paths:
description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: body
in: body
- description: logical-link object that needs to be created or updated
+ description: logical-link object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkLogicalLinksLogicalLink.json)
required: true
schema:
$ref: "#/definitions/logical-link"
+ patch:
+ tags:
+ - Network
+ summary: update an existing logical-link
+ description: |
+ Update an existing logical-link
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkLogicalLinksLogicalLink
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: link-name
+ in: path
+ description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
+ required: true
+ type: string
+ example: __LINK-NAME__
+ - name: body
+ in: body
+ description: logical-link object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/logical-link"
delete:
tags:
- Network
@@ -15625,6 +20297,7 @@ paths:
description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -15644,7 +20317,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/logical-links"
+ $ref: "#/getDefinitions/logical-links"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}/classes-of-service/class-of-service/{cos}/relationship-list/relationship:
@@ -15668,24 +20341,28 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: cos
in: path
description: unique identifier of probe
required: true
type: string
+ example: __COS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -15710,21 +20387,25 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: cos
in: path
description: unique identifier of probe
required: true
type: string
+ example: __COS__
/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}/classes-of-service/class-of-service/{cos}:
get:
tags:
@@ -15739,7 +20420,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/class-of-service"
+ $ref: "#/getDefinitions/class-of-service"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -15748,26 +20429,33 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: cos
in: path
description: unique identifier of probe
required: true
type: string
+ example: __COS__
put:
tags:
- Network
summary: create or update an existing class-of-service
- description: create or update an existing class-of-service
+ description: |
+ Create or update an existing class-of-service.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService
consumes:
- application/json
@@ -15784,27 +20472,88 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: cos
in: path
description: unique identifier of probe
required: true
type: string
+ example: __COS__
- name: body
in: body
- description: class-of-service object that needs to be created or updated
+ description: class-of-service object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService.json)
required: true
schema:
$ref: "#/definitions/class-of-service"
+ patch:
+ tags:
+ - Network
+ summary: update an existing class-of-service
+ description: |
+ Update an existing class-of-service
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: site-pair-set-id
+ in: path
+ description: Unique id of site pair set.
+ required: true
+ type: string
+ example: __SITE-PAIR-SET-ID__
+ - name: routing-instance-id
+ in: path
+ description: Unique id of routing instance
+ required: true
+ type: string
+ example: __ROUTING-INSTANCE-ID__
+ - name: site-pair-id
+ in: path
+ description: unique identifier of probe
+ required: true
+ type: string
+ example: __SITE-PAIR-ID__
+ - name: cos
+ in: path
+ description: unique identifier of probe
+ required: true
+ type: string
+ example: __COS__
+ - name: body
+ in: body
+ description: class-of-service object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/class-of-service"
delete:
tags:
- Network
@@ -15826,21 +20575,25 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: cos
in: path
description: unique identifier of probe
required: true
type: string
+ example: __COS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -15860,7 +20613,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/classes-of-service"
+ $ref: "#/getDefinitions/classes-of-service"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -15869,16 +20622,19 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}/relationship-list/relationship:
put:
tags:
@@ -15900,19 +20656,22 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -15937,16 +20696,19 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}:
get:
tags:
@@ -15961,7 +20723,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/site-pair"
+ $ref: "#/getDefinitions/site-pair"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -15970,21 +20732,27 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
put:
tags:
- Network
summary: create or update an existing site-pair
- description: create or update an existing site-pair
+ description: |
+ Create or update an existing site-pair.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair
consumes:
- application/json
@@ -16001,22 +20769,76 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: body
in: body
- description: site-pair object that needs to be created or updated
+ description: site-pair object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair.json)
required: true
schema:
$ref: "#/definitions/site-pair"
+ patch:
+ tags:
+ - Network
+ summary: update an existing site-pair
+ description: |
+ Update an existing site-pair
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: site-pair-set-id
+ in: path
+ description: Unique id of site pair set.
+ required: true
+ type: string
+ example: __SITE-PAIR-SET-ID__
+ - name: routing-instance-id
+ in: path
+ description: Unique id of routing instance
+ required: true
+ type: string
+ example: __ROUTING-INSTANCE-ID__
+ - name: site-pair-id
+ in: path
+ description: unique identifier of probe
+ required: true
+ type: string
+ example: __SITE-PAIR-ID__
+ - name: body
+ in: body
+ description: site-pair object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/site-pair"
delete:
tags:
- Network
@@ -16038,16 +20860,19 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -16067,7 +20892,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/site-pairs"
+ $ref: "#/getDefinitions/site-pairs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -16076,11 +20901,13 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/relationship-list/relationship:
put:
tags:
@@ -16102,14 +20929,16 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -16134,11 +20963,13 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}:
get:
tags:
@@ -16153,7 +20984,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/routing-instance"
+ $ref: "#/getDefinitions/routing-instance"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -16162,16 +20993,21 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
put:
tags:
- Network
summary: create or update an existing routing-instance
- description: create or update an existing routing-instance
+ description: |
+ Create or update an existing routing-instance.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance
consumes:
- application/json
@@ -16188,17 +21024,64 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: body
in: body
- description: routing-instance object that needs to be created or updated
+ description: routing-instance object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance.json)
required: true
schema:
$ref: "#/definitions/routing-instance"
+ patch:
+ tags:
+ - Network
+ summary: update an existing routing-instance
+ description: |
+ Update an existing routing-instance
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: site-pair-set-id
+ in: path
+ description: Unique id of site pair set.
+ required: true
+ type: string
+ example: __SITE-PAIR-SET-ID__
+ - name: routing-instance-id
+ in: path
+ description: Unique id of routing instance
+ required: true
+ type: string
+ example: __ROUTING-INSTANCE-ID__
+ - name: body
+ in: body
+ description: routing-instance object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/routing-instance"
delete:
tags:
- Network
@@ -16220,11 +21103,13 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -16244,7 +21129,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/routing-instances"
+ $ref: "#/getDefinitions/routing-instances"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -16253,6 +21138,7 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
/network/site-pair-sets/site-pair-set/{site-pair-set-id}/relationship-list/relationship:
put:
tags:
@@ -16274,9 +21160,10 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSet.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -16301,6 +21188,7 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
/network/site-pair-sets/site-pair-set/{site-pair-set-id}:
get:
tags:
@@ -16315,7 +21203,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/site-pair-set"
+ $ref: "#/getDefinitions/site-pair-set"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -16324,11 +21212,15 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
put:
tags:
- Network
summary: create or update an existing site-pair-set
- description: create or update an existing site-pair-set
+ description: |
+ Create or update an existing site-pair-set.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkSitePairSetsSitePairSet
consumes:
- application/json
@@ -16345,12 +21237,52 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: body
in: body
- description: site-pair-set object that needs to be created or updated
+ description: site-pair-set object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSet.json)
required: true
schema:
$ref: "#/definitions/site-pair-set"
+ patch:
+ tags:
+ - Network
+ summary: update an existing site-pair-set
+ description: |
+ Update an existing site-pair-set
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkSitePairSetsSitePairSet
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: site-pair-set-id
+ in: path
+ description: Unique id of site pair set.
+ required: true
+ type: string
+ example: __SITE-PAIR-SET-ID__
+ - name: body
+ in: body
+ description: site-pair-set object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/site-pair-set"
delete:
tags:
- Network
@@ -16372,6 +21304,7 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -16391,7 +21324,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/site-pair-sets"
+ $ref: "#/getDefinitions/site-pair-sets"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/vpn-bindings/vpn-binding/{vpn-id}/route-targets/route-target/{global-route-target}/{route-target-role}/relationship-list/relationship:
@@ -16415,19 +21348,22 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
- name: global-route-target
in: path
description: Number used to identify an RT, globally unique in the network
required: true
type: string
+ example: __GLOBAL-ROUTE-TARGET__
- name: route-target-role
in: path
description: Role assigned to this route target
required: true
type: string
+ example: __ROUTE-TARGET-ROLE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVpnBindingsVpnBindingRouteTargetsRouteTarget.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -16452,16 +21388,19 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
- name: global-route-target
in: path
description: Number used to identify an RT, globally unique in the network
required: true
type: string
+ example: __GLOBAL-ROUTE-TARGET__
- name: route-target-role
in: path
description: Role assigned to this route target
required: true
type: string
+ example: __ROUTE-TARGET-ROLE__
/network/vpn-bindings/vpn-binding/{vpn-id}/route-targets/route-target/{global-route-target}/{route-target-role}:
get:
tags:
@@ -16476,7 +21415,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/route-target"
+ $ref: "#/getDefinitions/route-target"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -16485,16 +21424,19 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
- name: global-route-target
in: path
description: Number used to identify an RT, globally unique in the network
required: true
type: string
+ example: __GLOBAL-ROUTE-TARGET__
- name: route-target-role
in: path
description: Role assigned to this route target
required: true
type: string
+ example: __ROUTE-TARGET-ROLE__
- name: vpn-name
in: query
description: VPN Name
@@ -16509,7 +21451,10 @@ paths:
tags:
- Network
summary: create or update an existing route-target
- description: create or update an existing route-target
+ description: |
+ Create or update an existing route-target.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVpnBindingsVpnBindingRouteTargetsRouteTarget
consumes:
- application/json
@@ -16526,22 +21471,76 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
- name: global-route-target
in: path
description: Number used to identify an RT, globally unique in the network
required: true
type: string
+ example: __GLOBAL-ROUTE-TARGET__
- name: route-target-role
in: path
description: Role assigned to this route target
required: true
type: string
+ example: __ROUTE-TARGET-ROLE__
- name: body
in: body
- description: route-target object that needs to be created or updated
+ description: route-target object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVpnBindingsVpnBindingRouteTargetsRouteTarget.json)
required: true
schema:
$ref: "#/definitions/route-target"
+ patch:
+ tags:
+ - Network
+ summary: update an existing route-target
+ description: |
+ Update an existing route-target
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVpnBindingsVpnBindingRouteTargetsRouteTarget
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vpn-id
+ in: path
+ description: VPN ID, globally unique within A&AI
+ required: true
+ type: string
+ example: __VPN-ID__
+ - name: global-route-target
+ in: path
+ description: Number used to identify an RT, globally unique in the network
+ required: true
+ type: string
+ example: __GLOBAL-ROUTE-TARGET__
+ - name: route-target-role
+ in: path
+ description: Role assigned to this route target
+ required: true
+ type: string
+ example: __ROUTE-TARGET-ROLE__
+ - name: body
+ in: body
+ description: route-target object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/route-target"
delete:
tags:
- Network
@@ -16563,16 +21562,19 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
- name: global-route-target
in: path
description: Number used to identify an RT, globally unique in the network
required: true
type: string
+ example: __GLOBAL-ROUTE-TARGET__
- name: route-target-role
in: path
description: Role assigned to this route target
required: true
type: string
+ example: __ROUTE-TARGET-ROLE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -16592,7 +21594,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/route-targets"
+ $ref: "#/getDefinitions/route-targets"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -16601,6 +21603,7 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
- name: vpn-name
in: query
description: VPN Name
@@ -16632,9 +21635,10 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVpnBindingsVpnBinding.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -16659,6 +21663,7 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
/network/vpn-bindings/vpn-binding/{vpn-id}:
get:
tags:
@@ -16673,7 +21678,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vpn-binding"
+ $ref: "#/getDefinitions/vpn-binding"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -16682,6 +21687,7 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
- name: vpn-name
in: query
description: VPN Name
@@ -16696,7 +21702,10 @@ paths:
tags:
- Network
summary: create or update an existing vpn-binding
- description: create or update an existing vpn-binding
+ description: |
+ Create or update an existing vpn-binding.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVpnBindingsVpnBinding
consumes:
- application/json
@@ -16713,12 +21722,52 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
- name: body
in: body
- description: vpn-binding object that needs to be created or updated
+ description: vpn-binding object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVpnBindingsVpnBinding.json)
required: true
schema:
$ref: "#/definitions/vpn-binding"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vpn-binding
+ description: |
+ Update an existing vpn-binding
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVpnBindingsVpnBinding
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vpn-id
+ in: path
+ description: VPN ID, globally unique within A&AI
+ required: true
+ type: string
+ example: __VPN-ID__
+ - name: body
+ in: body
+ description: vpn-binding object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vpn-binding"
delete:
tags:
- Network
@@ -16740,6 +21789,7 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -16759,7 +21809,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vpn-bindings"
+ $ref: "#/getDefinitions/vpn-bindings"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/vpls-pes/vpls-pe/{equipment-name}/relationship-list/relationship:
@@ -16782,9 +21832,10 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPe.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -16808,6 +21859,7 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/relationship-list/relationship:
put:
tags:
@@ -16828,14 +21880,16 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -16859,11 +21913,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -16884,24 +21940,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -16925,21 +21985,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -16960,29 +22024,34 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -17006,26 +22075,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -17040,7 +22114,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -17048,26 +22122,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -17124,7 +22203,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -17140,32 +22222,99 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -17186,26 +22335,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -17231,29 +22385,34 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -17277,26 +22436,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -17311,7 +22475,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -17319,26 +22483,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -17395,7 +22564,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -17411,32 +22583,99 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -17457,26 +22696,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -17496,7 +22740,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -17504,21 +22748,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -17559,7 +22807,10 @@ paths:
tags:
- Network
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -17575,27 +22826,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- Network
@@ -17616,21 +22927,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -17650,7 +22965,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -17658,16 +22973,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -17713,24 +23031,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -17754,21 +23076,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -17783,7 +23109,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -17791,21 +23117,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -17855,7 +23185,10 @@ paths:
tags:
- Network
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -17871,27 +23204,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- Network
@@ -17912,21 +23305,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -17946,7 +23343,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -17954,16 +23351,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -18009,19 +23409,22 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -18045,16 +23448,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -18075,24 +23481,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -18116,21 +23526,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -18145,7 +23559,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -18153,21 +23567,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -18213,7 +23631,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -18229,27 +23650,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -18270,21 +23751,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -18310,24 +23795,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -18351,21 +23840,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -18380,7 +23873,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -18388,21 +23881,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -18448,7 +23945,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -18464,27 +23964,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -18505,21 +24065,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -18539,7 +24103,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -18547,16 +24111,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -18586,7 +24153,10 @@ paths:
tags:
- Network
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface
consumes:
- application/json
@@ -18602,22 +24172,75 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- Network
@@ -18638,16 +24261,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -18667,7 +24293,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -18675,11 +24301,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -18704,7 +24332,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/p-interface"
+ $ref: "#/getDefinitions/p-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -18712,11 +24340,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -18731,7 +24361,10 @@ paths:
tags:
- Network
summary: create or update an existing p-interface
- description: create or update an existing p-interface
+ description: |
+ Create or update an existing p-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterface
consumes:
- application/json
@@ -18747,17 +24380,63 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: p-interface object that needs to be created or updated
+ description: p-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterface.json)
required: true
schema:
$ref: "#/definitions/p-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing p-interface
+ description: |
+ Update an existing p-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: p-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/p-interface"
delete:
tags:
- Network
@@ -18778,11 +24457,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -18802,7 +24483,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/p-interfaces"
+ $ref: "#/getDefinitions/p-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -18810,6 +24491,7 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -18835,14 +24517,16 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -18866,11 +24550,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -18891,24 +24577,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -18932,21 +24622,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -18967,29 +24661,34 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -19013,26 +24712,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -19047,7 +24751,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -19055,26 +24759,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -19136,7 +24845,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -19152,32 +24864,99 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -19198,26 +24977,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -19243,29 +25027,34 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -19289,26 +25078,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -19323,7 +25117,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -19331,26 +25125,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -19412,7 +25211,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -19428,32 +25230,99 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -19474,26 +25343,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -19513,7 +25387,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -19521,21 +25395,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -19581,7 +25459,10 @@ paths:
tags:
- Network
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -19597,27 +25478,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- Network
@@ -19638,21 +25579,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -19672,7 +25617,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -19680,16 +25625,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -19740,24 +25688,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -19781,21 +25733,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -19810,7 +25766,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -19818,21 +25774,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -19887,7 +25847,10 @@ paths:
tags:
- Network
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -19903,27 +25866,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- Network
@@ -19944,21 +25967,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -19978,7 +26005,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -19986,16 +26013,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -20046,19 +26076,22 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -20082,16 +26115,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -20112,24 +26148,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -20153,21 +26193,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -20182,7 +26226,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -20190,21 +26234,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -20255,7 +26303,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -20271,27 +26322,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -20312,21 +26423,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -20352,24 +26467,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -20393,21 +26512,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -20422,7 +26545,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -20430,21 +26553,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -20495,7 +26622,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -20511,27 +26641,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -20552,21 +26742,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -20586,7 +26780,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -20594,16 +26788,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -20638,7 +26835,10 @@ paths:
tags:
- Network
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface
consumes:
- application/json
@@ -20654,22 +26854,75 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- Network
@@ -20690,16 +26943,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -20719,7 +26975,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -20727,11 +26983,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -20761,7 +27019,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interface"
+ $ref: "#/getDefinitions/lag-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -20769,11 +27027,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -20793,7 +27053,10 @@ paths:
tags:
- Network
summary: create or update an existing lag-interface
- description: create or update an existing lag-interface
+ description: |
+ Create or update an existing lag-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterface
consumes:
- application/json
@@ -20809,17 +27072,63 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: lag-interface object that needs to be created or updated
+ description: lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/lag-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing lag-interface
+ description: |
+ Update an existing lag-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: lag-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/lag-interface"
delete:
tags:
- Network
@@ -20840,11 +27149,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -20864,7 +27175,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interfaces"
+ $ref: "#/getDefinitions/lag-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -20872,6 +27183,7 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -20891,7 +27203,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vpls-pe"
+ $ref: "#/getDefinitions/vpls-pe"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -20899,6 +27211,7 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -20908,7 +27221,10 @@ paths:
tags:
- Network
summary: create or update an existing vpls-pe
- description: create or update an existing vpls-pe
+ description: |
+ Create or update an existing vpls-pe.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPe
consumes:
- application/json
@@ -20924,12 +27240,51 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: body
in: body
- description: vpls-pe object that needs to be created or updated
+ description: vpls-pe object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPe.json)
required: true
schema:
$ref: "#/definitions/vpls-pe"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vpls-pe
+ description: |
+ Update an existing vpls-pe
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPe
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: body
+ in: body
+ description: vpls-pe object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vpls-pe"
delete:
tags:
- Network
@@ -20950,6 +27305,7 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -20969,7 +27325,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vpls-pes"
+ $ref: "#/getDefinitions/vpls-pes"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/multicast-configurations/multicast-configuration/{multicast-configuration-id}/relationship-list/relationship:
@@ -20993,9 +27349,10 @@ paths:
description: Unique id of multicast configuration.
required: true
type: string
+ example: __MULTICAST-CONFIGURATION-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkMulticastConfigurationsMulticastConfiguration.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -21020,6 +27377,7 @@ paths:
description: Unique id of multicast configuration.
required: true
type: string
+ example: __MULTICAST-CONFIGURATION-ID__
/network/multicast-configurations/multicast-configuration/{multicast-configuration-id}:
get:
tags:
@@ -21034,7 +27392,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/multicast-configuration"
+ $ref: "#/getDefinitions/multicast-configuration"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -21043,11 +27401,15 @@ paths:
description: Unique id of multicast configuration.
required: true
type: string
+ example: __MULTICAST-CONFIGURATION-ID__
put:
tags:
- Network
summary: create or update an existing multicast-configuration
- description: create or update an existing multicast-configuration
+ description: |
+ Create or update an existing multicast-configuration.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkMulticastConfigurationsMulticastConfiguration
consumes:
- application/json
@@ -21064,12 +27426,52 @@ paths:
description: Unique id of multicast configuration.
required: true
type: string
+ example: __MULTICAST-CONFIGURATION-ID__
- name: body
in: body
- description: multicast-configuration object that needs to be created or updated
+ description: multicast-configuration object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkMulticastConfigurationsMulticastConfiguration.json)
required: true
schema:
$ref: "#/definitions/multicast-configuration"
+ patch:
+ tags:
+ - Network
+ summary: update an existing multicast-configuration
+ description: |
+ Update an existing multicast-configuration
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkMulticastConfigurationsMulticastConfiguration
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: multicast-configuration-id
+ in: path
+ description: Unique id of multicast configuration.
+ required: true
+ type: string
+ example: __MULTICAST-CONFIGURATION-ID__
+ - name: body
+ in: body
+ description: multicast-configuration object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/multicast-configuration"
delete:
tags:
- Network
@@ -21091,6 +27493,7 @@ paths:
description: Unique id of multicast configuration.
required: true
type: string
+ example: __MULTICAST-CONFIGURATION-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -21110,7 +27513,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/multicast-configurations"
+ $ref: "#/getDefinitions/multicast-configurations"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}/cvlan-tags/cvlan-tag-entry/{cvlan-tag}/relationship-list/relationship:
@@ -21134,20 +27537,23 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: cvlan-tag
in: path
description: See mis-na-virtualization-platform.yang
required: true
type: integer
format: int64
+ example: __CVLAN-TAG__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -21172,17 +27578,20 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: cvlan-tag
in: path
description: See mis-na-virtualization-platform.yang
required: true
type: integer
format: int64
+ example: __CVLAN-TAG__
/network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}/cvlan-tags/cvlan-tag-entry/{cvlan-tag}:
get:
tags:
@@ -21197,7 +27606,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/cvlan-tag-entry"
+ $ref: "#/getDefinitions/cvlan-tag-entry"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -21206,17 +27615,20 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: cvlan-tag
in: path
description: See mis-na-virtualization-platform.yang
required: true
type: integer
format: int64
+ example: __CVLAN-TAG__
- name: vnf-name
in: query
description: Name of VNF.
@@ -21276,7 +27688,10 @@ paths:
tags:
- Network
summary: create or update an existing cvlan-tag-entry
- description: create or update an existing cvlan-tag-entry
+ description: |
+ Create or update an existing cvlan-tag-entry.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry
consumes:
- application/json
@@ -21293,23 +27708,78 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: cvlan-tag
in: path
description: See mis-na-virtualization-platform.yang
required: true
type: integer
format: int64
+ example: __CVLAN-TAG__
- name: body
in: body
- description: cvlan-tag-entry object that needs to be created or updated
+ description: cvlan-tag-entry object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry.json)
required: true
schema:
$ref: "#/definitions/cvlan-tag-entry"
+ patch:
+ tags:
+ - Network
+ summary: update an existing cvlan-tag-entry
+ description: |
+ Update an existing cvlan-tag-entry
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-id
+ in: path
+ description: Unique ID of the interface
+ required: true
+ type: string
+ example: __INTERFACE-ID__
+ - name: cvlan-tag
+ in: path
+ description: See mis-na-virtualization-platform.yang
+ required: true
+ type: integer
+ format: int64
+ example: __CVLAN-TAG__
+ - name: body
+ in: body
+ description: cvlan-tag-entry object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/cvlan-tag-entry"
delete:
tags:
- Network
@@ -21331,17 +27801,20 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: cvlan-tag
in: path
description: See mis-na-virtualization-platform.yang
required: true
type: integer
format: int64
+ example: __CVLAN-TAG__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -21361,7 +27834,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/cvlan-tags"
+ $ref: "#/getDefinitions/cvlan-tags"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -21370,11 +27843,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -21451,14 +27926,16 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVcePortGroupsPortGroup.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -21483,11 +27960,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
/network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}:
get:
tags:
@@ -21502,7 +27981,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/port-group"
+ $ref: "#/getDefinitions/port-group"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -21511,11 +27990,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -21575,7 +28056,10 @@ paths:
tags:
- Network
summary: create or update an existing port-group
- description: create or update an existing port-group
+ description: |
+ Create or update an existing port-group.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVcesVcePortGroupsPortGroup
consumes:
- application/json
@@ -21592,17 +28076,64 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: body
in: body
- description: port-group object that needs to be created or updated
+ description: port-group object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVcePortGroupsPortGroup.json)
required: true
schema:
$ref: "#/definitions/port-group"
+ patch:
+ tags:
+ - Network
+ summary: update an existing port-group
+ description: |
+ Update an existing port-group
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVcesVcePortGroupsPortGroup
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-id
+ in: path
+ description: Unique ID of the interface
+ required: true
+ type: string
+ example: __INTERFACE-ID__
+ - name: body
+ in: body
+ description: port-group object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/port-group"
delete:
tags:
- Network
@@ -21624,11 +28155,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -21648,7 +28181,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/port-groups"
+ $ref: "#/getDefinitions/port-groups"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -21657,6 +28190,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -21718,19 +28252,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the license group the resource belongs to, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of a license resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVceLicensesLicense.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -21755,16 +28292,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the license group the resource belongs to, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of a license resource.
required: true
type: string
+ example: __RESOURCE-UUID__
/network/vces/vce/{vnf-id}/licenses/license/{group-uuid}/{resource-uuid}:
get:
tags:
@@ -21779,7 +28319,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/license"
+ $ref: "#/getDefinitions/license"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -21788,16 +28328,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the license group the resource belongs to, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of a license resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -21842,7 +28385,10 @@ paths:
tags:
- Network
summary: create or update an existing license
- description: create or update an existing license
+ description: |
+ Create or update an existing license.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVcesVceLicensesLicense
consumes:
- application/json
@@ -21859,22 +28405,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the license group the resource belongs to, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of a license resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: body
in: body
- description: license object that needs to be created or updated
+ description: license object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVceLicensesLicense.json)
required: true
schema:
$ref: "#/definitions/license"
+ patch:
+ tags:
+ - Network
+ summary: update an existing license
+ description: |
+ Update an existing license
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVcesVceLicensesLicense
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: group-uuid
+ in: path
+ description: Unique ID for the license group the resource belongs to, should be uuid.
+ required: true
+ type: string
+ example: __GROUP-UUID__
+ - name: resource-uuid
+ in: path
+ description: Unique ID of a license resource.
+ required: true
+ type: string
+ example: __RESOURCE-UUID__
+ - name: body
+ in: body
+ description: license object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/license"
delete:
tags:
- Network
@@ -21896,16 +28496,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the license group the resource belongs to, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of a license resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -21925,7 +28528,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/licenses"
+ $ref: "#/getDefinitions/licenses"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -21934,6 +28537,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -21995,19 +28599,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the entitlement group the resource comes from, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of an entitlement resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVceEntitlementsEntitlement.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -22032,16 +28639,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the entitlement group the resource comes from, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of an entitlement resource.
required: true
type: string
+ example: __RESOURCE-UUID__
/network/vces/vce/{vnf-id}/entitlements/entitlement/{group-uuid}/{resource-uuid}:
get:
tags:
@@ -22056,7 +28666,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/entitlement"
+ $ref: "#/getDefinitions/entitlement"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -22065,16 +28675,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the entitlement group the resource comes from, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of an entitlement resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -22119,7 +28732,10 @@ paths:
tags:
- Network
summary: create or update an existing entitlement
- description: create or update an existing entitlement
+ description: |
+ Create or update an existing entitlement.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVcesVceEntitlementsEntitlement
consumes:
- application/json
@@ -22136,22 +28752,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the entitlement group the resource comes from, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of an entitlement resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: body
in: body
- description: entitlement object that needs to be created or updated
+ description: entitlement object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVceEntitlementsEntitlement.json)
required: true
schema:
$ref: "#/definitions/entitlement"
+ patch:
+ tags:
+ - Network
+ summary: update an existing entitlement
+ description: |
+ Update an existing entitlement
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVcesVceEntitlementsEntitlement
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: group-uuid
+ in: path
+ description: Unique ID for the entitlement group the resource comes from, should be uuid.
+ required: true
+ type: string
+ example: __GROUP-UUID__
+ - name: resource-uuid
+ in: path
+ description: Unique ID of an entitlement resource.
+ required: true
+ type: string
+ example: __RESOURCE-UUID__
+ - name: body
+ in: body
+ description: entitlement object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/entitlement"
delete:
tags:
- Network
@@ -22173,16 +28843,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the entitlement group the resource comes from, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of an entitlement resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -22202,7 +28875,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/entitlements"
+ $ref: "#/getDefinitions/entitlements"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -22211,6 +28884,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -22272,9 +28946,10 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVce.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -22299,6 +28974,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
/network/vces/vce/{vnf-id}:
get:
tags:
@@ -22313,7 +28989,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vce"
+ $ref: "#/getDefinitions/vce"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -22322,6 +28998,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -22366,7 +29043,10 @@ paths:
tags:
- Network
summary: create or update an existing vce
- description: create or update an existing vce
+ description: |
+ Create or update an existing vce.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVcesVce
consumes:
- application/json
@@ -22383,12 +29063,52 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: body
in: body
- description: vce object that needs to be created or updated
+ description: vce object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVce.json)
required: true
schema:
$ref: "#/definitions/vce"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vce
+ description: |
+ Update an existing vce
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVcesVce
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: body
+ in: body
+ description: vce object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vce"
delete:
tags:
- Network
@@ -22410,6 +29130,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -22429,7 +29150,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vces"
+ $ref: "#/getDefinitions/vces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/vnfcs/vnfc/{vnfc-name}/relationship-list/relationship:
@@ -22453,9 +29174,10 @@ paths:
description: Unique ID of vnfc.
required: true
type: string
+ example: __VNFC-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVnfcsVnfc.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -22480,6 +29202,7 @@ paths:
description: Unique ID of vnfc.
required: true
type: string
+ example: __VNFC-NAME__
/network/vnfcs/vnfc/{vnfc-name}:
get:
tags:
@@ -22494,7 +29217,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vnfc"
+ $ref: "#/getDefinitions/vnfc"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -22503,6 +29226,7 @@ paths:
description: Unique ID of vnfc.
required: true
type: string
+ example: __VNFC-NAME__
- name: vnfc-function-code
in: query
description: function code
@@ -22540,7 +29264,10 @@ paths:
tags:
- Network
summary: create or update an existing vnfc
- description: create or update an existing vnfc
+ description: |
+ Create or update an existing vnfc.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVnfcsVnfc
consumes:
- application/json
@@ -22557,12 +29284,52 @@ paths:
description: Unique ID of vnfc.
required: true
type: string
+ example: __VNFC-NAME__
- name: body
in: body
- description: vnfc object that needs to be created or updated
+ description: vnfc object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVnfcsVnfc.json)
required: true
schema:
$ref: "#/definitions/vnfc"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vnfc
+ description: |
+ Update an existing vnfc
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVnfcsVnfc
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnfc-name
+ in: path
+ description: Unique ID of vnfc.
+ required: true
+ type: string
+ example: __VNFC-NAME__
+ - name: body
+ in: body
+ description: vnfc object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vnfc"
delete:
tags:
- Network
@@ -22584,6 +29351,7 @@ paths:
description: Unique ID of vnfc.
required: true
type: string
+ example: __VNFC-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -22603,7 +29371,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vnfcs"
+ $ref: "#/getDefinitions/vnfcs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/l3-networks/l3-network/{network-id}/subnets/subnet/{subnet-id}/relationship-list/relationship:
@@ -22627,14 +29395,16 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: subnet-id
in: path
description: Subnet ID, should be UUID.
required: true
type: string
+ example: __SUBNET-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3NetworkSubnetsSubnet.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -22659,11 +29429,13 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: subnet-id
in: path
description: Subnet ID, should be UUID.
required: true
type: string
+ example: __SUBNET-ID__
/network/l3-networks/l3-network/{network-id}/subnets/subnet/{subnet-id}:
get:
tags:
@@ -22678,7 +29450,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/subnet"
+ $ref: "#/getDefinitions/subnet"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -22687,11 +29459,13 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: subnet-id
in: path
description: Subnet ID, should be UUID.
required: true
type: string
+ example: __SUBNET-ID__
- name: network-name
in: query
description: Name of the network, governed by some naming convention..
@@ -22746,7 +29520,10 @@ paths:
tags:
- Network
summary: create or update an existing subnet
- description: create or update an existing subnet
+ description: |
+ Create or update an existing subnet.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkL3NetworksL3NetworkSubnetsSubnet
consumes:
- application/json
@@ -22763,17 +29540,64 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: subnet-id
in: path
description: Subnet ID, should be UUID.
required: true
type: string
+ example: __SUBNET-ID__
- name: body
in: body
- description: subnet object that needs to be created or updated
+ description: subnet object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3NetworkSubnetsSubnet.json)
required: true
schema:
$ref: "#/definitions/subnet"
+ patch:
+ tags:
+ - Network
+ summary: update an existing subnet
+ description: |
+ Update an existing subnet
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkL3NetworksL3NetworkSubnetsSubnet
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: network-id
+ in: path
+ description: Network ID, should be uuid. Unique across A&AI.
+ required: true
+ type: string
+ example: __NETWORK-ID__
+ - name: subnet-id
+ in: path
+ description: Subnet ID, should be UUID.
+ required: true
+ type: string
+ example: __SUBNET-ID__
+ - name: body
+ in: body
+ description: subnet object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/subnet"
delete:
tags:
- Network
@@ -22795,11 +29619,13 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: subnet-id
in: path
description: Subnet ID, should be UUID.
required: true
type: string
+ example: __SUBNET-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -22819,7 +29645,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/subnets"
+ $ref: "#/getDefinitions/subnets"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -22828,6 +29654,7 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: network-name
in: query
description: Name of the network, governed by some naming convention..
@@ -22894,15 +29721,17 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: vlan-id-inner
in: path
description: id.
required: true
type: integer
format: int64
+ example: __VLAN-ID-INNER__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -22927,12 +29756,14 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: vlan-id-inner
in: path
description: id.
required: true
type: integer
format: int64
+ example: __VLAN-ID-INNER__
/network/l3-networks/l3-network/{network-id}/ctag-assignments/ctag-assignment/{vlan-id-inner}:
get:
tags:
@@ -22947,7 +29778,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/ctag-assignment"
+ $ref: "#/getDefinitions/ctag-assignment"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -22956,12 +29787,14 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: vlan-id-inner
in: path
description: id.
required: true
type: integer
format: int64
+ example: __VLAN-ID-INNER__
- name: network-name
in: query
description: Name of the network, governed by some naming convention..
@@ -23011,7 +29844,10 @@ paths:
tags:
- Network
summary: create or update an existing ctag-assignment
- description: create or update an existing ctag-assignment
+ description: |
+ Create or update an existing ctag-assignment.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment
consumes:
- application/json
@@ -23028,18 +29864,66 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: vlan-id-inner
in: path
description: id.
required: true
type: integer
format: int64
+ example: __VLAN-ID-INNER__
- name: body
in: body
- description: ctag-assignment object that needs to be created or updated
+ description: ctag-assignment object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment.json)
required: true
schema:
$ref: "#/definitions/ctag-assignment"
+ patch:
+ tags:
+ - Network
+ summary: update an existing ctag-assignment
+ description: |
+ Update an existing ctag-assignment
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: network-id
+ in: path
+ description: Network ID, should be uuid. Unique across A&AI.
+ required: true
+ type: string
+ example: __NETWORK-ID__
+ - name: vlan-id-inner
+ in: path
+ description: id.
+ required: true
+ type: integer
+ format: int64
+ example: __VLAN-ID-INNER__
+ - name: body
+ in: body
+ description: ctag-assignment object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/ctag-assignment"
delete:
tags:
- Network
@@ -23061,12 +29945,14 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: vlan-id-inner
in: path
description: id.
required: true
type: integer
format: int64
+ example: __VLAN-ID-INNER__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -23086,7 +29972,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/ctag-assignments"
+ $ref: "#/getDefinitions/ctag-assignments"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -23095,6 +29981,7 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: network-name
in: query
description: Name of the network, governed by some naming convention..
@@ -23161,14 +30048,16 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: segmentation-id
in: path
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __SEGMENTATION-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -23193,11 +30082,13 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: segmentation-id
in: path
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __SEGMENTATION-ID__
/network/l3-networks/l3-network/{network-id}/segmentation-assignments/segmentation-assignment/{segmentation-id}:
get:
tags:
@@ -23212,7 +30103,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/segmentation-assignment"
+ $ref: "#/getDefinitions/segmentation-assignment"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -23221,11 +30112,13 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: segmentation-id
in: path
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __SEGMENTATION-ID__
- name: network-name
in: query
description: Name of the network, governed by some naming convention..
@@ -23275,7 +30168,10 @@ paths:
tags:
- Network
summary: create or update an existing segmentation-assignment
- description: create or update an existing segmentation-assignment
+ description: |
+ Create or update an existing segmentation-assignment.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment
consumes:
- application/json
@@ -23292,17 +30188,64 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: segmentation-id
in: path
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __SEGMENTATION-ID__
- name: body
in: body
- description: segmentation-assignment object that needs to be created or updated
+ description: segmentation-assignment object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment.json)
required: true
schema:
$ref: "#/definitions/segmentation-assignment"
+ patch:
+ tags:
+ - Network
+ summary: update an existing segmentation-assignment
+ description: |
+ Update an existing segmentation-assignment
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: network-id
+ in: path
+ description: Network ID, should be uuid. Unique across A&AI.
+ required: true
+ type: string
+ example: __NETWORK-ID__
+ - name: segmentation-id
+ in: path
+ description: Route Table Reference id, UUID assigned to this instance.
+ required: true
+ type: string
+ example: __SEGMENTATION-ID__
+ - name: body
+ in: body
+ description: segmentation-assignment object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/segmentation-assignment"
delete:
tags:
- Network
@@ -23324,11 +30267,13 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: segmentation-id
in: path
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __SEGMENTATION-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -23348,7 +30293,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/segmentation-assignments"
+ $ref: "#/getDefinitions/segmentation-assignments"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -23357,6 +30302,7 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: network-name
in: query
description: Name of the network, governed by some naming convention..
@@ -23423,9 +30369,10 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3Network.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -23450,6 +30397,7 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
/network/l3-networks/l3-network/{network-id}:
get:
tags:
@@ -23464,7 +30412,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-network"
+ $ref: "#/getDefinitions/l3-network"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -23473,6 +30421,7 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: network-name
in: query
description: Name of the network, governed by some naming convention..
@@ -23522,7 +30471,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-network
- description: create or update an existing l3-network
+ description: |
+ Create or update an existing l3-network.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkL3NetworksL3Network
consumes:
- application/json
@@ -23539,12 +30491,52 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: body
in: body
- description: l3-network object that needs to be created or updated
+ description: l3-network object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3Network.json)
required: true
schema:
$ref: "#/definitions/l3-network"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-network
+ description: |
+ Update an existing l3-network
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkL3NetworksL3Network
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: network-id
+ in: path
+ description: Network ID, should be uuid. Unique across A&AI.
+ required: true
+ type: string
+ example: __NETWORK-ID__
+ - name: body
+ in: body
+ description: l3-network object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-network"
delete:
tags:
- Network
@@ -23566,6 +30558,7 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -23585,7 +30578,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-networks"
+ $ref: "#/getDefinitions/l3-networks"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/network-policies/network-policy/{network-policy-id}/relationship-list/relationship:
@@ -23609,9 +30602,10 @@ paths:
description: UUID representing unique key to this instance
required: true
type: string
+ example: __NETWORK-POLICY-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNetworkPoliciesNetworkPolicy.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -23636,6 +30630,7 @@ paths:
description: UUID representing unique key to this instance
required: true
type: string
+ example: __NETWORK-POLICY-ID__
/network/network-policies/network-policy/{network-policy-id}:
get:
tags:
@@ -23650,7 +30645,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/network-policy"
+ $ref: "#/getDefinitions/network-policy"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -23659,6 +30654,7 @@ paths:
description: UUID representing unique key to this instance
required: true
type: string
+ example: __NETWORK-POLICY-ID__
- name: network-policy-fqdn
in: query
description: Contrail FQDN for the policy
@@ -23668,7 +30664,10 @@ paths:
tags:
- Network
summary: create or update an existing network-policy
- description: create or update an existing network-policy
+ description: |
+ Create or update an existing network-policy.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNetworkPoliciesNetworkPolicy
consumes:
- application/json
@@ -23685,12 +30684,52 @@ paths:
description: UUID representing unique key to this instance
required: true
type: string
+ example: __NETWORK-POLICY-ID__
- name: body
in: body
- description: network-policy object that needs to be created or updated
+ description: network-policy object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNetworkPoliciesNetworkPolicy.json)
required: true
schema:
$ref: "#/definitions/network-policy"
+ patch:
+ tags:
+ - Network
+ summary: update an existing network-policy
+ description: |
+ Update an existing network-policy
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNetworkPoliciesNetworkPolicy
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: network-policy-id
+ in: path
+ description: UUID representing unique key to this instance
+ required: true
+ type: string
+ example: __NETWORK-POLICY-ID__
+ - name: body
+ in: body
+ description: network-policy object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/network-policy"
delete:
tags:
- Network
@@ -23712,6 +30751,7 @@ paths:
description: UUID representing unique key to this instance
required: true
type: string
+ example: __NETWORK-POLICY-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -23731,7 +30771,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/network-policies"
+ $ref: "#/getDefinitions/network-policies"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/generic-vnfs/generic-vnf/{vnf-id}/relationship-list/relationship:
@@ -23755,9 +30795,10 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -23782,6 +30823,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -23803,19 +30845,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -23840,16 +30885,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -23871,24 +30919,28 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -23913,21 +30965,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -23942,7 +30998,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -23951,21 +31007,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -24095,7 +31155,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -24112,27 +31175,88 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -24154,21 +31278,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -24195,24 +31323,28 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -24237,21 +31369,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -24266,7 +31402,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -24275,21 +31411,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -24419,7 +31559,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -24436,27 +31579,88 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -24478,21 +31682,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -24512,7 +31720,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -24521,16 +31729,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: vnf-name
in: query
description: Name of VNF.
@@ -24644,7 +31855,10 @@ paths:
tags:
- Network
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -24661,22 +31875,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- Network
@@ -24698,16 +31966,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -24727,7 +31998,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -24736,11 +32007,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -24860,19 +32133,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -24897,16 +32173,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -24921,7 +32200,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -24930,16 +32209,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -25062,7 +32344,10 @@ paths:
tags:
- Network
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -25079,22 +32364,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- Network
@@ -25116,16 +32455,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -25145,7 +32487,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -25154,11 +32496,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -25278,14 +32622,16 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -25310,11 +32656,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -25336,19 +32684,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -25373,16 +32724,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -25397,7 +32751,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -25406,16 +32760,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -25534,7 +32891,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -25551,22 +32911,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -25588,16 +33002,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -25624,19 +33041,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -25661,16 +33081,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -25685,7 +33108,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -25694,16 +33117,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -25822,7 +33248,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -25839,22 +33268,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -25876,16 +33359,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -25905,7 +33391,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -25914,11 +33400,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -26021,7 +33509,10 @@ paths:
tags:
- Network
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterface
consumes:
- application/json
@@ -26038,17 +33529,64 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- Network
@@ -26070,11 +33608,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -26094,7 +33634,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -26103,6 +33643,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -26207,14 +33748,16 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -26239,11 +33782,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -26265,24 +33810,28 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -26307,21 +33856,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -26343,29 +33896,34 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -26390,26 +33948,31 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -26424,7 +33987,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -26433,26 +33996,31 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -26592,7 +34160,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -26609,32 +34180,100 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -26656,26 +34295,31 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -26702,29 +34346,34 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -26749,26 +34398,31 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -26783,7 +34437,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -26792,26 +34446,31 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -26951,7 +34610,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -26968,32 +34630,100 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -27015,26 +34745,31 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -27054,7 +34789,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -27063,21 +34798,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: vnf-name
in: query
description: Name of VNF.
@@ -27201,7 +34940,10 @@ paths:
tags:
- Network
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -27218,27 +34960,88 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- Network
@@ -27260,21 +35063,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -27294,7 +35101,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -27303,16 +35110,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -27442,24 +35252,28 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -27484,21 +35298,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -27513,7 +35331,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -27522,21 +35340,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -27669,7 +35491,10 @@ paths:
tags:
- Network
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -27686,27 +35511,88 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- Network
@@ -27728,21 +35614,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -27762,7 +35652,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -27771,16 +35661,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -27910,19 +35803,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -27947,16 +35843,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -27978,24 +35877,28 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -28020,21 +35923,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -28049,7 +35956,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -28058,21 +35965,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -28201,7 +36112,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -28218,27 +36132,88 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -28260,21 +36235,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -28301,24 +36280,28 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -28343,21 +36326,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -28372,7 +36359,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -28381,21 +36368,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -28524,7 +36515,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -28541,27 +36535,88 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -28583,21 +36638,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -28617,7 +36676,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -28626,16 +36685,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -28748,7 +36810,10 @@ paths:
tags:
- Network
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface
consumes:
- application/json
@@ -28765,22 +36830,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- Network
@@ -28802,16 +36921,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -28831,7 +36953,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -28840,11 +36962,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -28952,7 +37076,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interface"
+ $ref: "#/getDefinitions/lag-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -28961,11 +37085,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -29063,7 +37189,10 @@ paths:
tags:
- Network
summary: create or update an existing lag-interface
- description: create or update an existing lag-interface
+ description: |
+ Create or update an existing lag-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterface
consumes:
- application/json
@@ -29080,17 +37209,64 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: lag-interface object that needs to be created or updated
+ description: lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/lag-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing lag-interface
+ description: |
+ Update an existing lag-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: lag-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/lag-interface"
delete:
tags:
- Network
@@ -29112,11 +37288,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -29136,7 +37314,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interfaces"
+ $ref: "#/getDefinitions/lag-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -29145,6 +37323,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -29249,14 +37428,16 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vf-module-id
in: path
description: Unique ID of vf-module.
required: true
type: string
+ example: __VF-MODULE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfVfModulesVfModule.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -29281,11 +37462,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vf-module-id
in: path
description: Unique ID of vf-module.
required: true
type: string
+ example: __VF-MODULE-ID__
/network/generic-vnfs/generic-vnf/{vnf-id}/vf-modules/vf-module/{vf-module-id}:
get:
tags:
@@ -29300,7 +37483,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vf-module"
+ $ref: "#/getDefinitions/vf-module"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -29309,11 +37492,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vf-module-id
in: path
description: Unique ID of vf-module.
required: true
type: string
+ example: __VF-MODULE-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -29436,7 +37621,10 @@ paths:
tags:
- Network
summary: create or update an existing vf-module
- description: create or update an existing vf-module
+ description: |
+ Create or update an existing vf-module.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfVfModulesVfModule
consumes:
- application/json
@@ -29453,17 +37641,64 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vf-module-id
in: path
description: Unique ID of vf-module.
required: true
type: string
+ example: __VF-MODULE-ID__
- name: body
in: body
- description: vf-module object that needs to be created or updated
+ description: vf-module object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfVfModulesVfModule.json)
required: true
schema:
$ref: "#/definitions/vf-module"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vf-module
+ description: |
+ Update an existing vf-module
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfVfModulesVfModule
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: vf-module-id
+ in: path
+ description: Unique ID of vf-module.
+ required: true
+ type: string
+ example: __VF-MODULE-ID__
+ - name: body
+ in: body
+ description: vf-module object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vf-module"
delete:
tags:
- Network
@@ -29485,11 +37720,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vf-module-id
in: path
description: Unique ID of vf-module.
required: true
type: string
+ example: __VF-MODULE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -29509,7 +37746,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vf-modules"
+ $ref: "#/getDefinitions/vf-modules"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -29518,6 +37755,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -29622,19 +37860,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the license group the resource belongs to, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of a license resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLicensesLicense.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -29659,16 +37900,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the license group the resource belongs to, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of a license resource.
required: true
type: string
+ example: __RESOURCE-UUID__
/network/generic-vnfs/generic-vnf/{vnf-id}/licenses/license/{group-uuid}/{resource-uuid}:
get:
tags:
@@ -29683,7 +37927,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/license"
+ $ref: "#/getDefinitions/license"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -29692,16 +37936,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the license group the resource belongs to, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of a license resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -29789,7 +38036,10 @@ paths:
tags:
- Network
summary: create or update an existing license
- description: create or update an existing license
+ description: |
+ Create or update an existing license.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLicensesLicense
consumes:
- application/json
@@ -29806,22 +38056,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the license group the resource belongs to, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of a license resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: body
in: body
- description: license object that needs to be created or updated
+ description: license object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLicensesLicense.json)
required: true
schema:
$ref: "#/definitions/license"
+ patch:
+ tags:
+ - Network
+ summary: update an existing license
+ description: |
+ Update an existing license
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLicensesLicense
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: group-uuid
+ in: path
+ description: Unique ID for the license group the resource belongs to, should be uuid.
+ required: true
+ type: string
+ example: __GROUP-UUID__
+ - name: resource-uuid
+ in: path
+ description: Unique ID of a license resource.
+ required: true
+ type: string
+ example: __RESOURCE-UUID__
+ - name: body
+ in: body
+ description: license object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/license"
delete:
tags:
- Network
@@ -29843,16 +38147,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the license group the resource belongs to, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of a license resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -29872,7 +38179,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/licenses"
+ $ref: "#/getDefinitions/licenses"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -29881,6 +38188,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -29985,19 +38293,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the entitlement group the resource comes from, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of an entitlement resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfEntitlementsEntitlement.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -30022,16 +38333,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the entitlement group the resource comes from, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of an entitlement resource.
required: true
type: string
+ example: __RESOURCE-UUID__
/network/generic-vnfs/generic-vnf/{vnf-id}/entitlements/entitlement/{group-uuid}/{resource-uuid}:
get:
tags:
@@ -30046,7 +38360,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/entitlement"
+ $ref: "#/getDefinitions/entitlement"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -30055,16 +38369,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the entitlement group the resource comes from, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of an entitlement resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -30152,7 +38469,10 @@ paths:
tags:
- Network
summary: create or update an existing entitlement
- description: create or update an existing entitlement
+ description: |
+ Create or update an existing entitlement.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfEntitlementsEntitlement
consumes:
- application/json
@@ -30169,22 +38489,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the entitlement group the resource comes from, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of an entitlement resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: body
in: body
- description: entitlement object that needs to be created or updated
+ description: entitlement object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfEntitlementsEntitlement.json)
required: true
schema:
$ref: "#/definitions/entitlement"
+ patch:
+ tags:
+ - Network
+ summary: update an existing entitlement
+ description: |
+ Update an existing entitlement
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfEntitlementsEntitlement
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: group-uuid
+ in: path
+ description: Unique ID for the entitlement group the resource comes from, should be uuid.
+ required: true
+ type: string
+ example: __GROUP-UUID__
+ - name: resource-uuid
+ in: path
+ description: Unique ID of an entitlement resource.
+ required: true
+ type: string
+ example: __RESOURCE-UUID__
+ - name: body
+ in: body
+ description: entitlement object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/entitlement"
delete:
tags:
- Network
@@ -30206,16 +38580,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the entitlement group the resource comes from, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of an entitlement resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -30235,7 +38612,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/entitlements"
+ $ref: "#/getDefinitions/entitlements"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -30244,6 +38621,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -30341,7 +38719,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/generic-vnf"
+ $ref: "#/getDefinitions/generic-vnf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -30350,6 +38728,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -30437,7 +38816,10 @@ paths:
tags:
- Network
summary: create or update an existing generic-vnf
- description: create or update an existing generic-vnf
+ description: |
+ Create or update an existing generic-vnf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnf
consumes:
- application/json
@@ -30454,12 +38836,52 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: body
in: body
- description: generic-vnf object that needs to be created or updated
+ description: generic-vnf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnf.json)
required: true
schema:
$ref: "#/definitions/generic-vnf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing generic-vnf
+ description: |
+ Update an existing generic-vnf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: body
+ in: body
+ description: generic-vnf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/generic-vnf"
delete:
tags:
- Network
@@ -30481,6 +38903,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -30500,7 +38923,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/generic-vnfs"
+ $ref: "#/getDefinitions/generic-vnfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/lag-links/lag-link/{link-name}/relationship-list/relationship:
@@ -30524,9 +38947,10 @@ paths:
description: Alphabetical concatenation of lag-interface names
required: true
type: string
+ example: __LINK-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkLagLinksLagLink.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -30551,6 +38975,7 @@ paths:
description: Alphabetical concatenation of lag-interface names
required: true
type: string
+ example: __LINK-NAME__
/network/lag-links/lag-link/{link-name}:
get:
tags:
@@ -30565,7 +38990,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-link"
+ $ref: "#/getDefinitions/lag-link"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -30574,11 +38999,15 @@ paths:
description: Alphabetical concatenation of lag-interface names
required: true
type: string
+ example: __LINK-NAME__
put:
tags:
- Network
summary: create or update an existing lag-link
- description: create or update an existing lag-link
+ description: |
+ Create or update an existing lag-link.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkLagLinksLagLink
consumes:
- application/json
@@ -30595,12 +39024,52 @@ paths:
description: Alphabetical concatenation of lag-interface names
required: true
type: string
+ example: __LINK-NAME__
- name: body
in: body
- description: lag-link object that needs to be created or updated
+ description: lag-link object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkLagLinksLagLink.json)
required: true
schema:
$ref: "#/definitions/lag-link"
+ patch:
+ tags:
+ - Network
+ summary: update an existing lag-link
+ description: |
+ Update an existing lag-link
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkLagLinksLagLink
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: link-name
+ in: path
+ description: Alphabetical concatenation of lag-interface names
+ required: true
+ type: string
+ example: __LINK-NAME__
+ - name: body
+ in: body
+ description: lag-link object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/lag-link"
delete:
tags:
- Network
@@ -30622,6 +39091,7 @@ paths:
description: Alphabetical concatenation of lag-interface names
required: true
type: string
+ example: __LINK-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -30641,7 +39111,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-links"
+ $ref: "#/getDefinitions/lag-links"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/newvces/newvce/{vnf-id2}/relationship-list/relationship:
@@ -30665,9 +39135,10 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvce.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -30692,6 +39163,7 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -30713,19 +39185,22 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -30750,16 +39225,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -30781,24 +39259,28 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -30823,21 +39305,25 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -30852,7 +39338,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -30861,21 +39347,25 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -30947,7 +39437,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -30964,27 +39457,88 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -31006,21 +39560,25 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -31047,24 +39605,28 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -31089,21 +39651,25 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -31118,7 +39684,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -31127,21 +39693,25 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -31213,7 +39783,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -31230,27 +39803,88 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -31272,21 +39906,25 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -31306,7 +39944,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -31315,16 +39953,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: vnf-name
in: query
description: Name of VNF.
@@ -31380,7 +40021,10 @@ paths:
tags:
- Network
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -31397,22 +40041,76 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- Network
@@ -31434,16 +40132,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -31463,7 +40164,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -31472,11 +40173,13 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -31538,19 +40241,22 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -31575,16 +40281,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -31599,7 +40308,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -31608,16 +40317,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -31682,7 +40394,10 @@ paths:
tags:
- Network
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -31699,22 +40414,76 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- Network
@@ -31736,16 +40505,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -31765,7 +40537,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -31774,11 +40546,13 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -31840,14 +40614,16 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -31872,11 +40648,13 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -31898,19 +40676,22 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -31935,16 +40716,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -31959,7 +40743,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -31968,16 +40752,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -32038,7 +40825,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -32055,22 +40845,76 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -32092,16 +40936,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -32128,19 +40975,22 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -32165,16 +41015,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -32189,7 +41042,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -32198,16 +41051,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -32268,7 +41124,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -32285,22 +41144,76 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -32322,16 +41235,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -32351,7 +41267,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -32360,11 +41276,13 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -32409,7 +41327,10 @@ paths:
tags:
- Network
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterface
consumes:
- application/json
@@ -32426,17 +41347,64 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- Network
@@ -32458,11 +41426,13 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -32482,7 +41452,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -32491,6 +41461,7 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: vnf-name
in: query
description: Name of VNF.
@@ -32530,7 +41501,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/newvce"
+ $ref: "#/getDefinitions/newvce"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -32539,6 +41510,7 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: vnf-name
in: query
description: Name of VNF.
@@ -32568,7 +41540,10 @@ paths:
tags:
- Network
summary: create or update an existing newvce
- description: create or update an existing newvce
+ description: |
+ Create or update an existing newvce.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvce
consumes:
- application/json
@@ -32585,12 +41560,52 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: body
in: body
- description: newvce object that needs to be created or updated
+ description: newvce object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvce.json)
required: true
schema:
$ref: "#/definitions/newvce"
+ patch:
+ tags:
+ - Network
+ summary: update an existing newvce
+ description: |
+ Update an existing newvce
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvce
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: body
+ in: body
+ description: newvce object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/newvce"
delete:
tags:
- Network
@@ -32612,6 +41627,7 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -32631,7 +41647,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/newvces"
+ $ref: "#/getDefinitions/newvces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/pnfs/pnf/{pnf-name}/relationship-list/relationship:
@@ -32655,9 +41671,10 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -32682,6 +41699,7 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/relationship-list/relationship:
put:
tags:
@@ -32703,14 +41721,16 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -32735,11 +41755,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -32761,24 +41783,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -32803,21 +41829,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -32839,29 +41869,34 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -32886,26 +41921,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -32920,7 +41960,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -32929,26 +41969,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -33005,7 +42050,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -33022,32 +42070,100 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -33069,26 +42185,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -33115,29 +42236,34 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -33162,26 +42288,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -33196,7 +42327,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -33205,26 +42336,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -33281,7 +42417,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -33298,32 +42437,100 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -33345,26 +42552,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -33384,7 +42596,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -33393,21 +42605,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -33448,7 +42664,10 @@ paths:
tags:
- Network
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -33465,27 +42684,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- Network
@@ -33507,21 +42787,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -33541,7 +42825,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -33550,16 +42834,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -33606,24 +42893,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -33648,21 +42939,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -33677,7 +42972,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -33686,21 +42981,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -33750,7 +43049,10 @@ paths:
tags:
- Network
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -33767,27 +43069,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- Network
@@ -33809,21 +43172,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -33843,7 +43210,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -33852,16 +43219,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -33908,19 +43278,22 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -33945,16 +43318,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -33976,24 +43352,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -34018,21 +43398,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -34047,7 +43431,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -34056,21 +43440,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -34116,7 +43504,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -34133,27 +43524,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -34175,21 +43627,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -34216,24 +43672,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -34258,21 +43718,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -34287,7 +43751,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -34296,21 +43760,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -34356,7 +43824,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -34373,27 +43844,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -34415,21 +43947,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -34449,7 +43985,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -34458,16 +43994,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -34497,7 +44036,10 @@ paths:
tags:
- Network
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface
consumes:
- application/json
@@ -34514,22 +44056,76 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- Network
@@ -34551,16 +44147,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -34580,7 +44179,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -34589,11 +44188,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -34618,7 +44219,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/p-interface"
+ $ref: "#/getDefinitions/p-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -34627,11 +44228,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -34646,7 +44249,10 @@ paths:
tags:
- Network
summary: create or update an existing p-interface
- description: create or update an existing p-interface
+ description: |
+ Create or update an existing p-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterface
consumes:
- application/json
@@ -34663,17 +44269,64 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: p-interface object that needs to be created or updated
+ description: p-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterface.json)
required: true
schema:
$ref: "#/definitions/p-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing p-interface
+ description: |
+ Update an existing p-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: p-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/p-interface"
delete:
tags:
- Network
@@ -34695,11 +44348,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -34719,7 +44374,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/p-interfaces"
+ $ref: "#/getDefinitions/p-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -34728,6 +44383,7 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -34754,14 +44410,16 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -34786,11 +44444,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -34812,24 +44472,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -34854,21 +44518,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -34890,29 +44558,34 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -34937,26 +44610,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -34971,7 +44649,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -34980,26 +44658,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -35061,7 +44744,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -35078,32 +44764,100 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -35125,26 +44879,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -35171,29 +44930,34 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -35218,26 +44982,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -35252,7 +45021,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -35261,26 +45030,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -35342,7 +45116,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -35359,32 +45136,100 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -35406,26 +45251,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -35445,7 +45295,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -35454,21 +45304,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -35514,7 +45368,10 @@ paths:
tags:
- Network
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -35531,27 +45388,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- Network
@@ -35573,21 +45491,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -35607,7 +45529,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -35616,16 +45538,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -35677,24 +45602,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -35719,21 +45648,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -35748,7 +45681,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -35757,21 +45690,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -35826,7 +45763,10 @@ paths:
tags:
- Network
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -35843,27 +45783,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- Network
@@ -35885,21 +45886,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -35919,7 +45924,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -35928,16 +45933,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -35989,19 +45997,22 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -36026,16 +46037,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -36057,24 +46071,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -36099,21 +46117,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -36128,7 +46150,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -36137,21 +46159,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -36202,7 +46228,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -36219,27 +46248,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -36261,21 +46351,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -36302,24 +46396,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -36344,21 +46442,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -36373,7 +46475,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -36382,21 +46484,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -36447,7 +46553,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -36464,27 +46573,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -36506,21 +46676,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -36540,7 +46714,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -36549,16 +46723,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -36593,7 +46770,10 @@ paths:
tags:
- Network
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface
consumes:
- application/json
@@ -36610,22 +46790,76 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- Network
@@ -36647,16 +46881,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -36676,7 +46913,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -36685,11 +46922,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -36719,7 +46958,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interface"
+ $ref: "#/getDefinitions/lag-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -36728,11 +46967,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -36752,7 +46993,10 @@ paths:
tags:
- Network
summary: create or update an existing lag-interface
- description: create or update an existing lag-interface
+ description: |
+ Create or update an existing lag-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterface
consumes:
- application/json
@@ -36769,17 +47013,64 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: lag-interface object that needs to be created or updated
+ description: lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/lag-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing lag-interface
+ description: |
+ Update an existing lag-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: lag-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/lag-interface"
delete:
tags:
- Network
@@ -36801,11 +47092,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -36825,7 +47118,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interfaces"
+ $ref: "#/getDefinitions/lag-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -36834,6 +47127,7 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -36853,7 +47147,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/pnf"
+ $ref: "#/getDefinitions/pnf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -36862,6 +47156,7 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -36871,7 +47166,10 @@ paths:
tags:
- Network
summary: create or update an existing pnf
- description: create or update an existing pnf
+ description: |
+ Create or update an existing pnf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnf
consumes:
- application/json
@@ -36888,12 +47186,52 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: body
in: body
- description: pnf object that needs to be created or updated
+ description: pnf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnf.json)
required: true
schema:
$ref: "#/definitions/pnf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing pnf
+ description: |
+ Update an existing pnf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: body
+ in: body
+ description: pnf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/pnf"
delete:
tags:
- Network
@@ -36915,6 +47253,7 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -36934,7 +47273,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/pnfs"
+ $ref: "#/getDefinitions/pnfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/physical-links/physical-link/{link-name}/relationship-list/relationship:
@@ -36958,9 +47297,10 @@ paths:
description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPhysicalLinksPhysicalLink.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -36985,6 +47325,7 @@ paths:
description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
required: true
type: string
+ example: __LINK-NAME__
/network/physical-links/physical-link/{link-name}:
get:
tags:
@@ -36999,7 +47340,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/physical-link"
+ $ref: "#/getDefinitions/physical-link"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -37008,6 +47349,7 @@ paths:
description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: circuit-id
in: query
description: Circuit it
@@ -37017,7 +47359,10 @@ paths:
tags:
- Network
summary: create or update an existing physical-link
- description: create or update an existing physical-link
+ description: |
+ Create or update an existing physical-link.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPhysicalLinksPhysicalLink
consumes:
- application/json
@@ -37034,12 +47379,52 @@ paths:
description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: body
in: body
- description: physical-link object that needs to be created or updated
+ description: physical-link object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPhysicalLinksPhysicalLink.json)
required: true
schema:
$ref: "#/definitions/physical-link"
+ patch:
+ tags:
+ - Network
+ summary: update an existing physical-link
+ description: |
+ Update an existing physical-link
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPhysicalLinksPhysicalLink
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: link-name
+ in: path
+ description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
+ required: true
+ type: string
+ example: __LINK-NAME__
+ - name: body
+ in: body
+ description: physical-link object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/physical-link"
delete:
tags:
- Network
@@ -37061,6 +47446,7 @@ paths:
description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -37080,7 +47466,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/physical-links"
+ $ref: "#/getDefinitions/physical-links"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}/relationship-list/relationship:
@@ -37104,9 +47490,10 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkIpsecConfigurationsIpsecConfiguration.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -37131,6 +47518,7 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
/network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}/vig-servers/vig-server/{vig-address-type}/relationship-list/relationship:
put:
tags:
@@ -37152,14 +47540,16 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: vig-address-type
in: path
description: indicates whether the VIG is for AVPN or INTERNET
required: true
type: string
+ example: __VIG-ADDRESS-TYPE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -37184,11 +47574,13 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: vig-address-type
in: path
description: indicates whether the VIG is for AVPN or INTERNET
required: true
type: string
+ example: __VIG-ADDRESS-TYPE__
/network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}/vig-servers/vig-server/{vig-address-type}:
get:
tags:
@@ -37203,7 +47595,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vig-server"
+ $ref: "#/getDefinitions/vig-server"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -37212,16 +47604,21 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: vig-address-type
in: path
description: indicates whether the VIG is for AVPN or INTERNET
required: true
type: string
+ example: __VIG-ADDRESS-TYPE__
put:
tags:
- Network
summary: create or update an existing vig-server
- description: create or update an existing vig-server
+ description: |
+ Create or update an existing vig-server.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer
consumes:
- application/json
@@ -37238,17 +47635,64 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: vig-address-type
in: path
description: indicates whether the VIG is for AVPN or INTERNET
required: true
type: string
+ example: __VIG-ADDRESS-TYPE__
- name: body
in: body
- description: vig-server object that needs to be created or updated
+ description: vig-server object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer.json)
required: true
schema:
$ref: "#/definitions/vig-server"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vig-server
+ description: |
+ Update an existing vig-server
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: ipsec-configuration-id
+ in: path
+ description: UUID of this configuration
+ required: true
+ type: string
+ example: __IPSEC-CONFIGURATION-ID__
+ - name: vig-address-type
+ in: path
+ description: indicates whether the VIG is for AVPN or INTERNET
+ required: true
+ type: string
+ example: __VIG-ADDRESS-TYPE__
+ - name: body
+ in: body
+ description: vig-server object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vig-server"
delete:
tags:
- Network
@@ -37270,11 +47714,13 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: vig-address-type
in: path
description: indicates whether the VIG is for AVPN or INTERNET
required: true
type: string
+ example: __VIG-ADDRESS-TYPE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -37294,7 +47740,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vig-servers"
+ $ref: "#/getDefinitions/vig-servers"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -37303,6 +47749,7 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
/network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}:
get:
tags:
@@ -37317,7 +47764,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/ipsec-configuration"
+ $ref: "#/getDefinitions/ipsec-configuration"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -37326,11 +47773,15 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
put:
tags:
- Network
summary: create or update an existing ipsec-configuration
- description: create or update an existing ipsec-configuration
+ description: |
+ Create or update an existing ipsec-configuration.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkIpsecConfigurationsIpsecConfiguration
consumes:
- application/json
@@ -37347,12 +47798,52 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: body
in: body
- description: ipsec-configuration object that needs to be created or updated
+ description: ipsec-configuration object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkIpsecConfigurationsIpsecConfiguration.json)
required: true
schema:
$ref: "#/definitions/ipsec-configuration"
+ patch:
+ tags:
+ - Network
+ summary: update an existing ipsec-configuration
+ description: |
+ Update an existing ipsec-configuration
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkIpsecConfigurationsIpsecConfiguration
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: ipsec-configuration-id
+ in: path
+ description: UUID of this configuration
+ required: true
+ type: string
+ example: __IPSEC-CONFIGURATION-ID__
+ - name: body
+ in: body
+ description: ipsec-configuration object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/ipsec-configuration"
delete:
tags:
- Network
@@ -37374,6 +47865,7 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -37393,7 +47885,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/ipsec-configurations"
+ $ref: "#/getDefinitions/ipsec-configurations"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/route-table-references/route-table-reference/{route-table-reference-id}/relationship-list/relationship:
@@ -37417,9 +47909,10 @@ paths:
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __ROUTE-TABLE-REFERENCE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkRouteTableReferencesRouteTableReference.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -37444,6 +47937,7 @@ paths:
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __ROUTE-TABLE-REFERENCE-ID__
/network/route-table-references/route-table-reference/{route-table-reference-id}:
get:
tags:
@@ -37458,7 +47952,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/route-table-reference"
+ $ref: "#/getDefinitions/route-table-reference"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -37467,6 +47961,7 @@ paths:
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __ROUTE-TABLE-REFERENCE-ID__
- name: route-table-reference-fqdn
in: query
description: FQDN entry in the route table.
@@ -37476,7 +47971,10 @@ paths:
tags:
- Network
summary: create or update an existing route-table-reference
- description: create or update an existing route-table-reference
+ description: |
+ Create or update an existing route-table-reference.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkRouteTableReferencesRouteTableReference
consumes:
- application/json
@@ -37493,12 +47991,52 @@ paths:
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __ROUTE-TABLE-REFERENCE-ID__
- name: body
in: body
- description: route-table-reference object that needs to be created or updated
+ description: route-table-reference object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkRouteTableReferencesRouteTableReference.json)
required: true
schema:
$ref: "#/definitions/route-table-reference"
+ patch:
+ tags:
+ - Network
+ summary: update an existing route-table-reference
+ description: |
+ Update an existing route-table-reference
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkRouteTableReferencesRouteTableReference
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: route-table-reference-id
+ in: path
+ description: Route Table Reference id, UUID assigned to this instance.
+ required: true
+ type: string
+ example: __ROUTE-TABLE-REFERENCE-ID__
+ - name: body
+ in: body
+ description: route-table-reference object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/route-table-reference"
delete:
tags:
- Network
@@ -37520,6 +48058,7 @@ paths:
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __ROUTE-TABLE-REFERENCE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -37539,7 +48078,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/route-table-references"
+ $ref: "#/getDefinitions/route-table-references"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/instance-groups/instance-group/{id}/relationship-list/relationship:
@@ -37563,9 +48102,10 @@ paths:
description: Instance Group ID, UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkInstanceGroupsInstanceGroup.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -37590,6 +48130,7 @@ paths:
description: Instance Group ID, UUID assigned to this instance.
required: true
type: string
+ example: __ID__
/network/instance-groups/instance-group/{id}:
get:
tags:
@@ -37604,7 +48145,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/instance-group"
+ $ref: "#/getDefinitions/instance-group"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -37613,6 +48154,7 @@ paths:
description: Instance Group ID, UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: description
in: query
description: Descriptive text to help identify the usage of this instance-group
@@ -37632,7 +48174,10 @@ paths:
tags:
- Network
summary: create or update an existing instance-group
- description: create or update an existing instance-group
+ description: |
+ Create or update an existing instance-group.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkInstanceGroupsInstanceGroup
consumes:
- application/json
@@ -37649,12 +48194,52 @@ paths:
description: Instance Group ID, UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: body
in: body
- description: instance-group object that needs to be created or updated
+ description: instance-group object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkInstanceGroupsInstanceGroup.json)
required: true
schema:
$ref: "#/definitions/instance-group"
+ patch:
+ tags:
+ - Network
+ summary: update an existing instance-group
+ description: |
+ Update an existing instance-group
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkInstanceGroupsInstanceGroup
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: id
+ in: path
+ description: Instance Group ID, UUID assigned to this instance.
+ required: true
+ type: string
+ example: __ID__
+ - name: body
+ in: body
+ description: instance-group object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/instance-group"
delete:
tags:
- Network
@@ -37676,6 +48261,7 @@ paths:
description: Instance Group ID, UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -37695,7 +48281,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/instance-groups"
+ $ref: "#/getDefinitions/instance-groups"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/zones/zone/{zone-id}/relationship-list/relationship:
@@ -37719,9 +48305,10 @@ paths:
description: Code assigned by AIC to the zone
required: true
type: string
+ example: __ZONE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkZonesZone.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -37746,6 +48333,7 @@ paths:
description: Code assigned by AIC to the zone
required: true
type: string
+ example: __ZONE-ID__
/network/zones/zone/{zone-id}:
get:
tags:
@@ -37760,7 +48348,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/zone"
+ $ref: "#/getDefinitions/zone"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -37769,6 +48357,7 @@ paths:
description: Code assigned by AIC to the zone
required: true
type: string
+ example: __ZONE-ID__
- name: design-type
in: query
description: Design of zone [Medium/Large?]
@@ -37783,7 +48372,10 @@ paths:
tags:
- Network
summary: create or update an existing zone
- description: create or update an existing zone
+ description: |
+ Create or update an existing zone.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkZonesZone
consumes:
- application/json
@@ -37800,12 +48392,52 @@ paths:
description: Code assigned by AIC to the zone
required: true
type: string
+ example: __ZONE-ID__
- name: body
in: body
- description: zone object that needs to be created or updated
+ description: zone object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkZonesZone.json)
required: true
schema:
$ref: "#/definitions/zone"
+ patch:
+ tags:
+ - Network
+ summary: update an existing zone
+ description: |
+ Update an existing zone
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkZonesZone
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: zone-id
+ in: path
+ description: Code assigned by AIC to the zone
+ required: true
+ type: string
+ example: __ZONE-ID__
+ - name: body
+ in: body
+ description: zone object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/zone"
delete:
tags:
- Network
@@ -37827,6 +48459,7 @@ paths:
description: Code assigned by AIC to the zone
required: true
type: string
+ example: __ZONE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -37846,24 +48479,30 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/zones"
+ $ref: "#/getDefinitions/zones"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
definitions:
- search:
+ aai-internal:
properties:
- edge-tag-query-result:
- type: object
- $ref: "#/definitions/edge-tag-query-result"
- edge-tag-query-request:
- type: object
- $ref: "#/definitions/edge-tag-query-request"
- search-results:
- type: object
- $ref: "#/definitions/search-results"
- sdn-zone-response:
- type: object
- $ref: "#/definitions/sdn-zone-response"
+ property-name:
+ type: string
+ property-value:
+ type: string
+ action:
+ properties:
+ action-type:
+ type: string
+ action-data:
+ type: array
+ items:
+ $ref: "#/definitions/action-data"
+ action-data:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
actions:
description: |
APIs that are more action related than REST (e.g., notify, update).
@@ -37874,103 +48513,301 @@ definitions:
notify:
type: object
$ref: "#/definitions/notify"
- relationship-data:
+ allotted-resource:
+ description: |
+ Represents a slice or partial piece of a resource that gets separately allotted
+ ###### Related Nodes
+ - TO generic-vnf( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY)
+ - TO instance-group( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO l3-network( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY)
+ - TO network-policy( allotted-resource org.onap.relationships.inventory.Uses network-policy, ONE2ONE)
+ - TO vlan( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY)
+ - TO service-instance( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM tunnel-xconnect( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY)
+ - ALLOTTED-RESOURCE is DELETED when these are DELETED TUNNEL-XCONNECT
required:
- - relationship-key
- - relationship-value
+ - id
properties:
- relationship-key:
+ id:
type: string
- description: A keyword provided by A&AI to indicate an attribute.
- relationship-value:
+ description: Allotted Resource id UUID assigned to this instance.
+ description:
type: string
- description: Value of the attribute.
- related-to-property:
- properties:
- property-key:
+ description: The descriptive information assigned to this allotted resource instance
+ selflink:
type: string
- description: Key part of a key/value pair
- property-value:
+ description: Link back to more information in the controller
+ model-invariant-id:
type: string
- description: Value part of a key/value pair
- relationship:
- properties:
- related-to:
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
type: string
- description: A keyword provided by A&AI to indicate type of node.
- related-link:
+ description: the ASDC model version for this resource or service model.
+ persona-model-version:
type: string
- description: URL to the object in A&AI.
- relationship-data:
+ description: the ASDC model version for this resource or service model.
+ resource-version:
+ type: string
+ description: Concurrency value
+ orchestration-status:
+ type: string
+ description: Orchestration status
+ operational-status:
+ type: string
+ description: Indicator for whether the resource is considered operational
+ type:
+ type: string
+ description: Generic description of the type of allotted resource.
+ role:
+ type: string
+ description: role in the network that this resource will be providing.
+ tunnel-xconnects:
type: array
- items:
- $ref: "#/definitions/relationship-data"
- related-to-property:
+ items:
+ $ref: "#/definitions/tunnel-xconnect"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ allotted-resources:
+ description: |
+ This object is used to store slices of services being offered
+ properties:
+ allotted-resource:
type: array
items:
- $ref: "#/definitions/related-to-property"
- relationship-list:
+ $ref: "#/definitions/allotted-resource"
+ availability-zone:
+ description: |
+ Availability zone, a collection of compute hosts/pservers
+ ###### Related Nodes
+ - TO complex( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO service-capability( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - TO cloud-region( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM ctag-pool( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM dvs-switch( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - FROM pserver( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)
+ - FROM vce( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - AVAILABILITY-ZONE cannot be deleted if linked to CTAG-POOL,DVS-SWITCH,GENERIC-VNF,PSERVER,VCE
+ required:
+ - availability-zone-name
+ - hypervisor-type
properties:
- relationship:
+ availability-zone-name:
+ type: string
+ description: Name of the availability zone. Unique across a cloud region
+ hypervisor-type:
+ type: string
+ description: Type of hypervisor. Source of truth should define valid values.
+ operational-status:
+ type: string
+ description: State that indicates whether the availability zone should be used, etc. Source of truth should define valid values.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ availability-zones:
+ description: |
+ Collection of availability zones
+ properties:
+ availability-zone:
type: array
items:
+ $ref: "#/definitions/availability-zone"
+ az-and-dvs-switches:
+ properties:
+ dvs-switches:
+ type: object
+ $ref: "#/definitions/dvs-switches"
+ availability-zone:
+ type: object
+ $ref: "#/definitions/availability-zone"
+ business:
+ description: |
+ Namespace for business related constructs
+ properties:
+ connectors:
+ type: array
+ items:
+ $ref: "#/definitions/connector"
+ customers:
+ type: array
+ items:
+ $ref: "#/definitions/customer"
+ class-of-service:
+ description: |
+ ###### Related Nodes
+ - TO site-pair( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)
+ required:
+ - cos
+ properties:
+ cos:
+ type: string
+ description: unique identifier of probe
+ probe-id:
+ type: string
+ description: identifier of probe
+ probe-type:
+ type: string
+ description: type of probe
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
$ref: "#/definitions/relationship"
- ctag-pool:
+ classes-of-service:
description: |
- A collection of C tags (vlan tags) grouped for a specific purpose.
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ class-of-service of probe
+ properties:
+ class-of-service:
+ type: array
+ items:
+ $ref: "#/definitions/class-of-service"
+ cloud-infrastructure:
+ description: |
+ Namespace for cloud infrastructure.
+ properties:
+ complexes:
+ type: array
+ items:
+ $ref: "#/definitions/complex"
+ cloud-regions:
+ type: array
+ items:
+ $ref: "#/definitions/cloud-region"
+ network-profiles:
+ type: array
+ items:
+ $ref: "#/definitions/network-profile"
+ pservers:
+ type: array
+ items:
+ $ref: "#/definitions/pserver"
+ virtual-data-centers:
+ type: array
+ items:
+ $ref: "#/definitions/virtual-data-center"
+ cloud-region:
+ description: |
+ cloud-region designates an installation of a cloud cluster or region or instantiation
###### Related Nodes
- - TO availability-zone (Many2Many)
- - FROM complex (is composed of ctag-pool)
- - FROM vpls-pe
+ - TO complex( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO l3-network( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO zone( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM dvs-switch( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM flavor( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM group-assignment( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM image( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM snapshot( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM volume-group( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn cloud-region, MANY2MANY)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)
+ - CLOUD-REGION cannot be deleted if linked to DVS-SWITCH,FLAVOR,GROUP-ASSIGNMENT,IMAGE,OAM-NETWORK,SNAPSHOT,TENANT,VOLUME-GROUP
+ - CLOUD-REGION is DELETED when these are DELETED AVAILABILITY-ZONE
required:
- - target-pe
- - availability-zone-name
- - ctag-pool-purpose
+ - cloud-owner
+ - cloud-region-id
properties:
- target-pe:
+ cloud-owner:
type: string
- description: The Target provider edge router
- availability-zone-name:
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ cloud-region-id:
type: string
- description: Name of the availability zone
- ctag-pool-purpose:
+ description: Identifier used by the vendor for the region. Second part of composite key
+ cloud-type:
type: string
- description: Describes what the intended purpose of this pool is.
- ctag-values:
+ description: Type of the cloud (e.g., openstack)
+ owner-defined-type:
type: string
- description: Comma separated list of ctags
+ description: Cloud-owner defined type indicator (e.g., dcp, lcp)
+ cloud-region-version:
+ type: string
+ description: Software version employed at the site. NOTE - THIS FIELD IS NOT KEPT UP TO DATE.
+ identity-url:
+ type: string
+ description: URL of the keystone identity service
+ cloud-zone:
+ type: string
+ description: Zone where the cloud is homed. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
+ complex-name:
+ type: string
+ description: complex name for cloud-region instance. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ volume-groups:
+ type: array
+ items:
+ $ref: "#/definitions/volume-group"
+ tenants:
+ type: array
+ items:
+ $ref: "#/definitions/tenant"
+ flavors:
+ type: array
+ items:
+ $ref: "#/definitions/flavor"
+ group-assignments:
+ type: array
+ items:
+ $ref: "#/definitions/group-assignment"
+ snapshots:
+ type: array
+ items:
+ $ref: "#/definitions/snapshot"
+ images:
+ type: array
+ items:
+ $ref: "#/definitions/image"
+ dvs-switches:
+ type: array
+ items:
+ $ref: "#/definitions/dvs-switch"
+ oam-networks:
+ type: array
+ items:
+ $ref: "#/definitions/oam-network"
+ availability-zones:
+ type: array
+ items:
+ $ref: "#/definitions/availability-zone"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- ctag-pools:
+ cloud-regions:
properties:
- ctag-pool:
+ cloud-region:
type: array
items:
- $ref: "#/definitions/ctag-pool"
+ $ref: "#/definitions/cloud-region"
complex:
description: |
Collection of physical locations that can house cloud-regions.
- ###### Default Delete Scope
- ERROR_4_IN_EDGES_OR_CASCADE
- ###### Related Nodes
- - TO ctag-pool (comprises complex, Many2Many)
- - TO l3-network (Many2Many)
- - FROM availability-zone
- - FROM cloud-region
- - FROM oam-network
- - FROM pserver
- - FROM pnf
- - FROM vce
- - FROM vpls-pe
- - FROM volume-group
- - FROM zone
+ ###### Related Nodes
+ - TO l3-network( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM ctag-pool( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)
+ - FROM pnf( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM vce( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)
+ - FROM volume-group( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM vpls-pe( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM zone( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - COMPLEX cannot be deleted if linked to AVAILABILITY-ZONE,CLOUD-REGION,OAM-NETWORK,PNF,PSERVER,VCE,VOLUME-GROUP,VPLS-PE,ZONE
+ - COMPLEX is DELETED when these are DELETED CTAG-POOL
required:
- physical-location-id
- physical-location-type
@@ -38036,43 +48873,59 @@ definitions:
type: array
items:
$ref: "#/definitions/complex"
- volume-group:
+ configuration:
description: |
- Persistent block-level storage.
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Port Mirror Configuration.
###### Related Nodes
- - TO complex (Many2Many)
- - TO tenant (Many2Many)
- - FROM cloud-region (is composed of volume-group)
- - FROM vf-module
- - FROM generic-vnf
+ - TO allotted-resource( configuration org.onap.relationships.inventory.Uses allotted-resource, ONE2ONE)
+ - TO logical-link( configuration org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo configuration, MANY2ONE)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses configuration, ONE2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses configuration, ONE2MANY)
+ - CONFIGURATION is DELETED when these are DELETED METADATUM
+ - CONFIGURATION deletion means associated objects of these types are also DELETED:ALLOTTED-RESOURCE,LOGICAL-LINK
required:
- - volume-group-id
- - volume-group-name
- - vnf-type
+ - configuration-id
+ - configuration-type
+ - configuration-sub-type
+ - orchestration-status
+ - operational-status
+ - configuration-selflink
+ - model-customization-id
properties:
- volume-group-id:
+ configuration-id:
type: string
- description: Unique ID of volume-group.
- volume-group-name:
+ description: UUID assigned to configuration.
+ management-option:
type: string
- description: Name of the volume group.
- heat-stack-id:
+ description: Indicates the entity that will manage this feature. Could be an organization or the name of the application as well.
+ configuration-name:
type: string
- description: Heat stack id corresponding to this volume-group
- vnf-type:
+ description: Name of the configuration.
+ configuration-type:
type: string
- description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ description: port-mirroring-configuration.
+ configuration-sub-type:
+ type: string
+ description: vprobe, pprobe.
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
orchestration-status:
type: string
- description: Orchestration status of this volume-group
- model-customization-id:
+ description: Orchestration status of the configuration.
+ operational-status:
type: string
- description: captures the id of all the configuration used to customize the resource for the service.
- vf-module-model-customization-id:
+ description: Indicator for whether the resource is considered operational.
+ configuration-selflink:
type: string
- description: helps relate the volume group to the vf-module whose components will require the volume group
+ description: URL to endpoint where AAI can get more details from SDN-GC.
+ model-customization-id:
+ type: string
+ description: id of the configuration used to customize the resource
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
@@ -38080,474 +48933,641 @@ definitions:
type: array
items:
$ref: "#/definitions/relationship"
- volume-groups:
+ metadata:
+ type: array
+ items:
+ $ref: "#/definitions/metadatum"
+ configurations:
description: |
- Collection of persistent block-level storage.
+ Collection of configurations
properties:
- volume-group:
+ configuration:
type: array
items:
- $ref: "#/definitions/volume-group"
- volume:
+ $ref: "#/definitions/configuration"
+ connector:
description: |
- Ephemeral Block storage volume.
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Collection of resource instances used to connect a variety of disparate inventory widgets
###### Related Nodes
- - FROM vserver (is composed of volume)
+ - TO virtual-data-center( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)
+ - CONNECTOR is DELETED when these are DELETED METADATUM
required:
- - volume-id
- - volume-selflink
+ - resource-instance-id
properties:
- volume-id:
- type: string
- description: Unique ID of block storage volume relative to the vserver.
- volume-selflink:
+ resource-instance-id:
type: string
- description: URL to endpoint where AAI can get more details
+ description: Unique id of resource instance.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- volumes:
+ metadata:
+ type: array
+ items:
+ $ref: "#/definitions/metadatum"
+ connectors:
description: |
- Collection of ephemeral Block storage volumes.
+ Collection of resource instances used to connect a variety of disparate inventory widgets
properties:
- volume:
+ connector:
type: array
items:
- $ref: "#/definitions/volume"
- l3-interface-ipv4-address-list:
+ $ref: "#/definitions/connector"
+ constrained-element-set:
description: |
- IPv4 Address Range
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ This is how we would capture constraints defining allowed sets of elements.
###### Related Nodes
- - TO instance-group (Many2Many)
- - TO l3-network (Many2Many)
- - TO subnet (Many2Many)
- - FROM l-interface (is composed of l3-interface-ipv4-address-list)
- - FROM vlan (is composed of l3-interface-ipv4-address-list)
+ - TO model-constraint( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)
+ - TO model-element( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM element-choice-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)
+ - CONSTRAINED-ELEMENT-SET is DELETED when these are DELETED ELEMENT-CHOICE-SET
required:
- - l3-interface-ipv4-address
+ - constrained-element-set-uuid
+ - constraint-type
+ - check-type
properties:
- l3-interface-ipv4-address:
+ constrained-element-set-uuid:
type: string
- description: IP address
- l3-interface-ipv4-prefix-length:
- type: integer
- format: int64
- description: Prefix length, 32 for single address
- vlan-id-inner:
- type: integer
- format: int64
- description: Inner VLAN tag
- vlan-id-outer:
- type: integer
- format: int64
- description: Outer VLAN tag
- is-floating:
- type: boolean
- description: Indicator of fixed or floating address
- resource-version:
+ constraint-type:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- neutron-network-id:
+ check-type:
type: string
- description: Neutron network id of the interface that address belongs to
- neutron-subnet-id:
+ resource-version:
type: string
- description: Neutron id of subnet that address belongs to
+ element-choice-sets:
+ type: array
+ items:
+ $ref: "#/definitions/element-choice-set"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- l3-interface-ipv6-address-list:
+ constrained-element-sets:
+ properties:
+ constrained-element-set:
+ type: array
+ items:
+ $ref: "#/definitions/constrained-element-set"
+ ctag-assignment:
description: |
- IPv6 Address Range
- ###### Default Delete Scope
- THIS_NODE_ONLY
###### Related Nodes
- - TO instance-group (Many2Many)
- - TO l3-network (Many2Many)
- - TO subnet (Many2Many)
- - FROM l-interface (is composed of l3-interface-ipv6-address-list)
- - FROM vlan (is composed of l3-interface-ipv6-address-list)
+ - TO l3-network( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses ctag-assignment, ONE2MANY)
required:
- - l3-interface-ipv6-address
+ - vlan-id-inner
properties:
- l3-interface-ipv6-address:
- type: string
- description: IP address
- l3-interface-ipv6-prefix-length:
- type: integer
- format: int64
- description: Prefix length, 128 for single address
vlan-id-inner:
type: integer
format: int64
- description: Inner VLAN tag
- vlan-id-outer:
- type: integer
- format: int64
- description: Outer VLAN tag
- is-floating:
- type: boolean
- description: Indicator of fixed or floating address
+ description: id.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- neutron-network-id:
- type: string
- description: Neutron network id of the interface that address belongs to
- neutron-subnet-id:
- type: string
- description: Neutron id of subnet that address belongs to
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- vlan:
+ ctag-assignments:
+ properties:
+ ctag-assignment:
+ type: array
+ items:
+ $ref: "#/definitions/ctag-assignment"
+ ctag-pool:
description: |
- Definition of vlan
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
+ A collection of C tags (vlan tags) grouped for a specific purpose.
###### Related Nodes
- - TO l3-interface-ipv4-address-list (comprises vlan, Many2Many)
- - TO l3-interface-ipv6-address-list (comprises vlan, Many2Many)
- - TO multicast-configuration (Many2Many)
- - TO logical-link (Many2Many)
- - FROM l-interface (is composed of vlan)
- - FROM service-instance
- - FROM allotted-resource
+ - TO complex( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)
+ - TO availability-zone( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM vpls-pe( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)
required:
- - vlan-interface
- - in-maint
+ - target-pe
+ - availability-zone-name
+ - ctag-pool-purpose
properties:
- vlan-interface:
+ target-pe:
type: string
- description: String that identifies the interface
- vlan-id-inner:
- type: integer
- format: int64
- description: Inner VLAN tag
- vlan-id-outer:
- type: integer
- format: int64
- description: Outer VLAN tag
- resource-version:
+ description: The Target provider edge router
+ availability-zone-name:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- speed-value:
+ description: Name of the availability zone
+ ctag-pool-purpose:
type: string
- description: Captures the numeric part of the speed
- speed-units:
+ description: Describes what the intended purpose of this pool is.
+ ctag-values:
type: string
- description: Captures the units corresponding to the speed
- vlan-description:
+ description: Comma separated list of ctags
+ resource-version:
type: string
- description: Used to describe (the service associated with) the vlan
- backdoor-connection:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ ctag-pools:
+ properties:
+ ctag-pool:
+ type: array
+ items:
+ $ref: "#/definitions/ctag-pool"
+ customer:
+ description: |
+ customer identifiers to provide linkage back to BSS information.
+ ###### Related Nodes
+ - FROM service-subscription( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)
+ - CUSTOMER is DELETED when these are DELETED SERVICE-SUBSCRIPTION
+ required:
+ - global-customer-id
+ - subscriber-name
+ - subscriber-type
+ properties:
+ global-customer-id:
type: string
- description: Whether customer is going to use this VLAN for backdoor connection to another customer premise device.
- vpn-id:
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ subscriber-name:
type: string
- description: This indicates the customers VPN ID associated with this vlan
- orchestration-status:
+ description: Subscriber name, an alternate way to retrieve a customer.
+ subscriber-type:
type: string
- description: Status of a vnf's vlan interface, on which the customer circuit resides, mastered by SDN-C.
- in-maint:
- type: boolean
+ description: Subscriber type, a way to provide VID with only the INFRA customers.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ service-subscriptions:
+ type: array
+ items:
+ $ref: "#/definitions/service-subscription"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- l3-interface-ipv4-address-list:
+ customers:
+ description: |
+ Collection of customer identifiers to provide linkage back to BSS information.
+ properties:
+ customer:
type: array
items:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
- l3-interface-ipv6-address-list:
+ $ref: "#/definitions/customer"
+ cvlan-tag-entry:
+ required:
+ - cvlan-tag
+ properties:
+ cvlan-tag:
+ type: integer
+ format: int64
+ description: See mis-na-virtualization-platform.yang
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
- items:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
- vlans:
+ items:
+ $ref: "#/definitions/relationship"
+ cvlan-tags:
properties:
- vlan:
+ cvlan-tag-entry:
type: array
items:
- $ref: "#/definitions/vlan"
- sriov-vf:
+ $ref: "#/definitions/cvlan-tag-entry"
+ dvs-switch:
description: |
- SR-IOV Virtual Function (not to be confused with virtual network function)
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Digital virtual switch metadata, used by SDN-C to configure VCEs. A&AI needs to receive this data from the PO deployment team and administer it using the provisioningTool.sh into A&AI.
###### Related Nodes
- - FROM l-interface (is composed of sriov-vf)
+ - TO cloud-region( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO availability-zone( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
required:
- - pci-id
+ - switch-name
+ - vcenter-url
properties:
- pci-id:
- type: string
- description: PCI ID used to identify the sriov-vf
- vf-vlan-filter:
- type: string
- description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM.
- vf-mac-filter:
- type: string
- description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM.
- vf-vlan-strip:
- type: boolean
- description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM.
- vf-vlan-anti-spoof-check:
- type: boolean
- description: This option ensures anti VLAN spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
- vf-mac-anti-spoof-check:
- type: boolean
- description: This option ensures anti MAC spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
- vf-mirrors:
+ switch-name:
type: string
- description: This option defines the set of Mirror objects which essentially mirrors the traffic from source to set of collector VNF Ports.
- vf-broadcast-allow:
- type: boolean
- description: This option, if set to true, sets the VF in promiscuous mode and allows all broadcast traffic to reach the VM
- vf-unknown-multicast-allow:
- type: boolean
- description: This option, if set to true, sets the VF in promiscuous mode and allows unknown multicast traffic to reach the VM
- vf-unknown-unicast-allow:
- type: boolean
- description: This option, if set to true, sets the VF in promiscuous mode and allows unknown unicast traffic to reach the VM
- vf-insert-stag:
- type: boolean
- description: This option, if set to true, instructs to insert outer tag after traffic comes out of VM.
- vf-link-status:
+ description: DVS switch name
+ vcenter-url:
type: string
- description: This option is used to set the link status. Valid values as of 1607 are on, off, and auto.
+ description: URL used to reach the vcenter
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- neutron-network-id:
- type: string
- description: Neutron network id of the interface
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- sriov-vfs:
+ dvs-switches:
description: |
- Collection of SR-IOV Virtual Functions.
+ Collection of digital virtual switch metadata used for vmWare VCEs and GenericVnfs.
properties:
- sriov-vf:
+ dvs-switch:
type: array
items:
- $ref: "#/definitions/sriov-vf"
- l-interface:
+ $ref: "#/definitions/dvs-switch"
+ edge-prop-names:
description: |
- Logical interfaces, e.g., a vnic.
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
- ###### Related Nodes
- - TO instance-group (Many2Many)
- - TO l3-interface-ipv4-address-list (comprises l-interface, Many2Many)
- - TO l3-interface-ipv6-address-list (comprises l-interface, Many2Many)
- - TO l-interface (comprises l-interface, One2Many)
- - TO logical-link (Many2Many)
- - TO vlan (comprises l-interface, Many2Many)
- - TO sriov-vf (comprises l-interface, One2One)
- - FROM generic-vnf (is composed of l-interface)
- - FROM lag-interface (is composed of l-interface)
- - FROM newvce (is composed of l-interface)
- - FROM p-interface (is composed of l-interface)
- - FROM vserver (is composed of l-interface)
- - FROM l-interface (is composed of l-interface)
- required:
- - interface-name
- - is-port-mirrored
- - in-maint
+ Internal map to define the properties of an edge and interpret the map EdgeRules
properties:
- interface-name:
+ edgeLabel:
type: string
- description: Name given to the interface
- interface-role:
+ direction:
type: string
- description: E.g., CUSTOMER, UPLINK, etc.
- v6-wan-link-ip:
+ multiplicityRule:
type: string
- description: Questionably placed - v6 ip addr of this interface (is in vr-lan-interface from Mary B.
- selflink:
+ isParent:
+ type: boolean
+ usesResource:
+ type: boolean
+ hasDelTarget:
+ type: boolean
+ SVC-INFRA:
+ type: boolean
+ SVC-INFRA-REV:
+ type: boolean
+ edge-tag-query-request:
+ properties:
+ edge-tag:
type: string
- description: URL to endpoint where AAI can get more details
- interface-id:
+ result-detail:
type: string
- description: ID of interface
- macaddr:
+ start-node-type:
type: string
- description: MAC address for the interface
- network-name:
+ start-node-filter:
+ type: array
+ items:
+ $ref: "#/definitions/start-node-filter"
+ include-node-filter:
+ type: array
+ items:
+ $ref: "#/definitions/include-node-filter"
+ secondary-filter:
+ type: array
+ items:
+ $ref: "#/definitions/secondary-filter"
+ edge-tag-query-result:
+ properties:
+ tagged-inventory-item-list:
+ type: array
+ items:
+ $ref: "#/definitions/tagged-inventory-item-list"
+ element-choice-set:
+ description: |
+ This is how we would capture constraints defining allowed sets of elements.
+ ###### Related Nodes
+ - TO constrained-element-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)
+ - ELEMENT-CHOICE-SET is DELETED when these are DELETED MODEL-ELEMENT
+ required:
+ - element-choice-set-uuid
+ - element-choice-set-name
+ properties:
+ element-choice-set-uuid:
type: string
- description: Name of the network
- management-option:
+ element-choice-set-name:
type: string
- description: Whether A&AI should be managing this interface of not. Could have value like CUSTOMER
- interface-description:
+ cardinality:
type: string
- description: Human friendly text regarding this interface.
- is-port-mirrored:
- type: boolean
resource-version:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- in-maint:
- type: boolean
- vlans:
+ model-elements:
type: array
items:
- $ref: "#/definitions/vlan"
- sriov-vfs:
+ $ref: "#/definitions/model-element"
+ relationship-list:
type: array
items:
- $ref: "#/definitions/sriov-vf"
- l-interfaces:
+ $ref: "#/definitions/relationship"
+ element-choice-sets:
+ properties:
+ element-choice-set:
type: array
- items:
- $ref: "#/definitions/l-interface"
+ items:
+ $ref: "#/definitions/element-choice-set"
+ entitlement:
+ description: |
+ Metadata for entitlement group.
+ ###### Related Nodes
+ - TO generic-vnf( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vce( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ required:
+ - group-uuid
+ - resource-uuid
+ properties:
+ group-uuid:
+ type: string
+ description: Unique ID for the entitlement group the resource comes from, should be uuid.
+ resource-uuid:
+ type: string
+ description: Unique ID of an entitlement resource.
+ resource-version:
+ type: string
+ description: Concurrency value
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- l3-interface-ipv4-address-list:
- type: array
- items:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
- l3-interface-ipv6-address-list:
+ entitlements:
+ description: |
+ Entitlements, keyed by group-uuid and resource-uuid, related to license management
+ properties:
+ entitlement:
type: array
items:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
- l-interfaces:
+ $ref: "#/definitions/entitlement"
+ esr-ems:
description: |
- Collection of logical interfaces.
+ Persist EMS address information used by EMS driver.
+ ###### Related Nodes
+ - TO esr-system-info (CHILD of esr-ems, esr-ems has esr-system-info, One2Many)
+ - ESR-EMS deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
+ required:
+ - ems-id
properties:
- l-interface:
+ ems-id:
+ type: string
+ description: Unique ID of EMS.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ esr-system-info-list:
+ type: object
+ $ref: "#/definitions/esr-system-info-list"
+ relationship-list:
+ type: object
+ $ref: "#/definitions/relationship-list"
+ esr-ems-list:
+ properties:
+ esr-ems:
type: array
items:
- $ref: "#/definitions/l-interface"
- vserver:
+ $ref: "#/definitions/esr-ems"
+ esr-system-info:
description: |
- Virtual Servers, aka virtual machine or VM.
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
- ###### Related Nodes
- - TO flavor (Many2One)
- - TO image (Many2One)
- - TO l-interface (comprises vserver, Many2Many)
- - TO pserver (Many2One)
- - TO volume (comprises vserver, Many2Many)
- - TO vnfc (Many2Many)
- - TO snapshot (One2One)
- - TO vf-module (Many2One)
- - FROM generic-vnf
- - FROM tenant (is composed of vserver)
- - FROM vce
+ Persist common address information of external systems.
+ ###### Related Nodes
+ - FROM esr-ems (PARENT of esr-system-info, esr-ems has esr-system-info)
+ - FROM esr-vnfm (PARENT of esr-system-info, esr-vnfm has esr-system-info)
+ - FROM esr-thirdparty-sdnc (PARENT of esr-system-info, esr-thirdparty-sdnc has esr-system-info)
+ - FROM cloud-region (PARENT of esr-system-info, cloud-region has esr-system-info)
required:
- - vserver-id
- - vserver-name
- - vserver-selflink
- - in-maint
- - is-closed-loop-disabled
+ - esr-system-info-id
+ - user-name
+ - password
+ - system-type
properties:
- vserver-id:
+ esr-system-info-id:
type: string
- description: Unique identifier for this vserver relative to its tenant
- vserver-name:
+ description: Unique ID of esr system info.
+ system-name:
type: string
- description: Name of vserver
- vserver-name2:
+ description: name of external system.
+ type:
type: string
- description: Alternative name of vserver
- prov-status:
+ description: type of external systems.
+ vendor:
type: string
- description: Trigger for operational monitoring of this resource by Service Assurance systems.
- vserver-selflink:
+ description: vendor of external systems.
+ version:
type: string
- description: URL to endpoint where AAI can get more details
- in-maint:
+ description: version of external systems.
+ service-url:
+ type: string
+ description: url used to access external systems.
+ user-name:
+ type: string
+ description: username used to access external systems.
+ password:
+ type: string
+ description: password used to access external systems.
+ system-type:
+ type: string
+ description: it could be vim/vnfm/thirdparty-sdnc/ems-resource/ems-performance/ems-alarm.
+ protocol:
+ type: string
+ description: protocol of third party SDNC, for example netconf/snmp.
+ ssl-cacert:
+ type: string
+ description: ca file content if enabled ssl on auth-url.
+ ssl-insecure:
type: boolean
- is-closed-loop-disabled:
+ description: Whether to verify VIM's certificate.
+ ip-address:
+ type: string
+ description: service IP of ftp server.
+ port:
+ type: string
+ description: service port of ftp server.
+ cloud-domain:
+ type: string
+ description: domain info for authentication.
+ default-tenant:
+ type: string
+ description: default tenant of VIM.
+ passive:
type: boolean
+ description: ftp passive mode or not.
+ remote-path:
+ type: string
+ description: resource or performance data file path.
+ system-status:
+ type: string
+ description: the status of external system.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- volumes:
- type: array
- items:
- $ref: "#/definitions/volume"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- l-interfaces:
+ esr-system-info-list:
+ description: |
+ Collection of persistent block-level external system auth info.
+ properties:
+ esr-system-info:
type: array
- items:
- $ref: "#/definitions/l-interface"
- vservers:
+ items:
+ $ref: "#/definitions/esr-system-info"
+ esr-thirdparty-sdnc:
description: |
- Collection of virtual Servers, aka virtual machines or VMs.
+ Persist SDNC address information used by ONAP SDNC.
+ ###### Related Nodes
+ - TO esr-system-info (CHILD of esr-thirdparty-sdnc, esr-thirdparty-sdnc has esr-system-info, One2One)
+ - TO pnf( esr-thirdparty-sdnc has pnf, One2Many)
+ - ESR-THIRDPARTY-SDNC deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
+ required:
+ - thirdparty-sdnc-id
properties:
- vserver:
+ thirdparty-sdnc-id:
+ type: string
+ description: Unique ID of SDNC.
+ location:
+ type: string
+ description: used for DC type to indicate the location of SDNC, such as Core or Edge.
+ product-name:
+ type: string
+ description: password used to access SDNC server.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ esr-system-info-list:
+ type: object
+ $ref: "#/definitions/esr-system-info-list"
+ relationship-list:
+ type: object
+ $ref: "#/definitions/relationship-list"
+ esr-thirdparty-sdnc-list:
+ properties:
+ esr-thirdparty-sdnc:
type: array
items:
- $ref: "#/definitions/vserver"
- tenant:
+ $ref: "#/definitions/esr-thirdparty-sdnc"
+ esr-vnfm:
description: |
- Openstack tenant
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Persist VNFM address information used by VF-C.
###### Related Nodes
- - TO l3-network (Many2Many)
- - TO service-subscription (Many2Many)
- - TO vserver (comprises tenant, One2Many)
- - FROM cloud-region (is composed of tenant)
- - FROM group-assignment
- - FROM volume-group
+ - TO esr-system-info (CHILD of esr-vnfm, esr-vnfm has esr-system-info, One2One)
+ - ESR-VNFM deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
required:
- - tenant-id
- - tenant-name
+ - vnfm-id
properties:
- tenant-id:
+ vnfm-id:
type: string
- description: Unique id relative to the cloud-region.
- tenant-name:
+ description: Unique ID of VNFM.
+ vim-id:
type: string
- description: Readable name of tenant
+ description: indecate the VIM to deploy VNF.
+ certificate-url:
+ type: string
+ description: certificate url of VNFM.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- vservers:
+ esr-system-info-list:
+ type: object
+ $ref: "#/definitions/esr-system-info-list"
+ relationship-list:
+ type: object
+ $ref: "#/definitions/relationship-list"
+ esr-vnfm-list:
+ properties:
+ esr-vnfm:
type: array
- items:
- $ref: "#/definitions/vserver"
+ items:
+ $ref: "#/definitions/esr-vnfm"
+ evc:
+ description: |
+ evc object is an optional child object of the Configuration object.
+ ###### Related Nodes
+ - TO configuration( evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)
+ required:
+ - evc-id
+ properties:
+ evc-id:
+ type: string
+ description: Unique/key field for the evc object
+ forwarding-path-topology:
+ type: string
+ description: Point-to-Point, Multi-Point
+ cir-value:
+ type: string
+ description: Commited Information Rate
+ cir-units:
+ type: string
+ description: CIR units
+ connection-diversity-group-id:
+ type: string
+ description: Diversity Group ID
+ service-hours:
+ type: string
+ description: formerly Performance Group
+ esp-evc-circuit-id:
+ type: string
+ description: EVC Circuit ID of ESP EVC
+ esp-evc-cir-value:
+ type: string
+ description: Committed Information Rate (For ESP)
+ esp-evc-cir-units:
+ type: string
+ description: CIR units (For ESP)
+ esp-itu-code:
+ type: string
+ description: Identifies ESP
+ collector-pop-clli:
+ type: string
+ description: Collector POP CLLI (from the hostname of the access pnf)
+ inter-connect-type-ingress:
+ type: string
+ description: Interconnect type on ingress side of EVC.
+ tagmode-access-ingress:
+ type: string
+ description: tagode for collector side of EVC
+ tagmode-access-egress:
+ type: string
+ description: tagMode for network side of EVC
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- tenants:
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ evcs:
+ properties:
+ evc:
+ type: array
+ items:
+ $ref: "#/definitions/evc"
+ external-system:
description: |
- Collection of openstack tenants.
+ Namespace for external system.
properties:
- tenant:
+ esr-ems-list:
+ type: object
+ $ref: "#/definitions/esr-ems-list"
+ esr-vnfm-list:
+ type: object
+ $ref: "#/definitions/esr-vnfm-list"
+ esr-thirdparty-sdnc-list:
+ type: object
+ $ref: "#/definitions/esr-thirdparty-sdnc-list"
+ extra-properties:
+ description: |
+ Extra properties for inventory item for response list
+ properties:
+ extra-property:
type: array
items:
- $ref: "#/definitions/tenant"
+ $ref: "#/definitions/extra-property"
+ extra-property:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
flavor:
description: |
Openstack flavor.
- ###### Default Delete Scope
- ERROR_IF_ANY_IN_EDGES
###### Related Nodes
- - FROM cloud-region (is composed of flavor)
- - FROM vserver
+ - TO cloud-region( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)
+ - FLAVOR cannot be deleted if linked to VSERVER
required:
- flavor-id
- flavor-name
@@ -38602,143 +49622,400 @@ definitions:
type: array
items:
$ref: "#/definitions/flavor"
- group-assignment:
+ forwarder:
description: |
- Openstack group-assignment used to store exclusivity groups (EG).
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Entity describing a sequenced segment of forwarding path
###### Related Nodes
- - TO tenant (Many2Many)
- - TO pserver (One2Many)
- - FROM cloud-region (is composed of group-assignment)
+ - TO forwarding-path( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)
+ - TO l-interface( forwarder org.onap.relationships.inventory.ForwardsTo l-interface, MANY2ONE)
+ - TO configuration( forwarder org.onap.relationships.inventory.Uses configuration, ONE2ONE)
+ - TO lag-interface( forwarder org.onap.relationships.inventory.ForwardsTo lag-interface, MANY2ONE)
+ - TO p-interface( forwarder org.onap.relationships.inventory.ForwardsTo p-interface, MANY2ONE)
+ - FORWARDER deletion means associated objects of these types are also DELETED:CONFIGURATION
required:
- - group-id
- - group-type
- - group-name
+ - sequence
properties:
- group-id:
+ sequence:
+ type: integer
+ format: int32
+ description: Unique ID of this segmentation
+ forwarder-role:
type: string
- description: Group id, expected to be unique across cloud-region.
- group-type:
+ description: ingress, intermediate, egress
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ resource-version:
type: string
- description: Group type - the type of group this instance refers to
- group-name:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ forwarder-evc:
+ description: |
+ forwarder object is an optional child object of the Configuration object.
+ ###### Related Nodes
+ - TO configuration( forwarder-evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)
+ required:
+ - forwarder-evc-id
+ properties:
+ forwarder-evc-id:
type: string
- description: Group name - name assigned to the group
- group-description:
+ description: Key for forwarder-evc object
+ circuit-id:
type: string
- description: Group description - description of the group
- resource-version:
+ description: Circuit ID from customer/ESP/ingress end of EVC, or reference to beater circuit on gateway/network/egress end of EVC
+ ivlan:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ description: Internal VLAN.
+ svlan:
+ type: string
+ description: SVLAN value for ingress of egress forwarder.
+ cvlan:
+ type: string
+ description: CVLAN value for ingress of egress forwarder.
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- group-assignments:
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ forwarder-evcs:
+ properties:
+ forwarder-evc:
+ type: array
+ items:
+ $ref: "#/definitions/forwarder-evc"
+ forwarders:
+ properties:
+ forwarder:
+ type: array
+ items:
+ $ref: "#/definitions/forwarder"
+ forwarding-path:
description: |
- Collection of openstack group assignments
+ Entity that describes the sequenced forwarding path between interfaces of services or resources
+ ###### Related Nodes
+ - TO service-instance( forwarding-path org.onap.relationships.inventory.AppliesTo service-instance, MANY2ONE)
+ - TO configuration( forwarding-path org.onap.relationships.inventory.Uses configuration, ONE2ONE)
+ - FROM forwarder( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)
+ - FORWARDING-PATH is DELETED when these are DELETED FORWARDER
+ - FORWARDING-PATH deletion means associated objects of these types are also DELETED:CONFIGURATION
+ required:
+ - forwarding-path-id
+ - forwarding-path-name
properties:
- group-assignment:
+ forwarding-path-id:
+ type: string
+ description: Unique ID of this FP
+ forwarding-path-name:
+ type: string
+ description: Name of the FP
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ selflink:
+ type: string
+ description: the self link for this FP
+ forwarders:
+ type: array
+ items:
+ $ref: "#/definitions/forwarder"
+ forwarding-paths:
+ properties:
+ forwarding-path:
type: array
items:
- $ref: "#/definitions/group-assignment"
- snapshot:
+ $ref: "#/definitions/forwarding-path"
+ generic-vnf:
description: |
- Openstack snapshot
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ General purpose VNF
###### Related Nodes
- - FROM cloud-region (is composed of snapshot)
- - FROM vserver
+ - TO availability-zone( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - TO instance-group( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO ipsec-configuration( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)
+ - TO l3-network( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO license-key-resource( generic-vnf org.onap.relationships.inventory.Uses license-key-resource, MANY2MANY)
+ - TO pserver( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)
+ - TO vnf-image( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)
+ - TO volume-group( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - TO vserver( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)
+ - TO virtual-data-center( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY)
+ - FROM entitlement( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM lag-interface( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM license( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM network-profile( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)
+ - FROM site-pair-set( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)
+ - GENERIC-VNF is DELETED when these are DELETED ENTITLEMENT,VNFC,LAG-INTERFACE,LICENSE,L-INTERFACE,VF-MODULE
required:
- - snapshot-id
+ - vnf-id
+ - vnf-name
+ - vnf-type
+ - in-maint
+ - is-closed-loop-disabled
properties:
- snapshot-id:
+ vnf-id:
type: string
- description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
- snapshot-name:
+ description: Unique id of VNF. This is unique across the graph.
+ vnf-name:
type: string
- description: Snapshot name
- snapshot-architecture:
+ description: Name of VNF.
+ vnf-name2:
type: string
- description: Operating system architecture
- snapshot-os-distro:
+ description: Alternate name of VNF.
+ vnf-type:
type: string
- description: The common name of the operating system distribution in lowercase
- snapshot-os-version:
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ service-id:
type: string
- description: The operating system version as specified by the distributor.
- application:
+ description: Unique identifier of service, does not necessarily map to ASDC service models. SOON TO BE DEPRECATED
+ regional-resource-zone:
type: string
- description: The application that the image instantiates.
- application-vendor:
+ description: Regional way of organizing pservers, source of truth should define values
+ prov-status:
type: string
- description: The vendor of the application.
- application-version:
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ operational-status:
type: string
- description: The version of the application.
- snapshot-selflink:
+ description: Indicator for whether the resource is considered operational. Valid values are in-service-path and out-of-service-path.
+ license-key:
type: string
- description: URL to endpoint where AAI can get more details
- prev-snapshot-id:
+ description: OBSOLETE - do not use
+ equipment-role:
type: string
- description: This field contains the UUID of the previous snapshot (if any).
+ description: Client should send valid enumerated value
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, used by MSO.
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ management-option:
+ type: string
+ description: identifier of managed by company or customer
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by generic-vnf.
+ ipv4-loopback0-address:
+ type: string
+ description: v4 Loopback0 address
+ nm-lan-v6-address:
+ type: string
+ description: v6 Loopback address
+ management-v6-address:
+ type: string
+ description: v6 management address
+ vcpu:
+ type: integer
+ format: int64
+ description: number of vcpus ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases
+ vcpu-units:
+ type: string
+ description: units associated with vcpu, used for VNFs with no vservers/flavors, to be used only in some usecases
+ vmemory:
+ type: integer
+ format: int64
+ description: number of GB of memory ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases
+ vmemory-units:
+ type: string
+ description: units associated with vmemory, used for VNFs with no vservers/flavors, to be used only in some usecases
+ vdisk:
+ type: integer
+ format: int64
+ description: number of vdisks ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases
+ vdisk-units:
+ type: string
+ description: units associated with vdisk, used for VNFs with no vservers/flavors, to be used only in some usecases
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ summary-status:
+ type: string
+ description: details regarding the generic-vnf operation, PLEASE DISCONTINUE USE OF THIS FIELD.
+ encrypted-access-flag:
+ type: boolean
+ description: indicates whether generic-vnf access uses SSH
+ entitlement-assignment-group-uuid:
+ type: string
+ description: UUID of the Entitlement group used for licensing VNFs, OBSOLETE - See child relationships.
+ entitlement-resource-uuid:
+ type: string
+ description: UUID of the specific entitlement resource. OBSOLETE - See child relationships.
+ license-assignment-group-uuid:
+ type: string
+ description: UUID of the license assignment group. OBSOLETE - See child relationships.
+ license-key-uuid:
+ type: string
+ description: UUID of the actual license resource. OBSOLETE - See child relationships.
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ model-customization-id:
+ type: string
+ description: captures the id of all the configuration used to customize the resource for the service.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ as-number:
+ type: string
+ description: as-number of the VNF
+ regional-resource-subzone:
+ type: string
+ description: represents sub zone of the rr plane
+ nf-type:
+ type: string
+ description: Generic description of the type of NF
+ nf-function:
+ type: string
+ description: English description of Network function that the specific VNF deployment is providing
+ nf-role:
+ type: string
+ description: role in the network that this model will be providing
+ nf-naming-code:
+ type: string
+ description: string assigned to this model used for naming purposes
+ selflink:
+ type: string
+ description: Path to the controller object.
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- snapshots:
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/l-interface"
+ lag-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/lag-interface"
+ vf-modules:
+ type: array
+ items:
+ $ref: "#/definitions/vf-module"
+ licenses:
+ type: array
+ items:
+ $ref: "#/definitions/license"
+ entitlements:
+ type: array
+ items:
+ $ref: "#/definitions/entitlement"
+ generic-vnfs:
description: |
- Collection of openstack snapshots
+ Collection of VNFs
properties:
- snapshot:
+ generic-vnf:
type: array
items:
- $ref: "#/definitions/snapshot"
- metadatum:
+ $ref: "#/definitions/generic-vnf"
+ group-assignment:
description: |
- Key/value pairs
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Openstack group-assignment used to store exclusivity groups (EG).
###### Related Nodes
- - FROM image (is composed of metadatum)
- - FROM model-ver (is composed of metadatum)
- - FROM service-instance (is composed of metadatum)
- - FROM connector (is composed of metadatum)
+ - TO cloud-region( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)
required:
- - metaname
- - metaval
+ - group-id
+ - group-type
+ - group-name
properties:
- metaname:
+ group-id:
type: string
- metaval:
+ description: Group id, expected to be unique across cloud-region.
+ group-type:
+ type: string
+ description: Group type - the type of group this instance refers to
+ group-name:
+ type: string
+ description: Group name - name assigned to the group
+ group-description:
type: string
+ description: Group description - description of the group
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- metadata:
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ group-assignments:
description: |
- Collection of metadatum (key/value pairs)
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Collection of openstack group assignments
properties:
- metadatum:
+ group-assignment:
type: array
items:
- $ref: "#/definitions/metadatum"
+ $ref: "#/definitions/group-assignment"
+ host-route:
+ description: |
+ ###### Related Nodes
+ - TO subnet( host-route org.onap.relationships.inventory.BelongsTo subnet, MANY2ONE)
+ required:
+ - host-route-id
+ - route-prefix
+ - next-hop
+ properties:
+ host-route-id:
+ type: string
+ description: host-route id
+ route-prefix:
+ type: string
+ description: subnet prefix
+ next-hop:
+ type: string
+ description: Could be ip-address, hostname, or service-instance
+ next-hop-type:
+ type: string
+ description: Should be ip-address, hostname, or service-instance to match next-hop
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ host-routes:
+ properties:
+ host-route:
+ type: array
+ items:
+ $ref: "#/definitions/host-route"
image:
description: |
Openstack image.
- ###### Default Delete Scope
- ERROR_4_IN_EDGES_OR_CASCADE
###### Related Nodes
- - TO metadatum (comprises image, Many2Many)
- - FROM cloud-region (is composed of image)
- - FROM vserver
+ - TO cloud-region( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)
+ - IMAGE cannot be deleted if linked to VSERVER
+ - IMAGE is DELETED when these are DELETED METADATUM
required:
- image-id
- image-name
@@ -38792,24 +50069,205 @@ definitions:
type: array
items:
$ref: "#/definitions/image"
- dvs-switch:
+ include-node-filter:
+ properties:
+ include-node-type:
+ type: string
+ instance-filter:
description: |
- Digital virtual switch metadata, used by SDN-C to configure VCEs. A&AI needs to receive this data from the PO deployment team and administer it using the provisioningTool.sh into A&AI.
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ InstanceFilter for performing a named-query or model query
+ instance-filters:
+ description: |
+ InstanceFilters for performing a named-query or model query
+ properties:
+ instance-filter:
+ type: array
+ items:
+ $ref: "#/definitions/instance-filter"
+ instance-group:
+ description: |
+ General mechanism for grouping instances
###### Related Nodes
- - TO availability-zone (Many2Many)
- - FROM cloud-region (is composed of dvs-switch)
+ - TO model( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM pnf( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
required:
- - switch-name
- - vcenter-url
+ - id
+ - description
+ - type
properties:
- switch-name:
+ id:
type: string
- description: DVS switch name
- vcenter-url:
+ description: Instance Group ID, UUID assigned to this instance.
+ description:
type: string
- description: URL used to reach the vcenter
+ description: Descriptive text to help identify the usage of this instance-group
+ type:
+ type: string
+ description: Only valid value today is lower case ha for high availability
+ sub-type:
+ type: string
+ description: Valid values for ha type are [geo-activeactive, geo-activestandby, local-activeactive, local-activestandby]
+ resource-version:
+ type: string
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ instance-groups:
+ description: |
+ Collection of openstack route table references
+ properties:
+ instance-group:
+ type: array
+ items:
+ $ref: "#/definitions/instance-group"
+ inventory:
+ properties:
+ search:
+ type: object
+ $ref: "#/definitions/search"
+ actions:
+ type: object
+ $ref: "#/definitions/actions"
+ cloud-infrastructure:
+ type: object
+ $ref: "#/definitions/cloud-infrastructure"
+ business:
+ type: object
+ $ref: "#/definitions/business"
+ service-design-and-creation:
+ type: object
+ $ref: "#/definitions/service-design-and-creation"
+ network:
+ type: object
+ $ref: "#/definitions/network"
+ aai-internal:
+ type: object
+ $ref: "#/definitions/aai-internal"
+ nodes:
+ type: array
+ items:
+ $ref: "#/definitions/aai-internal"
+ inventory-item:
+ properties:
+ inventory-item-type:
+ type: string
+ inventory-item-link:
+ type: string
+ inventory-item-data:
+ type: array
+ items:
+ $ref: "#/definitions/inventory-item-data"
+ tagged-inventory-item-list:
+ type: array
+ items:
+ $ref: "#/definitions/tagged-inventory-item-list"
+ inventory-item-data:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ inventory-response-item:
+ description: |
+ Inventory item for response list
+ properties:
+ model-name:
+ type: string
+ extra-properties:
+ type: object
+ $ref: "#/definitions/extra-properties"
+ inventory-response-items:
+ type: object
+ $ref: "#/definitions/inventory-response-items"
+ inventory-response-items:
+ description: |
+ Container for inventory items in response list
+ properties:
+ inventory-response-item:
+ type: array
+ items:
+ $ref: "#/definitions/inventory-response-item"
+ ipsec-configuration:
+ description: |
+ IPSec configuration node will contain various configuration data for the NMTE VNF. This node will have an edge to the generic-vnf (vnf type = TE). Starting 1607, this data will be populated by SDN-C
+ ###### Related Nodes
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)
+ - FROM vig-server( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)
+ - IPSEC-CONFIGURATION is DELETED when these are DELETED VIG-SERVER
+ required:
+ - ipsec-configuration-id
+ properties:
+ ipsec-configuration-id:
+ type: string
+ description: UUID of this configuration
+ requested-vig-address-type:
+ type: string
+ description: Indicate the type of VIG server like AVPN, INTERNET, BOTH
+ requested-encryption-strength:
+ type: string
+ description: Encryption values like 3des-cbc, des-cbc, aes-128-cbc, aes-192-cbc, aes-265-cbc
+ requested-dmz-type:
+ type: string
+ description: can offer a shared DMZ or a DMZ specific to a customer
+ shared-dmz-network-address:
+ type: string
+ description: Network address of shared DMZ
+ requested-customer-name:
+ type: string
+ description: If the DMZ is a custom DMZ, this field will indicate the customer information
+ ike-version:
+ type: string
+ description: can be 1 or 2
+ ikev1-authentication:
+ type: string
+ description: Contains values like md5, sha1, sha256, sha384
+ ikev1-encryption:
+ type: string
+ description: Encyption values like 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
+ ikev1-dh-group:
+ type: string
+ description: Diffie-Hellman group like DH-GROUP2, DH-GROUP5, DH-GROUP14
+ ikev1-am-group-id:
+ type: string
+ description: Group name defined in VIG for clients using aggressive mode
+ ikev1-am-password:
+ type: string
+ description: pre-shared key for the above group name
+ ikev1-sa-lifetime:
+ type: string
+ description: Lifetime for IKEv1 SA
+ ipsec-authentication:
+ type: string
+ description: md5, sha1, sha256, sha384
+ ipsec-encryption:
+ type: string
+ description: 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
+ ipsec-sa-lifetime:
+ type: string
+ description: Life time for IPSec SA
+ ipsec-pfs:
+ type: string
+ description: enable PFS or not
+ xauth-userid:
+ type: string
+ description: user ID for xAuth, sm-user, ,nmteHostName
+ xauth-user-password:
+ type: string
+ description: Encrypted using the Juniper $9$ algorithm
+ dpd-interval:
+ type: string
+ description: The time between DPD probe
+ dpd-frequency:
+ type: string
+ description: Maximum number of DPD before claiming the tunnel is down
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
@@ -38817,206 +50275,998 @@ definitions:
type: array
items:
$ref: "#/definitions/relationship"
- dvs-switches:
+ vig-servers:
+ type: array
+ items:
+ $ref: "#/definitions/vig-server"
+ ipsec-configurations:
+ properties:
+ ipsec-configuration:
+ type: array
+ items:
+ $ref: "#/definitions/ipsec-configuration"
+ key-data:
+ properties:
+ key-name:
+ type: string
+ key-value:
+ type: string
+ l-interface:
description: |
- Collection of digital virtual switch metadata used for vmWare VCEs and GenericVnfs.
+ Logical interfaces, e.g., a vnic.
+ ###### Related Nodes
+ - TO generic-vnf( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO lag-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)
+ - TO instance-group( l-interface org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO l-interface( l-interface org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - TO logical-link( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)
+ - TO newvce( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)
+ - TO p-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)
+ - TO vserver( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - FROM sriov-vf( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)
+ - FROM vlan( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - L-INTERFACE is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST,SRIOV-VF,VLAN
+ - L-INTERFACE deletion means associated objects of these types are also DELETED:LOGICAL-LINK
+ required:
+ - interface-name
+ - is-port-mirrored
+ - in-maint
properties:
- dvs-switch:
+ interface-name:
+ type: string
+ description: Name given to the interface
+ interface-role:
+ type: string
+ description: E.g., CUSTOMER, UPLINK, etc.
+ v6-wan-link-ip:
+ type: string
+ description: Questionably placed - v6 ip addr of this interface (is in vr-lan-interface from Mary B.
+ selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ interface-id:
+ type: string
+ description: ID of interface
+ macaddr:
+ type: string
+ description: MAC address for the interface
+ network-name:
+ type: string
+ description: Name of the network
+ management-option:
+ type: string
+ description: Whether A&AI should be managing this interface of not. Could have value like CUSTOMER
+ interface-description:
+ type: string
+ description: Human friendly text regarding this interface.
+ is-port-mirrored:
+ type: boolean
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ in-maint:
+ type: boolean
+ vlans:
+ type: array
+ items:
+ $ref: "#/definitions/vlan"
+ sriov-vfs:
+ type: array
+ items:
+ $ref: "#/definitions/sriov-vf"
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/l-interface"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ l3-interface-ipv4-address-list:
type: array
items:
- $ref: "#/definitions/dvs-switch"
- oam-network:
+ $ref: "#/definitions/l3-interface-ipv4-address-list"
+ l3-interface-ipv6-address-list:
+ type: array
+ items:
+ $ref: "#/definitions/l3-interface-ipv6-address-list"
+ l-interfaces:
description: |
- OAM network, to be deprecated shortly. Do not use for new purposes.
- ###### Default Delete Scope
- ERROR_IF_ANY_IN_EDGES
+ Collection of logical interfaces.
+ properties:
+ l-interface:
+ type: array
+ items:
+ $ref: "#/definitions/l-interface"
+ l3-interface-ipv4-address-list:
+ description: |
+ IPv4 Address Range
###### Related Nodes
- - TO complex (Many2Many)
- - TO service-capability (Many2Many)
- - FROM cloud-region (is composed of oam-network)
+ - TO instance-group( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)
+ - TO l3-network( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - TO subnet( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - TO l-interface( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - TO vlan( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
required:
- - network-uuid
+ - l3-interface-ipv4-address
+ properties:
+ l3-interface-ipv4-address:
+ type: string
+ description: IP address
+ l3-interface-ipv4-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 32 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
+ type: string
+ description: Neutron network id of the interface that address belongs to
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of subnet that address belongs to
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ l3-interface-ipv6-address-list:
+ description: |
+ IPv6 Address Range
+ ###### Related Nodes
+ - TO instance-group( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)
+ - TO l3-network( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - TO subnet( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - TO l-interface( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - TO vlan( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ required:
+ - l3-interface-ipv6-address
+ properties:
+ l3-interface-ipv6-address:
+ type: string
+ description: IP address
+ l3-interface-ipv6-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 128 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
+ type: string
+ description: Neutron network id of the interface that address belongs to
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of subnet that address belongs to
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ l3-network:
+ description: |
+ Generic network definition
+ ###### Related Nodes
+ - TO network-policy( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)
+ - TO route-table-reference( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)
+ - TO vpn-binding( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM complex( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - FROM ctag-assignment( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM segmentation-assignment( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)
+ - FROM subnet( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)
+ - L3-NETWORK is DELETED when these are DELETED CTAG-ASSIGNMENT,SEGMENTATION-ASSIGNMENT,SUBNET
+ required:
+ - network-id
- network-name
- - cvlan-tag
+ - is-bound-to-vpn
+ - is-provider-network
+ - is-shared-network
+ - is-external-network
properties:
- network-uuid:
+ network-id:
type: string
- description: UUID of the network. Unique across a cloud-region
+ description: Network ID, should be uuid. Unique across A&AI.
network-name:
type: string
- description: Name of the network.
- cvlan-tag:
+ description: Name of the network, governed by some naming convention..
+ network-type:
+ type: string
+ description: Type of the network - who defines these values?
+ network-role:
+ type: string
+ description: Role the network plans - who defines these values?
+ network-technology:
+ type: string
+ description: Network technology - who defines these values?
+ neutron-network-id:
+ type: string
+ description: Neutron network id of this Interface
+ is-bound-to-vpn:
+ type: boolean
+ service-id:
+ type: string
+ description: Unique identifier of service from ASDC. Does not strictly map to ASDC services. SOON TO BE DEPRECATED
+ network-role-instance:
type: integer
format: int64
- description: cvlan-id
- ipv4-oam-gateway-address:
+ description: network role instance
+ resource-version:
type: string
- description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
- ipv4-oam-gateway-address-prefix-length:
- type: integer
- format: int32
- description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ contrail-network-fqdn:
+ type: string
+ description: Contrail FQDN for the network
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ model-customization-id:
+ type: string
+ description: captures the id of all the configuration used to customize the resource for the service.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ physical-network-name:
+ type: string
+ description: Name associated with the physical network.
+ is-provider-network:
+ type: boolean
+ is-shared-network:
+ type: boolean
+ is-external-network:
+ type: boolean
+ selflink:
+ type: string
+ description: Path to the controller object.
+ operational-status:
+ type: string
+ description: Indicator for whether the resource is considered operational.
+ subnets:
+ type: array
+ items:
+ $ref: "#/definitions/subnet"
+ ctag-assignments:
+ type: array
+ items:
+ $ref: "#/definitions/ctag-assignment"
+ segmentation-assignments:
+ type: array
+ items:
+ $ref: "#/definitions/segmentation-assignment"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ description: Relates to tenant (or is it a child of tenant), complex, service, vpn-binding
+ l3-networks:
+ properties:
+ l3-network:
+ type: array
+ items:
+ $ref: "#/definitions/l3-network"
+ lag-interface:
+ description: |
+ Link aggregate interface
+ ###### Related Nodes
+ - TO generic-vnf( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO lag-link( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)
+ - TO logical-link( lag-interface org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - TO p-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)
+ - TO pnf( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - TO pserver( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - TO vpls-pe( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)
+ - LAG-INTERFACE is DELETED when these are DELETED L-INTERFACE
+ - LAG-INTERFACE deletion means associated objects of these types are also DELETED:LAG-LINK,LOGICAL-LINK
+ required:
+ - interface-name
+ - in-maint
+ properties:
+ interface-name:
+ type: string
+ description: Name that identifies the link aggregate interface
+ interface-description:
+ type: string
+ description: Human friendly text regarding this interface.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ interface-id:
+ type: string
+ description: ID of interface
+ interface-role:
+ type: string
+ description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ in-maint:
+ type: boolean
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- oam-networks:
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/l-interface"
+ lag-interfaces:
description: |
- Collection of OAM networks, to be deprecated shortly. Do not use for new purposes.
+ Collection of link aggregate interfaces.
properties:
- oam-network:
+ lag-interface:
type: array
items:
- $ref: "#/definitions/oam-network"
- availability-zone:
+ $ref: "#/definitions/lag-interface"
+ lag-link:
description: |
- Availability zone, a collection of compute hosts/pservers
- ###### Default Delete Scope
- ERROR_IF_ANY_IN_EDGES
- ###### Related Nodes
- - TO complex (Many2Many)
- - TO service-capability (Many2Many)
- - FROM cloud-region (is composed of availability-zone)
- - FROM ctag-pool
- - FROM dvs-switch
- - FROM generic-vnf
- - FROM pserver
- - FROM vce
+ LAG links can connect lag-interfaces
+ ###### Related Nodes
+ - FROM lag-interface( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)
required:
- - availability-zone-name
- - hypervisor-type
+ - link-name
properties:
- availability-zone-name:
+ link-name:
type: string
- description: Name of the availability zone. Unique across a cloud region
- hypervisor-type:
+ description: Alphabetical concatenation of lag-interface names
+ resource-version:
type: string
- description: Type of hypervisor. Source of truth should define valid values.
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ lag-links:
+ description: |
+ Collection of link aggregation connections
+ properties:
+ lag-link:
+ type: array
+ items:
+ $ref: "#/definitions/lag-link"
+ license:
+ description: |
+ Metadata for license group.
+ ###### Related Nodes
+ - TO generic-vnf( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vce( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ required:
+ - group-uuid
+ - resource-uuid
+ properties:
+ group-uuid:
+ type: string
+ description: Unique ID for the license group the resource belongs to, should be uuid.
+ resource-uuid:
+ type: string
+ description: Unique ID of a license resource.
+ resource-version:
+ type: string
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ licenses:
+ description: |
+ Licenses to be allocated across resources, keyed by group-uuid and resource-uuid, related to license management
+ properties:
+ license:
+ type: array
+ items:
+ $ref: "#/definitions/license"
+ line-of-business:
+ description: |
+ describes a line-of-business
+ ###### Related Nodes
+ - TO generic-vnf( line-of-business org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)
+ required:
+ - line-of-business-name
+ properties:
+ line-of-business-name:
+ type: string
+ description: Name of the line-of-business (product)
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ lines-of-business:
+ description: |
+ Collection of lines-of-business
+ properties:
+ line-of-business:
+ type: array
+ items:
+ $ref: "#/definitions/line-of-business"
+ logical-link:
+ description: |
+ Logical links generally connect l-interfaces but are used to express logical connectivity between two points
+ ###### Related Nodes
+ - TO cloud-region( logical-link org.onap.relationships.inventory.LocatedIn cloud-region, MANY2MANY)
+ - TO generic-vnf( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)
+ - TO lag-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)
+ - TO logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - TO pnf( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)
+ - TO pserver( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)
+ - TO vpn-binding( logical-link org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - TO virtual-data-center( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM lag-interface( lag-interface org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)
+ - FROM p-interface( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - FROM vlan( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ required:
+ - link-name
+ - link-type
+ properties:
+ link-name:
+ type: string
+ description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
+ link-type:
+ type: string
+ description: Type of logical link, e.g., evc
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ ip-version:
+ type: string
+ description: v4, v6, or ds for dual stack
+ routing-protocol:
+ type: string
+ description: For example, static or BGP
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
operational-status:
type: string
- description: State that indicates whether the availability zone should be used, etc. Source of truth should define valid values.
+ description: Indication of operational status of the logical link.
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+ link-role:
+ type: string
+ description: Indication of the network use of the logical link.
+ link-name2:
+ type: string
+ description: Alias or alternate name (CLCI or D1 name).
+ link-id:
+ type: string
+ description: UUID of the logical-link, SDNC generates this.
+ circuit-id:
+ type: string
+ description: Circuit id
+ purpose:
+ type: string
+ description: Reason for this entity, role it is playing
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ logical-links:
+ description: |
+ Collection of logical connections
+ properties:
+ logical-link:
+ type: array
+ items:
+ $ref: "#/definitions/logical-link"
+ metadata:
+ description: |
+ Collection of metadatum (key/value pairs)
+ properties:
+ metadatum:
+ type: array
+ items:
+ $ref: "#/definitions/metadatum"
+ metadatum:
+ description: |
+ Key/value pairs
+ ###### Related Nodes
+ - TO connector( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)
+ - TO image( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)
+ - TO service-instance( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - TO model-ver( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ required:
+ - metaname
+ - metaval
+ properties:
+ metaname:
+ type: string
+ metaval:
+ type: string
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model:
+ description: |
+ Subgraph definition provided by ASDC to describe an inventory asset and its connections related to ASDC models, independent of version
+ ###### Related Nodes
+ - TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - FROM instance-group( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY)
+ - FROM model-ver( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - FROM named-query( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)
+ - MODEL cannot be deleted if linked to INSTANCE-GROUP,NAMED-QUERY,NAMED-QUERY-ELEMENT
+ - MODEL is DELETED when these are DELETED MODEL-VER
+ required:
+ - model-invariant-id
+ - model-type
+ properties:
+ model-invariant-id:
+ type: string
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ model-type:
+ type: string
+ description: Type of the model, e.g., service, resource, widget, etc.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-vers:
+ type: array
+ items:
+ $ref: "#/definitions/model-ver"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- availability-zones:
+ model-and-named-query-search:
description: |
- Collection of availability zones
+ ModelAndNamedQuerySearch holds query-parameters and instance-properties for performing a named-query or model query
properties:
- availability-zone:
+ query-parameters:
+ type: object
+ $ref: "#/definitions/query-parameters"
+ instance-filters:
+ type: object
+ $ref: "#/definitions/instance-filters"
+ secondary-filts:
+ type: object
+ $ref: "#/definitions/secondary-filts"
+ top-node-type:
+ type: string
+ secondary-filter-cut-point:
+ type: string
+ model-constraint:
+ description: |
+ This is how we would capture constraints defining allowed sets of elements.
+ ###### Related Nodes
+ - TO model-element( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)
+ - MODEL-CONSTRAINT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET
+ required:
+ - model-constraint-uuid
+ - constrained-element-set-uuid-to-replace
+ properties:
+ model-constraint-uuid:
+ type: string
+ constrained-element-set-uuid-to-replace:
+ type: string
+ constrained-element-sets:
+ type: array
+ items:
+ $ref: "#/definitions/constrained-element-set"
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-constraints:
+ properties:
+ model-constraint:
type: array
items:
- $ref: "#/definitions/availability-zone"
- cloud-region:
+ $ref: "#/definitions/model-constraint"
+ model-element:
description: |
- cloud-region designates an installation of a cloud cluster or region or instantiation
- ###### Default Delete Scope
- THIS_NODE_ONLY
- ###### Related Nodes
- - TO complex (Many2One)
- - TO l3-network (Many2Many)
- - TO tenant (comprises cloud-region, One2Many)
- - TO image (comprises cloud-region, One2Many)
- - TO flavor (comprises cloud-region, One2Many)
- - TO availability-zone (comprises cloud-region, One2Many)
- - TO oam-network (comprises cloud-region, One2Many)
- - TO dvs-switch (comprises cloud-region, One2Many)
- - TO volume-group (comprises cloud-region, One2Many)
- - TO group-assignment (comprises cloud-region, One2Many)
- - TO snapshot (comprises cloud-region, One2Many)
- - TO zone (Many2One)
- - FROM pserver
- - FROM logical-link
+ Defines how other models combine to make up a higher-level model.
+ ###### Related Nodes
+ - TO element-choice-set( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)
+ - TO model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - TO model-ver( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE)
+ - TO model-ver( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM model-constraint( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - MODEL-ELEMENT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET,MODEL-CONSTRAINT
required:
- - cloud-owner
- - cloud-region-id
+ - model-element-uuid
+ - new-data-del-flag
+ - cardinality
properties:
- cloud-owner:
+ model-element-uuid:
type: string
- description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
- cloud-region-id:
+ new-data-del-flag:
type: string
- description: Identifier used by the vendor for the region. Second part of composite key
- cloud-type:
+ description: Indicates whether this element was created as part of instantiation from this model
+ cardinality:
type: string
- description: Type of the cloud (e.g., openstack)
- owner-defined-type:
+ description: How many of this type of element are required/allowed
+ linkage-points:
type: string
- description: Cloud-owner defined type indicator (e.g., dcp, lcp)
- cloud-region-version:
+ resource-version:
type: string
- description: Software version employed at the site. NOTE - THIS FIELD IS NOT KEPT UP TO DATE.
- identity-url:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-elements:
+ type: array
+ items:
+ $ref: "#/definitions/model-element"
+ description: Defines how other models combine to make up a higher-level model
+ model-constraints:
+ type: array
+ items:
+ $ref: "#/definitions/model-constraint"
+ description: Describes new constraints on this model element that are not part of that model's definition
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ model-elements:
+ properties:
+ model-element:
+ type: array
+ items:
+ $ref: "#/definitions/model-element"
+ model-ver:
+ description: |
+ Subgraph definition provided by ASDC to describe a specific version of an inventory asset and its connections related to ASDC models
+ ###### Related Nodes
+ - TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - MODEL-VER cannot be deleted if linked to MODEL-ELEMENT
+ - MODEL-VER is DELETED when these are DELETED MODEL-ELEMENT,METADATUM
+ required:
+ - model-version-id
+ - model-name
+ - model-version
+ properties:
+ model-version-id:
type: string
- description: URL of the keystone identity service
- cloud-zone:
+ description: Unique identifier corresponding to one version of a model in ASDC
+ model-name:
type: string
- description: Zone where the cloud is homed. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
- complex-name:
+ description: Name of the model, which can change from version to version.
+ model-version:
type: string
- description: complex name for cloud-region instance. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
+ description: Version
+ model-description:
+ type: string
+ description: Description
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- volume-groups:
+ model-elements:
type: array
items:
- $ref: "#/definitions/volume-group"
- tenants:
+ $ref: "#/definitions/model-element"
+ metadata:
type: array
items:
- $ref: "#/definitions/tenant"
- flavors:
+ $ref: "#/definitions/metadatum"
+ relationship-list:
type: array
items:
- $ref: "#/definitions/flavor"
- group-assignments:
+ $ref: "#/definitions/relationship"
+ model-vers:
+ properties:
+ model-ver:
+ type: array
+ items:
+ $ref: "#/definitions/model-ver"
+ models:
+ description: |
+ Collection of subgraph definitions provided by ASDC to describe the inventory assets and their connections related to ASDC models
+ properties:
+ model:
+ type: array
+ items:
+ $ref: "#/definitions/model"
+ multicast-configuration:
+ description: |
+ ###### Related Nodes
+ - FROM vlan( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)
+ required:
+ - multicast-configuration-id
+ - multicast-protocol
+ - rp-type
+ properties:
+ multicast-configuration-id:
+ type: string
+ description: Unique id of multicast configuration.
+ multicast-protocol:
+ type: string
+ description: protocol of multicast configuration
+ rp-type:
+ type: string
+ description: rp type of multicast configuration
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/group-assignment"
- snapshots:
+ $ref: "#/definitions/relationship"
+ multicast-configurations:
+ description: |
+ multicast configuration of generic-vnf ip-address
+ properties:
+ multicast-configuration:
+ type: array
+ items:
+ $ref: "#/definitions/multicast-configuration"
+ named-queries:
+ properties:
+ named-query:
+ type: array
+ items:
+ $ref: "#/definitions/named-query"
+ named-query:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - TO model( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - NAMED-QUERY is DELETED when these are DELETED NAMED-QUERY-ELEMENT
+ required:
+ - named-query-uuid
+ - named-query-name
+ - named-query-version
+ properties:
+ named-query-uuid:
+ type: string
+ named-query-name:
+ type: string
+ named-query-version:
+ type: string
+ required-input-param:
+ type: string
+ description:
+ type: string
+ resource-version:
+ type: string
+ named-query-elements:
type: array
items:
- $ref: "#/definitions/snapshot"
- images:
+ $ref: "#/definitions/named-query-element"
+ relationship-list:
type: array
items:
- $ref: "#/definitions/image"
- dvs-switches:
+ $ref: "#/definitions/relationship"
+ named-query-element:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - TO model( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)
+ - TO named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM property-constraint( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM related-lookup( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - NAMED-QUERY-ELEMENT is DELETED when these are DELETED PROPERTY-CONSTRAINT,RELATED-LOOKUP
+ required:
+ - named-query-element-uuid
+ properties:
+ named-query-element-uuid:
+ type: string
+ property-collect-list:
+ type: string
+ resource-version:
+ type: string
+ property-limit-desc:
+ type: string
+ do-not-output:
+ type: string
+ named-query-elements:
type: array
items:
- $ref: "#/definitions/dvs-switch"
- oam-networks:
+ $ref: "#/definitions/named-query-element"
+ related-lookups:
type: array
items:
- $ref: "#/definitions/oam-network"
- availability-zones:
+ $ref: "#/definitions/related-lookup"
+ property-constraints:
type: array
items:
- $ref: "#/definitions/availability-zone"
+ $ref: "#/definitions/property-constraint"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- cloud-regions:
+ named-query-elements:
properties:
- cloud-region:
+ named-query-element:
type: array
items:
- $ref: "#/definitions/cloud-region"
+ $ref: "#/definitions/named-query-element"
+ network:
+ description: |
+ Namespace for network inventory resources.
+ properties:
+ logical-links:
+ type: array
+ items:
+ $ref: "#/definitions/logical-link"
+ site-pair-sets:
+ type: array
+ items:
+ $ref: "#/definitions/site-pair-set"
+ vpn-bindings:
+ type: array
+ items:
+ $ref: "#/definitions/vpn-binding"
+ vpls-pes:
+ type: array
+ items:
+ $ref: "#/definitions/vpls-pe"
+ multicast-configurations:
+ type: array
+ items:
+ $ref: "#/definitions/multicast-configuration"
+ vces:
+ type: array
+ items:
+ $ref: "#/definitions/vce"
+ vnfcs:
+ type: array
+ items:
+ $ref: "#/definitions/vnfc"
+ l3-networks:
+ type: array
+ items:
+ $ref: "#/definitions/l3-network"
+ network-policies:
+ type: array
+ items:
+ $ref: "#/definitions/network-policy"
+ generic-vnfs:
+ type: array
+ items:
+ $ref: "#/definitions/generic-vnf"
+ lag-links:
+ type: array
+ items:
+ $ref: "#/definitions/lag-link"
+ newvces:
+ type: array
+ items:
+ $ref: "#/definitions/newvce"
+ pnfs:
+ type: array
+ items:
+ $ref: "#/definitions/pnf"
+ physical-links:
+ type: array
+ items:
+ $ref: "#/definitions/physical-link"
+ ipsec-configurations:
+ type: array
+ items:
+ $ref: "#/definitions/ipsec-configuration"
+ route-table-references:
+ type: array
+ items:
+ $ref: "#/definitions/route-table-reference"
+ instance-groups:
+ type: array
+ items:
+ $ref: "#/definitions/instance-group"
+ zones:
+ type: array
+ items:
+ $ref: "#/definitions/zone"
+ network-policies:
+ properties:
+ network-policy:
+ type: array
+ items:
+ $ref: "#/definitions/network-policy"
+ network-policy:
+ description: |
+ ###### Related Nodes
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.Uses network-policy, ONE2ONE)
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)
+ required:
+ - network-policy-id
+ properties:
+ network-policy-id:
+ type: string
+ description: UUID representing unique key to this instance
+ network-policy-fqdn:
+ type: string
+ description: Contrail FQDN for the policy
+ heat-stack-id:
+ type: string
+ description: ID for the openStack Heat instance
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
network-profile:
description: |
Network profile populated by SDN-GP for SNMP
- ###### Default Delete Scope
- THIS_NODE_ONLY
###### Related Nodes
- - FROM generic-vnf
+ - TO generic-vnf( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
required:
- nm-profile-name
properties:
@@ -39041,19 +51291,301 @@ definitions:
type: array
items:
$ref: "#/definitions/network-profile"
+ newvce:
+ description: |
+ This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce.
+ ###### Related Nodes
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)
+ - NEWVCE is DELETED when these are DELETED L-INTERFACE
+ required:
+ - vnf-id2
+ - vnf-name
+ - vnf-type
+ properties:
+ vnf-id2:
+ type: string
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ vnf-name:
+ type: string
+ description: Name of VNF.
+ vnf-name2:
+ type: string
+ description: Alternate name of VNF.
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+ operational-status:
+ type: string
+ description: Indicator for whether the resource is considered operational
+ license-key:
+ type: string
+ description: OBSOLETE - do not use
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address).
+ equipment-role:
+ type: string
+ description: Client should send valid enumerated value.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ ipv4-loopback0-address:
+ type: string
+ description: v4 Loopback0 address
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO.
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/l-interface"
+ newvces:
+ description: |
+ This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce.
+ properties:
+ newvce:
+ type: array
+ items:
+ $ref: "#/definitions/newvce"
+ notification-event:
+ properties:
+ cambria.partition:
+ type: string
+ notification-event-header:
+ type: object
+ $ref: "#/definitions/notification-event-header"
+ notification-event-header:
+ properties:
+ id:
+ type: string
+ timestamp:
+ type: string
+ source-name:
+ type: string
+ domain:
+ type: string
+ sequence-number:
+ type: string
+ severity:
+ type: string
+ event-type:
+ type: string
+ version:
+ type: string
+ action:
+ type: string
+ entity-type:
+ type: string
+ top-entity-type:
+ type: string
+ entity-link:
+ type: string
+ status:
+ type: string
+ notify:
+ required:
+ - event-id
+ properties:
+ event-id:
+ type: string
+ node-type:
+ type: string
+ event-trigger:
+ type: string
+ key-data:
+ type: array
+ items:
+ $ref: "#/definitions/key-data"
+ selflink:
+ type: string
+ oam-network:
+ description: |
+ OAM network, to be deprecated shortly. Do not use for new purposes.
+ ###### Related Nodes
+ - TO cloud-region( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO complex( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)
+ - TO service-capability( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ required:
+ - network-uuid
+ - network-name
+ - cvlan-tag
+ properties:
+ network-uuid:
+ type: string
+ description: UUID of the network. Unique across a cloud-region
+ network-name:
+ type: string
+ description: Name of the network.
+ cvlan-tag:
+ type: integer
+ format: int64
+ description: cvlan-id
+ ipv4-oam-gateway-address:
+ type: string
+ description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
+ ipv4-oam-gateway-address-prefix-length:
+ type: integer
+ format: int32
+ description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ oam-networks:
+ description: |
+ Collection of OAM networks, to be deprecated shortly. Do not use for new purposes.
+ properties:
+ oam-network:
+ type: array
+ items:
+ $ref: "#/definitions/oam-network"
+ operational-environment:
+ description: |
+ It is a logical partition of the cloud which allows to have multiple environments in the production AIC.
+ ###### Related Nodes
+ - TO operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)
+ - FROM operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)
+ required:
+ - operational-environment-id
+ - operational-environment-name
+ - operational-environment-type
+ - operational-environment-status
+ - tenant-context
+ - workload-context
+ properties:
+ operational-environment-id:
+ type: string
+ description: UUID of an operational environment
+ operational-environment-name:
+ type: string
+ description: Operational Environment name
+ operational-environment-type:
+ type: string
+ description: Operational Environment Type.
+ operational-environment-status:
+ type: string
+ description: Status
+ tenant-context:
+ type: string
+ description: Tenant Context.
+ workload-context:
+ type: string
+ description: Workload Context.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ operational-environments:
+ description: |
+ a logical partition of the cloud which allows to have multiple environments in the production AIC.
+ properties:
+ operational-environment:
+ type: array
+ items:
+ $ref: "#/definitions/operational-environment"
+ overloaded-model:
+ description: |
+ Allows for legacy POST of old-style and new-style models
+ required:
+ - model-invariant-id
+ - model-name-version-id
+ - model-type
+ - model-name
+ - model-id
+ - model-version
+ properties:
+ model-invariant-id:
+ type: string
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ model-name-version-id:
+ type: string
+ description: Unique identifier corresponding to one version of a model in ASDC
+ model-type:
+ type: string
+ description: Type of the model, e.g., service, resource, widget, etc.
+ model-name:
+ type: string
+ description: Name of the model, which can change from version to version.
+ model-id:
+ type: string
+ description: Invariant unique ID which does not change from version to version
+ model-version:
+ type: string
+ description: Version
+ model-description:
+ type: string
+ description: Description
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-vers:
+ type: object
+ $ref: "#/definitions/model-vers"
+ relationship-list:
+ type: object
+ $ref: "#/definitions/relationship-list"
+ owning-entities:
+ description: |
+ Collection of owning-entities
+ properties:
+ owning-entity:
+ type: array
+ items:
+ $ref: "#/definitions/owning-entity"
+ owning-entity:
+ description: |
+ describes an owning-entity
+ ###### Related Nodes
+ - FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo owning-entity, MANY2ONE)
+ required:
+ - owning-entity-id
+ - owning-entity-name
+ properties:
+ owning-entity-id:
+ type: string
+ description: UUID of an owning entity
+ owning-entity-name:
+ type: string
+ description: Owning entity name
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
p-interface:
description: |
Physical interface (e.g., nic)
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
###### Related Nodes
- - TO l-interface (comprises p-interface, Many2Many)
- - TO physical-link (Many2Many)
- - TO logical-link (Many2One)
- - FROM lag-interface
- - FROM pserver (is composed of p-interface)
- - FROM pnf (is composed of p-interface)
- - FROM vpls-pe (is composed of p-interface)
+ - TO logical-link( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)
+ - TO physical-link( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)
+ - TO pnf( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - TO pserver( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - TO vpls-pe( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM lag-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)
+ - P-INTERFACE is DELETED when these are DELETED L-INTERFACE
+ - P-INTERFACE deletion means associated objects of these types are also DELETED:PHYSICAL-LINK
required:
- interface-name
- in-maint
@@ -39103,82 +51635,313 @@ definitions:
type: array
items:
$ref: "#/definitions/p-interface"
- lag-interface:
+ physical-link:
description: |
- Link aggregate interface
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
- ###### Related Nodes
- - TO logical-link (Many2Many)
- - TO lag-link (Many2Many)
- - TO p-interface (Many2Many)
- - TO l-interface (comprises lag-interface, Many2Many)
- - FROM generic-vnf (is composed of lag-interface)
- - FROM pserver (is composed of lag-interface)
- - FROM pnf (is composed of lag-interface)
- - FROM vpls-pe (is composed of lag-interface)
+ Collection of physical connections, typically between p-interfaces
+ ###### Related Nodes
+ - FROM p-interface( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)
required:
- - interface-name
+ - link-name
+ properties:
+ link-name:
+ type: string
+ description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ circuit-id:
+ type: string
+ description: Circuit it
+ dual-mode:
+ type: string
+ description: Dual access mode (e.g., primary, secondary
+ management-option:
+ type: string
+ description: To provide information on who manages this circuit. A&AI or 3rd party transport provider
+ service-provider-name:
+ type: string
+ description: Name of the service Provider on this link.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ physical-links:
+ description: |
+ Collection of physical connections, typically between p-interfaces
+ properties:
+ physical-link:
+ type: array
+ items:
+ $ref: "#/definitions/physical-link"
+ platform:
+ description: |
+ describes a platform
+ ###### Related Nodes
+ - TO generic-vnf( platform org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)
+ required:
+ - platform-name
+ properties:
+ platform-name:
+ type: string
+ description: Name of the platform
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ platforms:
+ description: |
+ Collection of platforms
+ properties:
+ platform:
+ type: array
+ items:
+ $ref: "#/definitions/platform"
+ pnf:
+ description: |
+ PNF represents a physical network function. typically equipment used in the D1 world.
+ ###### Related Nodes
+ - TO complex( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO instance-group( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO zone( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf pnf, ONE2MANY)
+ - PNF is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
+ required:
+ - pnf-name
- in-maint
properties:
- interface-name:
+ pnf-name:
type: string
- description: Name that identifies the link aggregate interface
- interface-description:
+ description: unique name of Physical Network Function.
+ pnf-name2:
type: string
- description: Human friendly text regarding this interface.
+ description: name of Physical Network Function.
+ pnf-name2-source:
+ type: string
+ description: source of name2
+ pnf-id:
+ type: string
+ description: id of pnf
+ equip-type:
+ type: string
+ description: Equipment type. Source of truth should define valid values.
+ equip-vendor:
+ type: string
+ description: Equipment vendor. Source of truth should define valid values.
+ equip-model:
+ type: string
+ description: Equipment model. Source of truth should define valid values.
+ management-option:
+ type: string
+ description: identifier of managed by company or customer
+ ipaddress-v4-oam:
+ type: string
+ description: ipv4-oam-address with new naming convention for IP addresses
+ sw-version:
+ type: string
+ description: sw-version is the version of SW for the hosted application on the PNF.
+ in-maint:
+ type: boolean
+ frame-id:
+ type: string
+ description: ID of the physical frame (relay rack) where pnf is installed.
+ serial-number:
+ type: string
+ description: Serial number of the device
+ ipaddress-v4-loopback-0:
+ type: string
+ description: IPV4 Loopback 0 address
+ ipaddress-v6-loopback-0:
+ type: string
+ description: IPV6 Loopback 0 address
+ ipaddress-v4-aim:
+ type: string
+ description: IPV4 AIM address
+ ipaddress-v6-aim:
+ type: string
+ description: IPV6 AIM address
+ ipaddress-v6-oam:
+ type: string
+ description: IPV6 OAM address
+ inv-status:
+ type: string
+ description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- speed-value:
+ prov-status:
type: string
- description: Captures the numeric part of the speed
- speed-units:
+ description: Prov Status of this device (not under canopi control) Valid values [PREPROV/NVTPROV/PROV]
+ nf-role:
type: string
- description: Captures the units corresponding to the speed
+ description: Nf Role is the role performed by this instance in the network.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ p-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/p-interface"
+ lag-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/lag-interface"
+ pnfs:
+ description: |
+ Collection of Physical Network Functions.
+ properties:
+ pnf:
+ type: array
+ items:
+ $ref: "#/definitions/pnf"
+ port-group:
+ description: |
+ Used to capture the network interfaces of this VCE
+ ###### Related Nodes
+ - TO vce( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM cvlan-tag( cvlan-tag org.onap.relationships.inventory.BelongsTo port-group, MANY2ONE)
+ - PORT-GROUP is DELETED when these are DELETED CVLAN-TAG
+ required:
+ - interface-id
+ - orchestration-status
+ properties:
interface-id:
type: string
- description: ID of interface
+ description: Unique ID of the interface
+ neutron-network-id:
+ type: string
+ description: Neutron network id of this Interface
+ neutron-network-name:
+ type: string
+ description: Neutron network name of this Interface
interface-role:
type: string
description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
- prov-status:
+ resource-version:
type: string
- description: Trigger for operational monitoring of this resource by Service Assurance systems.
- in-maint:
- type: boolean
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ port-group-id:
+ type: string
+ description: Unique ID for port group in vmware
+ port-group-name:
+ type: string
+ description: Likely to duplicate value of neutron network name
+ switch-name:
+ type: string
+ description: DVS or standard switch name (should be non-null for port groups associated with DVS)
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ cvlan-tags:
+ type: array
+ items:
+ $ref: "#/definitions/cvlan-tag-entry"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- l-interfaces:
+ port-groups:
+ properties:
+ port-group:
+ type: array
+ items:
+ $ref: "#/definitions/port-group"
+ project:
+ description: |
+ describes the project
+ ###### Related Nodes
+ - TO service-instance( project org.onap.relationships.inventory.Uses service-instance, ONE2MANY)
+ required:
+ - project-name
+ properties:
+ project-name:
+ type: string
+ description: Name of the project deploying a service
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/l-interface"
- lag-interfaces:
+ $ref: "#/definitions/relationship"
+ projects:
description: |
- Collection of link aggregate interfaces.
+ Collection of projects
properties:
- lag-interface:
+ project:
type: array
items:
- $ref: "#/definitions/lag-interface"
+ $ref: "#/definitions/project"
+ properties:
+ description: |
+ Property holder for query properties or instance properties
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ property-constraint:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query-element( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ required:
+ - property-constraint-uuid
+ - constraint-type
+ - property-name
+ - property-value
+ properties:
+ property-constraint-uuid:
+ type: string
+ constraint-type:
+ type: string
+ property-name:
+ type: string
+ property-value:
+ type: string
+ resource-version:
+ type: string
+ property-constraints:
+ properties:
+ property-constraint:
+ type: array
+ items:
+ $ref: "#/definitions/property-constraint"
pserver:
description: |
Compute host whose hostname must be unique and must exactly match what is sent as a relationship to a vserver.
- ###### Default Delete Scope
- ERROR_4_IN_EDGES_OR_CASCADE
- ###### Related Nodes
- - TO complex (Many2One)
- - TO cloud-region (Many2One)
- - TO availability-zone (Many2One)
- - TO lag-interface (comprises pserver, Many2Many)
- - TO p-interface (comprises pserver, Many2Many)
- - TO zone (Many2One)
- - FROM generic-vnf
- - FROM group-assignment
- - FROM vserver
- - FROM logical-link
+ ###### Related Nodes
+ - TO group-assignment( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)
+ - TO availability-zone( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)
+ - TO cloud-region( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)
+ - TO complex( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO zone( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - FROM vserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)
+ - PSERVER cannot be deleted if linked to GENERIC-VNF,LOGICAL-LINK,VSERVER
+ - PSERVER is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
+ - PSERVER cannot be deleted if linked to GROUP-ASSIGNMENT
required:
- hostname
- in-maint
@@ -39280,245 +52043,396 @@ definitions:
type: array
items:
$ref: "#/definitions/pserver"
- virtual-data-center:
+ query-parameters:
description: |
- Virtual organization of cloud infrastructure elements in a data center context
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
+ QueryParameters for performing a named-query or model query
+ properties:
+ named-query:
+ type: object
+ $ref: "#/definitions/named-query"
+ overloaded-model:
+ type: object
+ $ref: "#/definitions/overloaded-model"
+ related-lookup:
+ description: |
+ TBD
###### Related Nodes
- - TO generic-vnf (Many2Many)
- - TO logical-link (Many2Many)
- - FROM connector
+ - TO named-query-element( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
required:
- - vdc-id
- - vdc-name
+ - related-lookup-uuid
+ - source-node-type
+ - source-node-property
+ - target-node-type
+ - target-node-property
properties:
- vdc-id:
+ related-lookup-uuid:
type: string
- description: Unique ID of the vdc
- vdc-name:
+ source-node-type:
+ type: string
+ source-node-property:
+ type: string
+ target-node-type:
+ type: string
+ target-node-property:
+ type: string
+ property-collect-list:
type: string
- description: Name of the virtual data center
resource-version:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- virtual-data-centers:
- description: |
- Virtual organization of cloud infrastructure elements in a data center context
+ related-lookups:
properties:
- virtual-data-center:
+ related-lookup:
type: array
items:
- $ref: "#/definitions/virtual-data-center"
- cloud-infrastructure:
- description: |
- Namespace for cloud infrastructure.
+ $ref: "#/definitions/related-lookup"
+ related-to-property:
properties:
- complexes:
- type: array
- items:
- $ref: "#/definitions/complex"
- cloud-regions:
- type: array
- items:
- $ref: "#/definitions/cloud-region"
- network-profiles:
- type: array
- items:
- $ref: "#/definitions/network-profile"
- pservers:
+ property-key:
+ type: string
+ description: Key part of a key/value pair
+ property-value:
+ type: string
+ description: Value part of a key/value pair
+ relationship:
+ properties:
+ related-to:
+ type: string
+ description: A keyword provided by A&AI to indicate type of node.
+ related-link:
+ type: string
+ description: URL to the object in A&AI.
+ relationship-data:
type: array
- items:
- $ref: "#/definitions/pserver"
- virtual-data-centers:
+ items:
+ $ref: "#/definitions/relationship-data"
+ relationship-data:
+ required:
+ - relationship-key
+ - relationship-value
+ properties:
+ relationship-key:
+ type: string
+ description: A keyword provided by A&AI to indicate an attribute.
+ relationship-value:
+ type: string
+ description: Value of the attribute.
+ relationship-list:
+ properties:
+ relationship:
type: array
- items:
- $ref: "#/definitions/virtual-data-center"
- connector:
+ items:
+ $ref: "#/definitions/relationship"
+ reserved-prop-names:
description: |
- Collection of resource instances used to connect a variety of disparate inventory widgets
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
- ###### Related Nodes
- - TO virtual-data-center (Many2Many)
- - TO metadatum (comprises connector, Many2Many)
- - FROM service-instance
- required:
- - resource-instance-id
+ Internal map to define some reserved properties of a vertex
properties:
- resource-instance-id:
+ last-mod-source-of-truth:
type: string
- description: Unique id of resource instance.
- resource-version:
+ aai-node-type:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- model-invariant-id:
+ aai-created-ts:
+ type: integer
+ format: int64
+ aai-unique-key:
type: string
- description: the ASDC model id for this resource or service model.
- model-version-id:
+ aai-last-mod-ts:
+ type: integer
+ format: int64
+ source-of-truth:
type: string
- description: the ASDC model version for this resource or service model.
- persona-model-version:
+ aai-uri:
type: string
- description: the ASDC model version for this resource or service model.
- widget-model-id:
+ response-list:
+ description: |
+ Response container for the results of a named-query or model query
+ properties:
+ inventory-response-items:
+ type: object
+ $ref: "#/definitions/inventory-response-items"
+ result-data:
+ properties:
+ resource-type:
type: string
- description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
- widget-model-version:
+ description: The specific type of node in the A&AI graph
+ resource-link:
type: string
- description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ description: The URL to the specific resource
+ route-table-reference:
+ description: |
+ Openstack route table reference.
+ ###### Related Nodes
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)
+ required:
+ - route-table-reference-id
+ - route-table-reference-fqdn
+ properties:
+ route-table-reference-id:
+ type: string
+ description: Route Table Reference id, UUID assigned to this instance.
+ route-table-reference-fqdn:
+ type: string
+ description: FQDN entry in the route table.
+ resource-version:
+ type: string
+ description: Concurrency value
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- metadata:
- type: array
- items:
- $ref: "#/definitions/metadatum"
- connectors:
+ route-table-references:
description: |
- Collection of resource instances used to connect a variety of disparate inventory widgets
+ Collection of openstack route table references
properties:
- connector:
+ route-table-reference:
type: array
items:
- $ref: "#/definitions/connector"
- tunnel-xconnect:
+ $ref: "#/definitions/route-table-reference"
+ route-target:
description: |
- Represents the specifics of a tunnel cross connect piece of a resource that gets separately allotted
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Route target information
###### Related Nodes
- - FROM allotted-resource (is composed of tunnel-xconnect)
+ - TO vpn-binding( route-target org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2ONE)
required:
- - id
- - bandwidth-up-wan1
- - bandwidth-down-wan1
- - bandwidth-up-wan2
- - bandwidth-down-wan2
+ - global-route-target
+ - route-target-role
properties:
- id:
- type: string
- description: Allotted Resource id UUID assigned to this instance.
- bandwidth-up-wan1:
- type: string
- description: The WAN uplink bandwidth for WAN1
- bandwidth-down-wan1:
- type: string
- description: The WAN downlink bandwidth for WAN1
- bandwidth-up-wan2:
+ global-route-target:
type: string
- description: The WAN uplink bandwidth for WAN2
- bandwidth-down-wan2:
+ description: Number used to identify an RT, globally unique in the network
+ route-target-role:
type: string
- description: The WAN downlink bandwidth for WAN2
+ description: Role assigned to this route target
resource-version:
type: string
- description: Concurrency value
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- tunnel-xconnects:
+ route-targets:
description: |
- This object is used to store the specific tunnel cross connect aspects of an allotted resource
+ Collection of route target information
properties:
- tunnel-xconnect:
+ route-target:
type: array
items:
- $ref: "#/definitions/tunnel-xconnect"
- allotted-resource:
+ $ref: "#/definitions/route-target"
+ routing-instance:
description: |
- Represents a slice or partial piece of a resource that gets separately allotted
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
- ###### Related Nodes
- - TO generic-vnf (Many2Many)
- - TO l3-network (Many2Many)
- - TO instance-group (Many2Many)
- - TO network-policy (One2One)
- - TO vlan (Many2Many)
- - TO tunnel-xconnect (comprises allotted-resource, One2One)
- - FROM service-instance (is composed of allotted-resource)
- - FROM service-instance
+ ###### Related Nodes
+ - TO site-pair-set( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)
+ - FROM site-pair( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)
+ - ROUTING-INSTANCE is DELETED when these are DELETED SITE-PAIR
required:
- - id
+ - routing-instance-id
properties:
- id:
+ routing-instance-id:
type: string
- description: Allotted Resource id UUID assigned to this instance.
- description:
+ description: Unique id of routing instance
+ rpm-owner:
type: string
- description: The descriptive information assigned to this allotted resource instance
- selflink:
+ description: rpm owner
+ resource-version:
type: string
- description: Link back to more information in the controller
- model-invariant-id:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ site-pairs:
+ type: array
+ items:
+ $ref: "#/definitions/site-pair"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ routing-instances:
+ description: |
+ set of probes related to generic-vnf routing instance
+ properties:
+ routing-instance:
+ type: array
+ items:
+ $ref: "#/definitions/routing-instance"
+ sdn-zone-response:
+ properties:
+ oam-networks:
+ type: object
+ $ref: "#/definitions/oam-networks"
+ az-and-dvs-switches:
+ type: array
+ items:
+ $ref: "#/definitions/az-and-dvs-switches"
+ search:
+ properties:
+ edge-tag-query-result:
+ type: object
+ $ref: "#/definitions/edge-tag-query-result"
+ edge-tag-query-request:
+ type: object
+ $ref: "#/definitions/edge-tag-query-request"
+ search-results:
+ type: object
+ $ref: "#/definitions/search-results"
+ sdn-zone-response:
+ type: object
+ $ref: "#/definitions/sdn-zone-response"
+ search-results:
+ properties:
+ result-data:
+ type: array
+ items:
+ $ref: "#/definitions/result-data"
+ secondary-filt:
+ description: |
+ SecondaryFilt for performing a named-query or model query
+ secondary-filter:
+ properties:
+ property-name:
type: string
- description: the ASDC model id for this resource or service model.
- model-version-id:
+ filter-type:
type: string
- description: the ASDC model version for this resource or service model.
- persona-model-version:
+ property-value:
type: string
- description: the ASDC model version for this resource or service model.
+ secondary-filts:
+ description: |
+ SecondaryFilts for performing a named-query or model query
+ properties:
+ secondary-filt:
+ type: array
+ items:
+ $ref: "#/definitions/secondary-filt"
+ segmentation-assignment:
+ description: |
+ Openstack segmentation assignment.
+ ###### Related Nodes
+ - TO l3-network( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ required:
+ - segmentation-id
+ properties:
+ segmentation-id:
+ type: string
+ description: Route Table Reference id, UUID assigned to this instance.
resource-version:
type: string
description: Concurrency value
- orchestration-status:
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ segmentation-assignments:
+ description: |
+ Collection of openstack segmentation assignments
+ properties:
+ segmentation-assignment:
+ type: array
+ items:
+ $ref: "#/definitions/segmentation-assignment"
+ service:
+ description: |
+ Stand-in for service model definitions. Likely to be deprecated in favor of models from ASDC. Does not strictly map to ASDC services.
+ required:
+ - service-id
+ - service-description
+ properties:
+ service-id:
type: string
- description: Orchestration status
- operational-status:
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ service-description:
type: string
- description: Indicator for whether the resource is considered operational
- type:
+ description: Description of the service
+ service-selflink:
type: string
- description: Generic description of the type of allotted resource.
- role:
+ description: URL to endpoint where AAI can get more details
+ resource-version:
type: string
- description: role in the network that this resource will be providing.
- tunnel-xconnects:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ service-version:
+ type: string
+ description: service version
+ relationship-list:
type: array
items:
- $ref: "#/definitions/tunnel-xconnect"
+ $ref: "#/definitions/relationship"
+ service-capabilities:
+ description: |
+ Collection of service capabilities.
+ properties:
+ service-capability:
+ type: array
+ items:
+ $ref: "#/definitions/service-capability"
+ service-capability:
+ description: |
+ Early definition of server/resource pairings, likely to be replaced by models. No new use should be made of this.
+ ###### Related Nodes
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - SERVICE-CAPABILITY cannot be deleted if linked to AVAILABILITY-ZONE,OAM-NETWORK
+ required:
+ - service-type
+ - vnf-type
+ properties:
+ service-type:
+ type: string
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- allotted-resources:
+ service-design-and-creation:
description: |
- This object is used to store slices of services being offered
+ Namespace for objects managed by ASDC
properties:
- allotted-resource:
+ vnf-images:
type: array
- items:
- $ref: "#/definitions/allotted-resource"
+ items:
+ $ref: "#/definitions/vnf-image"
+ services:
+ type: array
+ items:
+ $ref: "#/definitions/service"
+ service-capabilities:
+ type: array
+ items:
+ $ref: "#/definitions/service-capability"
+ models:
+ type: array
+ items:
+ $ref: "#/definitions/model"
+ named-queries:
+ type: array
+ items:
+ $ref: "#/definitions/named-query"
service-instance:
description: |
Instance of a service
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
- ###### Related Nodes
- - TO cvlan-tag (Many2Many)
- - TO pnf (One2Many)
- - TO connector (Many2Many)
- - TO metadatum (comprises service-instance, Many2Many)
- - TO logical-link (Many2Many)
- - TO vlan (One2Many)
- - TO service-instance (One2Many)
- - TO ctag-assignment (One2Many)
- - TO instance-group (Many2Many)
- - TO allotted-resource (comprises service-instance, Many2Many)
- - TO allotted-resource (Many2Many)
- - FROM generic-vnf
- - FROM l3-network
- - FROM service-subscription (is composed of service-instance)
- - FROM vce
- - FROM service-instance
+ ###### Related Nodes
+ - TO generic-vnf( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)
+ - TO l3-network( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)
+ - TO allotted-resource( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY)
+ - TO connector( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)
+ - TO ctag-assignment( service-instance org.onap.relationships.inventory.Uses ctag-assignment, ONE2MANY)
+ - TO cvlan-tag( service-instance org.onap.relationships.inventory.ComposedOf cvlan-tag, MANY2MANY)
+ - TO instance-group( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO logical-link( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - TO pnf( service-instance org.onap.relationships.inventory.ComposedOf pnf, ONE2MANY)
+ - TO service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)
+ - TO vlan( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)
+ - TO service-subscription( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)
+ - TO vce( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)
+ - SERVICE-INSTANCE is DELETED when these are DELETED ALLOTTED-RESOURCE,METADATUM
+ - SERVICE-INSTANCE deletion means associated objects of these types are also DELETED:LOGICAL-LINK
required:
- service-instance-id
properties:
@@ -39596,12 +52510,11 @@ definitions:
service-subscription:
description: |
Object that group service instances.
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
###### Related Nodes
- - TO service-instance (comprises service-subscription, Many2Many)
- - FROM customer (is composed of service-subscription)
- - FROM tenant
+ - TO customer( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)
+ - TO tenant( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)
+ - SERVICE-SUBSCRIPTION is DELETED when these are DELETED SERVICE-INSTANCE
required:
- service-type
properties:
@@ -39630,73 +52543,116 @@ definitions:
type: array
items:
$ref: "#/definitions/service-subscription"
- customer:
+ services:
+ description: |
+ Collection of service model definitions. Likely to be deprecated in favor of models from ASDC.
+ properties:
+ service:
+ type: array
+ items:
+ $ref: "#/definitions/service"
+ site-pair:
description: |
- customer identifiers to provide linkage back to BSS information.
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
###### Related Nodes
- - TO service-subscription (comprises customer, Many2Many)
+ - TO routing-instance( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)
+ - FROM class-of-service( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)
+ - SITE-PAIR is DELETED when these are DELETED CLASS-OF-SERVICE
required:
- - global-customer-id
- - subscriber-name
- - subscriber-type
+ - site-pair-id
properties:
- global-customer-id:
+ site-pair-id:
type: string
- description: Global customer id used across ECOMP to uniquely identify customer.
- subscriber-name:
+ description: unique identifier of probe
+ source-ip:
type: string
- description: Subscriber name, an alternate way to retrieve a customer.
- subscriber-type:
+ description: Prefix address
+ destination-ip:
type: string
- description: Subscriber type, a way to provide VID with only the INFRA customers.
+ description: Prefix address
+ ip-version:
+ type: string
+ description: ip version, v4, v6
+ destination-hostname:
+ type: string
+ description: Hostname of the destination equipment to which SLAs are measured against.
+ destination-equip-type:
+ type: string
+ description: The type of destinatination equipment. Could be Router, etc.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- service-subscriptions:
+ classes-of-service:
type: array
items:
- $ref: "#/definitions/service-subscription"
+ $ref: "#/definitions/class-of-service"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- customers:
+ site-pair-set:
description: |
- Collection of customer identifiers to provide linkage back to BSS information.
+ Set of instances for probes used to measure service level agreements
+ ###### Related Nodes
+ - TO generic-vnf( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM routing-instance( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)
+ - SITE-PAIR-SET is DELETED when these are DELETED ROUTING-INSTANCE
+ required:
+ - site-pair-set-id
properties:
- customer:
+ site-pair-set-id:
+ type: string
+ description: Unique id of site pair set.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ routing-instances:
type: array
- items:
- $ref: "#/definitions/customer"
- business:
+ items:
+ $ref: "#/definitions/routing-instance"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ site-pair-sets:
description: |
- Namespace for business related constructs
+ Collection of sets of instances for probes related to generic-vnf
properties:
- connectors:
+ site-pair-set:
type: array
- items:
- $ref: "#/definitions/connector"
- customers:
+ items:
+ $ref: "#/definitions/site-pair-set"
+ site-pairs:
+ description: |
+ probe within a set
+ properties:
+ site-pair:
type: array
- items:
- $ref: "#/definitions/customer"
- vnf-image:
+ items:
+ $ref: "#/definitions/site-pair"
+ snapshot:
description: |
- Image object that pertain to a VNF that doesn't have associated vservers. This is a kludge.
- ###### Default Delete Scope
- ERROR_IF_ANY_IN_EDGES
+ Openstack snapshot
###### Related Nodes
- - FROM generic-vnf
+ - TO cloud-region( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)
required:
- - vnf-image-uuid
- - application
- - application-vendor
+ - snapshot-id
properties:
- vnf-image-uuid:
+ snapshot-id:
type: string
- description: Unique ID of this asset
+ description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
+ snapshot-name:
+ type: string
+ description: Snapshot name
+ snapshot-architecture:
+ type: string
+ description: Operating system architecture
+ snapshot-os-distro:
+ type: string
+ description: The common name of the operating system distribution in lowercase
+ snapshot-os-version:
+ type: string
+ description: The operating system version as specified by the distributor.
application:
type: string
description: The application that the image instantiates.
@@ -39706,9 +52662,12 @@ definitions:
application-version:
type: string
description: The version of the application.
- selflink:
+ snapshot-selflink:
type: string
description: URL to endpoint where AAI can get more details
+ prev-snapshot-id:
+ type: string
+ description: This field contains the UUID of the previous snapshot (if any).
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
@@ -39716,542 +52675,1106 @@ definitions:
type: array
items:
$ref: "#/definitions/relationship"
- vnf-images:
+ snapshots:
description: |
- Collection of image objects that pertain to a VNF that doesn't have associated vservers. This is a kludge.
+ Collection of openstack snapshots
properties:
- vnf-image:
+ snapshot:
type: array
items:
- $ref: "#/definitions/vnf-image"
- service:
+ $ref: "#/definitions/snapshot"
+ sriov-pf:
description: |
- Stand-in for service model definitions. Likely to be deprecated in favor of models from ASDC. Does not strictly map to ASDC services.
- ###### Default Delete Scope
- ERROR_IF_ANY_IN_EDGES
+ SR-IOV Physical Function
+ ###### Related Nodes
+ - TO p-interface( sriov-pf org.onap.relationships.inventory.BelongsTo p-interface, ONE2ONE)
+ - FROM sriov-vf( sriov-vf org.onap.relationships.inventory.Uses sriov-pf, MANY2ONE)
required:
- - service-id
- - service-description
+ - pf-pci-id
properties:
- service-id:
- type: string
- description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
- service-description:
+ pf-pci-id:
type: string
- description: Description of the service
- service-selflink:
- type: string
- description: URL to endpoint where AAI can get more details
+ description: Identifier for the sriov-pf
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- service-version:
- type: string
- description: service version
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- services:
+ sriov-pfs:
description: |
- Collection of service model definitions. Likely to be deprecated in favor of models from ASDC.
+ Collection of SR-IOV Physical Functions.
properties:
- service:
+ sriov-pf:
type: array
items:
- $ref: "#/definitions/service"
- service-capability:
+ $ref: "#/definitions/sriov-pf"
+ sriov-vf:
description: |
- Early definition of server/resource pairings, likely to be replaced by models. No new use should be made of this.
- ###### Default Delete Scope
- ERROR_IF_ANY_IN_EDGES
+ SR-IOV Virtual Function (not to be confused with virtual network function)
###### Related Nodes
- - FROM availability-zone
- - FROM oam-network
+ - TO l-interface( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)
required:
- - service-type
- - vnf-type
+ - pci-id
properties:
- service-type:
+ pci-id:
type: string
- description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
- vnf-type:
+ description: PCI ID used to identify the sriov-vf
+ vf-vlan-filter:
type: string
- description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM.
+ vf-mac-filter:
+ type: string
+ description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM.
+ vf-vlan-strip:
+ type: boolean
+ description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM.
+ vf-vlan-anti-spoof-check:
+ type: boolean
+ description: This option ensures anti VLAN spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
+ vf-mac-anti-spoof-check:
+ type: boolean
+ description: This option ensures anti MAC spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
+ vf-mirrors:
+ type: string
+ description: This option defines the set of Mirror objects which essentially mirrors the traffic from source to set of collector VNF Ports.
+ vf-broadcast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows all broadcast traffic to reach the VM
+ vf-unknown-multicast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows unknown multicast traffic to reach the VM
+ vf-unknown-unicast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows unknown unicast traffic to reach the VM
+ vf-insert-stag:
+ type: boolean
+ description: This option, if set to true, instructs to insert outer tag after traffic comes out of VM.
+ vf-link-status:
+ type: string
+ description: This option is used to set the link status. Valid values as of 1607 are on, off, and auto.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
+ type: string
+ description: Neutron network id of the interface
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- service-capabilities:
+ sriov-vfs:
description: |
- Collection of service capabilities.
+ Collection of SR-IOV Virtual Functions.
properties:
- service-capability:
+ sriov-vf:
type: array
items:
- $ref: "#/definitions/service-capability"
- element-choice-set:
+ $ref: "#/definitions/sriov-vf"
+ start-node-filter:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ subnet:
description: |
- This is how we would capture constraints defining allowed sets of elements.
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
###### Related Nodes
- - TO model-element (comprises element-choice-set, One2Many)
- - FROM constrained-element-set (is composed of element-choice-set)
+ - TO l3-network( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - SUBNET cannot be deleted if linked to L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST
required:
- - element-choice-set-uuid
- - element-choice-set-name
+ - subnet-id
+ - dhcp-enabled
properties:
- element-choice-set-uuid:
+ subnet-id:
type: string
- element-choice-set-name:
+ description: Subnet ID, should be UUID.
+ subnet-name:
type: string
- cardinality:
+ description: Name associated with the subnet.
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of this subnet
+ gateway-address:
+ type: string
+ description: gateway ip address
+ network-start-address:
+ type: string
+ description: network start address
+ cidr-mask:
+ type: string
+ description: cidr mask
+ ip-version:
+ type: string
+ description: ip version
+ orchestration-status:
type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ dhcp-enabled:
+ type: boolean
+ dhcp-start:
+ type: string
+ description: the start address reserved for use by dhcp
+ dhcp-end:
+ type: string
+ description: the last address reserved for use by dhcp
resource-version:
type: string
- model-elements:
- type: array
- items:
- $ref: "#/definitions/model-element"
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- element-choice-sets:
+ subnets:
properties:
- element-choice-set:
+ subnet:
type: array
items:
- $ref: "#/definitions/element-choice-set"
- constrained-element-set:
+ $ref: "#/definitions/subnet"
+ tagged-inventory-item-list:
+ properties:
+ inventory-item:
+ type: array
+ items:
+ $ref: "#/definitions/inventory-item"
+ tenant:
description: |
- This is how we would capture constraints defining allowed sets of elements.
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
+ Openstack tenant
###### Related Nodes
- - TO element-choice-set (comprises constrained-element-set, One2Many)
- - FROM model-element (is composed of constrained-element-set)
- - FROM model-constraint (is composed of constrained-element-set)
+ - TO cloud-region( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO group-assignment( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)
+ - TO l3-network( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO volume-group( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - FROM service-subscription( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)
+ - FROM vserver( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)
+ - TENANT cannot be deleted if linked to VSERVER
required:
- - constrained-element-set-uuid
- - constraint-type
- - check-type
+ - tenant-id
+ - tenant-name
properties:
- constrained-element-set-uuid:
- type: string
- constraint-type:
+ tenant-id:
type: string
- check-type:
+ description: Unique id relative to the cloud-region.
+ tenant-name:
type: string
+ description: Readable name of tenant
resource-version:
type: string
- element-choice-sets:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ vservers:
type: array
items:
- $ref: "#/definitions/element-choice-set"
+ $ref: "#/definitions/vserver"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- constrained-element-sets:
+ tenants:
+ description: |
+ Collection of openstack tenants.
properties:
- constrained-element-set:
+ tenant:
type: array
items:
- $ref: "#/definitions/constrained-element-set"
- model-constraint:
+ $ref: "#/definitions/tenant"
+ tunnel-xconnect:
description: |
- This is how we would capture constraints defining allowed sets of elements.
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
+ Represents the specifics of a tunnel cross connect piece of a resource that gets separately allotted
###### Related Nodes
- - TO constrained-element-set (comprises model-constraint, One2Many)
- - FROM model-element (is composed of model-constraint)
+ - TO allotted-resource( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)
required:
- - model-constraint-uuid
- - constrained-element-set-uuid-to-replace
+ - id
+ - bandwidth-up-wan1
+ - bandwidth-down-wan1
+ - bandwidth-up-wan2
+ - bandwidth-down-wan2
properties:
- model-constraint-uuid:
+ id:
type: string
- constrained-element-set-uuid-to-replace:
+ description: Allotted Resource id UUID assigned to this instance.
+ bandwidth-up-wan1:
type: string
- constrained-element-sets:
- type: array
- items:
- $ref: "#/definitions/constrained-element-set"
+ description: The WAN uplink bandwidth for WAN1
+ bandwidth-down-wan1:
+ type: string
+ description: The WAN downlink bandwidth for WAN1
+ bandwidth-up-wan2:
+ type: string
+ description: The WAN uplink bandwidth for WAN2
+ bandwidth-down-wan2:
+ type: string
+ description: The WAN downlink bandwidth for WAN2
resource-version:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- model-constraints:
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ tunnel-xconnects:
+ description: |
+ This object is used to store the specific tunnel cross connect aspects of an allotted resource
properties:
- model-constraint:
+ tunnel-xconnect:
type: array
items:
- $ref: "#/definitions/model-constraint"
- model-element:
+ $ref: "#/definitions/tunnel-xconnect"
+ update:
description: |
- Defines how other models combine to make up a higher-level model.
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
+ Serves a PATCH like function. Does not enforce concurrency control. Clear each usage with AAI team.
+ required:
+ - update-node-type
+ properties:
+ update-node-type:
+ type: string
+ update-node-key:
+ type: array
+ items:
+ $ref: "#/definitions/update-node-key"
+ update-node-uri:
+ type: string
+ action:
+ type: array
+ items:
+ $ref: "#/definitions/action"
+ update-node-key:
+ properties:
+ key-name:
+ type: string
+ key-value:
+ type: string
+ vce:
+ description: |
+ Virtual Customer Edge Router, used specifically for Gamma. This object is deprecated.
###### Related Nodes
- - TO model-ver (Many2One)
- - TO model-element (comprises model-element, One2Many)
- - TO model-constraint (comprises model-element, One2Many)
- - TO constrained-element-set (comprises model-element, One2Many)
- - FROM model-ver (is composed of model-element)
- - FROM element-choice-set (is composed of model-element)
- - FROM model-element (is composed of model-element)
+ - TO availability-zone( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - TO complex( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)
+ - TO vserver( vce tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM entitlement( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM license( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM port-group( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)
+ - VCE is DELETED when these are DELETED ENTITLEMENT,LICENSE,PORT-GROUP
required:
- - model-element-uuid
- - new-data-del-flag
- - cardinality
+ - vnf-id
+ - vnf-name
+ - vnf-type
properties:
- model-element-uuid:
+ vnf-id:
type: string
- new-data-del-flag:
+ description: Unique id of VNF. This is unique across the graph.
+ vnf-name:
type: string
- description: Indicates whether this element was created as part of instantiation from this model
- cardinality:
+ description: Name of VNF.
+ vnf-name2:
type: string
- description: How many of this type of element are required/allowed
- linkage-points:
+ description: Alternate name of VNF.
+ vnf-type:
type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ service-id:
+ type: string
+ description: Unique identifier of service, does not strictly map to ASDC services, SOON TO BE DEPRECATED.
+ regional-resource-zone:
+ type: string
+ description: Regional way of organizing pservers, source of truth should define values
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ operational-status:
+ type: string
+ description: Indicator for whether the resource is considered operational
+ license-key:
+ type: string
+ description: OBSOLETE - do not use
+ equipment-role:
+ type: string
+ description: Network role being played by this VNF
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ vpe-id:
+ type: string
+ description: Unique ID of VPE connected to this VCE.
+ v6-vce-wan-address:
+ type: string
+ description: Valid v6 IP address for the WAN Link on this router. Implied length of /64.
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure vce, also used for troubleshooting and is IP used for traps generated by VCE.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- model-elements:
+ ipv4-loopback0-address:
+ type: string
+ description: Loopback0 address
+ entitlement-resource-uuid:
+ type: string
+ description: OBSOLETE - see child relationships
+ port-groups:
type: array
items:
- $ref: "#/definitions/model-element"
- description: Defines how other models combine to make up a higher-level model
- model-constraints:
+ $ref: "#/definitions/port-group"
+ licenses:
type: array
items:
- $ref: "#/definitions/model-constraint"
- description: Describes new constraints on this model element that are not part of that model's definition
+ $ref: "#/definitions/license"
+ entitlements:
+ type: array
+ items:
+ $ref: "#/definitions/entitlement"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- model-elements:
+ vces:
+ description: |
+ Collection of Virtual Customer Edge Routers, used specifically for Gamma. This object is deprecated.
properties:
- model-element:
+ vce:
type: array
items:
- $ref: "#/definitions/model-element"
- model-ver:
+ $ref: "#/definitions/vce"
+ vf-module:
description: |
- Subgraph definition provided by ASDC to describe a specific version of an inventory asset and its connections related to ASDC models
- ###### Default Delete Scope
- ERROR_4_IN_EDGES_OR_CASCADE
+ a deployment unit of VNFCs
###### Related Nodes
- - TO model-element (comprises model-ver, One2Many)
- - TO metadatum (comprises model-ver, One2Many)
- - FROM model (is composed of model-ver)
- - FROM model-element
+ - TO generic-vnf( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO l3-network( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)
+ - TO vnfc( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)
+ - TO volume-group( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)
+ - TO vserver( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)
+ - VF-MODULE cannot be deleted if linked to VNFC
required:
- - model-version-id
- - model-name
- - model-version
+ - vf-module-id
+ - is-base-vf-module
properties:
- model-version-id:
+ vf-module-id:
type: string
- description: Unique identifier corresponding to one version of a model in ASDC
- model-name:
+ description: Unique ID of vf-module.
+ vf-module-name:
type: string
- description: Name of the model, which can change from version to version.
- model-version:
+ description: Name of vf-module
+ heat-stack-id:
type: string
- description: Version
- model-description:
+ description: Heat stack id corresponding to this instance.
+ orchestration-status:
type: string
- description: Description
+ description: orchestration status of this vf-module, mastered by MSO
+ is-base-vf-module:
+ type: boolean
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- model-elements:
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ model-customization-id:
+ type: string
+ description: captures the id of all the configuration used to customize the resource for the service.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ contrail-service-instance-fqdn:
+ type: string
+ description: the Contrail unique ID for a service-instance
+ module-index:
+ type: integer
+ format: int32
+ description: the index will track the number of modules of a given type that have been deployed in a VNF, starting with 0, and always choosing the lowest available digit
+ selflink:
+ type: string
+ description: Path to the controller object.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/model-element"
- metadata:
+ $ref: "#/definitions/relationship"
+ vf-modules:
+ description: |
+ Collection of vf-modules, a deployment unit of VNFCs
+ properties:
+ vf-module:
type: array
- items:
- $ref: "#/definitions/metadatum"
+ items:
+ $ref: "#/definitions/vf-module"
+ vig-server:
+ description: |
+ vig-server contains information about a vig server used for IPSec-configuration. Populated by SDN-C from 1607
+ ###### Related Nodes
+ - TO ipsec-configuration( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)
+ required:
+ - vig-address-type
+ properties:
+ vig-address-type:
+ type: string
+ description: indicates whether the VIG is for AVPN or INTERNET
+ ipaddress-v4-vig:
+ type: string
+ description: v4 IP of the vig server
+ ipaddress-v6-vig:
+ type: string
+ description: v6 IP of the vig server
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- model-vers:
+ vig-servers:
properties:
- model-ver:
+ vig-server:
type: array
items:
- $ref: "#/definitions/model-ver"
- model:
+ $ref: "#/definitions/vig-server"
+ vip-ipv4-address-list:
description: |
- Subgraph definition provided by ASDC to describe an inventory asset and its connections related to ASDC models, independent of version
- ###### Default Delete Scope
- ERROR_4_IN_EDGES_OR_CASCADE
+ IPv4 Address Range
###### Related Nodes
- - TO model-ver (comprises model, One2Many)
- - FROM named-query
- - FROM named-query-element
- - FROM instance-group
+ - TO cloud-region( vip-ipv4-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO instance-group( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO subnet( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv4-address-list, MANY2MANY)
required:
- - model-invariant-id
- - model-type
+ - vip-ipv4-address
properties:
- model-invariant-id:
+ vip-ipv4-address:
type: string
- description: Unique identifier corresponding to the main definition of a model in ASDC
- model-type:
+ description: IP address
+ vip-ipv4-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 32 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ resource-version:
type: string
- description: Type of the model, e.g., service, resource, widget, etc.
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
+ type: string
+ description: Neutron network id of the interface that address belongs to
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of subnet that address belongs to
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ vip-ipv6-address-list:
+ description: |
+ IPv6 Address Range
+ ###### Related Nodes
+ - TO cloud-region( vip-ipv6-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO instance-group( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO subnet( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv6-address-list, MANY2MANY)
+ required:
+ - vip-ipv6-address
+ properties:
+ vip-ipv6-address:
+ type: string
+ description: IP address
+ vip-ipv6-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 128 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- model-vers:
+ neutron-network-id:
+ type: string
+ description: Neutron network id of the interface that address belongs to
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of subnet that address belongs to
+ relationship-list:
type: array
items:
- $ref: "#/definitions/model-ver"
+ $ref: "#/definitions/relationship"
+ virtual-data-center:
+ description: |
+ Virtual organization of cloud infrastructure elements in a data center context
+ ###### Related Nodes
+ - FROM connector( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ required:
+ - vdc-id
+ - vdc-name
+ properties:
+ vdc-id:
+ type: string
+ description: Unique ID of the vdc
+ vdc-name:
+ type: string
+ description: Name of the virtual data center
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- models:
+ virtual-data-centers:
description: |
- Collection of subgraph definitions provided by ASDC to describe the inventory assets and their connections related to ASDC models
+ Virtual organization of cloud infrastructure elements in a data center context
properties:
- model:
+ virtual-data-center:
type: array
items:
- $ref: "#/definitions/model"
- related-lookup:
+ $ref: "#/definitions/virtual-data-center"
+ vlan:
description: |
- TBD
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
+ Definition of vlan
###### Related Nodes
- - FROM named-query-element (is composed of related-lookup)
+ - TO l-interface( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)
+ - TO logical-link( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - TO multicast-configuration( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ - VLAN is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST
+ - VLAN deletion means associated objects of these types are also DELETED:LOGICAL-LINK
required:
- - related-lookup-uuid
- - source-node-type
- - source-node-property
- - target-node-type
- - target-node-property
+ - vlan-interface
+ - in-maint
properties:
- related-lookup-uuid:
+ vlan-interface:
type: string
- source-node-type:
+ description: String that identifies the interface
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ resource-version:
type: string
- source-node-property:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ speed-value:
type: string
- target-node-type:
+ description: Captures the numeric part of the speed
+ speed-units:
type: string
- target-node-property:
+ description: Captures the units corresponding to the speed
+ vlan-description:
type: string
- property-collect-list:
+ description: Used to describe (the service associated with) the vlan
+ backdoor-connection:
type: string
- resource-version:
+ description: Whether customer is going to use this VLAN for backdoor connection to another customer premise device.
+ vpn-id:
+ type: string
+ description: This indicates the customers VPN ID associated with this vlan
+ orchestration-status:
type: string
+ description: Status of a vnf's vlan interface, on which the customer circuit resides, mastered by SDN-C.
+ in-maint:
+ type: boolean
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- related-lookups:
+ l3-interface-ipv4-address-list:
+ type: array
+ items:
+ $ref: "#/definitions/l3-interface-ipv4-address-list"
+ l3-interface-ipv6-address-list:
+ type: array
+ items:
+ $ref: "#/definitions/l3-interface-ipv6-address-list"
+ vlans:
properties:
- related-lookup:
+ vlan:
type: array
items:
- $ref: "#/definitions/related-lookup"
- property-constraint:
+ $ref: "#/definitions/vlan"
+ vnf:
description: |
- TBD
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
+ Abstract vnf class
+ required:
+ - vnf-id
+ properties:
+ vnf-id:
+ type: string
+ description: Unique id of VNF. This is unique across the graph.
+ vnf-image:
+ description: |
+ Image object that pertain to a VNF that doesn't have associated vservers. This is a kludge.
###### Related Nodes
- - FROM named-query-element (is composed of property-constraint)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)
+ - VNF-IMAGE cannot be deleted if linked to GENERIC-VNF
required:
- - property-constraint-uuid
- - constraint-type
- - property-name
- - property-value
+ - vnf-image-uuid
+ - application
+ - application-vendor
properties:
- property-constraint-uuid:
+ vnf-image-uuid:
type: string
- constraint-type:
+ description: Unique ID of this asset
+ application:
type: string
- property-name:
+ description: The application that the image instantiates.
+ application-vendor:
type: string
- property-value:
+ description: The vendor of the application.
+ application-version:
type: string
+ description: The version of the application.
+ selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
resource-version:
type: string
- property-constraints:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ vnf-images:
+ description: |
+ Collection of image objects that pertain to a VNF that doesn't have associated vservers. This is a kludge.
properties:
- property-constraint:
+ vnf-image:
type: array
items:
- $ref: "#/definitions/property-constraint"
- named-query-element:
+ $ref: "#/definitions/vnf-image"
+ vnfc:
description: |
- TBD
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
###### Related Nodes
- - TO named-query-element (comprises named-query-element, Many2Many)
- - TO model (Many2One)
- - TO property-constraint (comprises named-query-element, One2Many)
- - TO related-lookup (comprises named-query-element, One2Many)
- - FROM named-query (is composed of named-query-element)
- - FROM named-query-element (is composed of named-query-element)
+ - TO generic-vnf( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vserver( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)
required:
- - named-query-element-uuid
+ - vnfc-name
+ - vnfc-function-code
+ - vnfc-type
+ - in-maint
+ - is-closed-loop-disabled
properties:
- named-query-element-uuid:
+ vnfc-name:
type: string
- property-collect-list:
+ description: Unique ID of vnfc.
+ vnfc-function-code:
type: string
- resource-version:
+ description: function code
+ vnfc-type:
type: string
- property-limit-desc:
+ description: type
+ prov-status:
type: string
- do-not-output:
+ description: prov status of this vnfc
+ orchestration-status:
type: string
- named-query-elements:
+ description: Orchestration status of this VNF, mastered by APP-C
+ ipaddress-v4-oam-vip:
+ type: string
+ description: Oam V4 vip address of this vnfc
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
+ group-notation:
+ type: string
+ description: Group notation of VNFC
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/named-query-element"
- related-lookups:
+ $ref: "#/definitions/relationship"
+ vnfcs:
+ description: |
+ virtual network components associated with a vserver from application controller.
+ properties:
+ vnfc:
+ type: array
+ items:
+ $ref: "#/definitions/vnfc"
+ volume:
+ description: |
+ Ephemeral Block storage volume.
+ ###### Related Nodes
+ - FROM vserver (PARENT of volume, vserver tosca.relationships.AttachesTo volume)
+ required:
+ - volume-id
+ - volume-selflink
+ properties:
+ volume-id:
+ type: string
+ description: Unique ID of block storage volume relative to the vserver.
+ volume-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/related-lookup"
- property-constraints:
+ $ref: "#/definitions/relationship"
+ volume-group:
+ description: |
+ Persistent block-level storage.
+ ###### Related Nodes
+ - TO cloud-region( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO complex( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ required:
+ - volume-group-id
+ - volume-group-name
+ - vnf-type
+ properties:
+ volume-group-id:
+ type: string
+ description: Unique ID of volume-group.
+ volume-group-name:
+ type: string
+ description: Name of the volume group.
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this volume-group
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ orchestration-status:
+ type: string
+ description: Orchestration status of this volume-group
+ model-customization-id:
+ type: string
+ description: captures the id of all the configuration used to customize the resource for the service.
+ vf-module-model-customization-id:
+ type: string
+ description: helps relate the volume group to the vf-module whose components will require the volume group
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/property-constraint"
+ $ref: "#/definitions/relationship"
+ volume-groups:
+ description: |
+ Collection of persistent block-level storage.
+ properties:
+ volume-group:
+ type: array
+ items:
+ $ref: "#/definitions/volume-group"
+ volumes:
+ description: |
+ Collection of ephemeral Block storage volumes.
+ properties:
+ volume:
+ type: array
+ items:
+ $ref: "#/definitions/volume"
+ vpls-pe:
+ description: |
+ VPLS Provider Edge routers.
+ ###### Related Nodes
+ - TO complex( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO ctag-pool( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - VPLS-PE is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
+ required:
+ - equipment-name
+ properties:
+ equipment-name:
+ type: string
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address).
+ equipment-role:
+ type: string
+ description: Client should send valid enumerated value, e.g., VPLS-PE.
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Temporary location for stag to get to VCE
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- named-query-elements:
+ p-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/p-interface"
+ lag-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/lag-interface"
+ vpls-pes:
+ description: |
+ Collection of VPLS Provider Edge routers
properties:
- named-query-element:
+ vpls-pe:
type: array
items:
- $ref: "#/definitions/named-query-element"
- named-query:
+ $ref: "#/definitions/vpls-pe"
+ vpn-binding:
description: |
- TBD
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
+ VPN binding
###### Related Nodes
- - TO model (One2Many)
- - TO named-query-element (comprises named-query, One2One)
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - FROM route-target( route-target org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2ONE)
+ - VPN-BINDING cannot be deleted if linked to L3-NETWORK,LOGICAL-LINK
+ - VPN-BINDING is DELETED when these are DELETED ROUTE-TARGET
required:
- - named-query-uuid
- - named-query-name
- - named-query-version
+ - vpn-id
+ - vpn-name
properties:
- named-query-uuid:
+ vpn-id:
type: string
- named-query-name:
+ description: VPN ID, globally unique within A&AI
+ vpn-name:
type: string
- named-query-version:
+ description: VPN Name
+ vpn-platform:
type: string
- required-input-param:
+ description: the platform associated with the VPN example AVPN, Mobility
+ vpn-type:
type: string
- description:
+ description: Type of the vpn, should be taken from enumerated/valid values
+ route-distinguisher:
type: string
+ description: Used to distinguish the distinct VPN routes of separate customers who connect to the provider in an MPLS network.
resource-version:
type: string
- named-query-elements:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ route-targets:
type: array
items:
- $ref: "#/definitions/named-query-element"
+ $ref: "#/definitions/route-target"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- named-queries:
+ description: l3-networks relate to vpn-bindings
+ vpn-bindings:
properties:
- named-query:
+ vpn-binding:
type: array
items:
- $ref: "#/definitions/named-query"
- service-design-and-creation:
+ $ref: "#/definitions/vpn-binding"
+ vserver:
description: |
- Namespace for objects managed by ASDC
+ Virtual Servers, aka virtual machine or VM.
+ ###### Related Nodes
+ - TO tenant( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)
+ - TO flavor( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)
+ - TO image( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)
+ - TO pserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)
+ - TO snapshot( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)
+ - TO volume (CHILD of vserver, vserver tosca.relationships.AttachesTo volume, ONE2MANY)
+ - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM vce( vce tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)
+ - FROM vnfc( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)
+ - VSERVER is DELETED when these are DELETED L-INTERFACE
+ - VSERVER deletion means associated objects of these types are also DELETED:VOLUME
+ required:
+ - vserver-id
+ - vserver-name
+ - vserver-selflink
+ - in-maint
+ - is-closed-loop-disabled
properties:
- vnf-images:
+ vserver-id:
+ type: string
+ description: Unique identifier for this vserver relative to its tenant
+ vserver-name:
+ type: string
+ description: Name of vserver
+ vserver-name2:
+ type: string
+ description: Alternative name of vserver
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ vserver-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ volumes:
type: array
items:
- $ref: "#/definitions/vnf-image"
- services:
+ $ref: "#/definitions/volume"
+ relationship-list:
type: array
items:
- $ref: "#/definitions/service"
- service-capabilities:
+ $ref: "#/definitions/relationship"
+ l-interfaces:
type: array
items:
- $ref: "#/definitions/service-capability"
- models:
+ $ref: "#/definitions/l-interface"
+ vservers:
+ description: |
+ Collection of virtual Servers, aka virtual machines or VMs.
+ properties:
+ vserver:
type: array
- items:
- $ref: "#/definitions/model"
- named-queries:
+ items:
+ $ref: "#/definitions/vserver"
+ zone:
+ description: |
+ A zone is a grouping of assets in a location homing to the same connections into the CBB
+ ###### Related Nodes
+ - TO complex( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM pnf( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ required:
+ - zone-id
+ - zone-name
+ - design-type
+ - zone-context
+ properties:
+ zone-id:
+ type: string
+ description: Code assigned by AIC to the zone
+ zone-name:
+ type: string
+ description: English name associated with the zone
+ design-type:
+ type: string
+ description: Design of zone [Medium/Large?]
+ zone-context:
+ type: string
+ description: Context of zone [production/test]
+ status:
+ type: string
+ description: Status of a zone.
+ resource-version:
+ type: string
+ description: Concurrency value
+ relationship-list:
type: array
items:
- $ref: "#/definitions/named-query"
- logical-link:
+ $ref: "#/definitions/relationship"
+ zones:
description: |
- Logical links generally connect l-interfaces but are used to express logical connectivity between two points
- ###### Default Delete Scope
- THIS_NODE_ONLY
- ###### Related Nodes
- - TO lag-link (Many2Many)
- - TO pnf (Many2Many)
- - TO logical-link (One2Many)
- - TO generic-vnf (Many2Many)
- - TO pserver (Many2Many)
- - TO cloud-region (Many2Many)
- - TO vpn-binding (Many2Many)
- - FROM l-interface
- - FROM lag-interface
- - FROM p-interface
- - FROM service-instance
- - FROM virtual-data-center
- - FROM vlan
- - FROM logical-link
- required:
- - link-name
- - link-type
+ Collection of zones
properties:
- link-name:
+ zone:
+ type: array
+ items:
+ $ref: "#/definitions/zone"
+patchDefinitions:
+ aai-internal:
+ properties:
+ property-name:
type: string
- description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
- link-type:
+ property-value:
type: string
- description: Type of logical link, e.g., evc
- speed-value:
+ action:
+ properties:
+ action-type:
type: string
- description: Captures the numeric part of the speed
- speed-units:
+ action-data:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/action-data"
+ action-data:
+ properties:
+ property-name:
type: string
- description: Captures the units corresponding to the speed
- ip-version:
+ property-value:
type: string
- description: v4, v6, or ds for dual stack
- routing-protocol:
+ actions:
+ description: |
+ APIs that are more action related than REST (e.g., notify, update).
+ properties:
+ update:
+ type: object
+ $ref: "#/patchDefinitions/update"
+ notify:
+ type: object
+ $ref: "#/patchDefinitions/notify"
+ allotted-resource:
+ description: |
+ Represents a slice or partial piece of a resource that gets separately allotted
+ ###### Related Nodes
+ - TO generic-vnf( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY)
+ - TO instance-group( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO l3-network( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY)
+ - TO network-policy( allotted-resource org.onap.relationships.inventory.Uses network-policy, ONE2ONE)
+ - TO vlan( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY)
+ - TO service-instance( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM tunnel-xconnect( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY)
+ - ALLOTTED-RESOURCE is DELETED when these are DELETED TUNNEL-XCONNECT
+ required:
+ - id
+ properties:
+ id:
type: string
- description: For example, static or BGP
- resource-version:
+ description: Allotted Resource id UUID assigned to this instance.
+ description:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ description: The descriptive information assigned to this allotted resource instance
+ selflink:
+ type: string
+ description: Link back to more information in the controller
model-invariant-id:
type: string
description: the ASDC model id for this resource or service model.
@@ -40261,51 +53784,72 @@ definitions:
persona-model-version:
type: string
description: the ASDC model version for this resource or service model.
- widget-model-id:
+ allotted-resources:
+ description: |
+ This object is used to store slices of services being offered
+ properties:
+ allotted-resource:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/allotted-resource"
+ availability-zone:
+ description: |
+ Availability zone, a collection of compute hosts/pservers
+ ###### Related Nodes
+ - TO complex( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO service-capability( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - TO cloud-region( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM ctag-pool( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM dvs-switch( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - FROM pserver( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)
+ - FROM vce( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - AVAILABILITY-ZONE cannot be deleted if linked to CTAG-POOL,DVS-SWITCH,GENERIC-VNF,PSERVER,VCE
+ required:
+ - availability-zone-name
+ - hypervisor-type
+ properties:
+ availability-zone-name:
type: string
- description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
- widget-model-version:
+ description: Name of the availability zone. Unique across a cloud region
+ hypervisor-type:
type: string
- description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ description: Type of hypervisor. Source of truth should define valid values.
operational-status:
type: string
- description: Indication of operational status of the logical link.
- prov-status:
- type: string
- description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
- link-role:
- type: string
- description: Indication of the network use of the logical link.
- link-name2:
- type: string
- description: Alias or alternate name (CLCI or D1 name).
- link-id:
- type: string
- description: UUID of the logical-link, SDNC generates this.
- circuit-id:
- type: string
- description: Circuit id
- purpose:
- type: string
- description: Reason for this entity, role it is playing
- relationship-list:
- type: array
- items:
- $ref: "#/definitions/relationship"
- logical-links:
+ description: State that indicates whether the availability zone should be used, etc. Source of truth should define valid values.
+ availability-zones:
description: |
- Collection of logical connections
+ Collection of availability zones
properties:
- logical-link:
+ availability-zone:
type: array
items:
- $ref: "#/definitions/logical-link"
+ $ref: "#/patchDefinitions/availability-zone"
+ az-and-dvs-switches:
+ properties:
+ dvs-switches:
+ type: object
+ $ref: "#/patchDefinitions/dvs-switches"
+ availability-zone:
+ type: object
+ $ref: "#/patchDefinitions/availability-zone"
+ business:
+ description: |
+ Namespace for business related constructs
+ properties:
+ connectors:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/connector"
+ customers:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/customer"
class-of-service:
description: |
- ###### Default Delete Scope
- THIS_NODE_ONLY
###### Related Nodes
- - FROM site-pair (is composed of class-of-service)
+ - TO site-pair( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)
required:
- cos
properties:
@@ -40318,13 +53862,6 @@ definitions:
probe-type:
type: string
description: type of probe
- resource-version:
- type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- relationship-list:
- type: array
- items:
- $ref: "#/definitions/relationship"
classes-of-service:
description: |
class-of-service of probe
@@ -40332,257 +53869,1733 @@ definitions:
class-of-service:
type: array
items:
- $ref: "#/definitions/class-of-service"
- site-pair:
+ $ref: "#/patchDefinitions/class-of-service"
+ cloud-infrastructure:
description: |
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
+ Namespace for cloud infrastructure.
+ properties:
+ complexes:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/complex"
+ cloud-regions:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/cloud-region"
+ network-profiles:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/network-profile"
+ pservers:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/pserver"
+ virtual-data-centers:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/virtual-data-center"
+ cloud-region:
+ description: |
+ cloud-region designates an installation of a cloud cluster or region or instantiation
###### Related Nodes
- - TO class-of-service (comprises site-pair, Many2Many)
- - FROM routing-instance (is composed of site-pair)
+ - TO complex( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO l3-network( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO zone( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM dvs-switch( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM flavor( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM group-assignment( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM image( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM snapshot( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM volume-group( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn cloud-region, MANY2MANY)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)
+ - CLOUD-REGION cannot be deleted if linked to DVS-SWITCH,FLAVOR,GROUP-ASSIGNMENT,IMAGE,OAM-NETWORK,SNAPSHOT,TENANT,VOLUME-GROUP
+ - CLOUD-REGION is DELETED when these are DELETED AVAILABILITY-ZONE
required:
- - site-pair-id
+ - cloud-owner
+ - cloud-region-id
properties:
- site-pair-id:
+ cloud-owner:
type: string
- description: unique identifier of probe
- source-ip:
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ cloud-region-id:
type: string
- description: Prefix address
- destination-ip:
+ description: Identifier used by the vendor for the region. Second part of composite key
+ cloud-type:
type: string
- description: Prefix address
- ip-version:
+ description: Type of the cloud (e.g., openstack)
+ owner-defined-type:
type: string
- description: ip version, v4, v6
- destination-hostname:
+ description: Cloud-owner defined type indicator (e.g., dcp, lcp)
+ cloud-region-version:
type: string
- description: Hostname of the destination equipment to which SLAs are measured against.
- destination-equip-type:
+ description: Software version employed at the site. NOTE - THIS FIELD IS NOT KEPT UP TO DATE.
+ identity-url:
type: string
- description: The type of destinatination equipment. Could be Router, etc.
- resource-version:
+ description: URL of the keystone identity service
+ cloud-zone:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- classes-of-service:
+ description: Zone where the cloud is homed. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
+ complex-name:
+ type: string
+ description: complex name for cloud-region instance. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
+ cloud-regions:
+ properties:
+ cloud-region:
type: array
- items:
- $ref: "#/definitions/class-of-service"
- relationship-list:
+ items:
+ $ref: "#/patchDefinitions/cloud-region"
+ complex:
+ description: |
+ Collection of physical locations that can house cloud-regions.
+ ###### Related Nodes
+ - TO l3-network( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM ctag-pool( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)
+ - FROM pnf( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM vce( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)
+ - FROM volume-group( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM vpls-pe( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM zone( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - COMPLEX cannot be deleted if linked to AVAILABILITY-ZONE,CLOUD-REGION,OAM-NETWORK,PNF,PSERVER,VCE,VOLUME-GROUP,VPLS-PE,ZONE
+ - COMPLEX is DELETED when these are DELETED CTAG-POOL
+ required:
+ - physical-location-id
+ - physical-location-type
+ - street1
+ - city
+ - postal-code
+ - country
+ - region
+ properties:
+ physical-location-id:
+ type: string
+ description: Unique identifier for physical location, e.g., CLLI
+ data-center-code:
+ type: string
+ description: Data center code which can be an alternate way to identify a complex
+ complex-name:
+ type: string
+ description: Gamma complex name for LCP instance.
+ identity-url:
+ type: string
+ description: URL of the keystone identity service
+ complexes:
+ description: |
+ Collection of physical locations that can house cloud-regions.
+ properties:
+ complex:
type: array
- items:
- $ref: "#/definitions/relationship"
- site-pairs:
+ items:
+ $ref: "#/patchDefinitions/complex"
+ configuration:
description: |
- probe within a set
+ Port Mirror Configuration.
+ ###### Related Nodes
+ - TO allotted-resource( configuration org.onap.relationships.inventory.Uses allotted-resource, ONE2ONE)
+ - TO logical-link( configuration org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo configuration, MANY2ONE)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses configuration, ONE2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses configuration, ONE2MANY)
+ - CONFIGURATION is DELETED when these are DELETED METADATUM
+ - CONFIGURATION deletion means associated objects of these types are also DELETED:ALLOTTED-RESOURCE,LOGICAL-LINK
+ required:
+ - configuration-id
+ - configuration-type
+ - configuration-sub-type
+ - orchestration-status
+ - operational-status
+ - configuration-selflink
+ - model-customization-id
properties:
- site-pair:
+ configuration-id:
+ type: string
+ description: UUID assigned to configuration.
+ management-option:
+ type: string
+ description: Indicates the entity that will manage this feature. Could be an organization or the name of the application as well.
+ configuration-name:
+ type: string
+ description: Name of the configuration.
+ configuration-type:
+ type: string
+ description: port-mirroring-configuration.
+ configuration-sub-type:
+ type: string
+ description: vprobe, pprobe.
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ orchestration-status:
+ type: string
+ description: Orchestration status of the configuration.
+ operational-status:
+ type: string
+ description: Indicator for whether the resource is considered operational.
+ configuration-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details from SDN-GC.
+ model-customization-id:
+ type: string
+ description: id of the configuration used to customize the resource
+ configurations:
+ description: |
+ Collection of configurations
+ properties:
+ configuration:
type: array
items:
- $ref: "#/definitions/site-pair"
- routing-instance:
+ $ref: "#/patchDefinitions/configuration"
+ connector:
description: |
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
+ Collection of resource instances used to connect a variety of disparate inventory widgets
###### Related Nodes
- - TO site-pair (comprises routing-instance, Many2Many)
- - FROM site-pair-set (is composed of routing-instance)
+ - TO virtual-data-center( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)
+ - CONNECTOR is DELETED when these are DELETED METADATUM
required:
- - routing-instance-id
+ - resource-instance-id
properties:
- routing-instance-id:
+ resource-instance-id:
type: string
- description: Unique id of routing instance
- rpm-owner:
+ description: Unique id of resource instance.
+ connectors:
+ description: |
+ Collection of resource instances used to connect a variety of disparate inventory widgets
+ properties:
+ connector:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/connector"
+ constrained-element-set:
+ description: |
+ This is how we would capture constraints defining allowed sets of elements.
+ ###### Related Nodes
+ - TO model-constraint( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)
+ - TO model-element( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM element-choice-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)
+ - CONSTRAINED-ELEMENT-SET is DELETED when these are DELETED ELEMENT-CHOICE-SET
+ required:
+ - constrained-element-set-uuid
+ - constraint-type
+ - check-type
+ properties:
+ constrained-element-set-uuid:
type: string
- description: rpm owner
- resource-version:
+ constraint-type:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- site-pairs:
+ check-type:
+ type: string
+ constrained-element-sets:
+ properties:
+ constrained-element-set:
type: array
- items:
- $ref: "#/definitions/site-pair"
- relationship-list:
+ items:
+ $ref: "#/patchDefinitions/constrained-element-set"
+ ctag-assignment:
+ description: |
+ ###### Related Nodes
+ - TO l3-network( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses ctag-assignment, ONE2MANY)
+ required:
+ - vlan-id-inner
+ properties:
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: id.
+ ctag-assignments:
+ properties:
+ ctag-assignment:
type: array
- items:
- $ref: "#/definitions/relationship"
- routing-instances:
+ items:
+ $ref: "#/patchDefinitions/ctag-assignment"
+ ctag-pool:
description: |
- set of probes related to generic-vnf routing instance
+ A collection of C tags (vlan tags) grouped for a specific purpose.
+ ###### Related Nodes
+ - TO complex( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)
+ - TO availability-zone( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM vpls-pe( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)
+ required:
+ - target-pe
+ - availability-zone-name
+ - ctag-pool-purpose
properties:
- routing-instance:
+ target-pe:
+ type: string
+ description: The Target provider edge router
+ availability-zone-name:
+ type: string
+ description: Name of the availability zone
+ ctag-pool-purpose:
+ type: string
+ description: Describes what the intended purpose of this pool is.
+ ctag-values:
+ type: string
+ description: Comma separated list of ctags
+ ctag-pools:
+ properties:
+ ctag-pool:
type: array
items:
- $ref: "#/definitions/routing-instance"
- site-pair-set:
+ $ref: "#/patchDefinitions/ctag-pool"
+ customer:
description: |
- Set of instances for probes used to measure service level agreements
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
+ customer identifiers to provide linkage back to BSS information.
###### Related Nodes
- - TO routing-instance (comprises site-pair-set, Many2Many)
- - FROM generic-vnf
+ - FROM service-subscription( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)
+ - CUSTOMER is DELETED when these are DELETED SERVICE-SUBSCRIPTION
required:
- - site-pair-set-id
+ - global-customer-id
+ - subscriber-name
+ - subscriber-type
properties:
- site-pair-set-id:
+ global-customer-id:
type: string
- description: Unique id of site pair set.
- resource-version:
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ subscriber-name:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- routing-instances:
+ description: Subscriber name, an alternate way to retrieve a customer.
+ subscriber-type:
+ type: string
+ description: Subscriber type, a way to provide VID with only the INFRA customers.
+ customers:
+ description: |
+ Collection of customer identifiers to provide linkage back to BSS information.
+ properties:
+ customer:
type: array
- items:
- $ref: "#/definitions/routing-instance"
- relationship-list:
+ items:
+ $ref: "#/patchDefinitions/customer"
+ cvlan-tag-entry:
+ required:
+ - cvlan-tag
+ properties:
+ cvlan-tag:
+ type: integer
+ format: int64
+ description: See mis-na-virtualization-platform.yang
+ cvlan-tags:
+ properties:
+ cvlan-tag-entry:
type: array
- items:
- $ref: "#/definitions/relationship"
- site-pair-sets:
+ items:
+ $ref: "#/patchDefinitions/cvlan-tag-entry"
+ dvs-switch:
description: |
- Collection of sets of instances for probes related to generic-vnf
+ Digital virtual switch metadata, used by SDN-C to configure VCEs. A&AI needs to receive this data from the PO deployment team and administer it using the provisioningTool.sh into A&AI.
+ ###### Related Nodes
+ - TO cloud-region( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO availability-zone( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ required:
+ - switch-name
+ - vcenter-url
properties:
- site-pair-set:
+ switch-name:
+ type: string
+ description: DVS switch name
+ vcenter-url:
+ type: string
+ description: URL used to reach the vcenter
+ dvs-switches:
+ description: |
+ Collection of digital virtual switch metadata used for vmWare VCEs and GenericVnfs.
+ properties:
+ dvs-switch:
type: array
items:
- $ref: "#/definitions/site-pair-set"
- route-target:
+ $ref: "#/patchDefinitions/dvs-switch"
+ edge-prop-names:
description: |
- Route target information
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
+ Internal map to define the properties of an edge and interpret the map EdgeRules
+ properties:
+ edgeLabel:
+ type: string
+ direction:
+ type: string
+ multiplicityRule:
+ type: string
+ isParent:
+ type: boolean
+ usesResource:
+ type: boolean
+ hasDelTarget:
+ type: boolean
+ SVC-INFRA:
+ type: boolean
+ SVC-INFRA-REV:
+ type: boolean
+ edge-tag-query-request:
+ properties:
+ edge-tag:
+ type: string
+ result-detail:
+ type: string
+ start-node-type:
+ type: string
+ start-node-filter:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/start-node-filter"
+ include-node-filter:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/include-node-filter"
+ secondary-filter:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/secondary-filter"
+ edge-tag-query-result:
+ properties:
+ tagged-inventory-item-list:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/tagged-inventory-item-list"
+ element-choice-set:
+ description: |
+ This is how we would capture constraints defining allowed sets of elements.
###### Related Nodes
- - FROM vpn-binding (is composed of route-target)
+ - TO constrained-element-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)
+ - ELEMENT-CHOICE-SET is DELETED when these are DELETED MODEL-ELEMENT
required:
- - global-route-target
- - route-target-role
+ - element-choice-set-uuid
+ - element-choice-set-name
properties:
- global-route-target:
+ element-choice-set-uuid:
type: string
- description: Number used to identify an RT, globally unique in the network
- route-target-role:
+ element-choice-set-name:
type: string
- description: Role assigned to this route target
- resource-version:
+ cardinality:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- relationship-list:
+ element-choice-sets:
+ properties:
+ element-choice-set:
type: array
- items:
- $ref: "#/definitions/relationship"
- route-targets:
+ items:
+ $ref: "#/patchDefinitions/element-choice-set"
+ entitlement:
description: |
- Collection of route target information
+ Metadata for entitlement group.
+ ###### Related Nodes
+ - TO generic-vnf( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vce( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ required:
+ - group-uuid
+ - resource-uuid
properties:
- route-target:
+ group-uuid:
+ type: string
+ description: Unique ID for the entitlement group the resource comes from, should be uuid.
+ resource-uuid:
+ type: string
+ description: Unique ID of an entitlement resource.
+ entitlements:
+ description: |
+ Entitlements, keyed by group-uuid and resource-uuid, related to license management
+ properties:
+ entitlement:
type: array
items:
- $ref: "#/definitions/route-target"
- vpn-binding:
+ $ref: "#/patchDefinitions/entitlement"
+ esr-ems:
description: |
- VPN binding
- ###### Default Delete Scope
- ERROR_4_IN_EDGES_OR_CASCADE
+ Persist EMS address information used by EMS driver.
###### Related Nodes
- - TO route-target (comprises vpn-binding, One2Many)
- - FROM l3-network
- - FROM logical-link
+ - TO esr-system-info (CHILD of esr-ems, esr-ems has esr-system-info, One2Many)
+ - ESR-EMS deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
required:
- - vpn-id
- - vpn-name
+ - ems-id
properties:
- vpn-id:
+ ems-id:
type: string
- description: VPN ID, globally unique within A&AI
- vpn-name:
+ description: Unique ID of EMS.
+ esr-ems-list:
+ properties:
+ esr-ems:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/esr-ems"
+ esr-system-info:
+ description: |
+ Persist common address information of external systems.
+ ###### Related Nodes
+ - FROM esr-ems (PARENT of esr-system-info, esr-ems has esr-system-info)
+ - FROM esr-vnfm (PARENT of esr-system-info, esr-vnfm has esr-system-info)
+ - FROM esr-thirdparty-sdnc (PARENT of esr-system-info, esr-thirdparty-sdnc has esr-system-info)
+ - FROM cloud-region (PARENT of esr-system-info, cloud-region has esr-system-info)
+ required:
+ - esr-system-info-id
+ - user-name
+ - password
+ - system-type
+ properties:
+ esr-system-info-id:
type: string
- description: VPN Name
- vpn-platform:
+ description: Unique ID of esr system info.
+ system-name:
type: string
- description: the platform associated with the VPN example AVPN, Mobility
- vpn-type:
+ description: name of external system.
+ type:
type: string
- description: Type of the vpn, should be taken from enumerated/valid values
- route-distinguisher:
+ description: type of external systems.
+ vendor:
type: string
- description: Used to distinguish the distinct VPN routes of separate customers who connect to the provider in an MPLS network.
- resource-version:
+ description: vendor of external systems.
+ version:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- route-targets:
+ description: version of external systems.
+ service-url:
+ type: string
+ description: url used to access external systems.
+ user-name:
+ type: string
+ description: username used to access external systems.
+ password:
+ type: string
+ description: password used to access external systems.
+ system-type:
+ type: string
+ description: it could be vim/vnfm/thirdparty-sdnc/ems-resource/ems-performance/ems-alarm.
+ protocol:
+ type: string
+ description: protocol of third party SDNC, for example netconf/snmp.
+ ssl-cacert:
+ type: string
+ description: ca file content if enabled ssl on auth-url.
+ ssl-insecure:
+ type: boolean
+ description: Whether to verify VIM's certificate.
+ ip-address:
+ type: string
+ description: service IP of ftp server.
+ port:
+ type: string
+ description: service port of ftp server.
+ cloud-domain:
+ type: string
+ description: domain info for authentication.
+ default-tenant:
+ type: string
+ description: default tenant of VIM.
+ passive:
+ type: boolean
+ description: ftp passive mode or not.
+ remote-path:
+ type: string
+ description: resource or performance data file path.
+ system-status:
+ type: string
+ description: the status of external system.
+ esr-system-info-list:
+ description: |
+ Collection of persistent block-level external system auth info.
+ properties:
+ esr-system-info:
type: array
- items:
- $ref: "#/definitions/route-target"
- relationship-list:
+ items:
+ $ref: "#/patchDefinitions/esr-system-info"
+ esr-thirdparty-sdnc:
+ description: |
+ Persist SDNC address information used by ONAP SDNC.
+ ###### Related Nodes
+ - TO esr-system-info (CHILD of esr-thirdparty-sdnc, esr-thirdparty-sdnc has esr-system-info, One2One)
+ - TO pnf( esr-thirdparty-sdnc has pnf, One2Many)
+ - ESR-THIRDPARTY-SDNC deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
+ required:
+ - thirdparty-sdnc-id
+ properties:
+ thirdparty-sdnc-id:
+ type: string
+ description: Unique ID of SDNC.
+ location:
+ type: string
+ description: used for DC type to indicate the location of SDNC, such as Core or Edge.
+ product-name:
+ type: string
+ description: password used to access SDNC server.
+ esr-thirdparty-sdnc-list:
+ properties:
+ esr-thirdparty-sdnc:
type: array
- items:
- $ref: "#/definitions/relationship"
- description: l3-networks relate to vpn-bindings
- vpn-bindings:
+ items:
+ $ref: "#/patchDefinitions/esr-thirdparty-sdnc"
+ esr-vnfm:
+ description: |
+ Persist VNFM address information used by VF-C.
+ ###### Related Nodes
+ - TO esr-system-info (CHILD of esr-vnfm, esr-vnfm has esr-system-info, One2One)
+ - ESR-VNFM deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
+ required:
+ - vnfm-id
properties:
- vpn-binding:
+ vnfm-id:
+ type: string
+ description: Unique ID of VNFM.
+ vim-id:
+ type: string
+ description: indecate the VIM to deploy VNF.
+ certificate-url:
+ type: string
+ description: certificate url of VNFM.
+ esr-vnfm-list:
+ properties:
+ esr-vnfm:
type: array
items:
- $ref: "#/definitions/vpn-binding"
- vpls-pe:
+ $ref: "#/patchDefinitions/esr-vnfm"
+ evc:
description: |
- VPLS Provider Edge routers.
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
+ evc object is an optional child object of the Configuration object.
###### Related Nodes
- - TO complex (Many2Many)
- - TO ctag-pool (Many2Many)
- - TO p-interface (comprises vpls-pe, Many2Many)
- - TO lag-interface (comprises vpls-pe, Many2Many)
+ - TO configuration( evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)
required:
- - equipment-name
+ - evc-id
properties:
- equipment-name:
+ evc-id:
+ type: string
+ description: Unique/key field for the evc object
+ forwarding-path-topology:
+ type: string
+ description: Point-to-Point, Multi-Point
+ cir-value:
+ type: string
+ description: Commited Information Rate
+ cir-units:
+ type: string
+ description: CIR units
+ connection-diversity-group-id:
+ type: string
+ description: Diversity Group ID
+ service-hours:
+ type: string
+ description: formerly Performance Group
+ esp-evc-circuit-id:
+ type: string
+ description: EVC Circuit ID of ESP EVC
+ esp-evc-cir-value:
+ type: string
+ description: Committed Information Rate (For ESP)
+ esp-evc-cir-units:
+ type: string
+ description: CIR units (For ESP)
+ esp-itu-code:
+ type: string
+ description: Identifies ESP
+ collector-pop-clli:
+ type: string
+ description: Collector POP CLLI (from the hostname of the access pnf)
+ inter-connect-type-ingress:
+ type: string
+ description: Interconnect type on ingress side of EVC.
+ tagmode-access-ingress:
+ type: string
+ description: tagode for collector side of EVC
+ tagmode-access-egress:
+ type: string
+ description: tagMode for network side of EVC
+ evcs:
+ properties:
+ evc:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/evc"
+ external-system:
+ description: |
+ Namespace for external system.
+ properties:
+ esr-ems-list:
+ type: object
+ $ref: "#/patchDefinitions/esr-ems-list"
+ esr-vnfm-list:
+ type: object
+ $ref: "#/patchDefinitions/esr-vnfm-list"
+ esr-thirdparty-sdnc-list:
+ type: object
+ $ref: "#/patchDefinitions/esr-thirdparty-sdnc-list"
+ extra-properties:
+ description: |
+ Extra properties for inventory item for response list
+ properties:
+ extra-property:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/extra-property"
+ extra-property:
+ properties:
+ property-name:
+ type: string
+ property-value:
type: string
+ flavor:
+ description: |
+ Openstack flavor.
+ ###### Related Nodes
+ - TO cloud-region( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)
+ - FLAVOR cannot be deleted if linked to VSERVER
+ required:
+ - flavor-id
+ - flavor-name
+ - flavor-selflink
+ properties:
+ flavor-id:
+ type: string
+ description: Flavor id, expected to be unique across cloud-region.
+ flavor-name:
+ type: string
+ description: Flavor name
+ flavor-vcpus:
+ type: integer
+ format: int32
+ description: Number of CPUs
+ flavor-ram:
+ type: integer
+ format: int32
+ description: Amount of memory
+ flavor-disk:
+ type: integer
+ format: int32
+ description: Disk space
+ flavor-ephemeral:
+ type: integer
+ format: int32
+ description: Amount of ephemeral disk space
+ flavor-swap:
+ type: string
+ description: amount of swap space allocation
+ flavor-is-public:
+ type: boolean
+ description: whether flavor is available to all users or private to the tenant it was created in.
+ flavor-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ flavor-disabled:
+ type: boolean
+ description: Boolean as to whether this flavor is no longer enabled
+ flavors:
+ description: |
+ Collection of openstack flavors.
+ properties:
+ flavor:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/flavor"
+ forwarder:
+ description: |
+ Entity describing a sequenced segment of forwarding path
+ ###### Related Nodes
+ - TO forwarding-path( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)
+ - TO l-interface( forwarder org.onap.relationships.inventory.ForwardsTo l-interface, MANY2ONE)
+ - TO configuration( forwarder org.onap.relationships.inventory.Uses configuration, ONE2ONE)
+ - TO lag-interface( forwarder org.onap.relationships.inventory.ForwardsTo lag-interface, MANY2ONE)
+ - TO p-interface( forwarder org.onap.relationships.inventory.ForwardsTo p-interface, MANY2ONE)
+ - FORWARDER deletion means associated objects of these types are also DELETED:CONFIGURATION
+ required:
+ - sequence
+ properties:
+ sequence:
+ type: integer
+ format: int32
+ description: Unique ID of this segmentation
+ forwarder-role:
+ type: string
+ description: ingress, intermediate, egress
+ forwarder-evc:
+ description: |
+ forwarder object is an optional child object of the Configuration object.
+ ###### Related Nodes
+ - TO configuration( forwarder-evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)
+ required:
+ - forwarder-evc-id
+ properties:
+ forwarder-evc-id:
+ type: string
+ description: Key for forwarder-evc object
+ circuit-id:
+ type: string
+ description: Circuit ID from customer/ESP/ingress end of EVC, or reference to beater circuit on gateway/network/egress end of EVC
+ ivlan:
+ type: string
+ description: Internal VLAN.
+ svlan:
+ type: string
+ description: SVLAN value for ingress of egress forwarder.
+ cvlan:
+ type: string
+ description: CVLAN value for ingress of egress forwarder.
+ forwarder-evcs:
+ properties:
+ forwarder-evc:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/forwarder-evc"
+ forwarders:
+ properties:
+ forwarder:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/forwarder"
+ forwarding-path:
+ description: |
+ Entity that describes the sequenced forwarding path between interfaces of services or resources
+ ###### Related Nodes
+ - TO service-instance( forwarding-path org.onap.relationships.inventory.AppliesTo service-instance, MANY2ONE)
+ - TO configuration( forwarding-path org.onap.relationships.inventory.Uses configuration, ONE2ONE)
+ - FROM forwarder( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)
+ - FORWARDING-PATH is DELETED when these are DELETED FORWARDER
+ - FORWARDING-PATH deletion means associated objects of these types are also DELETED:CONFIGURATION
+ required:
+ - forwarding-path-id
+ - forwarding-path-name
+ properties:
+ forwarding-path-id:
+ type: string
+ description: Unique ID of this FP
+ forwarding-path-name:
+ type: string
+ description: Name of the FP
+ forwarding-paths:
+ properties:
+ forwarding-path:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/forwarding-path"
+ generic-vnf:
+ description: |
+ General purpose VNF
+ ###### Related Nodes
+ - TO availability-zone( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - TO instance-group( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO ipsec-configuration( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)
+ - TO l3-network( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO license-key-resource( generic-vnf org.onap.relationships.inventory.Uses license-key-resource, MANY2MANY)
+ - TO pserver( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)
+ - TO vnf-image( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)
+ - TO volume-group( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - TO vserver( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)
+ - TO virtual-data-center( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY)
+ - FROM entitlement( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM lag-interface( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM license( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM network-profile( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)
+ - FROM site-pair-set( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)
+ - GENERIC-VNF is DELETED when these are DELETED ENTITLEMENT,VNFC,LAG-INTERFACE,LICENSE,L-INTERFACE,VF-MODULE
+ required:
+ - vnf-id
+ - vnf-name
+ - vnf-type
+ - in-maint
+ - is-closed-loop-disabled
+ properties:
+ vnf-id:
+ type: string
+ description: Unique id of VNF. This is unique across the graph.
+ vnf-name:
+ type: string
+ description: Name of VNF.
+ vnf-name2:
+ type: string
+ description: Alternate name of VNF.
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ service-id:
+ type: string
+ description: Unique identifier of service, does not necessarily map to ASDC service models. SOON TO BE DEPRECATED
+ regional-resource-zone:
+ type: string
+ description: Regional way of organizing pservers, source of truth should define values
prov-status:
type: string
- description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
- ipv4-oam-address:
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ operational-status:
type: string
- description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address).
+ description: Indicator for whether the resource is considered operational. Valid values are in-service-path and out-of-service-path.
+ license-key:
+ type: string
+ description: OBSOLETE - do not use
equipment-role:
type: string
- description: Client should send valid enumerated value, e.g., VPLS-PE.
- vlan-id-outer:
+ description: Client should send valid enumerated value
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, used by MSO.
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ management-option:
+ type: string
+ description: identifier of managed by company or customer
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by generic-vnf.
+ ipv4-loopback0-address:
+ type: string
+ description: v4 Loopback0 address
+ nm-lan-v6-address:
+ type: string
+ description: v6 Loopback address
+ management-v6-address:
+ type: string
+ description: v6 management address
+ vcpu:
type: integer
format: int64
- description: Temporary location for stag to get to VCE
- resource-version:
+ description: number of vcpus ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases
+ vcpu-units:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- relationship-list:
+ description: units associated with vcpu, used for VNFs with no vservers/flavors, to be used only in some usecases
+ vmemory:
+ type: integer
+ format: int64
+ description: number of GB of memory ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases
+ vmemory-units:
+ type: string
+ description: units associated with vmemory, used for VNFs with no vservers/flavors, to be used only in some usecases
+ vdisk:
+ type: integer
+ format: int64
+ description: number of vdisks ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases
+ vdisk-units:
+ type: string
+ description: units associated with vdisk, used for VNFs with no vservers/flavors, to be used only in some usecases
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
+ generic-vnfs:
+ description: |
+ Collection of VNFs
+ properties:
+ generic-vnf:
type: array
- items:
- $ref: "#/definitions/relationship"
- p-interfaces:
+ items:
+ $ref: "#/patchDefinitions/generic-vnf"
+ group-assignment:
+ description: |
+ Openstack group-assignment used to store exclusivity groups (EG).
+ ###### Related Nodes
+ - TO cloud-region( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)
+ required:
+ - group-id
+ - group-type
+ - group-name
+ properties:
+ group-id:
+ type: string
+ description: Group id, expected to be unique across cloud-region.
+ group-type:
+ type: string
+ description: Group type - the type of group this instance refers to
+ group-name:
+ type: string
+ description: Group name - name assigned to the group
+ group-description:
+ type: string
+ description: Group description - description of the group
+ group-assignments:
+ description: |
+ Collection of openstack group assignments
+ properties:
+ group-assignment:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/group-assignment"
+ host-route:
+ description: |
+ ###### Related Nodes
+ - TO subnet( host-route org.onap.relationships.inventory.BelongsTo subnet, MANY2ONE)
+ required:
+ - host-route-id
+ - route-prefix
+ - next-hop
+ properties:
+ host-route-id:
+ type: string
+ description: host-route id
+ route-prefix:
+ type: string
+ description: subnet prefix
+ next-hop:
+ type: string
+ description: Could be ip-address, hostname, or service-instance
+ next-hop-type:
+ type: string
+ description: Should be ip-address, hostname, or service-instance to match next-hop
+ host-routes:
+ properties:
+ host-route:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/host-route"
+ image:
+ description: |
+ Openstack image.
+ ###### Related Nodes
+ - TO cloud-region( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)
+ - IMAGE cannot be deleted if linked to VSERVER
+ - IMAGE is DELETED when these are DELETED METADATUM
+ required:
+ - image-id
+ - image-name
+ - image-os-distro
+ - image-os-version
+ - image-selflink
+ properties:
+ image-id:
+ type: string
+ description: Image id, expected to be unique across cloud region
+ image-name:
+ type: string
+ description: Image name
+ image-architecture:
+ type: string
+ description: Operating system architecture.
+ image-os-distro:
+ type: string
+ description: The common name of the operating system distribution in lowercase
+ image-os-version:
+ type: string
+ description: The operating system version as specified by the distributor.
+ application:
+ type: string
+ description: The application that the image instantiates.
+ application-vendor:
+ type: string
+ description: The vendor of the application.
+ application-version:
+ type: string
+ description: The version of the application.
+ image-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ images:
+ description: |
+ Collectio of Openstack images.
+ properties:
+ image:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/image"
+ include-node-filter:
+ properties:
+ include-node-type:
+ type: string
+ instance-filter:
+ description: |
+ InstanceFilter for performing a named-query or model query
+ instance-filters:
+ description: |
+ InstanceFilters for performing a named-query or model query
+ properties:
+ instance-filter:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/instance-filter"
+ instance-group:
+ description: |
+ General mechanism for grouping instances
+ ###### Related Nodes
+ - TO model( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM pnf( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ required:
+ - id
+ - description
+ - type
+ properties:
+ id:
+ type: string
+ description: Instance Group ID, UUID assigned to this instance.
+ description:
+ type: string
+ description: Descriptive text to help identify the usage of this instance-group
+ type:
+ type: string
+ description: Only valid value today is lower case ha for high availability
+ sub-type:
+ type: string
+ description: Valid values for ha type are [geo-activeactive, geo-activestandby, local-activeactive, local-activestandby]
+ instance-groups:
+ description: |
+ Collection of openstack route table references
+ properties:
+ instance-group:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/instance-group"
+ inventory:
+ properties:
+ search:
+ type: object
+ $ref: "#/patchDefinitions/search"
+ actions:
+ type: object
+ $ref: "#/patchDefinitions/actions"
+ cloud-infrastructure:
+ type: object
+ $ref: "#/patchDefinitions/cloud-infrastructure"
+ business:
+ type: object
+ $ref: "#/patchDefinitions/business"
+ service-design-and-creation:
+ type: object
+ $ref: "#/patchDefinitions/service-design-and-creation"
+ network:
+ type: object
+ $ref: "#/patchDefinitions/network"
+ aai-internal:
+ type: object
+ $ref: "#/patchDefinitions/aai-internal"
+ nodes:
type: array
items:
- $ref: "#/definitions/p-interface"
- lag-interfaces:
+ $ref: "#/patchDefinitions/aai-internal"
+ inventory-item:
+ properties:
+ inventory-item-type:
+ type: string
+ inventory-item-link:
+ type: string
+ inventory-item-data:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/inventory-item-data"
+ tagged-inventory-item-list:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/tagged-inventory-item-list"
+ inventory-item-data:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ inventory-response-item:
+ description: |
+ Inventory item for response list
+ properties:
+ model-name:
+ type: string
+ extra-properties:
+ type: object
+ $ref: "#/patchDefinitions/extra-properties"
+ inventory-response-items:
+ type: object
+ $ref: "#/patchDefinitions/inventory-response-items"
+ inventory-response-items:
+ description: |
+ Container for inventory items in response list
+ properties:
+ inventory-response-item:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/inventory-response-item"
+ ipsec-configuration:
+ description: |
+ IPSec configuration node will contain various configuration data for the NMTE VNF. This node will have an edge to the generic-vnf (vnf type = TE). Starting 1607, this data will be populated by SDN-C
+ ###### Related Nodes
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)
+ - FROM vig-server( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)
+ - IPSEC-CONFIGURATION is DELETED when these are DELETED VIG-SERVER
+ required:
+ - ipsec-configuration-id
+ properties:
+ ipsec-configuration-id:
+ type: string
+ description: UUID of this configuration
+ requested-vig-address-type:
+ type: string
+ description: Indicate the type of VIG server like AVPN, INTERNET, BOTH
+ requested-encryption-strength:
+ type: string
+ description: Encryption values like 3des-cbc, des-cbc, aes-128-cbc, aes-192-cbc, aes-265-cbc
+ requested-dmz-type:
+ type: string
+ description: can offer a shared DMZ or a DMZ specific to a customer
+ shared-dmz-network-address:
+ type: string
+ description: Network address of shared DMZ
+ requested-customer-name:
+ type: string
+ description: If the DMZ is a custom DMZ, this field will indicate the customer information
+ ike-version:
+ type: string
+ description: can be 1 or 2
+ ikev1-authentication:
+ type: string
+ description: Contains values like md5, sha1, sha256, sha384
+ ikev1-encryption:
+ type: string
+ description: Encyption values like 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
+ ikev1-dh-group:
+ type: string
+ description: Diffie-Hellman group like DH-GROUP2, DH-GROUP5, DH-GROUP14
+ ikev1-am-group-id:
+ type: string
+ description: Group name defined in VIG for clients using aggressive mode
+ ikev1-am-password:
+ type: string
+ description: pre-shared key for the above group name
+ ikev1-sa-lifetime:
+ type: string
+ description: Lifetime for IKEv1 SA
+ ipsec-authentication:
+ type: string
+ description: md5, sha1, sha256, sha384
+ ipsec-encryption:
+ type: string
+ description: 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
+ ipsec-sa-lifetime:
+ type: string
+ description: Life time for IPSec SA
+ ipsec-pfs:
+ type: string
+ description: enable PFS or not
+ xauth-userid:
+ type: string
+ description: user ID for xAuth, sm-user, ,nmteHostName
+ xauth-user-password:
+ type: string
+ description: Encrypted using the Juniper $9$ algorithm
+ dpd-interval:
+ type: string
+ description: The time between DPD probe
+ dpd-frequency:
+ type: string
+ description: Maximum number of DPD before claiming the tunnel is down
+ ipsec-configurations:
+ properties:
+ ipsec-configuration:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/ipsec-configuration"
+ key-data:
+ properties:
+ key-name:
+ type: string
+ key-value:
+ type: string
+ l-interface:
+ description: |
+ Logical interfaces, e.g., a vnic.
+ ###### Related Nodes
+ - TO generic-vnf( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO lag-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)
+ - TO instance-group( l-interface org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO l-interface( l-interface org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - TO logical-link( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)
+ - TO newvce( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)
+ - TO p-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)
+ - TO vserver( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - FROM sriov-vf( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)
+ - FROM vlan( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - L-INTERFACE is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST,SRIOV-VF,VLAN
+ - L-INTERFACE deletion means associated objects of these types are also DELETED:LOGICAL-LINK
+ required:
+ - interface-name
+ - is-port-mirrored
+ - in-maint
+ properties:
+ interface-name:
+ type: string
+ description: Name given to the interface
+ interface-role:
+ type: string
+ description: E.g., CUSTOMER, UPLINK, etc.
+ v6-wan-link-ip:
+ type: string
+ description: Questionably placed - v6 ip addr of this interface (is in vr-lan-interface from Mary B.
+ selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ interface-id:
+ type: string
+ description: ID of interface
+ macaddr:
+ type: string
+ description: MAC address for the interface
+ network-name:
+ type: string
+ description: Name of the network
+ management-option:
+ type: string
+ description: Whether A&AI should be managing this interface of not. Could have value like CUSTOMER
+ interface-description:
+ type: string
+ description: Human friendly text regarding this interface.
+ is-port-mirrored:
+ type: boolean
+ l-interfaces:
+ description: |
+ Collection of logical interfaces.
+ properties:
+ l-interface:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/l-interface"
+ l3-interface-ipv4-address-list:
+ description: |
+ IPv4 Address Range
+ ###### Related Nodes
+ - TO instance-group( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)
+ - TO l3-network( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - TO subnet( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - TO l-interface( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - TO vlan( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ required:
+ - l3-interface-ipv4-address
+ properties:
+ l3-interface-ipv4-address:
+ type: string
+ description: IP address
+ l3-interface-ipv4-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 32 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ l3-interface-ipv6-address-list:
+ description: |
+ IPv6 Address Range
+ ###### Related Nodes
+ - TO instance-group( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)
+ - TO l3-network( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - TO subnet( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - TO l-interface( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - TO vlan( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ required:
+ - l3-interface-ipv6-address
+ properties:
+ l3-interface-ipv6-address:
+ type: string
+ description: IP address
+ l3-interface-ipv6-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 128 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ l3-network:
+ description: |
+ Generic network definition
+ ###### Related Nodes
+ - TO network-policy( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)
+ - TO route-table-reference( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)
+ - TO vpn-binding( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM complex( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - FROM ctag-assignment( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM segmentation-assignment( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)
+ - FROM subnet( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)
+ - L3-NETWORK is DELETED when these are DELETED CTAG-ASSIGNMENT,SEGMENTATION-ASSIGNMENT,SUBNET
+ required:
+ - network-id
+ - network-name
+ - is-bound-to-vpn
+ - is-provider-network
+ - is-shared-network
+ - is-external-network
+ properties:
+ network-id:
+ type: string
+ description: Network ID, should be uuid. Unique across A&AI.
+ network-name:
+ type: string
+ description: Name of the network, governed by some naming convention..
+ network-type:
+ type: string
+ description: Type of the network - who defines these values?
+ network-role:
+ type: string
+ description: Role the network plans - who defines these values?
+ network-technology:
+ type: string
+ description: Network technology - who defines these values?
+ neutron-network-id:
+ type: string
+ description: Neutron network id of this Interface
+ is-bound-to-vpn:
+ type: boolean
+ service-id:
+ type: string
+ description: Unique identifier of service from ASDC. Does not strictly map to ASDC services. SOON TO BE DEPRECATED
+ network-role-instance:
+ type: integer
+ format: int64
+ description: network role instance
+ l3-networks:
+ properties:
+ l3-network:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/l3-network"
+ lag-interface:
+ description: |
+ Link aggregate interface
+ ###### Related Nodes
+ - TO generic-vnf( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO lag-link( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)
+ - TO logical-link( lag-interface org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - TO p-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)
+ - TO pnf( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - TO pserver( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - TO vpls-pe( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)
+ - LAG-INTERFACE is DELETED when these are DELETED L-INTERFACE
+ - LAG-INTERFACE deletion means associated objects of these types are also DELETED:LAG-LINK,LOGICAL-LINK
+ required:
+ - interface-name
+ - in-maint
+ properties:
+ interface-name:
+ type: string
+ description: Name that identifies the link aggregate interface
+ interface-description:
+ type: string
+ description: Human friendly text regarding this interface.
+ lag-interfaces:
+ description: |
+ Collection of link aggregate interfaces.
+ properties:
+ lag-interface:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/lag-interface"
+ lag-link:
+ description: |
+ LAG links can connect lag-interfaces
+ ###### Related Nodes
+ - FROM lag-interface( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)
+ required:
+ - link-name
+ properties:
+ link-name:
+ type: string
+ description: Alphabetical concatenation of lag-interface names
+ lag-links:
+ description: |
+ Collection of link aggregation connections
+ properties:
+ lag-link:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/lag-link"
+ license:
+ description: |
+ Metadata for license group.
+ ###### Related Nodes
+ - TO generic-vnf( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vce( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ required:
+ - group-uuid
+ - resource-uuid
+ properties:
+ group-uuid:
+ type: string
+ description: Unique ID for the license group the resource belongs to, should be uuid.
+ resource-uuid:
+ type: string
+ description: Unique ID of a license resource.
+ licenses:
+ description: |
+ Licenses to be allocated across resources, keyed by group-uuid and resource-uuid, related to license management
+ properties:
+ license:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/license"
+ line-of-business:
+ description: |
+ describes a line-of-business
+ ###### Related Nodes
+ - TO generic-vnf( line-of-business org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)
+ required:
+ - line-of-business-name
+ properties:
+ line-of-business-name:
+ type: string
+ description: Name of the line-of-business (product)
+ lines-of-business:
+ description: |
+ Collection of lines-of-business
+ properties:
+ line-of-business:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/line-of-business"
+ logical-link:
+ description: |
+ Logical links generally connect l-interfaces but are used to express logical connectivity between two points
+ ###### Related Nodes
+ - TO cloud-region( logical-link org.onap.relationships.inventory.LocatedIn cloud-region, MANY2MANY)
+ - TO generic-vnf( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)
+ - TO lag-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)
+ - TO logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - TO pnf( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)
+ - TO pserver( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)
+ - TO vpn-binding( logical-link org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - TO virtual-data-center( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM lag-interface( lag-interface org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)
+ - FROM p-interface( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - FROM vlan( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ required:
+ - link-name
+ - link-type
+ properties:
+ link-name:
+ type: string
+ description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
+ link-type:
+ type: string
+ description: Type of logical link, e.g., evc
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ ip-version:
+ type: string
+ description: v4, v6, or ds for dual stack
+ routing-protocol:
+ type: string
+ description: For example, static or BGP
+ logical-links:
+ description: |
+ Collection of logical connections
+ properties:
+ logical-link:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/logical-link"
+ metadata:
+ description: |
+ Collection of metadatum (key/value pairs)
+ properties:
+ metadatum:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/metadatum"
+ metadatum:
+ description: |
+ Key/value pairs
+ ###### Related Nodes
+ - TO connector( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)
+ - TO image( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)
+ - TO service-instance( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - TO model-ver( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ required:
+ - metaname
+ - metaval
+ properties:
+ metaname:
+ type: string
+ metaval:
+ type: string
+ model:
+ description: |
+ Subgraph definition provided by ASDC to describe an inventory asset and its connections related to ASDC models, independent of version
+ ###### Related Nodes
+ - TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - FROM instance-group( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY)
+ - FROM model-ver( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - FROM named-query( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)
+ - MODEL cannot be deleted if linked to INSTANCE-GROUP,NAMED-QUERY,NAMED-QUERY-ELEMENT
+ - MODEL is DELETED when these are DELETED MODEL-VER
+ required:
+ - model-invariant-id
+ - model-type
+ properties:
+ model-invariant-id:
+ type: string
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ model-type:
+ type: string
+ description: Type of the model, e.g., service, resource, widget, etc.
+ model-and-named-query-search:
+ description: |
+ ModelAndNamedQuerySearch holds query-parameters and instance-properties for performing a named-query or model query
+ properties:
+ query-parameters:
+ type: object
+ $ref: "#/patchDefinitions/query-parameters"
+ instance-filters:
+ type: object
+ $ref: "#/patchDefinitions/instance-filters"
+ secondary-filts:
+ type: object
+ $ref: "#/patchDefinitions/secondary-filts"
+ top-node-type:
+ type: string
+ secondary-filter-cut-point:
+ type: string
+ model-constraint:
+ description: |
+ This is how we would capture constraints defining allowed sets of elements.
+ ###### Related Nodes
+ - TO model-element( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)
+ - MODEL-CONSTRAINT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET
+ required:
+ - model-constraint-uuid
+ - constrained-element-set-uuid-to-replace
+ properties:
+ model-constraint-uuid:
+ type: string
+ constrained-element-set-uuid-to-replace:
+ type: string
+ constrained-element-sets:
type: array
items:
- $ref: "#/definitions/lag-interface"
- vpls-pes:
+ $ref: "#/patchDefinitions/constrained-element-set"
+ model-constraints:
+ properties:
+ model-constraint:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/model-constraint"
+ model-element:
description: |
- Collection of VPLS Provider Edge routers
+ Defines how other models combine to make up a higher-level model.
+ ###### Related Nodes
+ - TO element-choice-set( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)
+ - TO model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - TO model-ver( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE)
+ - TO model-ver( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM model-constraint( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - MODEL-ELEMENT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET,MODEL-CONSTRAINT
+ required:
+ - model-element-uuid
+ - new-data-del-flag
+ - cardinality
properties:
- vpls-pe:
+ model-element-uuid:
+ type: string
+ new-data-del-flag:
+ type: string
+ description: Indicates whether this element was created as part of instantiation from this model
+ cardinality:
+ type: string
+ description: How many of this type of element are required/allowed
+ linkage-points:
+ type: string
+ model-elements:
+ properties:
+ model-element:
type: array
items:
- $ref: "#/definitions/vpls-pe"
+ $ref: "#/patchDefinitions/model-element"
+ model-ver:
+ description: |
+ Subgraph definition provided by ASDC to describe a specific version of an inventory asset and its connections related to ASDC models
+ ###### Related Nodes
+ - TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - MODEL-VER cannot be deleted if linked to MODEL-ELEMENT
+ - MODEL-VER is DELETED when these are DELETED MODEL-ELEMENT,METADATUM
+ required:
+ - model-version-id
+ - model-name
+ - model-version
+ properties:
+ model-version-id:
+ type: string
+ description: Unique identifier corresponding to one version of a model in ASDC
+ model-name:
+ type: string
+ description: Name of the model, which can change from version to version.
+ model-version:
+ type: string
+ description: Version
+ model-description:
+ type: string
+ description: Description
+ model-vers:
+ properties:
+ model-ver:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/model-ver"
+ models:
+ description: |
+ Collection of subgraph definitions provided by ASDC to describe the inventory assets and their connections related to ASDC models
+ properties:
+ model:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/model"
multicast-configuration:
description: |
- ###### Default Delete Scope
- THIS_NODE_ONLY
###### Related Nodes
- - FROM vlan
+ - FROM vlan( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)
required:
- multicast-configuration-id
- multicast-protocol
@@ -40597,13 +55610,6 @@ definitions:
rp-type:
type: string
description: rp type of multicast configuration
- resource-version:
- type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- relationship-list:
- type: array
- items:
- $ref: "#/definitions/relationship"
multicast-configurations:
description: |
multicast configuration of generic-vnf ip-address
@@ -40611,36 +55617,602 @@ definitions:
multicast-configuration:
type: array
items:
- $ref: "#/definitions/multicast-configuration"
- cvlan-tag-entry:
+ $ref: "#/patchDefinitions/multicast-configuration"
+ named-queries:
+ properties:
+ named-query:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/named-query"
+ named-query:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - TO model( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - NAMED-QUERY is DELETED when these are DELETED NAMED-QUERY-ELEMENT
+ required:
+ - named-query-uuid
+ - named-query-name
+ - named-query-version
+ properties:
+ named-query-uuid:
+ type: string
+ named-query-name:
+ type: string
+ named-query-version:
+ type: string
+ required-input-param:
+ type: string
+ description:
+ type: string
+ named-query-element:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - TO model( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)
+ - TO named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM property-constraint( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM related-lookup( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - NAMED-QUERY-ELEMENT is DELETED when these are DELETED PROPERTY-CONSTRAINT,RELATED-LOOKUP
+ required:
+ - named-query-element-uuid
+ properties:
+ named-query-element-uuid:
+ type: string
+ property-collect-list:
+ type: string
+ named-query-elements:
+ properties:
+ named-query-element:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/named-query-element"
+ network:
+ description: |
+ Namespace for network inventory resources.
+ properties:
+ logical-links:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/logical-link"
+ site-pair-sets:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/site-pair-set"
+ vpn-bindings:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vpn-binding"
+ vpls-pes:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vpls-pe"
+ multicast-configurations:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/multicast-configuration"
+ vces:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vce"
+ vnfcs:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vnfc"
+ l3-networks:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/l3-network"
+ network-policies:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/network-policy"
+ generic-vnfs:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/generic-vnf"
+ lag-links:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/lag-link"
+ newvces:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/newvce"
+ pnfs:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/pnf"
+ physical-links:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/physical-link"
+ ipsec-configurations:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/ipsec-configuration"
+ route-table-references:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/route-table-reference"
+ instance-groups:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/instance-group"
+ zones:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/zone"
+ network-policies:
+ properties:
+ network-policy:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/network-policy"
+ network-policy:
+ description: |
+ ###### Related Nodes
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.Uses network-policy, ONE2ONE)
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)
+ required:
+ - network-policy-id
+ properties:
+ network-policy-id:
+ type: string
+ description: UUID representing unique key to this instance
+ network-policy-fqdn:
+ type: string
+ description: Contrail FQDN for the policy
+ heat-stack-id:
+ type: string
+ description: ID for the openStack Heat instance
+ network-profile:
+ description: |
+ Network profile populated by SDN-GP for SNMP
+ ###### Related Nodes
+ - TO generic-vnf( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
required:
+ - nm-profile-name
+ properties:
+ nm-profile-name:
+ type: string
+ description: Unique name of network profile.
+ community-string:
+ type: string
+ description: Encrypted SNMP community string
+ network-profiles:
+ description: |
+ Collection of network profiles
+ properties:
+ network-profile:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/network-profile"
+ newvce:
+ description: |
+ This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce.
+ ###### Related Nodes
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)
+ - NEWVCE is DELETED when these are DELETED L-INTERFACE
+ required:
+ - vnf-id2
+ - vnf-name
+ - vnf-type
+ properties:
+ vnf-id2:
+ type: string
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ vnf-name:
+ type: string
+ description: Name of VNF.
+ vnf-name2:
+ type: string
+ description: Alternate name of VNF.
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+ operational-status:
+ type: string
+ description: Indicator for whether the resource is considered operational
+ license-key:
+ type: string
+ description: OBSOLETE - do not use
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address).
+ equipment-role:
+ type: string
+ description: Client should send valid enumerated value.
+ newvces:
+ description: |
+ This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce.
+ properties:
+ newvce:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/newvce"
+ notification-event:
+ properties:
+ cambria.partition:
+ type: string
+ notification-event-header:
+ type: object
+ $ref: "#/patchDefinitions/notification-event-header"
+ notification-event-header:
+ properties:
+ id:
+ type: string
+ timestamp:
+ type: string
+ source-name:
+ type: string
+ domain:
+ type: string
+ sequence-number:
+ type: string
+ severity:
+ type: string
+ event-type:
+ type: string
+ version:
+ type: string
+ action:
+ type: string
+ entity-type:
+ type: string
+ top-entity-type:
+ type: string
+ entity-link:
+ type: string
+ status:
+ type: string
+ notify:
+ required:
+ - event-id
+ properties:
+ event-id:
+ type: string
+ node-type:
+ type: string
+ event-trigger:
+ type: string
+ key-data:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/key-data"
+ selflink:
+ type: string
+ oam-network:
+ description: |
+ OAM network, to be deprecated shortly. Do not use for new purposes.
+ ###### Related Nodes
+ - TO cloud-region( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO complex( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)
+ - TO service-capability( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ required:
+ - network-uuid
+ - network-name
- cvlan-tag
properties:
+ network-uuid:
+ type: string
+ description: UUID of the network. Unique across a cloud-region
+ network-name:
+ type: string
+ description: Name of the network.
cvlan-tag:
type: integer
format: int64
- description: See mis-na-virtualization-platform.yang
- resource-version:
+ description: cvlan-id
+ ipv4-oam-gateway-address:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- relationship-list:
+ description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
+ ipv4-oam-gateway-address-prefix-length:
+ type: integer
+ format: int32
+ description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
+ oam-networks:
+ description: |
+ Collection of OAM networks, to be deprecated shortly. Do not use for new purposes.
+ properties:
+ oam-network:
type: array
- items:
- $ref: "#/definitions/relationship"
- cvlan-tags:
+ items:
+ $ref: "#/patchDefinitions/oam-network"
+ operational-environment:
+ description: |
+ It is a logical partition of the cloud which allows to have multiple environments in the production AIC.
+ ###### Related Nodes
+ - TO operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)
+ - FROM operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)
+ required:
+ - operational-environment-id
+ - operational-environment-name
+ - operational-environment-type
+ - operational-environment-status
+ - tenant-context
+ - workload-context
properties:
- cvlan-tag-entry:
+ operational-environment-id:
+ type: string
+ description: UUID of an operational environment
+ operational-environment-name:
+ type: string
+ description: Operational Environment name
+ operational-environment-type:
+ type: string
+ description: Operational Environment Type.
+ operational-environment-status:
+ type: string
+ description: Status
+ tenant-context:
+ type: string
+ description: Tenant Context.
+ workload-context:
+ type: string
+ description: Workload Context.
+ operational-environments:
+ description: |
+ a logical partition of the cloud which allows to have multiple environments in the production AIC.
+ properties:
+ operational-environment:
type: array
items:
- $ref: "#/definitions/cvlan-tag-entry"
+ $ref: "#/patchDefinitions/operational-environment"
+ overloaded-model:
+ description: |
+ Allows for legacy POST of old-style and new-style models
+ required:
+ - model-invariant-id
+ - model-name-version-id
+ - model-type
+ - model-name
+ - model-id
+ - model-version
+ properties:
+ model-invariant-id:
+ type: string
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ model-name-version-id:
+ type: string
+ description: Unique identifier corresponding to one version of a model in ASDC
+ model-type:
+ type: string
+ description: Type of the model, e.g., service, resource, widget, etc.
+ model-name:
+ type: string
+ description: Name of the model, which can change from version to version.
+ model-id:
+ type: string
+ description: Invariant unique ID which does not change from version to version
+ model-version:
+ type: string
+ description: Version
+ model-description:
+ type: string
+ description: Description
+ owning-entities:
+ description: |
+ Collection of owning-entities
+ properties:
+ owning-entity:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/owning-entity"
+ owning-entity:
+ description: |
+ describes an owning-entity
+ ###### Related Nodes
+ - FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo owning-entity, MANY2ONE)
+ required:
+ - owning-entity-id
+ - owning-entity-name
+ properties:
+ owning-entity-id:
+ type: string
+ description: UUID of an owning entity
+ owning-entity-name:
+ type: string
+ description: Owning entity name
+ p-interface:
+ description: |
+ Physical interface (e.g., nic)
+ ###### Related Nodes
+ - TO logical-link( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)
+ - TO physical-link( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)
+ - TO pnf( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - TO pserver( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - TO vpls-pe( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM lag-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)
+ - P-INTERFACE is DELETED when these are DELETED L-INTERFACE
+ - P-INTERFACE deletion means associated objects of these types are also DELETED:PHYSICAL-LINK
+ required:
+ - interface-name
+ - in-maint
+ properties:
+ interface-name:
+ type: string
+ description: Name that identifies the physical interface
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ port-description:
+ type: string
+ description: Nature of the services and connectivity on this port.
+ equipment-identifier:
+ type: string
+ description: CLEI or other specification for p-interface hardware.
+ interface-role:
+ type: string
+ description: Role specification for p-interface hardware.
+ interface-type:
+ type: string
+ description: Indicates the physical properties of the interface.
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ p-interfaces:
+ description: |
+ Collection of physical interfaces.
+ properties:
+ p-interface:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/p-interface"
+ physical-link:
+ description: |
+ Collection of physical connections, typically between p-interfaces
+ ###### Related Nodes
+ - FROM p-interface( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)
+ required:
+ - link-name
+ properties:
+ link-name:
+ type: string
+ description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ circuit-id:
+ type: string
+ description: Circuit it
+ dual-mode:
+ type: string
+ description: Dual access mode (e.g., primary, secondary
+ management-option:
+ type: string
+ description: To provide information on who manages this circuit. A&AI or 3rd party transport provider
+ service-provider-name:
+ type: string
+ description: Name of the service Provider on this link.
+ physical-links:
+ description: |
+ Collection of physical connections, typically between p-interfaces
+ properties:
+ physical-link:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/physical-link"
+ platform:
+ description: |
+ describes a platform
+ ###### Related Nodes
+ - TO generic-vnf( platform org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)
+ required:
+ - platform-name
+ properties:
+ platform-name:
+ type: string
+ description: Name of the platform
+ platforms:
+ description: |
+ Collection of platforms
+ properties:
+ platform:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/platform"
+ pnf:
+ description: |
+ PNF represents a physical network function. typically equipment used in the D1 world.
+ ###### Related Nodes
+ - TO complex( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO instance-group( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO zone( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf pnf, ONE2MANY)
+ - PNF is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
+ required:
+ - pnf-name
+ - in-maint
+ properties:
+ pnf-name:
+ type: string
+ description: unique name of Physical Network Function.
+ pnf-name2:
+ type: string
+ description: name of Physical Network Function.
+ pnf-name2-source:
+ type: string
+ description: source of name2
+ pnf-id:
+ type: string
+ description: id of pnf
+ equip-type:
+ type: string
+ description: Equipment type. Source of truth should define valid values.
+ equip-vendor:
+ type: string
+ description: Equipment vendor. Source of truth should define valid values.
+ equip-model:
+ type: string
+ description: Equipment model. Source of truth should define valid values.
+ management-option:
+ type: string
+ description: identifier of managed by company or customer
+ ipaddress-v4-oam:
+ type: string
+ description: ipv4-oam-address with new naming convention for IP addresses
+ sw-version:
+ type: string
+ description: sw-version is the version of SW for the hosted application on the PNF.
+ in-maint:
+ type: boolean
+ frame-id:
+ type: string
+ description: ID of the physical frame (relay rack) where pnf is installed.
+ serial-number:
+ type: string
+ description: Serial number of the device
+ ipaddress-v4-loopback-0:
+ type: string
+ description: IPV4 Loopback 0 address
+ ipaddress-v6-loopback-0:
+ type: string
+ description: IPV6 Loopback 0 address
+ ipaddress-v4-aim:
+ type: string
+ description: IPV4 AIM address
+ ipaddress-v6-aim:
+ type: string
+ description: IPV6 AIM address
+ ipaddress-v6-oam:
+ type: string
+ description: IPV6 OAM address
+ inv-status:
+ type: string
+ description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
+ pnfs:
+ description: |
+ Collection of Physical Network Functions.
+ properties:
+ pnf:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/pnf"
port-group:
description: |
Used to capture the network interfaces of this VCE
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
###### Related Nodes
- - TO cvlan-tag (comprises port-group, Many2Many)
- - FROM vce (is composed of port-group)
+ - TO vce( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM cvlan-tag( cvlan-tag org.onap.relationships.inventory.BelongsTo port-group, MANY2ONE)
+ - PORT-GROUP is DELETED when these are DELETED CVLAN-TAG
required:
- interface-id
- orchestration-status
@@ -40657,120 +56229,913 @@ definitions:
interface-role:
type: string
description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
- resource-version:
+ port-groups:
+ properties:
+ port-group:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/port-group"
+ project:
+ description: |
+ describes the project
+ ###### Related Nodes
+ - TO service-instance( project org.onap.relationships.inventory.Uses service-instance, ONE2MANY)
+ required:
+ - project-name
+ properties:
+ project-name:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- port-group-id:
+ description: Name of the project deploying a service
+ projects:
+ description: |
+ Collection of projects
+ properties:
+ project:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/project"
+ properties:
+ description: |
+ Property holder for query properties or instance properties
+ properties:
+ property-name:
type: string
- description: Unique ID for port group in vmware
- port-group-name:
+ property-value:
type: string
- description: Likely to duplicate value of neutron network name
- switch-name:
+ property-constraint:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query-element( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ required:
+ - property-constraint-uuid
+ - constraint-type
+ - property-name
+ - property-value
+ properties:
+ property-constraint-uuid:
type: string
- description: DVS or standard switch name (should be non-null for port groups associated with DVS)
- orchestration-status:
+ constraint-type:
type: string
- description: Orchestration status of this VNF, mastered by MSO
- heat-stack-id:
+ property-name:
type: string
- description: Heat stack id corresponding to this instance, managed by MSO
- mso-catalog-key:
+ property-value:
type: string
- description: Corresponds to the SDN-C catalog id used to configure this VCE
- cvlan-tags:
+ property-constraints:
+ properties:
+ property-constraint:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/property-constraint"
+ pserver:
+ description: |
+ Compute host whose hostname must be unique and must exactly match what is sent as a relationship to a vserver.
+ ###### Related Nodes
+ - TO group-assignment( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)
+ - TO availability-zone( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)
+ - TO cloud-region( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)
+ - TO complex( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO zone( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - FROM vserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)
+ - PSERVER cannot be deleted if linked to GENERIC-VNF,LOGICAL-LINK,VSERVER
+ - PSERVER is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
+ - PSERVER cannot be deleted if linked to GROUP-ASSIGNMENT
+ required:
+ - hostname
+ - in-maint
+ properties:
+ hostname:
+ type: string
+ description: Value from executing hostname on the compute node.
+ ptnii-equip-name:
+ type: string
+ description: PTNII name
+ number-of-cpus:
+ type: integer
+ format: int32
+ description: Number of cpus
+ disk-in-gigabytes:
+ type: integer
+ format: int32
+ description: Disk size, in GBs
+ ram-in-megabytes:
+ type: integer
+ format: int32
+ description: RAM size, in MBs
+ equip-type:
+ type: string
+ description: Equipment type. Source of truth should define valid values.
+ equip-vendor:
+ type: string
+ description: Equipment vendor. Source of truth should define valid values.
+ equip-model:
+ type: string
+ description: Equipment model. Source of truth should define valid values.
+ fqdn:
+ type: string
+ description: Fully-qualified domain name
+ pserver-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ ipv4-oam-address:
+ type: string
+ description: Used to configure device, also used for troubleshooting and is IP used for traps generated by device.
+ serial-number:
+ type: string
+ description: Serial number, may be queried
+ ipaddress-v4-loopback-0:
+ type: string
+ description: IPV4 Loopback 0 address
+ ipaddress-v6-loopback-0:
+ type: string
+ description: IPV6 Loopback 0 address
+ ipaddress-v4-aim:
+ type: string
+ description: IPV4 AIM address
+ ipaddress-v6-aim:
+ type: string
+ description: IPV6 AIM address
+ ipaddress-v6-oam:
+ type: string
+ description: IPV6 OAM address
+ inv-status:
+ type: string
+ description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
+ pserver-id:
+ type: string
+ description: ID of Pserver
+ internet-topology:
+ type: string
+ description: internet topology of Pserver
+ in-maint:
+ type: boolean
+ pservers:
+ description: |
+ Collection of compute hosts.
+ properties:
+ pserver:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/pserver"
+ query-parameters:
+ description: |
+ QueryParameters for performing a named-query or model query
+ properties:
+ named-query:
+ type: object
+ $ref: "#/patchDefinitions/named-query"
+ overloaded-model:
+ type: object
+ $ref: "#/patchDefinitions/overloaded-model"
+ related-lookup:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query-element( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ required:
+ - related-lookup-uuid
+ - source-node-type
+ - source-node-property
+ - target-node-type
+ - target-node-property
+ properties:
+ related-lookup-uuid:
+ type: string
+ source-node-type:
+ type: string
+ source-node-property:
+ type: string
+ target-node-type:
+ type: string
+ target-node-property:
+ type: string
+ property-collect-list:
+ type: string
+ related-lookups:
+ properties:
+ related-lookup:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/related-lookup"
+ related-to-property:
+ properties:
+ property-key:
+ type: string
+ description: Key part of a key/value pair
+ property-value:
+ type: string
+ description: Value part of a key/value pair
+ relationship:
+ properties:
+ related-to:
+ type: string
+ description: A keyword provided by A&AI to indicate type of node.
+ related-link:
+ type: string
+ description: URL to the object in A&AI.
+ relationship-data:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/relationship-data"
+ related-to-property:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/related-to-property"
+ relationship-data:
+ required:
+ - relationship-key
+ - relationship-value
+ properties:
+ relationship-key:
+ type: string
+ description: A keyword provided by A&AI to indicate an attribute.
+ relationship-value:
+ type: string
+ description: Value of the attribute.
+ reserved-prop-names:
+ description: |
+ Internal map to define some reserved properties of a vertex
+ properties:
+ last-mod-source-of-truth:
+ type: string
+ aai-node-type:
+ type: string
+ aai-created-ts:
+ type: integer
+ format: int64
+ aai-unique-key:
+ type: string
+ aai-last-mod-ts:
+ type: integer
+ format: int64
+ source-of-truth:
+ type: string
+ aai-uri:
+ type: string
+ response-list:
+ description: |
+ Response container for the results of a named-query or model query
+ properties:
+ inventory-response-items:
+ type: object
+ $ref: "#/patchDefinitions/inventory-response-items"
+ result-data:
+ properties:
+ resource-type:
+ type: string
+ description: The specific type of node in the A&AI graph
+ resource-link:
+ type: string
+ description: The URL to the specific resource
+ route-table-reference:
+ description: |
+ Openstack route table reference.
+ ###### Related Nodes
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)
+ required:
+ - route-table-reference-id
+ - route-table-reference-fqdn
+ properties:
+ route-table-reference-id:
+ type: string
+ description: Route Table Reference id, UUID assigned to this instance.
+ route-table-reference-fqdn:
+ type: string
+ description: FQDN entry in the route table.
+ route-table-references:
+ description: |
+ Collection of openstack route table references
+ properties:
+ route-table-reference:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/route-table-reference"
+ route-target:
+ description: |
+ Route target information
+ ###### Related Nodes
+ - TO vpn-binding( route-target org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2ONE)
+ required:
+ - global-route-target
+ - route-target-role
+ properties:
+ global-route-target:
+ type: string
+ description: Number used to identify an RT, globally unique in the network
+ route-target-role:
+ type: string
+ description: Role assigned to this route target
+ route-targets:
+ description: |
+ Collection of route target information
+ properties:
+ route-target:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/route-target"
+ routing-instance:
+ description: |
+ ###### Related Nodes
+ - TO site-pair-set( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)
+ - FROM site-pair( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)
+ - ROUTING-INSTANCE is DELETED when these are DELETED SITE-PAIR
+ required:
+ - routing-instance-id
+ properties:
+ routing-instance-id:
+ type: string
+ description: Unique id of routing instance
+ rpm-owner:
+ type: string
+ description: rpm owner
+ routing-instances:
+ description: |
+ set of probes related to generic-vnf routing instance
+ properties:
+ routing-instance:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/routing-instance"
+ sdn-zone-response:
+ properties:
+ oam-networks:
+ type: object
+ $ref: "#/patchDefinitions/oam-networks"
+ az-and-dvs-switches:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/az-and-dvs-switches"
+ search:
+ properties:
+ edge-tag-query-result:
+ type: object
+ $ref: "#/patchDefinitions/edge-tag-query-result"
+ edge-tag-query-request:
+ type: object
+ $ref: "#/patchDefinitions/edge-tag-query-request"
+ search-results:
+ type: object
+ $ref: "#/patchDefinitions/search-results"
+ sdn-zone-response:
+ type: object
+ $ref: "#/patchDefinitions/sdn-zone-response"
+ search-results:
+ properties:
+ result-data:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/result-data"
+ secondary-filt:
+ description: |
+ SecondaryFilt for performing a named-query or model query
+ secondary-filter:
+ properties:
+ property-name:
+ type: string
+ filter-type:
+ type: string
+ property-value:
+ type: string
+ secondary-filts:
+ description: |
+ SecondaryFilts for performing a named-query or model query
+ properties:
+ secondary-filt:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/secondary-filt"
+ segmentation-assignment:
+ description: |
+ Openstack segmentation assignment.
+ ###### Related Nodes
+ - TO l3-network( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ required:
+ - segmentation-id
+ properties:
+ segmentation-id:
+ type: string
+ description: Route Table Reference id, UUID assigned to this instance.
+ segmentation-assignments:
+ description: |
+ Collection of openstack segmentation assignments
+ properties:
+ segmentation-assignment:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/segmentation-assignment"
+ service:
+ description: |
+ Stand-in for service model definitions. Likely to be deprecated in favor of models from ASDC. Does not strictly map to ASDC services.
+ required:
+ - service-id
+ - service-description
+ properties:
+ service-id:
+ type: string
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ service-description:
+ type: string
+ description: Description of the service
+ service-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ service-capabilities:
+ description: |
+ Collection of service capabilities.
+ properties:
+ service-capability:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/service-capability"
+ service-capability:
+ description: |
+ Early definition of server/resource pairings, likely to be replaced by models. No new use should be made of this.
+ ###### Related Nodes
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - SERVICE-CAPABILITY cannot be deleted if linked to AVAILABILITY-ZONE,OAM-NETWORK
+ required:
+ - service-type
+ - vnf-type
+ properties:
+ service-type:
+ type: string
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ service-design-and-creation:
+ description: |
+ Namespace for objects managed by ASDC
+ properties:
+ vnf-images:
type: array
items:
- $ref: "#/definitions/cvlan-tag-entry"
- relationship-list:
+ $ref: "#/patchDefinitions/vnf-image"
+ services:
type: array
items:
- $ref: "#/definitions/relationship"
- port-groups:
+ $ref: "#/patchDefinitions/service"
+ service-capabilities:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/service-capability"
+ models:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/model"
+ named-queries:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/named-query"
+ service-instance:
+ description: |
+ Instance of a service
+ ###### Related Nodes
+ - TO generic-vnf( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)
+ - TO l3-network( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)
+ - TO allotted-resource( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY)
+ - TO connector( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)
+ - TO ctag-assignment( service-instance org.onap.relationships.inventory.Uses ctag-assignment, ONE2MANY)
+ - TO cvlan-tag( service-instance org.onap.relationships.inventory.ComposedOf cvlan-tag, MANY2MANY)
+ - TO instance-group( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO logical-link( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - TO pnf( service-instance org.onap.relationships.inventory.ComposedOf pnf, ONE2MANY)
+ - TO service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)
+ - TO vlan( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)
+ - TO service-subscription( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)
+ - TO vce( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)
+ - SERVICE-INSTANCE is DELETED when these are DELETED ALLOTTED-RESOURCE,METADATUM
+ - SERVICE-INSTANCE deletion means associated objects of these types are also DELETED:LOGICAL-LINK
+ required:
+ - service-instance-id
properties:
- port-group:
+ service-instance-id:
+ type: string
+ description: Uniquely identifies this instance of a service
+ service-instance-name:
+ type: string
+ description: This field will store a name assigned to the service-instance.
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ bandwidth-total:
+ type: string
+ description: Indicates the total bandwidth to be used for this service.
+ bandwidth-up-wan1:
+ type: string
+ description: indicates the upstream bandwidth this service will use on the WAN1 port of the physical device.
+ bandwidth-down-wan1:
+ type: string
+ description: indicates the downstream bandwidth this service will use on the WAN1 port of the physical device.
+ bandwidth-up-wan2:
+ type: string
+ description: indicates the upstream bandwidth this service will use on the WAN2 port of the physical device.
+ bandwidth-down-wan2:
+ type: string
+ description: indicates the downstream bandwidth this service will use on the WAN2 port of the physical device.
+ vhn-portal-url:
+ type: string
+ description: URL customers will use to access the vHN Portal.
+ service-instance-location-id:
+ type: string
+ description: An identifier that customers assign to the location where this service is being used.
+ service-instances:
+ description: |
+ Collection of service instances
+ properties:
+ service-instance:
type: array
items:
- $ref: "#/definitions/port-group"
- license:
+ $ref: "#/patchDefinitions/service-instance"
+ service-subscription:
description: |
- Metadata for license group.
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Object that group service instances.
###### Related Nodes
- - FROM generic-vnf (is composed of license)
- - FROM vce (is composed of license)
+ - TO customer( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)
+ - TO tenant( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)
+ - SERVICE-SUBSCRIPTION is DELETED when these are DELETED SERVICE-INSTANCE
required:
- - group-uuid
- - resource-uuid
+ - service-type
properties:
- group-uuid:
+ service-type:
type: string
- description: Unique ID for the license group the resource belongs to, should be uuid.
- resource-uuid:
+ description: Value defined by orchestration to identify this service across ECOMP.
+ temp-ub-sub-account-id:
type: string
- description: Unique ID of a license resource.
- resource-version:
+ description: This property will be deleted from A&AI in the near future. Only stop gap solution.
+ service-subscriptions:
+ description: |
+ Collection of objects that group service instances.
+ properties:
+ service-subscription:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/service-subscription"
+ services:
+ description: |
+ Collection of service model definitions. Likely to be deprecated in favor of models from ASDC.
+ properties:
+ service:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/service"
+ site-pair:
+ description: |
+ ###### Related Nodes
+ - TO routing-instance( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)
+ - FROM class-of-service( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)
+ - SITE-PAIR is DELETED when these are DELETED CLASS-OF-SERVICE
+ required:
+ - site-pair-id
+ properties:
+ site-pair-id:
type: string
- description: Concurrency value
- relationship-list:
+ description: unique identifier of probe
+ source-ip:
+ type: string
+ description: Prefix address
+ destination-ip:
+ type: string
+ description: Prefix address
+ ip-version:
+ type: string
+ description: ip version, v4, v6
+ destination-hostname:
+ type: string
+ description: Hostname of the destination equipment to which SLAs are measured against.
+ destination-equip-type:
+ type: string
+ description: The type of destinatination equipment. Could be Router, etc.
+ site-pair-set:
+ description: |
+ Set of instances for probes used to measure service level agreements
+ ###### Related Nodes
+ - TO generic-vnf( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM routing-instance( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)
+ - SITE-PAIR-SET is DELETED when these are DELETED ROUTING-INSTANCE
+ required:
+ - site-pair-set-id
+ properties:
+ site-pair-set-id:
+ type: string
+ description: Unique id of site pair set.
+ site-pair-sets:
+ description: |
+ Collection of sets of instances for probes related to generic-vnf
+ properties:
+ site-pair-set:
type: array
- items:
- $ref: "#/definitions/relationship"
- licenses:
+ items:
+ $ref: "#/patchDefinitions/site-pair-set"
+ site-pairs:
description: |
- Licenses to be allocated across resources, keyed by group-uuid and resource-uuid, related to license management
+ probe within a set
properties:
- license:
+ site-pair:
type: array
items:
- $ref: "#/definitions/license"
- entitlement:
+ $ref: "#/patchDefinitions/site-pair"
+ snapshot:
description: |
- Metadata for entitlement group.
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Openstack snapshot
###### Related Nodes
- - FROM generic-vnf (is composed of entitlement)
- - FROM vce (is composed of entitlement)
+ - TO cloud-region( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)
required:
- - group-uuid
- - resource-uuid
+ - snapshot-id
properties:
- group-uuid:
+ snapshot-id:
type: string
- description: Unique ID for the entitlement group the resource comes from, should be uuid.
- resource-uuid:
+ description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
+ snapshot-name:
type: string
- description: Unique ID of an entitlement resource.
- resource-version:
+ description: Snapshot name
+ snapshot-architecture:
type: string
- description: Concurrency value
- relationship-list:
+ description: Operating system architecture
+ snapshot-os-distro:
+ type: string
+ description: The common name of the operating system distribution in lowercase
+ snapshot-os-version:
+ type: string
+ description: The operating system version as specified by the distributor.
+ application:
+ type: string
+ description: The application that the image instantiates.
+ application-vendor:
+ type: string
+ description: The vendor of the application.
+ application-version:
+ type: string
+ description: The version of the application.
+ snapshot-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ prev-snapshot-id:
+ type: string
+ description: This field contains the UUID of the previous snapshot (if any).
+ snapshots:
+ description: |
+ Collection of openstack snapshots
+ properties:
+ snapshot:
type: array
- items:
- $ref: "#/definitions/relationship"
- entitlements:
+ items:
+ $ref: "#/patchDefinitions/snapshot"
+ sriov-pf:
description: |
- Entitlements, keyed by group-uuid and resource-uuid, related to license management
+ SR-IOV Physical Function
+ ###### Related Nodes
+ - TO p-interface( sriov-pf org.onap.relationships.inventory.BelongsTo p-interface, ONE2ONE)
+ - FROM sriov-vf( sriov-vf org.onap.relationships.inventory.Uses sriov-pf, MANY2ONE)
+ required:
+ - pf-pci-id
properties:
- entitlement:
+ pf-pci-id:
+ type: string
+ description: Identifier for the sriov-pf
+ sriov-pfs:
+ description: |
+ Collection of SR-IOV Physical Functions.
+ properties:
+ sriov-pf:
type: array
items:
- $ref: "#/definitions/entitlement"
+ $ref: "#/patchDefinitions/sriov-pf"
+ sriov-vf:
+ description: |
+ SR-IOV Virtual Function (not to be confused with virtual network function)
+ ###### Related Nodes
+ - TO l-interface( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)
+ required:
+ - pci-id
+ properties:
+ pci-id:
+ type: string
+ description: PCI ID used to identify the sriov-vf
+ vf-vlan-filter:
+ type: string
+ description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM.
+ vf-mac-filter:
+ type: string
+ description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM.
+ vf-vlan-strip:
+ type: boolean
+ description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM.
+ vf-vlan-anti-spoof-check:
+ type: boolean
+ description: This option ensures anti VLAN spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
+ vf-mac-anti-spoof-check:
+ type: boolean
+ description: This option ensures anti MAC spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
+ vf-mirrors:
+ type: string
+ description: This option defines the set of Mirror objects which essentially mirrors the traffic from source to set of collector VNF Ports.
+ vf-broadcast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows all broadcast traffic to reach the VM
+ vf-unknown-multicast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows unknown multicast traffic to reach the VM
+ vf-unknown-unicast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows unknown unicast traffic to reach the VM
+ vf-insert-stag:
+ type: boolean
+ description: This option, if set to true, instructs to insert outer tag after traffic comes out of VM.
+ vf-link-status:
+ type: string
+ description: This option is used to set the link status. Valid values as of 1607 are on, off, and auto.
+ sriov-vfs:
+ description: |
+ Collection of SR-IOV Virtual Functions.
+ properties:
+ sriov-vf:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/sriov-vf"
+ start-node-filter:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ subnet:
+ description: |
+ ###### Related Nodes
+ - TO l3-network( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - SUBNET cannot be deleted if linked to L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST
+ required:
+ - subnet-id
+ - dhcp-enabled
+ properties:
+ subnet-id:
+ type: string
+ description: Subnet ID, should be UUID.
+ subnet-name:
+ type: string
+ description: Name associated with the subnet.
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of this subnet
+ gateway-address:
+ type: string
+ description: gateway ip address
+ network-start-address:
+ type: string
+ description: network start address
+ cidr-mask:
+ type: string
+ description: cidr mask
+ ip-version:
+ type: string
+ description: ip version
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ dhcp-enabled:
+ type: boolean
+ dhcp-start:
+ type: string
+ description: the start address reserved for use by dhcp
+ dhcp-end:
+ type: string
+ description: the last address reserved for use by dhcp
+ subnets:
+ properties:
+ subnet:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/subnet"
+ tagged-inventory-item-list:
+ properties:
+ inventory-item:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/inventory-item"
+ tenant:
+ description: |
+ Openstack tenant
+ ###### Related Nodes
+ - TO cloud-region( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO group-assignment( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)
+ - TO l3-network( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO volume-group( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - FROM service-subscription( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)
+ - FROM vserver( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)
+ - TENANT cannot be deleted if linked to VSERVER
+ required:
+ - tenant-id
+ - tenant-name
+ properties:
+ tenant-id:
+ type: string
+ description: Unique id relative to the cloud-region.
+ tenant-name:
+ type: string
+ description: Readable name of tenant
+ tenants:
+ description: |
+ Collection of openstack tenants.
+ properties:
+ tenant:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/tenant"
+ tunnel-xconnect:
+ description: |
+ Represents the specifics of a tunnel cross connect piece of a resource that gets separately allotted
+ ###### Related Nodes
+ - TO allotted-resource( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)
+ required:
+ - id
+ - bandwidth-up-wan1
+ - bandwidth-down-wan1
+ - bandwidth-up-wan2
+ - bandwidth-down-wan2
+ properties:
+ id:
+ type: string
+ description: Allotted Resource id UUID assigned to this instance.
+ bandwidth-up-wan1:
+ type: string
+ description: The WAN uplink bandwidth for WAN1
+ bandwidth-down-wan1:
+ type: string
+ description: The WAN downlink bandwidth for WAN1
+ bandwidth-up-wan2:
+ type: string
+ description: The WAN uplink bandwidth for WAN2
+ bandwidth-down-wan2:
+ type: string
+ description: The WAN downlink bandwidth for WAN2
+ tunnel-xconnects:
+ description: |
+ This object is used to store the specific tunnel cross connect aspects of an allotted resource
+ properties:
+ tunnel-xconnect:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/tunnel-xconnect"
+ update:
+ description: |
+ Serves a PATCH like function. Does not enforce concurrency control. Clear each usage with AAI team.
+ required:
+ - update-node-type
+ properties:
+ update-node-type:
+ type: string
+ update-node-key:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/update-node-key"
+ update-node-uri:
+ type: string
+ action:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/action"
+ update-node-key:
+ properties:
+ key-name:
+ type: string
+ key-value:
+ type: string
vce:
description: |
Virtual Customer Edge Router, used specifically for Gamma. This object is deprecated.
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
###### Related Nodes
- - TO availability-zone (Many2Many)
- - TO complex (Many2Many)
- - TO port-group (comprises vce, Many2Many)
- - TO vserver (Many2Many)
- - TO service-instance (Many2Many)
- - TO entitlement (comprises vce, One2Many)
- - TO license (comprises vce, One2Many)
+ - TO availability-zone( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - TO complex( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)
+ - TO vserver( vce tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM entitlement( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM license( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM port-group( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)
+ - VCE is DELETED when these are DELETED ENTITLEMENT,LICENSE,PORT-GROUP
required:
- vnf-id
- vnf-name
@@ -40824,47 +57189,239 @@ definitions:
ipv4-oam-address:
type: string
description: Address tail-f uses to configure vce, also used for troubleshooting and is IP used for traps generated by VCE.
- resource-version:
+ vces:
+ description: |
+ Collection of Virtual Customer Edge Routers, used specifically for Gamma. This object is deprecated.
+ properties:
+ vce:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vce"
+ vf-module:
+ description: |
+ a deployment unit of VNFCs
+ ###### Related Nodes
+ - TO generic-vnf( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO l3-network( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)
+ - TO vnfc( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)
+ - TO volume-group( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)
+ - TO vserver( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)
+ - VF-MODULE cannot be deleted if linked to VNFC
+ required:
+ - vf-module-id
+ - is-base-vf-module
+ properties:
+ vf-module-id:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- ipv4-loopback0-address:
+ description: Unique ID of vf-module.
+ vf-module-name:
type: string
- description: Loopback0 address
- entitlement-resource-uuid:
+ description: Name of vf-module
+ heat-stack-id:
type: string
- description: OBSOLETE - see child relationships
- port-groups:
+ description: Heat stack id corresponding to this instance.
+ orchestration-status:
+ type: string
+ description: orchestration status of this vf-module, mastered by MSO
+ is-base-vf-module:
+ type: boolean
+ vf-modules:
+ description: |
+ Collection of vf-modules, a deployment unit of VNFCs
+ properties:
+ vf-module:
type: array
- items:
- $ref: "#/definitions/port-group"
- licenses:
+ items:
+ $ref: "#/patchDefinitions/vf-module"
+ vig-server:
+ description: |
+ vig-server contains information about a vig server used for IPSec-configuration. Populated by SDN-C from 1607
+ ###### Related Nodes
+ - TO ipsec-configuration( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)
+ required:
+ - vig-address-type
+ properties:
+ vig-address-type:
+ type: string
+ description: indicates whether the VIG is for AVPN or INTERNET
+ ipaddress-v4-vig:
+ type: string
+ description: v4 IP of the vig server
+ ipaddress-v6-vig:
+ type: string
+ description: v6 IP of the vig server
+ vig-servers:
+ properties:
+ vig-server:
type: array
- items:
- $ref: "#/definitions/license"
- entitlements:
+ items:
+ $ref: "#/patchDefinitions/vig-server"
+ vip-ipv4-address-list:
+ description: |
+ IPv4 Address Range
+ ###### Related Nodes
+ - TO cloud-region( vip-ipv4-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO instance-group( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO subnet( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv4-address-list, MANY2MANY)
+ required:
+ - vip-ipv4-address
+ properties:
+ vip-ipv4-address:
+ type: string
+ description: IP address
+ vip-ipv4-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 32 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ vip-ipv6-address-list:
+ description: |
+ IPv6 Address Range
+ ###### Related Nodes
+ - TO cloud-region( vip-ipv6-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO instance-group( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO subnet( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv6-address-list, MANY2MANY)
+ required:
+ - vip-ipv6-address
+ properties:
+ vip-ipv6-address:
+ type: string
+ description: IP address
+ vip-ipv6-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 128 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ virtual-data-center:
+ description: |
+ Virtual organization of cloud infrastructure elements in a data center context
+ ###### Related Nodes
+ - FROM connector( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ required:
+ - vdc-id
+ - vdc-name
+ properties:
+ vdc-id:
+ type: string
+ description: Unique ID of the vdc
+ vdc-name:
+ type: string
+ description: Name of the virtual data center
+ virtual-data-centers:
+ description: |
+ Virtual organization of cloud infrastructure elements in a data center context
+ properties:
+ virtual-data-center:
type: array
- items:
- $ref: "#/definitions/entitlement"
- relationship-list:
+ items:
+ $ref: "#/patchDefinitions/virtual-data-center"
+ vlan:
+ description: |
+ Definition of vlan
+ ###### Related Nodes
+ - TO l-interface( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)
+ - TO logical-link( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - TO multicast-configuration( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ - VLAN is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST
+ - VLAN deletion means associated objects of these types are also DELETED:LOGICAL-LINK
+ required:
+ - vlan-interface
+ - in-maint
+ properties:
+ vlan-interface:
+ type: string
+ description: String that identifies the interface
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ vlans:
+ properties:
+ vlan:
type: array
- items:
- $ref: "#/definitions/relationship"
- vces:
+ items:
+ $ref: "#/patchDefinitions/vlan"
+ vnf:
description: |
- Collection of Virtual Customer Edge Routers, used specifically for Gamma. This object is deprecated.
+ Abstract vnf class
+ required:
+ - vnf-id
properties:
- vce:
+ vnf-id:
+ type: string
+ description: Unique id of VNF. This is unique across the graph.
+ vnf-image:
+ description: |
+ Image object that pertain to a VNF that doesn't have associated vservers. This is a kludge.
+ ###### Related Nodes
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)
+ - VNF-IMAGE cannot be deleted if linked to GENERIC-VNF
+ required:
+ - vnf-image-uuid
+ - application
+ - application-vendor
+ properties:
+ vnf-image-uuid:
+ type: string
+ description: Unique ID of this asset
+ application:
+ type: string
+ description: The application that the image instantiates.
+ application-vendor:
+ type: string
+ description: The vendor of the application.
+ application-version:
+ type: string
+ description: The version of the application.
+ selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ vnf-images:
+ description: |
+ Collection of image objects that pertain to a VNF that doesn't have associated vservers. This is a kludge.
+ properties:
+ vnf-image:
type: array
items:
- $ref: "#/definitions/vce"
+ $ref: "#/patchDefinitions/vnf-image"
vnfc:
description: |
- ###### Default Delete Scope
- THIS_NODE_ONLY
###### Related Nodes
- - FROM vserver
- - FROM vf-module
- - FROM generic-vnf
+ - TO generic-vnf( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vserver( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)
required:
- vnfc-name
- vnfc-function-code
@@ -40897,13 +57454,6 @@ definitions:
group-notation:
type: string
description: Group notation of VNFC
- resource-version:
- type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- relationship-list:
- type: array
- items:
- $ref: "#/definitions/relationship"
vnfcs:
description: |
virtual network components associated with a vserver from application controller.
@@ -40911,190 +57461,710 @@ definitions:
vnfc:
type: array
items:
- $ref: "#/definitions/vnfc"
- subnet:
+ $ref: "#/patchDefinitions/vnfc"
+ volume:
description: |
- ###### Default Delete Scope
- ERROR_IF_ANY_IN_EDGES
+ Ephemeral Block storage volume.
###### Related Nodes
- - FROM l3-interface-ipv4-address-list
- - FROM l3-interface-ipv6-address-list
- - FROM l3-network (is composed of subnet)
+ - FROM vserver (PARENT of volume, vserver tosca.relationships.AttachesTo volume)
required:
- - subnet-id
- - dhcp-enabled
+ - volume-id
+ - volume-selflink
properties:
- subnet-id:
- type: string
- description: Subnet ID, should be UUID.
- subnet-name:
+ volume-id:
type: string
- description: Name associated with the subnet.
- neutron-subnet-id:
+ description: Unique ID of block storage volume relative to the vserver.
+ volume-selflink:
type: string
- description: Neutron id of this subnet
- gateway-address:
+ description: URL to endpoint where AAI can get more details
+ volume-group:
+ description: |
+ Persistent block-level storage.
+ ###### Related Nodes
+ - TO cloud-region( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO complex( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ required:
+ - volume-group-id
+ - volume-group-name
+ - vnf-type
+ properties:
+ volume-group-id:
type: string
- description: gateway ip address
- network-start-address:
+ description: Unique ID of volume-group.
+ volume-group-name:
type: string
- description: network start address
- cidr-mask:
+ description: Name of the volume group.
+ heat-stack-id:
type: string
- description: cidr mask
- ip-version:
+ description: Heat stack id corresponding to this volume-group
+ vnf-type:
type: string
- description: ip version
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
orchestration-status:
type: string
- description: Orchestration status of this VNF, mastered by MSO
- dhcp-enabled:
+ description: Orchestration status of this volume-group
+ model-customization-id:
+ type: string
+ description: captures the id of all the configuration used to customize the resource for the service.
+ vf-module-model-customization-id:
+ type: string
+ description: helps relate the volume group to the vf-module whose components will require the volume group
+ volume-groups:
+ description: |
+ Collection of persistent block-level storage.
+ properties:
+ volume-group:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/volume-group"
+ volumes:
+ description: |
+ Collection of ephemeral Block storage volumes.
+ properties:
+ volume:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/volume"
+ vpls-pe:
+ description: |
+ VPLS Provider Edge routers.
+ ###### Related Nodes
+ - TO complex( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO ctag-pool( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - VPLS-PE is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
+ required:
+ - equipment-name
+ properties:
+ equipment-name:
+ type: string
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address).
+ equipment-role:
+ type: string
+ description: Client should send valid enumerated value, e.g., VPLS-PE.
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Temporary location for stag to get to VCE
+ vpls-pes:
+ description: |
+ Collection of VPLS Provider Edge routers
+ properties:
+ vpls-pe:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vpls-pe"
+ vpn-binding:
+ description: |
+ VPN binding
+ ###### Related Nodes
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - FROM route-target( route-target org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2ONE)
+ - VPN-BINDING cannot be deleted if linked to L3-NETWORK,LOGICAL-LINK
+ - VPN-BINDING is DELETED when these are DELETED ROUTE-TARGET
+ required:
+ - vpn-id
+ - vpn-name
+ properties:
+ vpn-id:
+ type: string
+ description: VPN ID, globally unique within A&AI
+ vpn-name:
+ type: string
+ description: VPN Name
+ vpn-platform:
+ type: string
+ description: the platform associated with the VPN example AVPN, Mobility
+ vpn-type:
+ type: string
+ description: Type of the vpn, should be taken from enumerated/valid values
+ route-distinguisher:
+ type: string
+ description: Used to distinguish the distinct VPN routes of separate customers who connect to the provider in an MPLS network.
+ vpn-bindings:
+ properties:
+ vpn-binding:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vpn-binding"
+ vserver:
+ description: |
+ Virtual Servers, aka virtual machine or VM.
+ ###### Related Nodes
+ - TO tenant( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)
+ - TO flavor( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)
+ - TO image( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)
+ - TO pserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)
+ - TO snapshot( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)
+ - TO volume (CHILD of vserver, vserver tosca.relationships.AttachesTo volume, ONE2MANY)
+ - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM vce( vce tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)
+ - FROM vnfc( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)
+ - VSERVER is DELETED when these are DELETED L-INTERFACE
+ - VSERVER deletion means associated objects of these types are also DELETED:VOLUME
+ required:
+ - vserver-id
+ - vserver-name
+ - vserver-selflink
+ - in-maint
+ - is-closed-loop-disabled
+ properties:
+ vserver-id:
+ type: string
+ description: Unique identifier for this vserver relative to its tenant
+ vserver-name:
+ type: string
+ description: Name of vserver
+ vserver-name2:
+ type: string
+ description: Alternative name of vserver
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ vserver-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ in-maint:
type: boolean
- dhcp-start:
+ is-closed-loop-disabled:
+ type: boolean
+ vservers:
+ description: |
+ Collection of virtual Servers, aka virtual machines or VMs.
+ properties:
+ vserver:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vserver"
+ zone:
+ description: |
+ A zone is a grouping of assets in a location homing to the same connections into the CBB
+ ###### Related Nodes
+ - TO complex( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM pnf( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ required:
+ - zone-id
+ - zone-name
+ - design-type
+ - zone-context
+ properties:
+ zone-id:
type: string
- description: the start address reserved for use by dhcp
- dhcp-end:
+ description: Code assigned by AIC to the zone
+ zone-name:
type: string
- description: the last address reserved for use by dhcp
+ description: English name associated with the zone
+ design-type:
+ type: string
+ description: Design of zone [Medium/Large?]
+ zone-context:
+ type: string
+ description: Context of zone [production/test]
+ status:
+ type: string
+ description: Status of a zone.
+ zones:
+ description: |
+ Collection of zones
+ properties:
+ zone:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/zone"
+getDefinitions:
+ aai-internal:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ action:
+ properties:
+ action-type:
+ type: string
+ action-data:
+ type: array
+ items:
+ $ref: "#/getDefinitions/action-data"
+ action-data:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ actions:
+ description: |
+ APIs that are more action related than REST (e.g., notify, update).
+ properties:
+ update:
+ type: object
+ $ref: "#/getDefinitions/update"
+ notify:
+ type: object
+ $ref: "#/getDefinitions/notify"
+ allotted-resource:
+ description: |
+ Represents a slice or partial piece of a resource that gets separately allotted
+ ###### Related Nodes
+ - TO generic-vnf( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY)
+ - TO instance-group( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO l3-network( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY)
+ - TO network-policy( allotted-resource org.onap.relationships.inventory.Uses network-policy, ONE2ONE)
+ - TO vlan( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY)
+ - TO service-instance( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM tunnel-xconnect( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY)
+ - ALLOTTED-RESOURCE is DELETED when these are DELETED TUNNEL-XCONNECT
+ required:
+ - id
+ properties:
+ id:
+ type: string
+ description: Allotted Resource id UUID assigned to this instance.
+ description:
+ type: string
+ description: The descriptive information assigned to this allotted resource instance
+ selflink:
+ type: string
+ description: Link back to more information in the controller
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
resource-version:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ description: Concurrency value
+ orchestration-status:
+ type: string
+ description: Orchestration status
+ operational-status:
+ type: string
+ description: Indicator for whether the resource is considered operational
+ type:
+ type: string
+ description: Generic description of the type of allotted resource.
+ role:
+ type: string
+ description: role in the network that this resource will be providing.
+ tunnel-xconnects:
+ type: array
+ items:
+ $ref: "#/getDefinitions/tunnel-xconnect"
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- subnets:
+ $ref: "#/getDefinitions/relationship"
+ allotted-resources:
+ description: |
+ This object is used to store slices of services being offered
properties:
- subnet:
+ allotted-resource:
type: array
items:
- $ref: "#/definitions/subnet"
- ctag-assignment:
+ $ref: "#/getDefinitions/allotted-resource"
+ availability-zone:
description: |
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Availability zone, a collection of compute hosts/pservers
###### Related Nodes
- - FROM l3-network (is composed of ctag-assignment)
- - FROM service-instance
+ - TO complex( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO service-capability( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - TO cloud-region( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM ctag-pool( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM dvs-switch( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - FROM pserver( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)
+ - FROM vce( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - AVAILABILITY-ZONE cannot be deleted if linked to CTAG-POOL,DVS-SWITCH,GENERIC-VNF,PSERVER,VCE
required:
- - vlan-id-inner
+ - availability-zone-name
+ - hypervisor-type
properties:
- vlan-id-inner:
- type: integer
- format: int64
- description: id.
+ availability-zone-name:
+ type: string
+ description: Name of the availability zone. Unique across a cloud region
+ hypervisor-type:
+ type: string
+ description: Type of hypervisor. Source of truth should define valid values.
+ operational-status:
+ type: string
+ description: State that indicates whether the availability zone should be used, etc. Source of truth should define valid values.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- ctag-assignments:
+ $ref: "#/getDefinitions/relationship"
+ availability-zones:
+ description: |
+ Collection of availability zones
properties:
- ctag-assignment:
+ availability-zone:
type: array
items:
- $ref: "#/definitions/ctag-assignment"
- segmentation-assignment:
+ $ref: "#/getDefinitions/availability-zone"
+ az-and-dvs-switches:
+ properties:
+ dvs-switches:
+ type: object
+ $ref: "#/getDefinitions/dvs-switches"
+ availability-zone:
+ type: object
+ $ref: "#/getDefinitions/availability-zone"
+ business:
+ description: |
+ Namespace for business related constructs
+ properties:
+ connectors:
+ type: array
+ items:
+ $ref: "#/getDefinitions/connector"
+ customers:
+ type: array
+ items:
+ $ref: "#/getDefinitions/customer"
+ class-of-service:
description: |
- Openstack segmentation assignment.
- ###### Default Delete Scope
- THIS_NODE_ONLY
###### Related Nodes
- - FROM l3-network (is composed of segmentation-assignment)
+ - TO site-pair( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)
required:
- - segmentation-id
+ - cos
properties:
- segmentation-id:
+ cos:
type: string
- description: Route Table Reference id, UUID assigned to this instance.
+ description: unique identifier of probe
+ probe-id:
+ type: string
+ description: identifier of probe
+ probe-type:
+ type: string
+ description: type of probe
resource-version:
type: string
- description: Concurrency value
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- segmentation-assignments:
+ $ref: "#/getDefinitions/relationship"
+ classes-of-service:
description: |
- Collection of openstack segmentation assignments
+ class-of-service of probe
properties:
- segmentation-assignment:
+ class-of-service:
type: array
items:
- $ref: "#/definitions/segmentation-assignment"
- l3-network:
+ $ref: "#/getDefinitions/class-of-service"
+ cloud-infrastructure:
description: |
- Generic network definition
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
- ###### Related Nodes
- - TO vpn-binding (Many2Many)
- - TO subnet (comprises l3-network, Many2Many)
- - TO service-instance (Many2Many)
- - TO ctag-assignment (comprises l3-network, Many2Many)
- - TO network-policy (Many2Many)
- - TO segmentation-assignment (comprises l3-network, One2Many)
- - TO route-table-reference (Many2Many)
- - FROM cloud-region
- - FROM complex
- - FROM generic-vnf
- - FROM l3-interface-ipv4-address-list
- - FROM l3-interface-ipv6-address-list
- - FROM tenant
- - FROM vf-module
- - FROM allotted-resource
+ Namespace for cloud infrastructure.
+ properties:
+ complexes:
+ type: array
+ items:
+ $ref: "#/getDefinitions/complex"
+ cloud-regions:
+ type: array
+ items:
+ $ref: "#/getDefinitions/cloud-region"
+ network-profiles:
+ type: array
+ items:
+ $ref: "#/getDefinitions/network-profile"
+ pservers:
+ type: array
+ items:
+ $ref: "#/getDefinitions/pserver"
+ virtual-data-centers:
+ type: array
+ items:
+ $ref: "#/getDefinitions/virtual-data-center"
+ cloud-region:
+ description: |
+ cloud-region designates an installation of a cloud cluster or region or instantiation
+ ###### Related Nodes
+ - TO complex( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO l3-network( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO zone( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM dvs-switch( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM flavor( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM group-assignment( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM image( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM snapshot( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM volume-group( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn cloud-region, MANY2MANY)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)
+ - CLOUD-REGION cannot be deleted if linked to DVS-SWITCH,FLAVOR,GROUP-ASSIGNMENT,IMAGE,OAM-NETWORK,SNAPSHOT,TENANT,VOLUME-GROUP
+ - CLOUD-REGION is DELETED when these are DELETED AVAILABILITY-ZONE
required:
- - network-id
- - network-name
- - is-bound-to-vpn
- - is-provider-network
- - is-shared-network
- - is-external-network
+ - cloud-owner
+ - cloud-region-id
properties:
- network-id:
+ cloud-owner:
type: string
- description: Network ID, should be uuid. Unique across A&AI.
- network-name:
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ cloud-region-id:
type: string
- description: Name of the network, governed by some naming convention..
- network-type:
+ description: Identifier used by the vendor for the region. Second part of composite key
+ cloud-type:
type: string
- description: Type of the network - who defines these values?
- network-role:
+ description: Type of the cloud (e.g., openstack)
+ owner-defined-type:
type: string
- description: Role the network plans - who defines these values?
- network-technology:
+ description: Cloud-owner defined type indicator (e.g., dcp, lcp)
+ cloud-region-version:
type: string
- description: Network technology - who defines these values?
- neutron-network-id:
+ description: Software version employed at the site. NOTE - THIS FIELD IS NOT KEPT UP TO DATE.
+ identity-url:
type: string
- description: Neutron network id of this Interface
- is-bound-to-vpn:
- type: boolean
- service-id:
+ description: URL of the keystone identity service
+ cloud-zone:
type: string
- description: Unique identifier of service from ASDC. Does not strictly map to ASDC services. SOON TO BE DEPRECATED
- network-role-instance:
- type: integer
- format: int64
- description: network role instance
+ description: Zone where the cloud is homed. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
+ complex-name:
+ type: string
+ description: complex name for cloud-region instance. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ volume-groups:
+ type: array
+ items:
+ $ref: "#/getDefinitions/volume-group"
+ tenants:
+ type: array
+ items:
+ $ref: "#/getDefinitions/tenant"
+ flavors:
+ type: array
+ items:
+ $ref: "#/getDefinitions/flavor"
+ group-assignments:
+ type: array
+ items:
+ $ref: "#/getDefinitions/group-assignment"
+ snapshots:
+ type: array
+ items:
+ $ref: "#/getDefinitions/snapshot"
+ images:
+ type: array
+ items:
+ $ref: "#/getDefinitions/image"
+ dvs-switches:
+ type: array
+ items:
+ $ref: "#/getDefinitions/dvs-switch"
+ oam-networks:
+ type: array
+ items:
+ $ref: "#/getDefinitions/oam-network"
+ availability-zones:
+ type: array
+ items:
+ $ref: "#/getDefinitions/availability-zone"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ cloud-regions:
+ properties:
+ cloud-region:
+ type: array
+ items:
+ $ref: "#/getDefinitions/cloud-region"
+ complex:
+ description: |
+ Collection of physical locations that can house cloud-regions.
+ ###### Related Nodes
+ - TO l3-network( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM ctag-pool( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)
+ - FROM pnf( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM vce( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)
+ - FROM volume-group( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM vpls-pe( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM zone( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - COMPLEX cannot be deleted if linked to AVAILABILITY-ZONE,CLOUD-REGION,OAM-NETWORK,PNF,PSERVER,VCE,VOLUME-GROUP,VPLS-PE,ZONE
+ - COMPLEX is DELETED when these are DELETED CTAG-POOL
+ required:
+ - physical-location-id
+ - physical-location-type
+ - street1
+ - city
+ - postal-code
+ - country
+ - region
+ properties:
+ physical-location-id:
+ type: string
+ description: Unique identifier for physical location, e.g., CLLI
+ data-center-code:
+ type: string
+ description: Data center code which can be an alternate way to identify a complex
+ complex-name:
+ type: string
+ description: Gamma complex name for LCP instance.
+ identity-url:
+ type: string
+ description: URL of the keystone identity service
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ physical-location-type:
+ type: string
+ description: Type, e.g., central office, data center.
+ street1:
+ type: string
+ street2:
+ type: string
+ city:
+ type: string
+ state:
+ type: string
+ postal-code:
+ type: string
+ country:
+ type: string
+ region:
+ type: string
+ latitude:
+ type: string
+ longitude:
+ type: string
+ elevation:
+ type: string
+ lata:
+ type: string
+ ctag-pools:
+ type: array
+ items:
+ $ref: "#/getDefinitions/ctag-pool"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ complexes:
+ description: |
+ Collection of physical locations that can house cloud-regions.
+ properties:
+ complex:
+ type: array
+ items:
+ $ref: "#/getDefinitions/complex"
+ configuration:
+ description: |
+ Port Mirror Configuration.
+ ###### Related Nodes
+ - TO allotted-resource( configuration org.onap.relationships.inventory.Uses allotted-resource, ONE2ONE)
+ - TO logical-link( configuration org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo configuration, MANY2ONE)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses configuration, ONE2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses configuration, ONE2MANY)
+ - CONFIGURATION is DELETED when these are DELETED METADATUM
+ - CONFIGURATION deletion means associated objects of these types are also DELETED:ALLOTTED-RESOURCE,LOGICAL-LINK
+ required:
+ - configuration-id
+ - configuration-type
+ - configuration-sub-type
+ - orchestration-status
+ - operational-status
+ - configuration-selflink
+ - model-customization-id
+ properties:
+ configuration-id:
+ type: string
+ description: UUID assigned to configuration.
+ management-option:
+ type: string
+ description: Indicates the entity that will manage this feature. Could be an organization or the name of the application as well.
+ configuration-name:
+ type: string
+ description: Name of the configuration.
+ configuration-type:
+ type: string
+ description: port-mirroring-configuration.
+ configuration-sub-type:
+ type: string
+ description: vprobe, pprobe.
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
orchestration-status:
type: string
- description: Orchestration status of this VNF, mastered by MSO
- heat-stack-id:
+ description: Orchestration status of the configuration.
+ operational-status:
type: string
- description: Heat stack id corresponding to this instance, managed by MSO
- mso-catalog-key:
+ description: Indicator for whether the resource is considered operational.
+ configuration-selflink:
type: string
- description: Corresponds to the SDN-C catalog id used to configure this VCE
- contrail-network-fqdn:
+ description: URL to endpoint where AAI can get more details from SDN-GC.
+ model-customization-id:
type: string
- description: Contrail FQDN for the network
+ description: id of the configuration used to customize the resource
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ metadata:
+ type: array
+ items:
+ $ref: "#/getDefinitions/metadatum"
+ configurations:
+ description: |
+ Collection of configurations
+ properties:
+ configuration:
+ type: array
+ items:
+ $ref: "#/getDefinitions/configuration"
+ connector:
+ description: |
+ Collection of resource instances used to connect a variety of disparate inventory widgets
+ ###### Related Nodes
+ - TO virtual-data-center( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)
+ - CONNECTOR is DELETED when these are DELETED METADATUM
+ required:
+ - resource-instance-id
+ properties:
+ resource-instance-id:
+ type: string
+ description: Unique id of resource instance.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
model-invariant-id:
type: string
description: the ASDC model id for this resource or service model.
@@ -41104,184 +58174,791 @@ definitions:
persona-model-version:
type: string
description: the ASDC model version for this resource or service model.
- model-customization-id:
- type: string
- description: captures the id of all the configuration used to customize the resource for the service.
widget-model-id:
type: string
description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
widget-model-version:
type: string
description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
- physical-network-name:
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ metadata:
+ type: array
+ items:
+ $ref: "#/getDefinitions/metadatum"
+ connectors:
+ description: |
+ Collection of resource instances used to connect a variety of disparate inventory widgets
+ properties:
+ connector:
+ type: array
+ items:
+ $ref: "#/getDefinitions/connector"
+ constrained-element-set:
+ description: |
+ This is how we would capture constraints defining allowed sets of elements.
+ ###### Related Nodes
+ - TO model-constraint( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)
+ - TO model-element( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM element-choice-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)
+ - CONSTRAINED-ELEMENT-SET is DELETED when these are DELETED ELEMENT-CHOICE-SET
+ required:
+ - constrained-element-set-uuid
+ - constraint-type
+ - check-type
+ properties:
+ constrained-element-set-uuid:
type: string
- description: Name associated with the physical network.
- is-provider-network:
+ constraint-type:
+ type: string
+ check-type:
+ type: string
+ resource-version:
+ type: string
+ element-choice-sets:
+ type: array
+ items:
+ $ref: "#/getDefinitions/element-choice-set"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ constrained-element-sets:
+ properties:
+ constrained-element-set:
+ type: array
+ items:
+ $ref: "#/getDefinitions/constrained-element-set"
+ ctag-assignment:
+ description: |
+ ###### Related Nodes
+ - TO l3-network( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses ctag-assignment, ONE2MANY)
+ required:
+ - vlan-id-inner
+ properties:
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: id.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ ctag-assignments:
+ properties:
+ ctag-assignment:
+ type: array
+ items:
+ $ref: "#/getDefinitions/ctag-assignment"
+ ctag-pool:
+ description: |
+ A collection of C tags (vlan tags) grouped for a specific purpose.
+ ###### Related Nodes
+ - TO complex( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)
+ - TO availability-zone( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM vpls-pe( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)
+ required:
+ - target-pe
+ - availability-zone-name
+ - ctag-pool-purpose
+ properties:
+ target-pe:
+ type: string
+ description: The Target provider edge router
+ availability-zone-name:
+ type: string
+ description: Name of the availability zone
+ ctag-pool-purpose:
+ type: string
+ description: Describes what the intended purpose of this pool is.
+ ctag-values:
+ type: string
+ description: Comma separated list of ctags
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ ctag-pools:
+ properties:
+ ctag-pool:
+ type: array
+ items:
+ $ref: "#/getDefinitions/ctag-pool"
+ customer:
+ description: |
+ customer identifiers to provide linkage back to BSS information.
+ ###### Related Nodes
+ - FROM service-subscription( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)
+ - CUSTOMER is DELETED when these are DELETED SERVICE-SUBSCRIPTION
+ required:
+ - global-customer-id
+ - subscriber-name
+ - subscriber-type
+ properties:
+ global-customer-id:
+ type: string
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ subscriber-name:
+ type: string
+ description: Subscriber name, an alternate way to retrieve a customer.
+ subscriber-type:
+ type: string
+ description: Subscriber type, a way to provide VID with only the INFRA customers.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ service-subscriptions:
+ type: array
+ items:
+ $ref: "#/getDefinitions/service-subscription"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ customers:
+ description: |
+ Collection of customer identifiers to provide linkage back to BSS information.
+ properties:
+ customer:
+ type: array
+ items:
+ $ref: "#/getDefinitions/customer"
+ cvlan-tag-entry:
+ required:
+ - cvlan-tag
+ properties:
+ cvlan-tag:
+ type: integer
+ format: int64
+ description: See mis-na-virtualization-platform.yang
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ cvlan-tags:
+ properties:
+ cvlan-tag-entry:
+ type: array
+ items:
+ $ref: "#/getDefinitions/cvlan-tag-entry"
+ dvs-switch:
+ description: |
+ Digital virtual switch metadata, used by SDN-C to configure VCEs. A&AI needs to receive this data from the PO deployment team and administer it using the provisioningTool.sh into A&AI.
+ ###### Related Nodes
+ - TO cloud-region( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO availability-zone( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ required:
+ - switch-name
+ - vcenter-url
+ properties:
+ switch-name:
+ type: string
+ description: DVS switch name
+ vcenter-url:
+ type: string
+ description: URL used to reach the vcenter
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ dvs-switches:
+ description: |
+ Collection of digital virtual switch metadata used for vmWare VCEs and GenericVnfs.
+ properties:
+ dvs-switch:
+ type: array
+ items:
+ $ref: "#/getDefinitions/dvs-switch"
+ edge-prop-names:
+ description: |
+ Internal map to define the properties of an edge and interpret the map EdgeRules
+ properties:
+ edgeLabel:
+ type: string
+ direction:
+ type: string
+ multiplicityRule:
+ type: string
+ isParent:
type: boolean
- is-shared-network:
+ usesResource:
type: boolean
- is-external-network:
+ hasDelTarget:
type: boolean
- selflink:
+ SVC-INFRA:
+ type: boolean
+ SVC-INFRA-REV:
+ type: boolean
+ edge-tag-query-request:
+ properties:
+ edge-tag:
type: string
- description: Path to the controller object.
- operational-status:
+ result-detail:
type: string
- description: Indicator for whether the resource is considered operational.
- subnets:
+ start-node-type:
+ type: string
+ start-node-filter:
type: array
- items:
- $ref: "#/definitions/subnet"
- ctag-assignments:
+ items:
+ $ref: "#/getDefinitions/start-node-filter"
+ include-node-filter:
+ type: array
+ items:
+ $ref: "#/getDefinitions/include-node-filter"
+ secondary-filter:
+ type: array
+ items:
+ $ref: "#/getDefinitions/secondary-filter"
+ edge-tag-query-result:
+ properties:
+ tagged-inventory-item-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/tagged-inventory-item-list"
+ element-choice-set:
+ description: |
+ This is how we would capture constraints defining allowed sets of elements.
+ ###### Related Nodes
+ - TO constrained-element-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)
+ - ELEMENT-CHOICE-SET is DELETED when these are DELETED MODEL-ELEMENT
+ required:
+ - element-choice-set-uuid
+ - element-choice-set-name
+ properties:
+ element-choice-set-uuid:
+ type: string
+ element-choice-set-name:
+ type: string
+ cardinality:
+ type: string
+ resource-version:
+ type: string
+ model-elements:
type: array
items:
- $ref: "#/definitions/ctag-assignment"
- segmentation-assignments:
+ $ref: "#/getDefinitions/model-element"
+ relationship-list:
type: array
items:
- $ref: "#/definitions/segmentation-assignment"
+ $ref: "#/getDefinitions/relationship"
+ element-choice-sets:
+ properties:
+ element-choice-set:
+ type: array
+ items:
+ $ref: "#/getDefinitions/element-choice-set"
+ entitlement:
+ description: |
+ Metadata for entitlement group.
+ ###### Related Nodes
+ - TO generic-vnf( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vce( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ required:
+ - group-uuid
+ - resource-uuid
+ properties:
+ group-uuid:
+ type: string
+ description: Unique ID for the entitlement group the resource comes from, should be uuid.
+ resource-uuid:
+ type: string
+ description: Unique ID of an entitlement resource.
+ resource-version:
+ type: string
+ description: Concurrency value
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- description: Relates to tenant (or is it a child of tenant), complex, service, vpn-binding
- l3-networks:
+ $ref: "#/getDefinitions/relationship"
+ entitlements:
+ description: |
+ Entitlements, keyed by group-uuid and resource-uuid, related to license management
properties:
- l3-network:
+ entitlement:
type: array
items:
- $ref: "#/definitions/l3-network"
- network-policy:
+ $ref: "#/getDefinitions/entitlement"
+ esr-ems:
description: |
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Persist EMS address information used by EMS driver.
###### Related Nodes
- - FROM l3-network
- - FROM allotted-resource
+ - TO esr-system-info (CHILD of esr-ems, esr-ems has esr-system-info, One2Many)
+ - ESR-EMS deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
required:
- - network-policy-id
+ - ems-id
properties:
- network-policy-id:
+ ems-id:
type: string
- description: UUID representing unique key to this instance
- network-policy-fqdn:
+ description: Unique ID of EMS.
+ resource-version:
type: string
- description: Contrail FQDN for the policy
- heat-stack-id:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ esr-system-info-list:
+ type: object
+ $ref: "#/getDefinitions/esr-system-info-list"
+ relationship-list:
+ type: object
+ $ref: "#/getDefinitions/relationship-list"
+ esr-ems-list:
+ properties:
+ esr-ems:
+ type: array
+ items:
+ $ref: "#/getDefinitions/esr-ems"
+ esr-system-info:
+ description: |
+ Persist common address information of external systems.
+ ###### Related Nodes
+ - FROM esr-ems (PARENT of esr-system-info, esr-ems has esr-system-info)
+ - FROM esr-vnfm (PARENT of esr-system-info, esr-vnfm has esr-system-info)
+ - FROM esr-thirdparty-sdnc (PARENT of esr-system-info, esr-thirdparty-sdnc has esr-system-info)
+ - FROM cloud-region (PARENT of esr-system-info, cloud-region has esr-system-info)
+ required:
+ - esr-system-info-id
+ - user-name
+ - password
+ - system-type
+ properties:
+ esr-system-info-id:
type: string
- description: ID for the openStack Heat instance
+ description: Unique ID of esr system info.
+ system-name:
+ type: string
+ description: name of external system.
+ type:
+ type: string
+ description: type of external systems.
+ vendor:
+ type: string
+ description: vendor of external systems.
+ version:
+ type: string
+ description: version of external systems.
+ service-url:
+ type: string
+ description: url used to access external systems.
+ user-name:
+ type: string
+ description: username used to access external systems.
+ password:
+ type: string
+ description: password used to access external systems.
+ system-type:
+ type: string
+ description: it could be vim/vnfm/thirdparty-sdnc/ems-resource/ems-performance/ems-alarm.
+ protocol:
+ type: string
+ description: protocol of third party SDNC, for example netconf/snmp.
+ ssl-cacert:
+ type: string
+ description: ca file content if enabled ssl on auth-url.
+ ssl-insecure:
+ type: boolean
+ description: Whether to verify VIM's certificate.
+ ip-address:
+ type: string
+ description: service IP of ftp server.
+ port:
+ type: string
+ description: service port of ftp server.
+ cloud-domain:
+ type: string
+ description: domain info for authentication.
+ default-tenant:
+ type: string
+ description: default tenant of VIM.
+ passive:
+ type: boolean
+ description: ftp passive mode or not.
+ remote-path:
+ type: string
+ description: resource or performance data file path.
+ system-status:
+ type: string
+ description: the status of external system.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- network-policies:
+ $ref: "#/getDefinitions/relationship"
+ esr-system-info-list:
+ description: |
+ Collection of persistent block-level external system auth info.
properties:
- network-policy:
+ esr-system-info:
type: array
items:
- $ref: "#/definitions/network-policy"
- vf-module:
+ $ref: "#/getDefinitions/esr-system-info"
+ esr-thirdparty-sdnc:
description: |
- a deployment unit of VNFCs
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Persist SDNC address information used by ONAP SDNC.
###### Related Nodes
- - TO volume-group (One2One)
- - TO l3-network (Many2Many)
- - TO vnfc (One2Many)
- - FROM vserver
- - FROM generic-vnf (is composed of vf-module)
+ - TO esr-system-info (CHILD of esr-thirdparty-sdnc, esr-thirdparty-sdnc has esr-system-info, One2One)
+ - TO pnf( esr-thirdparty-sdnc has pnf, One2Many)
+ - ESR-THIRDPARTY-SDNC deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
required:
- - vf-module-id
- - is-base-vf-module
+ - thirdparty-sdnc-id
properties:
- vf-module-id:
+ thirdparty-sdnc-id:
type: string
- description: Unique ID of vf-module.
- vf-module-name:
+ description: Unique ID of SDNC.
+ location:
type: string
- description: Name of vf-module
- heat-stack-id:
+ description: used for DC type to indicate the location of SDNC, such as Core or Edge.
+ product-name:
type: string
- description: Heat stack id corresponding to this instance.
- orchestration-status:
+ description: password used to access SDNC server.
+ resource-version:
type: string
- description: orchestration status of this vf-module, mastered by MSO
- is-base-vf-module:
- type: boolean
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ esr-system-info-list:
+ type: object
+ $ref: "#/getDefinitions/esr-system-info-list"
+ relationship-list:
+ type: object
+ $ref: "#/getDefinitions/relationship-list"
+ esr-thirdparty-sdnc-list:
+ properties:
+ esr-thirdparty-sdnc:
+ type: array
+ items:
+ $ref: "#/getDefinitions/esr-thirdparty-sdnc"
+ esr-vnfm:
+ description: |
+ Persist VNFM address information used by VF-C.
+ ###### Related Nodes
+ - TO esr-system-info (CHILD of esr-vnfm, esr-vnfm has esr-system-info, One2One)
+ - ESR-VNFM deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
+ required:
+ - vnfm-id
+ properties:
+ vnfm-id:
+ type: string
+ description: Unique ID of VNFM.
+ vim-id:
+ type: string
+ description: indecate the VIM to deploy VNF.
+ certificate-url:
+ type: string
+ description: certificate url of VNFM.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- model-invariant-id:
+ esr-system-info-list:
+ type: object
+ $ref: "#/getDefinitions/esr-system-info-list"
+ relationship-list:
+ type: object
+ $ref: "#/getDefinitions/relationship-list"
+ esr-vnfm-list:
+ properties:
+ esr-vnfm:
+ type: array
+ items:
+ $ref: "#/getDefinitions/esr-vnfm"
+ evc:
+ description: |
+ evc object is an optional child object of the Configuration object.
+ ###### Related Nodes
+ - TO configuration( evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)
+ required:
+ - evc-id
+ properties:
+ evc-id:
type: string
- description: the ASDC model id for this resource or service model.
- model-version-id:
+ description: Unique/key field for the evc object
+ forwarding-path-topology:
type: string
- description: the ASDC model version for this resource or service model.
- persona-model-version:
+ description: Point-to-Point, Multi-Point
+ cir-value:
type: string
- description: the ASDC model version for this resource or service model.
- model-customization-id:
+ description: Commited Information Rate
+ cir-units:
type: string
- description: captures the id of all the configuration used to customize the resource for the service.
- widget-model-id:
+ description: CIR units
+ connection-diversity-group-id:
type: string
- description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
- widget-model-version:
+ description: Diversity Group ID
+ service-hours:
type: string
- description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
- contrail-service-instance-fqdn:
+ description: formerly Performance Group
+ esp-evc-circuit-id:
type: string
- description: the Contrail unique ID for a service-instance
- module-index:
+ description: EVC Circuit ID of ESP EVC
+ esp-evc-cir-value:
+ type: string
+ description: Committed Information Rate (For ESP)
+ esp-evc-cir-units:
+ type: string
+ description: CIR units (For ESP)
+ esp-itu-code:
+ type: string
+ description: Identifies ESP
+ collector-pop-clli:
+ type: string
+ description: Collector POP CLLI (from the hostname of the access pnf)
+ inter-connect-type-ingress:
+ type: string
+ description: Interconnect type on ingress side of EVC.
+ tagmode-access-ingress:
+ type: string
+ description: tagode for collector side of EVC
+ tagmode-access-egress:
+ type: string
+ description: tagMode for network side of EVC
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ evcs:
+ properties:
+ evc:
+ type: array
+ items:
+ $ref: "#/getDefinitions/evc"
+ external-system:
+ description: |
+ Namespace for external system.
+ properties:
+ esr-ems-list:
+ type: object
+ $ref: "#/getDefinitions/esr-ems-list"
+ esr-vnfm-list:
+ type: object
+ $ref: "#/getDefinitions/esr-vnfm-list"
+ esr-thirdparty-sdnc-list:
+ type: object
+ $ref: "#/getDefinitions/esr-thirdparty-sdnc-list"
+ extra-properties:
+ description: |
+ Extra properties for inventory item for response list
+ properties:
+ extra-property:
+ type: array
+ items:
+ $ref: "#/getDefinitions/extra-property"
+ extra-property:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ flavor:
+ description: |
+ Openstack flavor.
+ ###### Related Nodes
+ - TO cloud-region( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)
+ - FLAVOR cannot be deleted if linked to VSERVER
+ required:
+ - flavor-id
+ - flavor-name
+ - flavor-selflink
+ properties:
+ flavor-id:
+ type: string
+ description: Flavor id, expected to be unique across cloud-region.
+ flavor-name:
+ type: string
+ description: Flavor name
+ flavor-vcpus:
type: integer
format: int32
- description: the index will track the number of modules of a given type that have been deployed in a VNF, starting with 0, and always choosing the lowest available digit
- selflink:
+ description: Number of CPUs
+ flavor-ram:
+ type: integer
+ format: int32
+ description: Amount of memory
+ flavor-disk:
+ type: integer
+ format: int32
+ description: Disk space
+ flavor-ephemeral:
+ type: integer
+ format: int32
+ description: Amount of ephemeral disk space
+ flavor-swap:
type: string
- description: Path to the controller object.
+ description: amount of swap space allocation
+ flavor-is-public:
+ type: boolean
+ description: whether flavor is available to all users or private to the tenant it was created in.
+ flavor-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ flavor-disabled:
+ type: boolean
+ description: Boolean as to whether this flavor is no longer enabled
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- vf-modules:
+ $ref: "#/getDefinitions/relationship"
+ flavors:
description: |
- Collection of vf-modules, a deployment unit of VNFCs
+ Collection of openstack flavors.
properties:
- vf-module:
+ flavor:
type: array
items:
- $ref: "#/definitions/vf-module"
+ $ref: "#/getDefinitions/flavor"
+ forwarder:
+ description: |
+ Entity describing a sequenced segment of forwarding path
+ ###### Related Nodes
+ - TO forwarding-path( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)
+ - TO l-interface( forwarder org.onap.relationships.inventory.ForwardsTo l-interface, MANY2ONE)
+ - TO configuration( forwarder org.onap.relationships.inventory.Uses configuration, ONE2ONE)
+ - TO lag-interface( forwarder org.onap.relationships.inventory.ForwardsTo lag-interface, MANY2ONE)
+ - TO p-interface( forwarder org.onap.relationships.inventory.ForwardsTo p-interface, MANY2ONE)
+ - FORWARDER deletion means associated objects of these types are also DELETED:CONFIGURATION
+ required:
+ - sequence
+ properties:
+ sequence:
+ type: integer
+ format: int32
+ description: Unique ID of this segmentation
+ forwarder-role:
+ type: string
+ description: ingress, intermediate, egress
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ forwarder-evc:
+ description: |
+ forwarder object is an optional child object of the Configuration object.
+ ###### Related Nodes
+ - TO configuration( forwarder-evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)
+ required:
+ - forwarder-evc-id
+ properties:
+ forwarder-evc-id:
+ type: string
+ description: Key for forwarder-evc object
+ circuit-id:
+ type: string
+ description: Circuit ID from customer/ESP/ingress end of EVC, or reference to beater circuit on gateway/network/egress end of EVC
+ ivlan:
+ type: string
+ description: Internal VLAN.
+ svlan:
+ type: string
+ description: SVLAN value for ingress of egress forwarder.
+ cvlan:
+ type: string
+ description: CVLAN value for ingress of egress forwarder.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ forwarder-evcs:
+ properties:
+ forwarder-evc:
+ type: array
+ items:
+ $ref: "#/getDefinitions/forwarder-evc"
+ forwarders:
+ properties:
+ forwarder:
+ type: array
+ items:
+ $ref: "#/getDefinitions/forwarder"
+ forwarding-path:
+ description: |
+ Entity that describes the sequenced forwarding path between interfaces of services or resources
+ ###### Related Nodes
+ - TO service-instance( forwarding-path org.onap.relationships.inventory.AppliesTo service-instance, MANY2ONE)
+ - TO configuration( forwarding-path org.onap.relationships.inventory.Uses configuration, ONE2ONE)
+ - FROM forwarder( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)
+ - FORWARDING-PATH is DELETED when these are DELETED FORWARDER
+ - FORWARDING-PATH deletion means associated objects of these types are also DELETED:CONFIGURATION
+ required:
+ - forwarding-path-id
+ - forwarding-path-name
+ properties:
+ forwarding-path-id:
+ type: string
+ description: Unique ID of this FP
+ forwarding-path-name:
+ type: string
+ description: Name of the FP
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ selflink:
+ type: string
+ description: the self link for this FP
+ forwarders:
+ type: array
+ items:
+ $ref: "#/getDefinitions/forwarder"
+ forwarding-paths:
+ properties:
+ forwarding-path:
+ type: array
+ items:
+ $ref: "#/getDefinitions/forwarding-path"
generic-vnf:
description: |
General purpose VNF
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
- ###### Related Nodes
- - TO license-key-resource (Many2Many)
- - TO l-interface (comprises generic-vnf, Many2Many)
- - TO availability-zone (Many2Many)
- - TO lag-interface (comprises generic-vnf, Many2Many)
- - TO l3-network (Many2Many)
- - TO pserver (Many2Many)
- - TO vnf-image (Many2One)
- - TO vserver (One2Many)
- - TO service-instance (Many2Many)
- - TO site-pair-set (Many2Many)
- - TO network-profile (Many2Many)
- - TO ipsec-configuration (Many2One)
- - TO vf-module (comprises generic-vnf, One2Many)
- - TO volume-group (One2Many)
- - TO vnfc (One2Many)
- - TO instance-group (Many2Many)
- - TO entitlement (comprises generic-vnf, One2Many)
- - TO license (comprises generic-vnf, One2Many)
- - FROM virtual-data-center
- - FROM logical-link
- - FROM allotted-resource
+ ###### Related Nodes
+ - TO availability-zone( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - TO instance-group( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO ipsec-configuration( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)
+ - TO l3-network( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO license-key-resource( generic-vnf org.onap.relationships.inventory.Uses license-key-resource, MANY2MANY)
+ - TO pserver( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)
+ - TO vnf-image( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)
+ - TO volume-group( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - TO vserver( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)
+ - TO virtual-data-center( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY)
+ - FROM entitlement( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM lag-interface( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM license( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM network-profile( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)
+ - FROM site-pair-set( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)
+ - GENERIC-VNF is DELETED when these are DELETED ENTITLEMENT,VNFC,LAG-INTERFACE,LICENSE,L-INTERFACE,VF-MODULE
required:
- vnf-id
- vnf-name
@@ -41431,27 +59108,27 @@ definitions:
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
+ $ref: "#/getDefinitions/relationship"
l-interfaces:
type: array
items:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
lag-interfaces:
type: array
items:
- $ref: "#/definitions/lag-interface"
+ $ref: "#/getDefinitions/lag-interface"
vf-modules:
type: array
items:
- $ref: "#/definitions/vf-module"
+ $ref: "#/getDefinitions/vf-module"
licenses:
type: array
items:
- $ref: "#/definitions/license"
+ $ref: "#/getDefinitions/license"
entitlements:
type: array
items:
- $ref: "#/definitions/entitlement"
+ $ref: "#/getDefinitions/entitlement"
generic-vnfs:
description: |
Collection of VNFs
@@ -41459,15 +59136,732 @@ definitions:
generic-vnf:
type: array
items:
- $ref: "#/definitions/generic-vnf"
+ $ref: "#/getDefinitions/generic-vnf"
+ group-assignment:
+ description: |
+ Openstack group-assignment used to store exclusivity groups (EG).
+ ###### Related Nodes
+ - TO cloud-region( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)
+ required:
+ - group-id
+ - group-type
+ - group-name
+ properties:
+ group-id:
+ type: string
+ description: Group id, expected to be unique across cloud-region.
+ group-type:
+ type: string
+ description: Group type - the type of group this instance refers to
+ group-name:
+ type: string
+ description: Group name - name assigned to the group
+ group-description:
+ type: string
+ description: Group description - description of the group
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ group-assignments:
+ description: |
+ Collection of openstack group assignments
+ properties:
+ group-assignment:
+ type: array
+ items:
+ $ref: "#/getDefinitions/group-assignment"
+ host-route:
+ description: |
+ ###### Related Nodes
+ - TO subnet( host-route org.onap.relationships.inventory.BelongsTo subnet, MANY2ONE)
+ required:
+ - host-route-id
+ - route-prefix
+ - next-hop
+ properties:
+ host-route-id:
+ type: string
+ description: host-route id
+ route-prefix:
+ type: string
+ description: subnet prefix
+ next-hop:
+ type: string
+ description: Could be ip-address, hostname, or service-instance
+ next-hop-type:
+ type: string
+ description: Should be ip-address, hostname, or service-instance to match next-hop
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ host-routes:
+ properties:
+ host-route:
+ type: array
+ items:
+ $ref: "#/getDefinitions/host-route"
+ image:
+ description: |
+ Openstack image.
+ ###### Related Nodes
+ - TO cloud-region( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)
+ - IMAGE cannot be deleted if linked to VSERVER
+ - IMAGE is DELETED when these are DELETED METADATUM
+ required:
+ - image-id
+ - image-name
+ - image-os-distro
+ - image-os-version
+ - image-selflink
+ properties:
+ image-id:
+ type: string
+ description: Image id, expected to be unique across cloud region
+ image-name:
+ type: string
+ description: Image name
+ image-architecture:
+ type: string
+ description: Operating system architecture.
+ image-os-distro:
+ type: string
+ description: The common name of the operating system distribution in lowercase
+ image-os-version:
+ type: string
+ description: The operating system version as specified by the distributor.
+ application:
+ type: string
+ description: The application that the image instantiates.
+ application-vendor:
+ type: string
+ description: The vendor of the application.
+ application-version:
+ type: string
+ description: The version of the application.
+ image-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ metadata:
+ type: array
+ items:
+ $ref: "#/getDefinitions/metadatum"
+ images:
+ description: |
+ Collectio of Openstack images.
+ properties:
+ image:
+ type: array
+ items:
+ $ref: "#/getDefinitions/image"
+ include-node-filter:
+ properties:
+ include-node-type:
+ type: string
+ instance-filter:
+ description: |
+ InstanceFilter for performing a named-query or model query
+ instance-filters:
+ description: |
+ InstanceFilters for performing a named-query or model query
+ properties:
+ instance-filter:
+ type: array
+ items:
+ $ref: "#/getDefinitions/instance-filter"
+ instance-group:
+ description: |
+ General mechanism for grouping instances
+ ###### Related Nodes
+ - TO model( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM pnf( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ required:
+ - id
+ - description
+ - type
+ properties:
+ id:
+ type: string
+ description: Instance Group ID, UUID assigned to this instance.
+ description:
+ type: string
+ description: Descriptive text to help identify the usage of this instance-group
+ type:
+ type: string
+ description: Only valid value today is lower case ha for high availability
+ sub-type:
+ type: string
+ description: Valid values for ha type are [geo-activeactive, geo-activestandby, local-activeactive, local-activestandby]
+ resource-version:
+ type: string
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ instance-groups:
+ description: |
+ Collection of openstack route table references
+ properties:
+ instance-group:
+ type: array
+ items:
+ $ref: "#/getDefinitions/instance-group"
+ inventory:
+ properties:
+ search:
+ type: object
+ $ref: "#/getDefinitions/search"
+ actions:
+ type: object
+ $ref: "#/getDefinitions/actions"
+ cloud-infrastructure:
+ type: object
+ $ref: "#/getDefinitions/cloud-infrastructure"
+ business:
+ type: object
+ $ref: "#/getDefinitions/business"
+ service-design-and-creation:
+ type: object
+ $ref: "#/getDefinitions/service-design-and-creation"
+ network:
+ type: object
+ $ref: "#/getDefinitions/network"
+ aai-internal:
+ type: object
+ $ref: "#/getDefinitions/aai-internal"
+ nodes:
+ type: array
+ items:
+ $ref: "#/getDefinitions/aai-internal"
+ inventory-item:
+ properties:
+ inventory-item-type:
+ type: string
+ inventory-item-link:
+ type: string
+ inventory-item-data:
+ type: array
+ items:
+ $ref: "#/getDefinitions/inventory-item-data"
+ tagged-inventory-item-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/tagged-inventory-item-list"
+ inventory-item-data:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ inventory-response-item:
+ description: |
+ Inventory item for response list
+ properties:
+ model-name:
+ type: string
+ extra-properties:
+ type: object
+ $ref: "#/getDefinitions/extra-properties"
+ inventory-response-items:
+ type: object
+ $ref: "#/getDefinitions/inventory-response-items"
+ inventory-response-items:
+ description: |
+ Container for inventory items in response list
+ properties:
+ inventory-response-item:
+ type: array
+ items:
+ $ref: "#/getDefinitions/inventory-response-item"
+ ipsec-configuration:
+ description: |
+ IPSec configuration node will contain various configuration data for the NMTE VNF. This node will have an edge to the generic-vnf (vnf type = TE). Starting 1607, this data will be populated by SDN-C
+ ###### Related Nodes
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)
+ - FROM vig-server( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)
+ - IPSEC-CONFIGURATION is DELETED when these are DELETED VIG-SERVER
+ required:
+ - ipsec-configuration-id
+ properties:
+ ipsec-configuration-id:
+ type: string
+ description: UUID of this configuration
+ requested-vig-address-type:
+ type: string
+ description: Indicate the type of VIG server like AVPN, INTERNET, BOTH
+ requested-encryption-strength:
+ type: string
+ description: Encryption values like 3des-cbc, des-cbc, aes-128-cbc, aes-192-cbc, aes-265-cbc
+ requested-dmz-type:
+ type: string
+ description: can offer a shared DMZ or a DMZ specific to a customer
+ shared-dmz-network-address:
+ type: string
+ description: Network address of shared DMZ
+ requested-customer-name:
+ type: string
+ description: If the DMZ is a custom DMZ, this field will indicate the customer information
+ ike-version:
+ type: string
+ description: can be 1 or 2
+ ikev1-authentication:
+ type: string
+ description: Contains values like md5, sha1, sha256, sha384
+ ikev1-encryption:
+ type: string
+ description: Encyption values like 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
+ ikev1-dh-group:
+ type: string
+ description: Diffie-Hellman group like DH-GROUP2, DH-GROUP5, DH-GROUP14
+ ikev1-am-group-id:
+ type: string
+ description: Group name defined in VIG for clients using aggressive mode
+ ikev1-am-password:
+ type: string
+ description: pre-shared key for the above group name
+ ikev1-sa-lifetime:
+ type: string
+ description: Lifetime for IKEv1 SA
+ ipsec-authentication:
+ type: string
+ description: md5, sha1, sha256, sha384
+ ipsec-encryption:
+ type: string
+ description: 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
+ ipsec-sa-lifetime:
+ type: string
+ description: Life time for IPSec SA
+ ipsec-pfs:
+ type: string
+ description: enable PFS or not
+ xauth-userid:
+ type: string
+ description: user ID for xAuth, sm-user, ,nmteHostName
+ xauth-user-password:
+ type: string
+ description: Encrypted using the Juniper $9$ algorithm
+ dpd-interval:
+ type: string
+ description: The time between DPD probe
+ dpd-frequency:
+ type: string
+ description: Maximum number of DPD before claiming the tunnel is down
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ vig-servers:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vig-server"
+ ipsec-configurations:
+ properties:
+ ipsec-configuration:
+ type: array
+ items:
+ $ref: "#/getDefinitions/ipsec-configuration"
+ key-data:
+ properties:
+ key-name:
+ type: string
+ key-value:
+ type: string
+ l-interface:
+ description: |
+ Logical interfaces, e.g., a vnic.
+ ###### Related Nodes
+ - TO generic-vnf( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO lag-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)
+ - TO instance-group( l-interface org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO l-interface( l-interface org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - TO logical-link( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)
+ - TO newvce( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)
+ - TO p-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)
+ - TO vserver( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - FROM sriov-vf( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)
+ - FROM vlan( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - L-INTERFACE is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST,SRIOV-VF,VLAN
+ - L-INTERFACE deletion means associated objects of these types are also DELETED:LOGICAL-LINK
+ required:
+ - interface-name
+ - is-port-mirrored
+ - in-maint
+ properties:
+ interface-name:
+ type: string
+ description: Name given to the interface
+ interface-role:
+ type: string
+ description: E.g., CUSTOMER, UPLINK, etc.
+ v6-wan-link-ip:
+ type: string
+ description: Questionably placed - v6 ip addr of this interface (is in vr-lan-interface from Mary B.
+ selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ interface-id:
+ type: string
+ description: ID of interface
+ macaddr:
+ type: string
+ description: MAC address for the interface
+ network-name:
+ type: string
+ description: Name of the network
+ management-option:
+ type: string
+ description: Whether A&AI should be managing this interface of not. Could have value like CUSTOMER
+ interface-description:
+ type: string
+ description: Human friendly text regarding this interface.
+ is-port-mirrored:
+ type: boolean
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ in-maint:
+ type: boolean
+ vlans:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vlan"
+ sriov-vfs:
+ type: array
+ items:
+ $ref: "#/getDefinitions/sriov-vf"
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l-interface"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ l3-interface-ipv4-address-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
+ l3-interface-ipv6-address-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
+ l-interfaces:
+ description: |
+ Collection of logical interfaces.
+ properties:
+ l-interface:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l-interface"
+ l3-interface-ipv4-address-list:
+ description: |
+ IPv4 Address Range
+ ###### Related Nodes
+ - TO instance-group( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)
+ - TO l3-network( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - TO subnet( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - TO l-interface( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - TO vlan( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ required:
+ - l3-interface-ipv4-address
+ properties:
+ l3-interface-ipv4-address:
+ type: string
+ description: IP address
+ l3-interface-ipv4-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 32 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
+ type: string
+ description: Neutron network id of the interface that address belongs to
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of subnet that address belongs to
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ l3-interface-ipv6-address-list:
+ description: |
+ IPv6 Address Range
+ ###### Related Nodes
+ - TO instance-group( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)
+ - TO l3-network( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - TO subnet( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - TO l-interface( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - TO vlan( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ required:
+ - l3-interface-ipv6-address
+ properties:
+ l3-interface-ipv6-address:
+ type: string
+ description: IP address
+ l3-interface-ipv6-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 128 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
+ type: string
+ description: Neutron network id of the interface that address belongs to
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of subnet that address belongs to
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ l3-network:
+ description: |
+ Generic network definition
+ ###### Related Nodes
+ - TO network-policy( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)
+ - TO route-table-reference( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)
+ - TO vpn-binding( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM complex( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - FROM ctag-assignment( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM segmentation-assignment( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)
+ - FROM subnet( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)
+ - L3-NETWORK is DELETED when these are DELETED CTAG-ASSIGNMENT,SEGMENTATION-ASSIGNMENT,SUBNET
+ required:
+ - network-id
+ - network-name
+ - is-bound-to-vpn
+ - is-provider-network
+ - is-shared-network
+ - is-external-network
+ properties:
+ network-id:
+ type: string
+ description: Network ID, should be uuid. Unique across A&AI.
+ network-name:
+ type: string
+ description: Name of the network, governed by some naming convention..
+ network-type:
+ type: string
+ description: Type of the network - who defines these values?
+ network-role:
+ type: string
+ description: Role the network plans - who defines these values?
+ network-technology:
+ type: string
+ description: Network technology - who defines these values?
+ neutron-network-id:
+ type: string
+ description: Neutron network id of this Interface
+ is-bound-to-vpn:
+ type: boolean
+ service-id:
+ type: string
+ description: Unique identifier of service from ASDC. Does not strictly map to ASDC services. SOON TO BE DEPRECATED
+ network-role-instance:
+ type: integer
+ format: int64
+ description: network role instance
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ contrail-network-fqdn:
+ type: string
+ description: Contrail FQDN for the network
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ model-customization-id:
+ type: string
+ description: captures the id of all the configuration used to customize the resource for the service.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ physical-network-name:
+ type: string
+ description: Name associated with the physical network.
+ is-provider-network:
+ type: boolean
+ is-shared-network:
+ type: boolean
+ is-external-network:
+ type: boolean
+ selflink:
+ type: string
+ description: Path to the controller object.
+ operational-status:
+ type: string
+ description: Indicator for whether the resource is considered operational.
+ subnets:
+ type: array
+ items:
+ $ref: "#/getDefinitions/subnet"
+ ctag-assignments:
+ type: array
+ items:
+ $ref: "#/getDefinitions/ctag-assignment"
+ segmentation-assignments:
+ type: array
+ items:
+ $ref: "#/getDefinitions/segmentation-assignment"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ description: Relates to tenant (or is it a child of tenant), complex, service, vpn-binding
+ l3-networks:
+ properties:
+ l3-network:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l3-network"
+ lag-interface:
+ description: |
+ Link aggregate interface
+ ###### Related Nodes
+ - TO generic-vnf( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO lag-link( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)
+ - TO logical-link( lag-interface org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - TO p-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)
+ - TO pnf( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - TO pserver( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - TO vpls-pe( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)
+ - LAG-INTERFACE is DELETED when these are DELETED L-INTERFACE
+ - LAG-INTERFACE deletion means associated objects of these types are also DELETED:LAG-LINK,LOGICAL-LINK
+ required:
+ - interface-name
+ - in-maint
+ properties:
+ interface-name:
+ type: string
+ description: Name that identifies the link aggregate interface
+ interface-description:
+ type: string
+ description: Human friendly text regarding this interface.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ interface-id:
+ type: string
+ description: ID of interface
+ interface-role:
+ type: string
+ description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ in-maint:
+ type: boolean
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l-interface"
+ lag-interfaces:
+ description: |
+ Collection of link aggregate interfaces.
+ properties:
+ lag-interface:
+ type: array
+ items:
+ $ref: "#/getDefinitions/lag-interface"
lag-link:
description: |
LAG links can connect lag-interfaces
- ###### Default Delete Scope
- THIS_NODE_ONLY
###### Related Nodes
- - FROM lag-interface
- - FROM logical-link
+ - FROM lag-interface( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)
required:
- link-name
properties:
@@ -41480,7 +59874,7 @@ definitions:
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
+ $ref: "#/getDefinitions/relationship"
lag-links:
description: |
Collection of link aggregation connections
@@ -41488,14 +59882,624 @@ definitions:
lag-link:
type: array
items:
- $ref: "#/definitions/lag-link"
+ $ref: "#/getDefinitions/lag-link"
+ license:
+ description: |
+ Metadata for license group.
+ ###### Related Nodes
+ - TO generic-vnf( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vce( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ required:
+ - group-uuid
+ - resource-uuid
+ properties:
+ group-uuid:
+ type: string
+ description: Unique ID for the license group the resource belongs to, should be uuid.
+ resource-uuid:
+ type: string
+ description: Unique ID of a license resource.
+ resource-version:
+ type: string
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ licenses:
+ description: |
+ Licenses to be allocated across resources, keyed by group-uuid and resource-uuid, related to license management
+ properties:
+ license:
+ type: array
+ items:
+ $ref: "#/getDefinitions/license"
+ line-of-business:
+ description: |
+ describes a line-of-business
+ ###### Related Nodes
+ - TO generic-vnf( line-of-business org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)
+ required:
+ - line-of-business-name
+ properties:
+ line-of-business-name:
+ type: string
+ description: Name of the line-of-business (product)
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ lines-of-business:
+ description: |
+ Collection of lines-of-business
+ properties:
+ line-of-business:
+ type: array
+ items:
+ $ref: "#/getDefinitions/line-of-business"
+ logical-link:
+ description: |
+ Logical links generally connect l-interfaces but are used to express logical connectivity between two points
+ ###### Related Nodes
+ - TO cloud-region( logical-link org.onap.relationships.inventory.LocatedIn cloud-region, MANY2MANY)
+ - TO generic-vnf( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)
+ - TO lag-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)
+ - TO logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - TO pnf( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)
+ - TO pserver( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)
+ - TO vpn-binding( logical-link org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - TO virtual-data-center( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM lag-interface( lag-interface org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)
+ - FROM p-interface( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - FROM vlan( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ required:
+ - link-name
+ - link-type
+ properties:
+ link-name:
+ type: string
+ description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
+ link-type:
+ type: string
+ description: Type of logical link, e.g., evc
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ ip-version:
+ type: string
+ description: v4, v6, or ds for dual stack
+ routing-protocol:
+ type: string
+ description: For example, static or BGP
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ operational-status:
+ type: string
+ description: Indication of operational status of the logical link.
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+ link-role:
+ type: string
+ description: Indication of the network use of the logical link.
+ link-name2:
+ type: string
+ description: Alias or alternate name (CLCI or D1 name).
+ link-id:
+ type: string
+ description: UUID of the logical-link, SDNC generates this.
+ circuit-id:
+ type: string
+ description: Circuit id
+ purpose:
+ type: string
+ description: Reason for this entity, role it is playing
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ logical-links:
+ description: |
+ Collection of logical connections
+ properties:
+ logical-link:
+ type: array
+ items:
+ $ref: "#/getDefinitions/logical-link"
+ metadata:
+ description: |
+ Collection of metadatum (key/value pairs)
+ properties:
+ metadatum:
+ type: array
+ items:
+ $ref: "#/getDefinitions/metadatum"
+ metadatum:
+ description: |
+ Key/value pairs
+ ###### Related Nodes
+ - TO connector( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)
+ - TO image( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)
+ - TO service-instance( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - TO model-ver( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ required:
+ - metaname
+ - metaval
+ properties:
+ metaname:
+ type: string
+ metaval:
+ type: string
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model:
+ description: |
+ Subgraph definition provided by ASDC to describe an inventory asset and its connections related to ASDC models, independent of version
+ ###### Related Nodes
+ - TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - FROM instance-group( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY)
+ - FROM model-ver( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - FROM named-query( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)
+ - MODEL cannot be deleted if linked to INSTANCE-GROUP,NAMED-QUERY,NAMED-QUERY-ELEMENT
+ - MODEL is DELETED when these are DELETED MODEL-VER
+ required:
+ - model-invariant-id
+ - model-type
+ properties:
+ model-invariant-id:
+ type: string
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ model-type:
+ type: string
+ description: Type of the model, e.g., service, resource, widget, etc.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-vers:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model-ver"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ model-and-named-query-search:
+ description: |
+ ModelAndNamedQuerySearch holds query-parameters and instance-properties for performing a named-query or model query
+ properties:
+ query-parameters:
+ type: object
+ $ref: "#/getDefinitions/query-parameters"
+ instance-filters:
+ type: object
+ $ref: "#/getDefinitions/instance-filters"
+ secondary-filts:
+ type: object
+ $ref: "#/getDefinitions/secondary-filts"
+ top-node-type:
+ type: string
+ secondary-filter-cut-point:
+ type: string
+ model-constraint:
+ description: |
+ This is how we would capture constraints defining allowed sets of elements.
+ ###### Related Nodes
+ - TO model-element( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)
+ - MODEL-CONSTRAINT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET
+ required:
+ - model-constraint-uuid
+ - constrained-element-set-uuid-to-replace
+ properties:
+ model-constraint-uuid:
+ type: string
+ constrained-element-set-uuid-to-replace:
+ type: string
+ constrained-element-sets:
+ type: array
+ items:
+ $ref: "#/getDefinitions/constrained-element-set"
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-constraints:
+ properties:
+ model-constraint:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model-constraint"
+ model-element:
+ description: |
+ Defines how other models combine to make up a higher-level model.
+ ###### Related Nodes
+ - TO element-choice-set( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)
+ - TO model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - TO model-ver( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE)
+ - TO model-ver( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM model-constraint( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - MODEL-ELEMENT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET,MODEL-CONSTRAINT
+ required:
+ - model-element-uuid
+ - new-data-del-flag
+ - cardinality
+ properties:
+ model-element-uuid:
+ type: string
+ new-data-del-flag:
+ type: string
+ description: Indicates whether this element was created as part of instantiation from this model
+ cardinality:
+ type: string
+ description: How many of this type of element are required/allowed
+ linkage-points:
+ type: string
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-elements:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model-element"
+ description: Defines how other models combine to make up a higher-level model
+ model-constraints:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model-constraint"
+ description: Describes new constraints on this model element that are not part of that model's definition
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ model-elements:
+ properties:
+ model-element:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model-element"
+ model-ver:
+ description: |
+ Subgraph definition provided by ASDC to describe a specific version of an inventory asset and its connections related to ASDC models
+ ###### Related Nodes
+ - TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - MODEL-VER cannot be deleted if linked to MODEL-ELEMENT
+ - MODEL-VER is DELETED when these are DELETED MODEL-ELEMENT,METADATUM
+ required:
+ - model-version-id
+ - model-name
+ - model-version
+ properties:
+ model-version-id:
+ type: string
+ description: Unique identifier corresponding to one version of a model in ASDC
+ model-name:
+ type: string
+ description: Name of the model, which can change from version to version.
+ model-version:
+ type: string
+ description: Version
+ model-description:
+ type: string
+ description: Description
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-elements:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model-element"
+ metadata:
+ type: array
+ items:
+ $ref: "#/getDefinitions/metadatum"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ model-vers:
+ properties:
+ model-ver:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model-ver"
+ models:
+ description: |
+ Collection of subgraph definitions provided by ASDC to describe the inventory assets and their connections related to ASDC models
+ properties:
+ model:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model"
+ multicast-configuration:
+ description: |
+ ###### Related Nodes
+ - FROM vlan( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)
+ required:
+ - multicast-configuration-id
+ - multicast-protocol
+ - rp-type
+ properties:
+ multicast-configuration-id:
+ type: string
+ description: Unique id of multicast configuration.
+ multicast-protocol:
+ type: string
+ description: protocol of multicast configuration
+ rp-type:
+ type: string
+ description: rp type of multicast configuration
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ multicast-configurations:
+ description: |
+ multicast configuration of generic-vnf ip-address
+ properties:
+ multicast-configuration:
+ type: array
+ items:
+ $ref: "#/getDefinitions/multicast-configuration"
+ named-queries:
+ properties:
+ named-query:
+ type: array
+ items:
+ $ref: "#/getDefinitions/named-query"
+ named-query:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - TO model( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - NAMED-QUERY is DELETED when these are DELETED NAMED-QUERY-ELEMENT
+ required:
+ - named-query-uuid
+ - named-query-name
+ - named-query-version
+ properties:
+ named-query-uuid:
+ type: string
+ named-query-name:
+ type: string
+ named-query-version:
+ type: string
+ required-input-param:
+ type: string
+ description:
+ type: string
+ resource-version:
+ type: string
+ named-query-elements:
+ type: array
+ items:
+ $ref: "#/getDefinitions/named-query-element"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ named-query-element:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - TO model( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)
+ - TO named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM property-constraint( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM related-lookup( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - NAMED-QUERY-ELEMENT is DELETED when these are DELETED PROPERTY-CONSTRAINT,RELATED-LOOKUP
+ required:
+ - named-query-element-uuid
+ properties:
+ named-query-element-uuid:
+ type: string
+ property-collect-list:
+ type: string
+ resource-version:
+ type: string
+ property-limit-desc:
+ type: string
+ do-not-output:
+ type: string
+ named-query-elements:
+ type: array
+ items:
+ $ref: "#/getDefinitions/named-query-element"
+ related-lookups:
+ type: array
+ items:
+ $ref: "#/getDefinitions/related-lookup"
+ property-constraints:
+ type: array
+ items:
+ $ref: "#/getDefinitions/property-constraint"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ named-query-elements:
+ properties:
+ named-query-element:
+ type: array
+ items:
+ $ref: "#/getDefinitions/named-query-element"
+ network:
+ description: |
+ Namespace for network inventory resources.
+ properties:
+ logical-links:
+ type: array
+ items:
+ $ref: "#/getDefinitions/logical-link"
+ site-pair-sets:
+ type: array
+ items:
+ $ref: "#/getDefinitions/site-pair-set"
+ vpn-bindings:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vpn-binding"
+ vpls-pes:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vpls-pe"
+ multicast-configurations:
+ type: array
+ items:
+ $ref: "#/getDefinitions/multicast-configuration"
+ vces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vce"
+ vnfcs:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vnfc"
+ l3-networks:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l3-network"
+ network-policies:
+ type: array
+ items:
+ $ref: "#/getDefinitions/network-policy"
+ generic-vnfs:
+ type: array
+ items:
+ $ref: "#/getDefinitions/generic-vnf"
+ lag-links:
+ type: array
+ items:
+ $ref: "#/getDefinitions/lag-link"
+ newvces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/newvce"
+ pnfs:
+ type: array
+ items:
+ $ref: "#/getDefinitions/pnf"
+ physical-links:
+ type: array
+ items:
+ $ref: "#/getDefinitions/physical-link"
+ ipsec-configurations:
+ type: array
+ items:
+ $ref: "#/getDefinitions/ipsec-configuration"
+ route-table-references:
+ type: array
+ items:
+ $ref: "#/getDefinitions/route-table-reference"
+ instance-groups:
+ type: array
+ items:
+ $ref: "#/getDefinitions/instance-group"
+ zones:
+ type: array
+ items:
+ $ref: "#/getDefinitions/zone"
+ network-policies:
+ properties:
+ network-policy:
+ type: array
+ items:
+ $ref: "#/getDefinitions/network-policy"
+ network-policy:
+ description: |
+ ###### Related Nodes
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.Uses network-policy, ONE2ONE)
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)
+ required:
+ - network-policy-id
+ properties:
+ network-policy-id:
+ type: string
+ description: UUID representing unique key to this instance
+ network-policy-fqdn:
+ type: string
+ description: Contrail FQDN for the policy
+ heat-stack-id:
+ type: string
+ description: ID for the openStack Heat instance
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ network-profile:
+ description: |
+ Network profile populated by SDN-GP for SNMP
+ ###### Related Nodes
+ - TO generic-vnf( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ required:
+ - nm-profile-name
+ properties:
+ nm-profile-name:
+ type: string
+ description: Unique name of network profile.
+ community-string:
+ type: string
+ description: Encrypted SNMP community string
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ network-profiles:
+ description: |
+ Collection of network profiles
+ properties:
+ network-profile:
+ type: array
+ items:
+ $ref: "#/getDefinitions/network-profile"
newvce:
description: |
This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce.
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
###### Related Nodes
- - TO l-interface (comprises newvce, Many2Many)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)
+ - NEWVCE is DELETED when these are DELETED L-INTERFACE
required:
- vnf-id2
- vnf-name
@@ -41546,11 +60550,11 @@ definitions:
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
+ $ref: "#/getDefinitions/relationship"
l-interfaces:
type: array
items:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
newvces:
description: |
This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce.
@@ -41558,20 +60562,364 @@ definitions:
newvce:
type: array
items:
- $ref: "#/definitions/newvce"
+ $ref: "#/getDefinitions/newvce"
+ notification-event:
+ properties:
+ cambria.partition:
+ type: string
+ notification-event-header:
+ type: object
+ $ref: "#/getDefinitions/notification-event-header"
+ notification-event-header:
+ properties:
+ id:
+ type: string
+ timestamp:
+ type: string
+ source-name:
+ type: string
+ domain:
+ type: string
+ sequence-number:
+ type: string
+ severity:
+ type: string
+ event-type:
+ type: string
+ version:
+ type: string
+ action:
+ type: string
+ entity-type:
+ type: string
+ top-entity-type:
+ type: string
+ entity-link:
+ type: string
+ status:
+ type: string
+ notify:
+ required:
+ - event-id
+ properties:
+ event-id:
+ type: string
+ node-type:
+ type: string
+ event-trigger:
+ type: string
+ key-data:
+ type: array
+ items:
+ $ref: "#/getDefinitions/key-data"
+ selflink:
+ type: string
+ oam-network:
+ description: |
+ OAM network, to be deprecated shortly. Do not use for new purposes.
+ ###### Related Nodes
+ - TO cloud-region( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO complex( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)
+ - TO service-capability( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ required:
+ - network-uuid
+ - network-name
+ - cvlan-tag
+ properties:
+ network-uuid:
+ type: string
+ description: UUID of the network. Unique across a cloud-region
+ network-name:
+ type: string
+ description: Name of the network.
+ cvlan-tag:
+ type: integer
+ format: int64
+ description: cvlan-id
+ ipv4-oam-gateway-address:
+ type: string
+ description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
+ ipv4-oam-gateway-address-prefix-length:
+ type: integer
+ format: int32
+ description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ oam-networks:
+ description: |
+ Collection of OAM networks, to be deprecated shortly. Do not use for new purposes.
+ properties:
+ oam-network:
+ type: array
+ items:
+ $ref: "#/getDefinitions/oam-network"
+ operational-environment:
+ description: |
+ It is a logical partition of the cloud which allows to have multiple environments in the production AIC.
+ ###### Related Nodes
+ - TO operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)
+ - FROM operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)
+ required:
+ - operational-environment-id
+ - operational-environment-name
+ - operational-environment-type
+ - operational-environment-status
+ - tenant-context
+ - workload-context
+ properties:
+ operational-environment-id:
+ type: string
+ description: UUID of an operational environment
+ operational-environment-name:
+ type: string
+ description: Operational Environment name
+ operational-environment-type:
+ type: string
+ description: Operational Environment Type.
+ operational-environment-status:
+ type: string
+ description: Status
+ tenant-context:
+ type: string
+ description: Tenant Context.
+ workload-context:
+ type: string
+ description: Workload Context.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ operational-environments:
+ description: |
+ a logical partition of the cloud which allows to have multiple environments in the production AIC.
+ properties:
+ operational-environment:
+ type: array
+ items:
+ $ref: "#/getDefinitions/operational-environment"
+ overloaded-model:
+ description: |
+ Allows for legacy POST of old-style and new-style models
+ required:
+ - model-invariant-id
+ - model-name-version-id
+ - model-type
+ - model-name
+ - model-id
+ - model-version
+ properties:
+ model-invariant-id:
+ type: string
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ model-name-version-id:
+ type: string
+ description: Unique identifier corresponding to one version of a model in ASDC
+ model-type:
+ type: string
+ description: Type of the model, e.g., service, resource, widget, etc.
+ model-name:
+ type: string
+ description: Name of the model, which can change from version to version.
+ model-id:
+ type: string
+ description: Invariant unique ID which does not change from version to version
+ model-version:
+ type: string
+ description: Version
+ model-description:
+ type: string
+ description: Description
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-vers:
+ type: object
+ $ref: "#/getDefinitions/model-vers"
+ relationship-list:
+ type: object
+ $ref: "#/getDefinitions/relationship-list"
+ owning-entities:
+ description: |
+ Collection of owning-entities
+ properties:
+ owning-entity:
+ type: array
+ items:
+ $ref: "#/getDefinitions/owning-entity"
+ owning-entity:
+ description: |
+ describes an owning-entity
+ ###### Related Nodes
+ - FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo owning-entity, MANY2ONE)
+ required:
+ - owning-entity-id
+ - owning-entity-name
+ properties:
+ owning-entity-id:
+ type: string
+ description: UUID of an owning entity
+ owning-entity-name:
+ type: string
+ description: Owning entity name
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ p-interface:
+ description: |
+ Physical interface (e.g., nic)
+ ###### Related Nodes
+ - TO logical-link( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)
+ - TO physical-link( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)
+ - TO pnf( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - TO pserver( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - TO vpls-pe( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM lag-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)
+ - P-INTERFACE is DELETED when these are DELETED L-INTERFACE
+ - P-INTERFACE deletion means associated objects of these types are also DELETED:PHYSICAL-LINK
+ required:
+ - interface-name
+ - in-maint
+ properties:
+ interface-name:
+ type: string
+ description: Name that identifies the physical interface
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ port-description:
+ type: string
+ description: Nature of the services and connectivity on this port.
+ equipment-identifier:
+ type: string
+ description: CLEI or other specification for p-interface hardware.
+ interface-role:
+ type: string
+ description: Role specification for p-interface hardware.
+ interface-type:
+ type: string
+ description: Indicates the physical properties of the interface.
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ in-maint:
+ type: boolean
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l-interface"
+ p-interfaces:
+ description: |
+ Collection of physical interfaces.
+ properties:
+ p-interface:
+ type: array
+ items:
+ $ref: "#/getDefinitions/p-interface"
+ physical-link:
+ description: |
+ Collection of physical connections, typically between p-interfaces
+ ###### Related Nodes
+ - FROM p-interface( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)
+ required:
+ - link-name
+ properties:
+ link-name:
+ type: string
+ description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ circuit-id:
+ type: string
+ description: Circuit it
+ dual-mode:
+ type: string
+ description: Dual access mode (e.g., primary, secondary
+ management-option:
+ type: string
+ description: To provide information on who manages this circuit. A&AI or 3rd party transport provider
+ service-provider-name:
+ type: string
+ description: Name of the service Provider on this link.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ physical-links:
+ description: |
+ Collection of physical connections, typically between p-interfaces
+ properties:
+ physical-link:
+ type: array
+ items:
+ $ref: "#/getDefinitions/physical-link"
+ platform:
+ description: |
+ describes a platform
+ ###### Related Nodes
+ - TO generic-vnf( platform org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)
+ required:
+ - platform-name
+ properties:
+ platform-name:
+ type: string
+ description: Name of the platform
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ platforms:
+ description: |
+ Collection of platforms
+ properties:
+ platform:
+ type: array
+ items:
+ $ref: "#/getDefinitions/platform"
pnf:
description: |
PNF represents a physical network function. typically equipment used in the D1 world.
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
###### Related Nodes
- - TO p-interface (comprises pnf, Many2Many)
- - TO lag-interface (comprises pnf, One2Many)
- - TO complex (Many2One)
- - TO instance-group (Many2Many)
- - TO zone (Many2One)
- - FROM logical-link
- - FROM service-instance
+ - TO complex( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO instance-group( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO zone( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf pnf, ONE2MANY)
+ - PNF is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
required:
- pnf-name
- in-maint
@@ -41644,15 +60992,15 @@ definitions:
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
+ $ref: "#/getDefinitions/relationship"
p-interfaces:
type: array
items:
- $ref: "#/definitions/p-interface"
+ $ref: "#/getDefinitions/p-interface"
lag-interfaces:
type: array
items:
- $ref: "#/definitions/lag-interface"
+ $ref: "#/getDefinitions/lag-interface"
pnfs:
description: |
Collection of Physical Network Functions.
@@ -41660,183 +61008,371 @@ definitions:
pnf:
type: array
items:
- $ref: "#/definitions/pnf"
- physical-link:
+ $ref: "#/getDefinitions/pnf"
+ port-group:
description: |
- Collection of physical connections, typically between p-interfaces
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Used to capture the network interfaces of this VCE
###### Related Nodes
- - FROM p-interface
+ - TO vce( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM cvlan-tag( cvlan-tag org.onap.relationships.inventory.BelongsTo port-group, MANY2ONE)
+ - PORT-GROUP is DELETED when these are DELETED CVLAN-TAG
required:
- - link-name
+ - interface-id
+ - orchestration-status
properties:
- link-name:
+ interface-id:
type: string
- description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
- speed-value:
+ description: Unique ID of the interface
+ neutron-network-id:
type: string
- description: Captures the numeric part of the speed
- speed-units:
+ description: Neutron network id of this Interface
+ neutron-network-name:
type: string
- description: Captures the units corresponding to the speed
- circuit-id:
+ description: Neutron network name of this Interface
+ interface-role:
type: string
- description: Circuit it
- dual-mode:
+ description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
+ resource-version:
type: string
- description: Dual access mode (e.g., primary, secondary
- management-option:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ port-group-id:
type: string
- description: To provide information on who manages this circuit. A&AI or 3rd party transport provider
- service-provider-name:
+ description: Unique ID for port group in vmware
+ port-group-name:
type: string
- description: Name of the service Provider on this link.
- resource-version:
+ description: Likely to duplicate value of neutron network name
+ switch-name:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ description: DVS or standard switch name (should be non-null for port groups associated with DVS)
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ cvlan-tags:
+ type: array
+ items:
+ $ref: "#/getDefinitions/cvlan-tag-entry"
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- physical-links:
- description: |
- Collection of physical connections, typically between p-interfaces
+ $ref: "#/getDefinitions/relationship"
+ port-groups:
properties:
- physical-link:
+ port-group:
type: array
items:
- $ref: "#/definitions/physical-link"
- vig-server:
+ $ref: "#/getDefinitions/port-group"
+ project:
description: |
- vig-server contains information about a vig server used for IPSec-configuration. Populated by SDN-C from 1607
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ describes the project
###### Related Nodes
- - FROM ipsec-configuration (is composed of vig-server)
+ - TO service-instance( project org.onap.relationships.inventory.Uses service-instance, ONE2MANY)
required:
- - vig-address-type
+ - project-name
properties:
- vig-address-type:
- type: string
- description: indicates whether the VIG is for AVPN or INTERNET
- ipaddress-v4-vig:
- type: string
- description: v4 IP of the vig server
- ipaddress-v6-vig:
+ project-name:
type: string
- description: v6 IP of the vig server
+ description: Name of the project deploying a service
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- vig-servers:
+ $ref: "#/getDefinitions/relationship"
+ projects:
+ description: |
+ Collection of projects
properties:
- vig-server:
+ project:
type: array
items:
- $ref: "#/definitions/vig-server"
- ipsec-configuration:
+ $ref: "#/getDefinitions/project"
+ properties:
description: |
- IPSec configuration node will contain various configuration data for the NMTE VNF. This node will have an edge to the generic-vnf (vnf type = TE). Starting 1607, this data will be populated by SDN-C
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
+ Property holder for query properties or instance properties
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ property-constraint:
+ description: |
+ TBD
###### Related Nodes
- - TO vig-server (comprises ipsec-configuration, One2Many)
- - FROM generic-vnf
+ - TO named-query-element( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
required:
- - ipsec-configuration-id
+ - property-constraint-uuid
+ - constraint-type
+ - property-name
+ - property-value
properties:
- ipsec-configuration-id:
+ property-constraint-uuid:
type: string
- description: UUID of this configuration
- requested-vig-address-type:
+ constraint-type:
type: string
- description: Indicate the type of VIG server like AVPN, INTERNET, BOTH
- requested-encryption-strength:
+ property-name:
type: string
- description: Encryption values like 3des-cbc, des-cbc, aes-128-cbc, aes-192-cbc, aes-265-cbc
- requested-dmz-type:
+ property-value:
type: string
- description: can offer a shared DMZ or a DMZ specific to a customer
- shared-dmz-network-address:
+ resource-version:
type: string
- description: Network address of shared DMZ
- requested-customer-name:
+ property-constraints:
+ properties:
+ property-constraint:
+ type: array
+ items:
+ $ref: "#/getDefinitions/property-constraint"
+ pserver:
+ description: |
+ Compute host whose hostname must be unique and must exactly match what is sent as a relationship to a vserver.
+ ###### Related Nodes
+ - TO group-assignment( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)
+ - TO availability-zone( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)
+ - TO cloud-region( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)
+ - TO complex( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO zone( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - FROM vserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)
+ - PSERVER cannot be deleted if linked to GENERIC-VNF,LOGICAL-LINK,VSERVER
+ - PSERVER is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
+ - PSERVER cannot be deleted if linked to GROUP-ASSIGNMENT
+ required:
+ - hostname
+ - in-maint
+ properties:
+ hostname:
type: string
- description: If the DMZ is a custom DMZ, this field will indicate the customer information
- ike-version:
+ description: Value from executing hostname on the compute node.
+ ptnii-equip-name:
type: string
- description: can be 1 or 2
- ikev1-authentication:
+ description: PTNII name
+ number-of-cpus:
+ type: integer
+ format: int32
+ description: Number of cpus
+ disk-in-gigabytes:
+ type: integer
+ format: int32
+ description: Disk size, in GBs
+ ram-in-megabytes:
+ type: integer
+ format: int32
+ description: RAM size, in MBs
+ equip-type:
type: string
- description: Contains values like md5, sha1, sha256, sha384
- ikev1-encryption:
+ description: Equipment type. Source of truth should define valid values.
+ equip-vendor:
type: string
- description: Encyption values like 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
- ikev1-dh-group:
+ description: Equipment vendor. Source of truth should define valid values.
+ equip-model:
type: string
- description: Diffie-Hellman group like DH-GROUP2, DH-GROUP5, DH-GROUP14
- ikev1-am-group-id:
+ description: Equipment model. Source of truth should define valid values.
+ fqdn:
type: string
- description: Group name defined in VIG for clients using aggressive mode
- ikev1-am-password:
+ description: Fully-qualified domain name
+ pserver-selflink:
type: string
- description: pre-shared key for the above group name
- ikev1-sa-lifetime:
+ description: URL to endpoint where AAI can get more details
+ ipv4-oam-address:
type: string
- description: Lifetime for IKEv1 SA
- ipsec-authentication:
+ description: Used to configure device, also used for troubleshooting and is IP used for traps generated by device.
+ serial-number:
type: string
- description: md5, sha1, sha256, sha384
- ipsec-encryption:
+ description: Serial number, may be queried
+ ipaddress-v4-loopback-0:
type: string
- description: 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
- ipsec-sa-lifetime:
+ description: IPV4 Loopback 0 address
+ ipaddress-v6-loopback-0:
type: string
- description: Life time for IPSec SA
- ipsec-pfs:
+ description: IPV6 Loopback 0 address
+ ipaddress-v4-aim:
type: string
- description: enable PFS or not
- xauth-userid:
+ description: IPV4 AIM address
+ ipaddress-v6-aim:
type: string
- description: user ID for xAuth, sm-user, ,nmteHostName
- xauth-user-password:
+ description: IPV6 AIM address
+ ipaddress-v6-oam:
type: string
- description: Encrypted using the Juniper $9$ algorithm
- dpd-interval:
+ description: IPV6 OAM address
+ inv-status:
type: string
- description: The time between DPD probe
- dpd-frequency:
+ description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
+ pserver-id:
type: string
- description: Maximum number of DPD before claiming the tunnel is down
+ description: ID of Pserver
+ internet-topology:
+ type: string
+ description: internet topology of Pserver
+ in-maint:
+ type: boolean
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ pserver-name2:
+ type: string
+ description: alternative pserver name
+ purpose:
+ type: string
+ description: purpose of pserver
+ prov-status:
+ type: string
+ description: Prov Status of this device (not under canopi control) Valid values [PREPROV/NVTPROV/PROV]
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- vig-servers:
+ $ref: "#/getDefinitions/relationship"
+ p-interfaces:
type: array
items:
- $ref: "#/definitions/vig-server"
- ipsec-configurations:
+ $ref: "#/getDefinitions/p-interface"
+ lag-interfaces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/lag-interface"
+ pservers:
+ description: |
+ Collection of compute hosts.
properties:
- ipsec-configuration:
+ pserver:
type: array
items:
- $ref: "#/definitions/ipsec-configuration"
+ $ref: "#/getDefinitions/pserver"
+ query-parameters:
+ description: |
+ QueryParameters for performing a named-query or model query
+ properties:
+ named-query:
+ type: object
+ $ref: "#/getDefinitions/named-query"
+ overloaded-model:
+ type: object
+ $ref: "#/getDefinitions/overloaded-model"
+ related-lookup:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query-element( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ required:
+ - related-lookup-uuid
+ - source-node-type
+ - source-node-property
+ - target-node-type
+ - target-node-property
+ properties:
+ related-lookup-uuid:
+ type: string
+ source-node-type:
+ type: string
+ source-node-property:
+ type: string
+ target-node-type:
+ type: string
+ target-node-property:
+ type: string
+ property-collect-list:
+ type: string
+ resource-version:
+ type: string
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ related-lookups:
+ properties:
+ related-lookup:
+ type: array
+ items:
+ $ref: "#/getDefinitions/related-lookup"
+ related-to-property:
+ properties:
+ property-key:
+ type: string
+ description: Key part of a key/value pair
+ property-value:
+ type: string
+ description: Value part of a key/value pair
+ relationship:
+ properties:
+ related-to:
+ type: string
+ description: A keyword provided by A&AI to indicate type of node.
+ related-link:
+ type: string
+ description: URL to the object in A&AI.
+ relationship-data:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship-data"
+ related-to-property:
+ type: array
+ items:
+ $ref: "#/getDefinitions/related-to-property"
+ relationship-data:
+ required:
+ - relationship-key
+ - relationship-value
+ properties:
+ relationship-key:
+ type: string
+ description: A keyword provided by A&AI to indicate an attribute.
+ relationship-value:
+ type: string
+ description: Value of the attribute.
+ relationship-list:
+ properties:
+ relationship:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ reserved-prop-names:
+ description: |
+ Internal map to define some reserved properties of a vertex
+ properties:
+ last-mod-source-of-truth:
+ type: string
+ aai-node-type:
+ type: string
+ aai-created-ts:
+ type: integer
+ format: int64
+ aai-unique-key:
+ type: string
+ aai-last-mod-ts:
+ type: integer
+ format: int64
+ source-of-truth:
+ type: string
+ aai-uri:
+ type: string
+ response-list:
+ description: |
+ Response container for the results of a named-query or model query
+ properties:
+ inventory-response-items:
+ type: object
+ $ref: "#/getDefinitions/inventory-response-items"
+ result-data:
+ properties:
+ resource-type:
+ type: string
+ description: The specific type of node in the A&AI graph
+ resource-link:
+ type: string
+ description: The URL to the specific resource
route-table-reference:
description: |
Openstack route table reference.
- ###### Default Delete Scope
- THIS_NODE_ONLY
###### Related Nodes
- - FROM l3-network
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)
required:
- route-table-reference-id
- route-table-reference-fqdn
@@ -41853,7 +61389,7 @@ definitions:
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
+ $ref: "#/getDefinitions/relationship"
route-table-references:
description: |
Collection of openstack route table references
@@ -41861,303 +61397,738 @@ definitions:
route-table-reference:
type: array
items:
- $ref: "#/definitions/route-table-reference"
- instance-group:
+ $ref: "#/getDefinitions/route-table-reference"
+ route-target:
description: |
- General mechanism for grouping instances
- ###### Default Delete Scope
- THIS_NODE_ONLY
- ###### Related Nodes
- - TO model (Many2Many)
- - FROM l-interface
- - FROM l3-interface-ipv4-address-list
- - FROM l3-interface-ipv6-address-list
- - FROM pnf
- - FROM allotted-resource
- - FROM generic-vnf
- - FROM service-instance
+ Route target information
+ ###### Related Nodes
+ - TO vpn-binding( route-target org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2ONE)
required:
- - id
- - description
- - type
+ - global-route-target
+ - route-target-role
properties:
- id:
- type: string
- description: Instance Group ID, UUID assigned to this instance.
- description:
- type: string
- description: Descriptive text to help identify the usage of this instance-group
- type:
+ global-route-target:
type: string
- description: Only valid value today is lower case ha for high availability
- sub-type:
+ description: Number used to identify an RT, globally unique in the network
+ route-target-role:
type: string
- description: Valid values for ha type are [geo-activeactive, geo-activestandby, local-activeactive, local-activestandby]
+ description: Role assigned to this route target
resource-version:
type: string
- description: Concurrency value
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- instance-groups:
+ $ref: "#/getDefinitions/relationship"
+ route-targets:
description: |
- Collection of openstack route table references
+ Collection of route target information
properties:
- instance-group:
+ route-target:
type: array
items:
- $ref: "#/definitions/instance-group"
- zone:
+ $ref: "#/getDefinitions/route-target"
+ routing-instance:
description: |
- A zone is a grouping of assets in a location homing to the same connections into the CBB
- ###### Default Delete Scope
- THIS_NODE_ONLY
###### Related Nodes
- - TO complex (Many2One)
- - FROM cloud-region
- - FROM pserver
- - FROM pnf
+ - TO site-pair-set( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)
+ - FROM site-pair( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)
+ - ROUTING-INSTANCE is DELETED when these are DELETED SITE-PAIR
required:
- - zone-id
- - zone-name
- - design-type
- - zone-context
+ - routing-instance-id
properties:
- zone-id:
+ routing-instance-id:
type: string
- description: Code assigned by AIC to the zone
- zone-name:
+ description: Unique id of routing instance
+ rpm-owner:
type: string
- description: English name associated with the zone
- design-type:
+ description: rpm owner
+ resource-version:
type: string
- description: Design of zone [Medium/Large?]
- zone-context:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ site-pairs:
+ type: array
+ items:
+ $ref: "#/getDefinitions/site-pair"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ routing-instances:
+ description: |
+ set of probes related to generic-vnf routing instance
+ properties:
+ routing-instance:
+ type: array
+ items:
+ $ref: "#/getDefinitions/routing-instance"
+ sdn-zone-response:
+ properties:
+ oam-networks:
+ type: object
+ $ref: "#/getDefinitions/oam-networks"
+ az-and-dvs-switches:
+ type: array
+ items:
+ $ref: "#/getDefinitions/az-and-dvs-switches"
+ search:
+ properties:
+ edge-tag-query-result:
+ type: object
+ $ref: "#/getDefinitions/edge-tag-query-result"
+ edge-tag-query-request:
+ type: object
+ $ref: "#/getDefinitions/edge-tag-query-request"
+ search-results:
+ type: object
+ $ref: "#/getDefinitions/search-results"
+ sdn-zone-response:
+ type: object
+ $ref: "#/getDefinitions/sdn-zone-response"
+ search-results:
+ properties:
+ result-data:
+ type: array
+ items:
+ $ref: "#/getDefinitions/result-data"
+ secondary-filt:
+ description: |
+ SecondaryFilt for performing a named-query or model query
+ secondary-filter:
+ properties:
+ property-name:
type: string
- description: Context of zone [production/test]
- status:
+ filter-type:
type: string
- description: Status of a zone.
+ property-value:
+ type: string
+ secondary-filts:
+ description: |
+ SecondaryFilts for performing a named-query or model query
+ properties:
+ secondary-filt:
+ type: array
+ items:
+ $ref: "#/getDefinitions/secondary-filt"
+ segmentation-assignment:
+ description: |
+ Openstack segmentation assignment.
+ ###### Related Nodes
+ - TO l3-network( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ required:
+ - segmentation-id
+ properties:
+ segmentation-id:
+ type: string
+ description: Route Table Reference id, UUID assigned to this instance.
resource-version:
type: string
description: Concurrency value
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- zones:
+ $ref: "#/getDefinitions/relationship"
+ segmentation-assignments:
description: |
- Collection of zones
+ Collection of openstack segmentation assignments
properties:
- zone:
+ segmentation-assignment:
type: array
items:
- $ref: "#/definitions/zone"
- network:
+ $ref: "#/getDefinitions/segmentation-assignment"
+ service:
description: |
- Namespace for network inventory resources.
+ Stand-in for service model definitions. Likely to be deprecated in favor of models from ASDC. Does not strictly map to ASDC services.
+ required:
+ - service-id
+ - service-description
properties:
- logical-links:
+ service-id:
+ type: string
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ service-description:
+ type: string
+ description: Description of the service
+ service-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ service-version:
+ type: string
+ description: service version
+ relationship-list:
type: array
items:
- $ref: "#/definitions/logical-link"
- site-pair-sets:
+ $ref: "#/getDefinitions/relationship"
+ service-capabilities:
+ description: |
+ Collection of service capabilities.
+ properties:
+ service-capability:
type: array
- items:
- $ref: "#/definitions/site-pair-set"
- vpn-bindings:
+ items:
+ $ref: "#/getDefinitions/service-capability"
+ service-capability:
+ description: |
+ Early definition of server/resource pairings, likely to be replaced by models. No new use should be made of this.
+ ###### Related Nodes
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - SERVICE-CAPABILITY cannot be deleted if linked to AVAILABILITY-ZONE,OAM-NETWORK
+ required:
+ - service-type
+ - vnf-type
+ properties:
+ service-type:
+ type: string
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/vpn-binding"
- vpls-pes:
+ $ref: "#/getDefinitions/relationship"
+ service-design-and-creation:
+ description: |
+ Namespace for objects managed by ASDC
+ properties:
+ vnf-images:
type: array
items:
- $ref: "#/definitions/vpls-pe"
- multicast-configurations:
+ $ref: "#/getDefinitions/vnf-image"
+ services:
type: array
items:
- $ref: "#/definitions/multicast-configuration"
- vces:
+ $ref: "#/getDefinitions/service"
+ service-capabilities:
type: array
items:
- $ref: "#/definitions/vce"
- vnfcs:
+ $ref: "#/getDefinitions/service-capability"
+ models:
type: array
items:
- $ref: "#/definitions/vnfc"
- l3-networks:
+ $ref: "#/getDefinitions/model"
+ named-queries:
type: array
items:
- $ref: "#/definitions/l3-network"
- network-policies:
+ $ref: "#/getDefinitions/named-query"
+ service-instance:
+ description: |
+ Instance of a service
+ ###### Related Nodes
+ - TO generic-vnf( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)
+ - TO l3-network( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)
+ - TO allotted-resource( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY)
+ - TO connector( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)
+ - TO ctag-assignment( service-instance org.onap.relationships.inventory.Uses ctag-assignment, ONE2MANY)
+ - TO cvlan-tag( service-instance org.onap.relationships.inventory.ComposedOf cvlan-tag, MANY2MANY)
+ - TO instance-group( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO logical-link( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - TO pnf( service-instance org.onap.relationships.inventory.ComposedOf pnf, ONE2MANY)
+ - TO service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)
+ - TO vlan( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)
+ - TO service-subscription( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)
+ - TO vce( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)
+ - SERVICE-INSTANCE is DELETED when these are DELETED ALLOTTED-RESOURCE,METADATUM
+ - SERVICE-INSTANCE deletion means associated objects of these types are also DELETED:LOGICAL-LINK
+ required:
+ - service-instance-id
+ properties:
+ service-instance-id:
+ type: string
+ description: Uniquely identifies this instance of a service
+ service-instance-name:
+ type: string
+ description: This field will store a name assigned to the service-instance.
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ bandwidth-total:
+ type: string
+ description: Indicates the total bandwidth to be used for this service.
+ bandwidth-up-wan1:
+ type: string
+ description: indicates the upstream bandwidth this service will use on the WAN1 port of the physical device.
+ bandwidth-down-wan1:
+ type: string
+ description: indicates the downstream bandwidth this service will use on the WAN1 port of the physical device.
+ bandwidth-up-wan2:
+ type: string
+ description: indicates the upstream bandwidth this service will use on the WAN2 port of the physical device.
+ bandwidth-down-wan2:
+ type: string
+ description: indicates the downstream bandwidth this service will use on the WAN2 port of the physical device.
+ vhn-portal-url:
+ type: string
+ description: URL customers will use to access the vHN Portal.
+ service-instance-location-id:
+ type: string
+ description: An identifier that customers assign to the location where this service is being used.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ selflink:
+ type: string
+ description: Path to the controller object.
+ orchestration-status:
+ type: string
+ description: Orchestration status of this service.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/network-policy"
- generic-vnfs:
+ $ref: "#/getDefinitions/relationship"
+ metadata:
type: array
items:
- $ref: "#/definitions/generic-vnf"
- lag-links:
+ $ref: "#/getDefinitions/metadatum"
+ allotted-resources:
type: array
items:
- $ref: "#/definitions/lag-link"
- newvces:
+ $ref: "#/getDefinitions/allotted-resource"
+ service-instances:
+ description: |
+ Collection of service instances
+ properties:
+ service-instance:
type: array
- items:
- $ref: "#/definitions/newvce"
- pnfs:
+ items:
+ $ref: "#/getDefinitions/service-instance"
+ service-subscription:
+ description: |
+ Object that group service instances.
+ ###### Related Nodes
+ - TO customer( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)
+ - TO tenant( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)
+ - SERVICE-SUBSCRIPTION is DELETED when these are DELETED SERVICE-INSTANCE
+ required:
+ - service-type
+ properties:
+ service-type:
+ type: string
+ description: Value defined by orchestration to identify this service across ECOMP.
+ temp-ub-sub-account-id:
+ type: string
+ description: This property will be deleted from A&AI in the near future. Only stop gap solution.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ service-instances:
type: array
items:
- $ref: "#/definitions/pnf"
- physical-links:
+ $ref: "#/getDefinitions/service-instance"
+ relationship-list:
type: array
items:
- $ref: "#/definitions/physical-link"
- ipsec-configurations:
+ $ref: "#/getDefinitions/relationship"
+ service-subscriptions:
+ description: |
+ Collection of objects that group service instances.
+ properties:
+ service-subscription:
type: array
- items:
- $ref: "#/definitions/ipsec-configuration"
- route-table-references:
+ items:
+ $ref: "#/getDefinitions/service-subscription"
+ services:
+ description: |
+ Collection of service model definitions. Likely to be deprecated in favor of models from ASDC.
+ properties:
+ service:
type: array
- items:
- $ref: "#/definitions/route-table-reference"
- instance-groups:
+ items:
+ $ref: "#/getDefinitions/service"
+ site-pair:
+ description: |
+ ###### Related Nodes
+ - TO routing-instance( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)
+ - FROM class-of-service( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)
+ - SITE-PAIR is DELETED when these are DELETED CLASS-OF-SERVICE
+ required:
+ - site-pair-id
+ properties:
+ site-pair-id:
+ type: string
+ description: unique identifier of probe
+ source-ip:
+ type: string
+ description: Prefix address
+ destination-ip:
+ type: string
+ description: Prefix address
+ ip-version:
+ type: string
+ description: ip version, v4, v6
+ destination-hostname:
+ type: string
+ description: Hostname of the destination equipment to which SLAs are measured against.
+ destination-equip-type:
+ type: string
+ description: The type of destinatination equipment. Could be Router, etc.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ classes-of-service:
type: array
items:
- $ref: "#/definitions/instance-group"
- zones:
+ $ref: "#/getDefinitions/class-of-service"
+ relationship-list:
type: array
items:
- $ref: "#/definitions/zone"
- inventory:
+ $ref: "#/getDefinitions/relationship"
+ site-pair-set:
+ description: |
+ Set of instances for probes used to measure service level agreements
+ ###### Related Nodes
+ - TO generic-vnf( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM routing-instance( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)
+ - SITE-PAIR-SET is DELETED when these are DELETED ROUTING-INSTANCE
+ required:
+ - site-pair-set-id
properties:
- search:
- type: object
- $ref: "#/definitions/search"
- actions:
- type: object
- $ref: "#/definitions/actions"
- cloud-infrastructure:
- type: object
- $ref: "#/definitions/cloud-infrastructure"
- business:
- type: object
- $ref: "#/definitions/business"
- service-design-and-creation:
- type: object
- $ref: "#/definitions/service-design-and-creation"
- network:
- type: object
- $ref: "#/definitions/network"
- aai-internal:
- type: object
- $ref: "#/definitions/aai-internal"
- nodes:
+ site-pair-set-id:
+ type: string
+ description: Unique id of site pair set.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ routing-instances:
type: array
items:
- $ref: "#/definitions/"
- edge-tag-query-result:
+ $ref: "#/getDefinitions/routing-instance"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ site-pair-sets:
+ description: |
+ Collection of sets of instances for probes related to generic-vnf
properties:
- tagged-inventory-item-list:
+ site-pair-set:
type: array
items:
- $ref: "#/definitions/tagged-inventory-item-list"
- tagged-inventory-item-list:
+ $ref: "#/getDefinitions/site-pair-set"
+ site-pairs:
+ description: |
+ probe within a set
properties:
- inventory-item:
+ site-pair:
type: array
items:
- $ref: "#/definitions/inventory-item"
- inventory-item:
+ $ref: "#/getDefinitions/site-pair"
+ snapshot:
+ description: |
+ Openstack snapshot
+ ###### Related Nodes
+ - TO cloud-region( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)
+ required:
+ - snapshot-id
properties:
- inventory-item-type:
+ snapshot-id:
type: string
- inventory-item-link:
+ description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
+ snapshot-name:
type: string
- inventory-item-data:
+ description: Snapshot name
+ snapshot-architecture:
+ type: string
+ description: Operating system architecture
+ snapshot-os-distro:
+ type: string
+ description: The common name of the operating system distribution in lowercase
+ snapshot-os-version:
+ type: string
+ description: The operating system version as specified by the distributor.
+ application:
+ type: string
+ description: The application that the image instantiates.
+ application-vendor:
+ type: string
+ description: The vendor of the application.
+ application-version:
+ type: string
+ description: The version of the application.
+ snapshot-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ prev-snapshot-id:
+ type: string
+ description: This field contains the UUID of the previous snapshot (if any).
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
- items:
- $ref: "#/definitions/inventory-item-data"
- tagged-inventory-item-list:
+ items:
+ $ref: "#/getDefinitions/relationship"
+ snapshots:
+ description: |
+ Collection of openstack snapshots
+ properties:
+ snapshot:
type: array
items:
- $ref: "#/definitions/tagged-inventory-item-list"
- inventory-item-data:
+ $ref: "#/getDefinitions/snapshot"
+ sriov-pf:
+ description: |
+ SR-IOV Physical Function
+ ###### Related Nodes
+ - TO p-interface( sriov-pf org.onap.relationships.inventory.BelongsTo p-interface, ONE2ONE)
+ - FROM sriov-vf( sriov-vf org.onap.relationships.inventory.Uses sriov-pf, MANY2ONE)
+ required:
+ - pf-pci-id
properties:
- property-name:
+ pf-pci-id:
type: string
- property-value:
+ description: Identifier for the sriov-pf
+ resource-version:
type: string
- edge-tag-query-request:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ sriov-pfs:
+ description: |
+ Collection of SR-IOV Physical Functions.
properties:
- edge-tag:
+ sriov-pf:
+ type: array
+ items:
+ $ref: "#/getDefinitions/sriov-pf"
+ sriov-vf:
+ description: |
+ SR-IOV Virtual Function (not to be confused with virtual network function)
+ ###### Related Nodes
+ - TO l-interface( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)
+ required:
+ - pci-id
+ properties:
+ pci-id:
type: string
- result-detail:
+ description: PCI ID used to identify the sriov-vf
+ vf-vlan-filter:
type: string
- start-node-type:
+ description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM.
+ vf-mac-filter:
type: string
- start-node-filter:
- type: array
- items:
- $ref: "#/definitions/start-node-filter"
- include-node-filter:
+ description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM.
+ vf-vlan-strip:
+ type: boolean
+ description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM.
+ vf-vlan-anti-spoof-check:
+ type: boolean
+ description: This option ensures anti VLAN spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
+ vf-mac-anti-spoof-check:
+ type: boolean
+ description: This option ensures anti MAC spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
+ vf-mirrors:
+ type: string
+ description: This option defines the set of Mirror objects which essentially mirrors the traffic from source to set of collector VNF Ports.
+ vf-broadcast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows all broadcast traffic to reach the VM
+ vf-unknown-multicast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows unknown multicast traffic to reach the VM
+ vf-unknown-unicast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows unknown unicast traffic to reach the VM
+ vf-insert-stag:
+ type: boolean
+ description: This option, if set to true, instructs to insert outer tag after traffic comes out of VM.
+ vf-link-status:
+ type: string
+ description: This option is used to set the link status. Valid values as of 1607 are on, off, and auto.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
+ type: string
+ description: Neutron network id of the interface
+ relationship-list:
type: array
- items:
- $ref: "#/definitions/include-node-filter"
- secondary-filter:
+ items:
+ $ref: "#/getDefinitions/relationship"
+ sriov-vfs:
+ description: |
+ Collection of SR-IOV Virtual Functions.
+ properties:
+ sriov-vf:
type: array
items:
- $ref: "#/definitions/secondary-filter"
+ $ref: "#/getDefinitions/sriov-vf"
start-node-filter:
properties:
property-name:
type: string
property-value:
type: string
- include-node-filter:
+ subnet:
+ description: |
+ ###### Related Nodes
+ - TO l3-network( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - SUBNET cannot be deleted if linked to L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST
+ required:
+ - subnet-id
+ - dhcp-enabled
properties:
- include-node-type:
+ subnet-id:
type: string
- secondary-filter:
- properties:
- property-name:
+ description: Subnet ID, should be UUID.
+ subnet-name:
type: string
- filter-type:
+ description: Name associated with the subnet.
+ neutron-subnet-id:
type: string
- property-value:
+ description: Neutron id of this subnet
+ gateway-address:
type: string
- search-results:
+ description: gateway ip address
+ network-start-address:
+ type: string
+ description: network start address
+ cidr-mask:
+ type: string
+ description: cidr mask
+ ip-version:
+ type: string
+ description: ip version
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ dhcp-enabled:
+ type: boolean
+ dhcp-start:
+ type: string
+ description: the start address reserved for use by dhcp
+ dhcp-end:
+ type: string
+ description: the last address reserved for use by dhcp
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ subnets:
properties:
- result-data:
+ subnet:
type: array
items:
- $ref: "#/definitions/result-data"
- result-data:
+ $ref: "#/getDefinitions/subnet"
+ tagged-inventory-item-list:
properties:
- resource-type:
+ inventory-item:
+ type: array
+ items:
+ $ref: "#/getDefinitions/inventory-item"
+ tenant:
+ description: |
+ Openstack tenant
+ ###### Related Nodes
+ - TO cloud-region( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO group-assignment( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)
+ - TO l3-network( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO volume-group( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - FROM service-subscription( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)
+ - FROM vserver( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)
+ - TENANT cannot be deleted if linked to VSERVER
+ required:
+ - tenant-id
+ - tenant-name
+ properties:
+ tenant-id:
type: string
- description: The specific type of node in the A&AI graph
- resource-link:
+ description: Unique id relative to the cloud-region.
+ tenant-name:
type: string
- description: The URL to the specific resource
- sdn-zone-response:
+ description: Readable name of tenant
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ vservers:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vserver"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ tenants:
+ description: |
+ Collection of openstack tenants.
properties:
- oam-networks:
- type: object
- $ref: "#/definitions/oam-networks"
- az-and-dvs-switches:
+ tenant:
type: array
items:
- $ref: "#/definitions/az-and-dvs-switches"
- az-and-dvs-switches:
+ $ref: "#/getDefinitions/tenant"
+ tunnel-xconnect:
+ description: |
+ Represents the specifics of a tunnel cross connect piece of a resource that gets separately allotted
+ ###### Related Nodes
+ - TO allotted-resource( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)
+ required:
+ - id
+ - bandwidth-up-wan1
+ - bandwidth-down-wan1
+ - bandwidth-up-wan2
+ - bandwidth-down-wan2
properties:
- dvs-switches:
- type: object
- $ref: "#/definitions/dvs-switches"
- availability-zone:
- type: object
- $ref: "#/definitions/availability-zone"
+ id:
+ type: string
+ description: Allotted Resource id UUID assigned to this instance.
+ bandwidth-up-wan1:
+ type: string
+ description: The WAN uplink bandwidth for WAN1
+ bandwidth-down-wan1:
+ type: string
+ description: The WAN downlink bandwidth for WAN1
+ bandwidth-up-wan2:
+ type: string
+ description: The WAN uplink bandwidth for WAN2
+ bandwidth-down-wan2:
+ type: string
+ description: The WAN downlink bandwidth for WAN2
+ resource-version:
+ type: string
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ tunnel-xconnects:
+ description: |
+ This object is used to store the specific tunnel cross connect aspects of an allotted resource
+ properties:
+ tunnel-xconnect:
+ type: array
+ items:
+ $ref: "#/getDefinitions/tunnel-xconnect"
update:
description: |
Serves a PATCH like function. Does not enforce concurrency control. Clear each usage with AAI team.
@@ -42169,275 +62140,789 @@ definitions:
update-node-key:
type: array
items:
- $ref: "#/definitions/update-node-key"
+ $ref: "#/getDefinitions/update-node-key"
update-node-uri:
type: string
action:
type: array
items:
- $ref: "#/definitions/action"
- action:
- properties:
- action-type:
- type: string
- action-data:
- type: array
- items:
- $ref: "#/definitions/action-data"
- action-data:
- properties:
- property-name:
- type: string
- property-value:
- type: string
+ $ref: "#/getDefinitions/action"
update-node-key:
properties:
key-name:
type: string
key-value:
type: string
- notify:
+ vce:
+ description: |
+ Virtual Customer Edge Router, used specifically for Gamma. This object is deprecated.
+ ###### Related Nodes
+ - TO availability-zone( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - TO complex( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)
+ - TO vserver( vce tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM entitlement( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM license( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM port-group( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)
+ - VCE is DELETED when these are DELETED ENTITLEMENT,LICENSE,PORT-GROUP
required:
- - event-id
+ - vnf-id
+ - vnf-name
+ - vnf-type
properties:
- event-id:
+ vnf-id:
type: string
- node-type:
+ description: Unique id of VNF. This is unique across the graph.
+ vnf-name:
type: string
- event-trigger:
+ description: Name of VNF.
+ vnf-name2:
type: string
- key-data:
- type: array
- items:
- $ref: "#/definitions/key-data"
- selflink:
+ description: Alternate name of VNF.
+ vnf-type:
type: string
- key-data:
- properties:
- key-name:
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ service-id:
type: string
- key-value:
+ description: Unique identifier of service, does not strictly map to ASDC services, SOON TO BE DEPRECATED.
+ regional-resource-zone:
type: string
- notification-event:
- properties:
- cambria.partition:
+ description: Regional way of organizing pservers, source of truth should define values
+ prov-status:
type: string
- notification-event-header:
- type: object
- $ref: "#/definitions/notification-event-header"
- notification-event-header:
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ operational-status:
+ type: string
+ description: Indicator for whether the resource is considered operational
+ license-key:
+ type: string
+ description: OBSOLETE - do not use
+ equipment-role:
+ type: string
+ description: Network role being played by this VNF
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ vpe-id:
+ type: string
+ description: Unique ID of VPE connected to this VCE.
+ v6-vce-wan-address:
+ type: string
+ description: Valid v6 IP address for the WAN Link on this router. Implied length of /64.
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure vce, also used for troubleshooting and is IP used for traps generated by VCE.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ ipv4-loopback0-address:
+ type: string
+ description: Loopback0 address
+ entitlement-resource-uuid:
+ type: string
+ description: OBSOLETE - see child relationships
+ port-groups:
+ type: array
+ items:
+ $ref: "#/getDefinitions/port-group"
+ licenses:
+ type: array
+ items:
+ $ref: "#/getDefinitions/license"
+ entitlements:
+ type: array
+ items:
+ $ref: "#/getDefinitions/entitlement"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ vces:
+ description: |
+ Collection of Virtual Customer Edge Routers, used specifically for Gamma. This object is deprecated.
properties:
- id:
+ vce:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vce"
+ vf-module:
+ description: |
+ a deployment unit of VNFCs
+ ###### Related Nodes
+ - TO generic-vnf( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO l3-network( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)
+ - TO vnfc( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)
+ - TO volume-group( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)
+ - TO vserver( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)
+ - VF-MODULE cannot be deleted if linked to VNFC
+ required:
+ - vf-module-id
+ - is-base-vf-module
+ properties:
+ vf-module-id:
type: string
- timestamp:
+ description: Unique ID of vf-module.
+ vf-module-name:
type: string
- source-name:
+ description: Name of vf-module
+ heat-stack-id:
type: string
- domain:
+ description: Heat stack id corresponding to this instance.
+ orchestration-status:
type: string
- sequence-number:
+ description: orchestration status of this vf-module, mastered by MSO
+ is-base-vf-module:
+ type: boolean
+ resource-version:
type: string
- severity:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-invariant-id:
type: string
- event-type:
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
type: string
- version:
+ description: the ASDC model version for this resource or service model.
+ persona-model-version:
type: string
- action:
+ description: the ASDC model version for this resource or service model.
+ model-customization-id:
type: string
- entity-type:
+ description: captures the id of all the configuration used to customize the resource for the service.
+ widget-model-id:
type: string
- top-entity-type:
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
type: string
- entity-link:
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ contrail-service-instance-fqdn:
type: string
- status:
+ description: the Contrail unique ID for a service-instance
+ module-index:
+ type: integer
+ format: int32
+ description: the index will track the number of modules of a given type that have been deployed in a VNF, starting with 0, and always choosing the lowest available digit
+ selflink:
type: string
- reserved-prop-names:
+ description: Path to the controller object.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ vf-modules:
description: |
- Internal map to define some reserved properties of a vertex
+ Collection of vf-modules, a deployment unit of VNFCs
properties:
- last-mod-source-of-truth:
+ vf-module:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vf-module"
+ vig-server:
+ description: |
+ vig-server contains information about a vig server used for IPSec-configuration. Populated by SDN-C from 1607
+ ###### Related Nodes
+ - TO ipsec-configuration( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)
+ required:
+ - vig-address-type
+ properties:
+ vig-address-type:
type: string
- aai-node-type:
+ description: indicates whether the VIG is for AVPN or INTERNET
+ ipaddress-v4-vig:
type: string
- aai-created-ts:
+ description: v4 IP of the vig server
+ ipaddress-v6-vig:
+ type: string
+ description: v6 IP of the vig server
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ vig-servers:
+ properties:
+ vig-server:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vig-server"
+ vip-ipv4-address-list:
+ description: |
+ IPv4 Address Range
+ ###### Related Nodes
+ - TO cloud-region( vip-ipv4-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO instance-group( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO subnet( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv4-address-list, MANY2MANY)
+ required:
+ - vip-ipv4-address
+ properties:
+ vip-ipv4-address:
+ type: string
+ description: IP address
+ vip-ipv4-prefix-length:
type: integer
format: int64
- aai-unique-key:
- type: string
- aai-last-mod-ts:
+ description: Prefix length, 32 for single address
+ vlan-id-inner:
type: integer
format: int64
- source-of-truth:
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ resource-version:
type: string
- aai-uri:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
type: string
- edge-prop-names:
+ description: Neutron network id of the interface that address belongs to
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of subnet that address belongs to
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ vip-ipv6-address-list:
description: |
- Internal map to define the properties of an edge and interpret the map EdgeRules
+ IPv6 Address Range
+ ###### Related Nodes
+ - TO cloud-region( vip-ipv6-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO instance-group( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO subnet( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv6-address-list, MANY2MANY)
+ required:
+ - vip-ipv6-address
properties:
- edgeLabel:
+ vip-ipv6-address:
type: string
- direction:
+ description: IP address
+ vip-ipv6-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 128 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ resource-version:
type: string
- multiplicityRule:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
type: string
- isParent:
- type: boolean
- usesResource:
- type: boolean
- hasDelTarget:
- type: boolean
- SVC-INFRA:
- type: boolean
- SVC-INFRA-REV:
- type: boolean
- model-and-named-query-search:
+ description: Neutron network id of the interface that address belongs to
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of subnet that address belongs to
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ virtual-data-center:
description: |
- ModelAndNamedQuerySearch holds query-parameters and instance-properties for performing a named-query or model query
+ Virtual organization of cloud infrastructure elements in a data center context
+ ###### Related Nodes
+ - FROM connector( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ required:
+ - vdc-id
+ - vdc-name
properties:
- query-parameters:
- type: object
- $ref: "#/definitions/query-parameters"
- instance-filters:
- type: object
- $ref: "#/definitions/instance-filters"
- secondary-filts:
- type: object
- $ref: "#/definitions/secondary-filts"
- top-node-type:
+ vdc-id:
type: string
- secondary-filter-cut-point:
+ description: Unique ID of the vdc
+ vdc-name:
type: string
- query-parameters:
+ description: Name of the virtual data center
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ virtual-data-centers:
description: |
- QueryParameters for performing a named-query or model query
+ Virtual organization of cloud infrastructure elements in a data center context
properties:
- named-query:
- type: object
- $ref: "#/definitions/named-query"
- overloaded-model:
- type: object
- $ref: "#/definitions/overloaded-model"
- overloaded-model:
+ virtual-data-center:
+ type: array
+ items:
+ $ref: "#/getDefinitions/virtual-data-center"
+ vlan:
description: |
- Allows for legacy POST of old-style and new-style models
+ Definition of vlan
+ ###### Related Nodes
+ - TO l-interface( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)
+ - TO logical-link( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - TO multicast-configuration( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ - VLAN is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST
+ - VLAN deletion means associated objects of these types are also DELETED:LOGICAL-LINK
required:
- - model-invariant-id
- - model-name-version-id
- - model-type
- - model-name
- - model-id
- - model-version
+ - vlan-interface
+ - in-maint
properties:
- model-invariant-id:
+ vlan-interface:
type: string
- description: Unique identifier corresponding to the main definition of a model in ASDC
- model-name-version-id:
+ description: String that identifies the interface
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ resource-version:
type: string
- description: Unique identifier corresponding to one version of a model in ASDC
- model-type:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ speed-value:
type: string
- description: Type of the model, e.g., service, resource, widget, etc.
- model-name:
+ description: Captures the numeric part of the speed
+ speed-units:
type: string
- description: Name of the model, which can change from version to version.
- model-id:
+ description: Captures the units corresponding to the speed
+ vlan-description:
type: string
- description: Invariant unique ID which does not change from version to version
- model-version:
+ description: Used to describe (the service associated with) the vlan
+ backdoor-connection:
type: string
- description: Version
- model-description:
+ description: Whether customer is going to use this VLAN for backdoor connection to another customer premise device.
+ vpn-id:
type: string
- description: Description
+ description: This indicates the customers VPN ID associated with this vlan
+ orchestration-status:
+ type: string
+ description: Status of a vnf's vlan interface, on which the customer circuit resides, mastered by SDN-C.
+ in-maint:
+ type: boolean
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ l3-interface-ipv4-address-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
+ l3-interface-ipv6-address-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
+ vlans:
+ properties:
+ vlan:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vlan"
+ vnf:
+ description: |
+ Abstract vnf class
+ required:
+ - vnf-id
+ properties:
+ vnf-id:
+ type: string
+ description: Unique id of VNF. This is unique across the graph.
+ vnf-image:
+ description: |
+ Image object that pertain to a VNF that doesn't have associated vservers. This is a kludge.
+ ###### Related Nodes
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)
+ - VNF-IMAGE cannot be deleted if linked to GENERIC-VNF
+ required:
+ - vnf-image-uuid
+ - application
+ - application-vendor
+ properties:
+ vnf-image-uuid:
+ type: string
+ description: Unique ID of this asset
+ application:
+ type: string
+ description: The application that the image instantiates.
+ application-vendor:
+ type: string
+ description: The vendor of the application.
+ application-version:
+ type: string
+ description: The version of the application.
+ selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- model-vers:
- type: object
- $ref: "#/definitions/model-vers"
relationship-list:
- type: object
- $ref: "#/definitions/relationship-list"
- instance-filters:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ vnf-images:
description: |
- InstanceFilters for performing a named-query or model query
+ Collection of image objects that pertain to a VNF that doesn't have associated vservers. This is a kludge.
properties:
- instance-filter:
+ vnf-image:
type: array
items:
- $ref: "#/definitions/instance-filter"
- instance-filter:
+ $ref: "#/getDefinitions/vnf-image"
+ vnfc:
description: |
- InstanceFilter for performing a named-query or model query
- secondary-filts:
+ ###### Related Nodes
+ - TO generic-vnf( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vserver( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)
+ required:
+ - vnfc-name
+ - vnfc-function-code
+ - vnfc-type
+ - in-maint
+ - is-closed-loop-disabled
+ properties:
+ vnfc-name:
+ type: string
+ description: Unique ID of vnfc.
+ vnfc-function-code:
+ type: string
+ description: function code
+ vnfc-type:
+ type: string
+ description: type
+ prov-status:
+ type: string
+ description: prov status of this vnfc
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by APP-C
+ ipaddress-v4-oam-vip:
+ type: string
+ description: Oam V4 vip address of this vnfc
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
+ group-notation:
+ type: string
+ description: Group notation of VNFC
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ vnfcs:
description: |
- SecondaryFilts for performing a named-query or model query
+ virtual network components associated with a vserver from application controller.
properties:
- secondary-filt:
+ vnfc:
type: array
items:
- $ref: "#/definitions/secondary-filt"
- secondary-filt:
+ $ref: "#/getDefinitions/vnfc"
+ volume:
description: |
- SecondaryFilt for performing a named-query or model query
- properties:
+ Ephemeral Block storage volume.
+ ###### Related Nodes
+ - FROM vserver (PARENT of volume, vserver tosca.relationships.AttachesTo volume)
+ required:
+ - volume-id
+ - volume-selflink
+ properties:
+ volume-id:
+ type: string
+ description: Unique ID of block storage volume relative to the vserver.
+ volume-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ volume-group:
description: |
- Property holder for query properties or instance properties
+ Persistent block-level storage.
+ ###### Related Nodes
+ - TO cloud-region( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO complex( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ required:
+ - volume-group-id
+ - volume-group-name
+ - vnf-type
properties:
- property-name:
+ volume-group-id:
type: string
- property-value:
+ description: Unique ID of volume-group.
+ volume-group-name:
type: string
- response-list:
+ description: Name of the volume group.
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this volume-group
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ orchestration-status:
+ type: string
+ description: Orchestration status of this volume-group
+ model-customization-id:
+ type: string
+ description: captures the id of all the configuration used to customize the resource for the service.
+ vf-module-model-customization-id:
+ type: string
+ description: helps relate the volume group to the vf-module whose components will require the volume group
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ volume-groups:
description: |
- Response container for the results of a named-query or model query
+ Collection of persistent block-level storage.
properties:
- inventory-response-items:
- type: object
- $ref: "#/definitions/inventory-response-items"
- inventory-response-items:
+ volume-group:
+ type: array
+ items:
+ $ref: "#/getDefinitions/volume-group"
+ volumes:
description: |
- Container for inventory items in response list
+ Collection of ephemeral Block storage volumes.
properties:
- inventory-response-item:
+ volume:
type: array
items:
- $ref: "#/definitions/inventory-response-item"
- inventory-response-item:
+ $ref: "#/getDefinitions/volume"
+ vpls-pe:
description: |
- Inventory item for response list
+ VPLS Provider Edge routers.
+ ###### Related Nodes
+ - TO complex( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO ctag-pool( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - VPLS-PE is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
+ required:
+ - equipment-name
properties:
- model-name:
+ equipment-name:
type: string
- extra-properties:
- type: object
- $ref: "#/definitions/extra-properties"
- inventory-response-items:
- type: object
- $ref: "#/definitions/inventory-response-items"
- extra-properties:
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address).
+ equipment-role:
+ type: string
+ description: Client should send valid enumerated value, e.g., VPLS-PE.
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Temporary location for stag to get to VCE
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ p-interfaces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/p-interface"
+ lag-interfaces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/lag-interface"
+ vpls-pes:
description: |
- Extra properties for inventory item for response list
+ Collection of VPLS Provider Edge routers
properties:
- extra-property:
+ vpls-pe:
type: array
items:
- $ref: "#/definitions/extra-property"
- extra-property:
+ $ref: "#/getDefinitions/vpls-pe"
+ vpn-binding:
+ description: |
+ VPN binding
+ ###### Related Nodes
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - FROM route-target( route-target org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2ONE)
+ - VPN-BINDING cannot be deleted if linked to L3-NETWORK,LOGICAL-LINK
+ - VPN-BINDING is DELETED when these are DELETED ROUTE-TARGET
+ required:
+ - vpn-id
+ - vpn-name
properties:
- property-name:
+ vpn-id:
type: string
- property-value:
+ description: VPN ID, globally unique within A&AI
+ vpn-name:
type: string
- vnf:
+ description: VPN Name
+ vpn-platform:
+ type: string
+ description: the platform associated with the VPN example AVPN, Mobility
+ vpn-type:
+ type: string
+ description: Type of the vpn, should be taken from enumerated/valid values
+ route-distinguisher:
+ type: string
+ description: Used to distinguish the distinct VPN routes of separate customers who connect to the provider in an MPLS network.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ route-targets:
+ type: array
+ items:
+ $ref: "#/getDefinitions/route-target"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ description: l3-networks relate to vpn-bindings
+ vpn-bindings:
+ properties:
+ vpn-binding:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vpn-binding"
+ vserver:
description: |
- Abstract vnf class
+ Virtual Servers, aka virtual machine or VM.
+ ###### Related Nodes
+ - TO tenant( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)
+ - TO flavor( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)
+ - TO image( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)
+ - TO pserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)
+ - TO snapshot( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)
+ - TO volume (CHILD of vserver, vserver tosca.relationships.AttachesTo volume, ONE2MANY)
+ - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM vce( vce tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)
+ - FROM vnfc( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)
+ - VSERVER is DELETED when these are DELETED L-INTERFACE
+ - VSERVER deletion means associated objects of these types are also DELETED:VOLUME
required:
- - vnf-id
+ - vserver-id
+ - vserver-name
+ - vserver-selflink
+ - in-maint
+ - is-closed-loop-disabled
properties:
- vnf-id:
+ vserver-id:
type: string
- description: Unique id of VNF. This is unique across the graph.
+ description: Unique identifier for this vserver relative to its tenant
+ vserver-name:
+ type: string
+ description: Name of vserver
+ vserver-name2:
+ type: string
+ description: Alternative name of vserver
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ vserver-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ volumes:
+ type: array
+ items:
+ $ref: "#/getDefinitions/volume"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l-interface"
+ vservers:
+ description: |
+ Collection of virtual Servers, aka virtual machines or VMs.
+ properties:
+ vserver:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vserver"
+ zone:
+ description: |
+ A zone is a grouping of assets in a location homing to the same connections into the CBB
+ ###### Related Nodes
+ - TO complex( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM pnf( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ required:
+ - zone-id
+ - zone-name
+ - design-type
+ - zone-context
+ properties:
+ zone-id:
+ type: string
+ description: Code assigned by AIC to the zone
+ zone-name:
+ type: string
+ description: English name associated with the zone
+ design-type:
+ type: string
+ description: Design of zone [Medium/Large?]
+ zone-context:
+ type: string
+ description: Context of zone [production/test]
+ status:
+ type: string
+ description: Status of a zone.
+ resource-version:
+ type: string
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ zones:
+ description: |
+ Collection of zones
+ properties:
+ zone:
+ type: array
+ items:
+ $ref: "#/getDefinitions/zone"
diff --git a/aai-schema/src/main/resources/aai_swagger_yaml/aai_swagger_v11.yaml b/aai-schema/src/main/resources/aai_swagger_yaml/aai_swagger_v11.yaml
index 4447f7f3..5e6105e4 100644
--- a/aai-schema/src/main/resources/aai_swagger_yaml/aai_swagger_v11.yaml
+++ b/aai-schema/src/main/resources/aai_swagger_yaml/aai_swagger_v11.yaml
@@ -1,28 +1,9 @@
-#
-# ============LICENSE_START=======================================================
-# org.onap.aai
-# ================================================================================
-# Copyright © 2017 AT&T Intellectual Property. All rights reserved.
-# ================================================================================
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-# http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-# ============LICENSE_END=========================================================
-#
-# ECOMP is a trademark and service mark of AT&T Intellectual Property.
-#
-
swagger: "2.0"
info:
description: |
+
+ [Differences versus the previous schema version](apidocs/aai_swagger_v11.diff)
+
Copyright &copy; 2017 AT&amp;T Intellectual Property. All rights reserved.
Licensed under the Creative Commons License, Attribution 4.0 Intl. (the &quot;License&quot;); you may not use this documentation except in compliance with the License.
@@ -71,19 +52,22 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: target-pe
in: path
description: The Target provider edge router
required: true
type: string
+ example: __TARGET-PE__
- name: availability-zone-name
in: path
description: Name of the availability zone
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureComplexesComplexCtagPoolsCtagPool.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -108,16 +92,19 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: target-pe
in: path
description: The Target provider edge router
required: true
type: string
+ example: __TARGET-PE__
- name: availability-zone-name
in: path
description: Name of the availability zone
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
/cloud-infrastructure/complexes/complex/{physical-location-id}/ctag-pools/ctag-pool/{target-pe}/{availability-zone-name}:
get:
tags:
@@ -132,7 +119,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/ctag-pool"
+ $ref: "#/getDefinitions/ctag-pool"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -141,16 +128,19 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: target-pe
in: path
description: The Target provider edge router
required: true
type: string
+ example: __TARGET-PE__
- name: availability-zone-name
in: path
description: Name of the availability zone
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: data-center-code
in: query
description: Data center code which can be an alternate way to identify a complex
@@ -170,7 +160,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing ctag-pool
- description: create or update an existing ctag-pool
+ description: |
+ Create or update an existing ctag-pool.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureComplexesComplexCtagPoolsCtagPool
consumes:
- application/json
@@ -187,22 +180,76 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: target-pe
in: path
description: The Target provider edge router
required: true
type: string
+ example: __TARGET-PE__
- name: availability-zone-name
in: path
description: Name of the availability zone
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: body
in: body
- description: ctag-pool object that needs to be created or updated
+ description: ctag-pool object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureComplexesComplexCtagPoolsCtagPool.json)
required: true
schema:
$ref: "#/definitions/ctag-pool"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing ctag-pool
+ description: |
+ Update an existing ctag-pool
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureComplexesComplexCtagPoolsCtagPool
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: physical-location-id
+ in: path
+ description: Unique identifier for physical location, e.g., CLLI
+ required: true
+ type: string
+ example: __PHYSICAL-LOCATION-ID__
+ - name: target-pe
+ in: path
+ description: The Target provider edge router
+ required: true
+ type: string
+ example: __TARGET-PE__
+ - name: availability-zone-name
+ in: path
+ description: Name of the availability zone
+ required: true
+ type: string
+ example: __AVAILABILITY-ZONE-NAME__
+ - name: body
+ in: body
+ description: ctag-pool object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/ctag-pool"
delete:
tags:
- CloudInfrastructure
@@ -224,16 +271,19 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: target-pe
in: path
description: The Target provider edge router
required: true
type: string
+ example: __TARGET-PE__
- name: availability-zone-name
in: path
description: Name of the availability zone
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -253,7 +303,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/ctag-pools"
+ $ref: "#/getDefinitions/ctag-pools"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -262,6 +312,7 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: data-center-code
in: query
description: Data center code which can be an alternate way to identify a complex
@@ -298,9 +349,10 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureComplexesComplex.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -325,6 +377,7 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
/cloud-infrastructure/complexes/complex/{physical-location-id}:
get:
tags:
@@ -339,7 +392,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/complex"
+ $ref: "#/getDefinitions/complex"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -348,6 +401,7 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: data-center-code
in: query
description: Data center code which can be an alternate way to identify a complex
@@ -367,7 +421,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing complex
- description: create or update an existing complex
+ description: |
+ Create or update an existing complex.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureComplexesComplex
consumes:
- application/json
@@ -384,12 +441,52 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: body
in: body
- description: complex object that needs to be created or updated
+ description: complex object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureComplexesComplex.json)
required: true
schema:
$ref: "#/definitions/complex"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing complex
+ description: |
+ Update an existing complex
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureComplexesComplex
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: physical-location-id
+ in: path
+ description: Unique identifier for physical location, e.g., CLLI
+ required: true
+ type: string
+ example: __PHYSICAL-LOCATION-ID__
+ - name: body
+ in: body
+ description: complex object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/complex"
delete:
tags:
- CloudInfrastructure
@@ -411,6 +508,7 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -430,7 +528,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/complexes"
+ $ref: "#/getDefinitions/complexes"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/volume-groups/volume-group/{volume-group-id}/relationship-list/relationship:
@@ -454,19 +552,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: volume-group-id
in: path
description: Unique ID of volume-group.
required: true
type: string
+ example: __VOLUME-GROUP-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -491,16 +592,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: volume-group-id
in: path
description: Unique ID of volume-group.
required: true
type: string
+ example: __VOLUME-GROUP-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/volume-groups/volume-group/{volume-group-id}:
get:
tags:
@@ -515,7 +619,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/volume-group"
+ $ref: "#/getDefinitions/volume-group"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -524,16 +628,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: volume-group-id
in: path
description: Unique ID of volume-group.
required: true
type: string
+ example: __VOLUME-GROUP-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -563,7 +670,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing volume-group
- description: create or update an existing volume-group
+ description: |
+ Create or update an existing volume-group.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup
consumes:
- application/json
@@ -580,22 +690,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: volume-group-id
in: path
description: Unique ID of volume-group.
required: true
type: string
+ example: __VOLUME-GROUP-ID__
- name: body
in: body
- description: volume-group object that needs to be created or updated
+ description: volume-group object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup.json)
required: true
schema:
$ref: "#/definitions/volume-group"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing volume-group
+ description: |
+ Update an existing volume-group
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: volume-group-id
+ in: path
+ description: Unique ID of volume-group.
+ required: true
+ type: string
+ example: __VOLUME-GROUP-ID__
+ - name: body
+ in: body
+ description: volume-group object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/volume-group"
delete:
tags:
- CloudInfrastructure
@@ -617,16 +781,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: volume-group-id
in: path
description: Unique ID of volume-group.
required: true
type: string
+ example: __VOLUME-GROUP-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -646,7 +813,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/volume-groups"
+ $ref: "#/getDefinitions/volume-groups"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -655,11 +822,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -691,29 +860,34 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: volume-id
in: path
description: Unique ID of block storage volume relative to the vserver.
required: true
type: string
+ example: __VOLUME-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -738,26 +912,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: volume-id
in: path
description: Unique ID of block storage volume relative to the vserver.
required: true
type: string
+ example: __VOLUME-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/volumes/volume/{volume-id}:
get:
tags:
@@ -772,7 +951,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/volume"
+ $ref: "#/getDefinitions/volume"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -781,26 +960,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: volume-id
in: path
description: Unique ID of block storage volume relative to the vserver.
required: true
type: string
+ example: __VOLUME-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -848,7 +1032,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing volume
- description: create or update an existing volume
+ description: |
+ Create or update an existing volume.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume
consumes:
- application/json
@@ -865,32 +1052,100 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: volume-id
in: path
description: Unique ID of block storage volume relative to the vserver.
required: true
type: string
+ example: __VOLUME-ID__
- name: body
in: body
- description: volume object that needs to be created or updated
+ description: volume object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume.json)
required: true
schema:
$ref: "#/definitions/volume"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing volume
+ description: |
+ Update an existing volume
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: volume-id
+ in: path
+ description: Unique ID of block storage volume relative to the vserver.
+ required: true
+ type: string
+ example: __VOLUME-ID__
+ - name: body
+ in: body
+ description: volume object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/volume"
delete:
tags:
- CloudInfrastructure
@@ -912,26 +1167,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: volume-id
in: path
description: Unique ID of block storage volume relative to the vserver.
required: true
type: string
+ example: __VOLUME-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -951,7 +1211,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/volumes"
+ $ref: "#/getDefinitions/volumes"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -960,21 +1220,25 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -1039,24 +1303,28 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -1081,21 +1349,25 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -1117,34 +1389,40 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -1169,31 +1447,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -1215,39 +1499,46 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -1272,36 +1563,43 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -1316,7 +1614,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -1325,36 +1623,43 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -1444,7 +1749,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -1461,42 +1769,124 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- CloudInfrastructure
@@ -1518,36 +1908,43 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -1574,39 +1971,46 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -1631,36 +2035,43 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -1675,7 +2086,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -1684,36 +2095,43 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -1803,7 +2221,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -1820,42 +2241,124 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- CloudInfrastructure
@@ -1877,36 +2380,43 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -1926,7 +2436,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -1935,31 +2445,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -2033,7 +2549,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -2050,37 +2569,112 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- CloudInfrastructure
@@ -2102,31 +2696,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -2146,7 +2746,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -2155,26 +2755,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -2254,34 +2859,40 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -2306,31 +2917,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -2345,7 +2962,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -2354,31 +2971,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -2461,7 +3084,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -2478,37 +3104,112 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- CloudInfrastructure
@@ -2530,31 +3231,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -2574,7 +3281,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -2583,26 +3290,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -2682,29 +3394,34 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -2729,26 +3446,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -2770,34 +3492,40 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -2822,31 +3550,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -2861,7 +3595,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -2870,31 +3604,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -2973,7 +3713,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -2990,37 +3733,112 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- CloudInfrastructure
@@ -3042,31 +3860,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -3093,34 +3917,40 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -3145,31 +3975,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -3184,7 +4020,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -3193,31 +4029,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -3296,7 +4138,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -3313,37 +4158,112 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- CloudInfrastructure
@@ -3365,31 +4285,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -3409,7 +4335,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -3418,26 +4344,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -3500,7 +4431,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface
consumes:
- application/json
@@ -3517,32 +4451,100 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- CloudInfrastructure
@@ -3564,26 +4566,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -3603,7 +4610,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -3612,21 +4619,25 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -3684,7 +4695,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vserver"
+ $ref: "#/getDefinitions/vserver"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -3693,21 +4704,25 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -3755,7 +4770,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing vserver
- description: create or update an existing vserver
+ description: |
+ Create or update an existing vserver.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver
consumes:
- application/json
@@ -3772,27 +4790,88 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: body
in: body
- description: vserver object that needs to be created or updated
+ description: vserver object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver.json)
required: true
schema:
$ref: "#/definitions/vserver"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing vserver
+ description: |
+ Update an existing vserver
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: body
+ in: body
+ description: vserver object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vserver"
delete:
tags:
- CloudInfrastructure
@@ -3814,21 +4893,25 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -3848,7 +4931,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vservers"
+ $ref: "#/getDefinitions/vservers"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -3857,16 +4940,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -3908,19 +4994,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenant.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -3945,16 +5034,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}:
get:
tags:
@@ -3969,7 +5061,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/tenant"
+ $ref: "#/getDefinitions/tenant"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -3978,16 +5070,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4012,7 +5107,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing tenant
- description: create or update an existing tenant
+ description: |
+ Create or update an existing tenant.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenant
consumes:
- application/json
@@ -4029,22 +5127,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: body
in: body
- description: tenant object that needs to be created or updated
+ description: tenant object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionTenantsTenant.json)
required: true
schema:
$ref: "#/definitions/tenant"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing tenant
+ description: |
+ Update an existing tenant
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenant
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: body
+ in: body
+ description: tenant object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/tenant"
delete:
tags:
- CloudInfrastructure
@@ -4066,16 +5218,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -4095,7 +5250,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/tenants"
+ $ref: "#/getDefinitions/tenants"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4104,11 +5259,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4140,19 +5297,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: flavor-id
in: path
description: Flavor id, expected to be unique across cloud-region.
required: true
type: string
+ example: __FLAVOR-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -4177,16 +5337,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: flavor-id
in: path
description: Flavor id, expected to be unique across cloud-region.
required: true
type: string
+ example: __FLAVOR-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/flavors/flavor/{flavor-id}:
get:
tags:
@@ -4201,7 +5364,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/flavor"
+ $ref: "#/getDefinitions/flavor"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4210,16 +5373,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: flavor-id
in: path
description: Flavor id, expected to be unique across cloud-region.
required: true
type: string
+ example: __FLAVOR-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4239,7 +5405,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing flavor
- description: create or update an existing flavor
+ description: |
+ Create or update an existing flavor.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor
consumes:
- application/json
@@ -4256,22 +5425,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: flavor-id
in: path
description: Flavor id, expected to be unique across cloud-region.
required: true
type: string
+ example: __FLAVOR-ID__
- name: body
in: body
- description: flavor object that needs to be created or updated
+ description: flavor object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor.json)
required: true
schema:
$ref: "#/definitions/flavor"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing flavor
+ description: |
+ Update an existing flavor
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: flavor-id
+ in: path
+ description: Flavor id, expected to be unique across cloud-region.
+ required: true
+ type: string
+ example: __FLAVOR-ID__
+ - name: body
+ in: body
+ description: flavor object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/flavor"
delete:
tags:
- CloudInfrastructure
@@ -4293,16 +5516,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: flavor-id
in: path
description: Flavor id, expected to be unique across cloud-region.
required: true
type: string
+ example: __FLAVOR-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -4322,7 +5548,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/flavors"
+ $ref: "#/getDefinitions/flavors"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4331,11 +5557,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4367,19 +5595,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: group-id
in: path
description: Group id, expected to be unique across cloud-region.
required: true
type: string
+ example: __GROUP-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -4404,16 +5635,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: group-id
in: path
description: Group id, expected to be unique across cloud-region.
required: true
type: string
+ example: __GROUP-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/group-assignments/group-assignment/{group-id}:
get:
tags:
@@ -4428,7 +5662,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/group-assignment"
+ $ref: "#/getDefinitions/group-assignment"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4437,16 +5671,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: group-id
in: path
description: Group id, expected to be unique across cloud-region.
required: true
type: string
+ example: __GROUP-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4471,7 +5708,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing group-assignment
- description: create or update an existing group-assignment
+ description: |
+ Create or update an existing group-assignment.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment
consumes:
- application/json
@@ -4488,22 +5728,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: group-id
in: path
description: Group id, expected to be unique across cloud-region.
required: true
type: string
+ example: __GROUP-ID__
- name: body
in: body
- description: group-assignment object that needs to be created or updated
+ description: group-assignment object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment.json)
required: true
schema:
$ref: "#/definitions/group-assignment"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing group-assignment
+ description: |
+ Update an existing group-assignment
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: group-id
+ in: path
+ description: Group id, expected to be unique across cloud-region.
+ required: true
+ type: string
+ example: __GROUP-ID__
+ - name: body
+ in: body
+ description: group-assignment object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/group-assignment"
delete:
tags:
- CloudInfrastructure
@@ -4525,16 +5819,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: group-id
in: path
description: Group id, expected to be unique across cloud-region.
required: true
type: string
+ example: __GROUP-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -4554,7 +5851,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/group-assignments"
+ $ref: "#/getDefinitions/group-assignments"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4563,11 +5860,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4599,19 +5898,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: snapshot-id
in: path
description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
required: true
type: string
+ example: __SNAPSHOT-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -4636,16 +5938,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: snapshot-id
in: path
description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
required: true
type: string
+ example: __SNAPSHOT-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/snapshots/snapshot/{snapshot-id}:
get:
tags:
@@ -4660,7 +5965,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/snapshot"
+ $ref: "#/getDefinitions/snapshot"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4669,16 +5974,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: snapshot-id
in: path
description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
required: true
type: string
+ example: __SNAPSHOT-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4718,7 +6026,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing snapshot
- description: create or update an existing snapshot
+ description: |
+ Create or update an existing snapshot.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot
consumes:
- application/json
@@ -4735,22 +6046,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: snapshot-id
in: path
description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
required: true
type: string
+ example: __SNAPSHOT-ID__
- name: body
in: body
- description: snapshot object that needs to be created or updated
+ description: snapshot object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot.json)
required: true
schema:
$ref: "#/definitions/snapshot"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing snapshot
+ description: |
+ Update an existing snapshot
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: snapshot-id
+ in: path
+ description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
+ required: true
+ type: string
+ example: __SNAPSHOT-ID__
+ - name: body
+ in: body
+ description: snapshot object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/snapshot"
delete:
tags:
- CloudInfrastructure
@@ -4772,16 +6137,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: snapshot-id
in: path
description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
required: true
type: string
+ example: __SNAPSHOT-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -4801,7 +6169,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/snapshots"
+ $ref: "#/getDefinitions/snapshots"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4810,11 +6178,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4846,19 +6216,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionImagesImage.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -4883,16 +6256,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}/metadata/metadatum/{metaname}:
get:
tags:
@@ -4907,7 +6283,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadatum"
+ $ref: "#/getDefinitions/metadatum"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4916,20 +6292,24 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4964,7 +6344,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing metadatum
- description: create or update an existing metadatum
+ description: |
+ Create or update an existing metadatum.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionImagesImageMetadataMetadatum
consumes:
- application/json
@@ -4981,26 +6364,86 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: body
in: body
- description: metadatum object that needs to be created or updated
+ description: metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionImagesImageMetadataMetadatum.json)
required: true
schema:
$ref: "#/definitions/metadatum"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing metadatum
+ description: |
+ Update an existing metadatum
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionImagesImageMetadataMetadatum
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: image-id
+ in: path
+ description: Image id, expected to be unique across cloud region
+ required: true
+ type: string
+ example: __IMAGE-ID__
+ - name: metaname
+ in: path
+ required: true
+ type: string
+ example: __METANAME__
+ - name: body
+ in: body
+ description: metadatum object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/metadatum"
delete:
tags:
- CloudInfrastructure
@@ -5022,20 +6465,24 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -5055,7 +6502,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadata"
+ $ref: "#/getDefinitions/metadata"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5064,16 +6511,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5118,7 +6568,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/image"
+ $ref: "#/getDefinitions/image"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5127,16 +6577,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5171,7 +6624,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing image
- description: create or update an existing image
+ description: |
+ Create or update an existing image.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionImagesImage
consumes:
- application/json
@@ -5188,22 +6644,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: body
in: body
- description: image object that needs to be created or updated
+ description: image object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionImagesImage.json)
required: true
schema:
$ref: "#/definitions/image"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing image
+ description: |
+ Update an existing image
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionImagesImage
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: image-id
+ in: path
+ description: Image id, expected to be unique across cloud region
+ required: true
+ type: string
+ example: __IMAGE-ID__
+ - name: body
+ in: body
+ description: image object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/image"
delete:
tags:
- CloudInfrastructure
@@ -5225,16 +6735,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -5254,7 +6767,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/images"
+ $ref: "#/getDefinitions/images"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5263,11 +6776,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5299,19 +6814,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: switch-name
in: path
description: DVS switch name
required: true
type: string
+ example: __SWITCH-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -5336,16 +6854,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: switch-name
in: path
description: DVS switch name
required: true
type: string
+ example: __SWITCH-NAME__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/dvs-switches/dvs-switch/{switch-name}:
get:
tags:
@@ -5360,7 +6881,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/dvs-switch"
+ $ref: "#/getDefinitions/dvs-switch"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5369,16 +6890,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: switch-name
in: path
description: DVS switch name
required: true
type: string
+ example: __SWITCH-NAME__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5398,7 +6922,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing dvs-switch
- description: create or update an existing dvs-switch
+ description: |
+ Create or update an existing dvs-switch.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch
consumes:
- application/json
@@ -5415,22 +6942,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: switch-name
in: path
description: DVS switch name
required: true
type: string
+ example: __SWITCH-NAME__
- name: body
in: body
- description: dvs-switch object that needs to be created or updated
+ description: dvs-switch object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch.json)
required: true
schema:
$ref: "#/definitions/dvs-switch"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing dvs-switch
+ description: |
+ Update an existing dvs-switch
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: switch-name
+ in: path
+ description: DVS switch name
+ required: true
+ type: string
+ example: __SWITCH-NAME__
+ - name: body
+ in: body
+ description: dvs-switch object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/dvs-switch"
delete:
tags:
- CloudInfrastructure
@@ -5452,16 +7033,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: switch-name
in: path
description: DVS switch name
required: true
type: string
+ example: __SWITCH-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -5481,7 +7065,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/dvs-switches"
+ $ref: "#/getDefinitions/dvs-switches"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5490,11 +7074,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5526,19 +7112,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: network-uuid
in: path
description: UUID of the network. Unique across a cloud-region
required: true
type: string
+ example: __NETWORK-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -5563,16 +7152,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: network-uuid
in: path
description: UUID of the network. Unique across a cloud-region
required: true
type: string
+ example: __NETWORK-UUID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/oam-networks/oam-network/{network-uuid}:
get:
tags:
@@ -5587,7 +7179,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/oam-network"
+ $ref: "#/getDefinitions/oam-network"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5596,16 +7188,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: network-uuid
in: path
description: UUID of the network. Unique across a cloud-region
required: true
type: string
+ example: __NETWORK-UUID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5631,7 +7226,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing oam-network
- description: create or update an existing oam-network
+ description: |
+ Create or update an existing oam-network.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork
consumes:
- application/json
@@ -5648,22 +7246,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: network-uuid
in: path
description: UUID of the network. Unique across a cloud-region
required: true
type: string
+ example: __NETWORK-UUID__
- name: body
in: body
- description: oam-network object that needs to be created or updated
+ description: oam-network object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork.json)
required: true
schema:
$ref: "#/definitions/oam-network"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing oam-network
+ description: |
+ Update an existing oam-network
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: network-uuid
+ in: path
+ description: UUID of the network. Unique across a cloud-region
+ required: true
+ type: string
+ example: __NETWORK-UUID__
+ - name: body
+ in: body
+ description: oam-network object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/oam-network"
delete:
tags:
- CloudInfrastructure
@@ -5685,16 +7337,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: network-uuid
in: path
description: UUID of the network. Unique across a cloud-region
required: true
type: string
+ example: __NETWORK-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -5714,7 +7369,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/oam-networks"
+ $ref: "#/getDefinitions/oam-networks"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5723,11 +7378,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5759,19 +7416,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: availability-zone-name
in: path
description: Name of the availability zone. Unique across a cloud region
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -5796,16 +7456,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: availability-zone-name
in: path
description: Name of the availability zone. Unique across a cloud region
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/availability-zones/availability-zone/{availability-zone-name}:
get:
tags:
@@ -5820,7 +7483,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/availability-zone"
+ $ref: "#/getDefinitions/availability-zone"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5829,16 +7492,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: availability-zone-name
in: path
description: Name of the availability zone. Unique across a cloud region
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5853,7 +7519,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing availability-zone
- description: create or update an existing availability-zone
+ description: |
+ Create or update an existing availability-zone.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone
consumes:
- application/json
@@ -5870,22 +7539,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: availability-zone-name
in: path
description: Name of the availability zone. Unique across a cloud region
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: body
in: body
- description: availability-zone object that needs to be created or updated
+ description: availability-zone object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone.json)
required: true
schema:
$ref: "#/definitions/availability-zone"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing availability-zone
+ description: |
+ Update an existing availability-zone
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: availability-zone-name
+ in: path
+ description: Name of the availability zone. Unique across a cloud region
+ required: true
+ type: string
+ example: __AVAILABILITY-ZONE-NAME__
+ - name: body
+ in: body
+ description: availability-zone object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/availability-zone"
delete:
tags:
- CloudInfrastructure
@@ -5907,16 +7630,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: availability-zone-name
in: path
description: Name of the availability zone. Unique across a cloud region
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -5936,7 +7662,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/availability-zones"
+ $ref: "#/getDefinitions/availability-zones"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5945,11 +7671,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5981,14 +7709,16 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegion.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -6013,11 +7743,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}/relationship-list/relationship:
put:
tags:
@@ -6039,19 +7771,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: esr-system-info-id
in: path
description: Unique ID of esr system info.
required: true
type: string
+ example: __ESR-SYSTEM-INFO-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionEsrSystemInfoListEsrSystemInfo.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -6076,16 +7811,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: esr-system-info-id
in: path
description: Unique ID of esr system info.
required: true
type: string
+ example: __ESR-SYSTEM-INFO-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}:
get:
tags:
@@ -6100,7 +7838,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/esr-system-info"
+ $ref: "#/getDefinitions/esr-system-info"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -6109,16 +7847,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: esr-system-info-id
in: path
description: Unique ID of esr system info.
required: true
type: string
+ example: __ESR-SYSTEM-INFO-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -6143,7 +7884,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing esr-system-info
- description: create or update an existing esr-system-info
+ description: |
+ Create or update an existing esr-system-info.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionEsrSystemInfoListEsrSystemInfo
consumes:
- application/json
@@ -6160,22 +7904,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: esr-system-info-id
in: path
description: Unique ID of esr system info.
required: true
type: string
+ example: __ESR-SYSTEM-INFO-ID__
- name: body
in: body
- description: esr-system-info object that needs to be created or updated
+ description: esr-system-info object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionEsrSystemInfoListEsrSystemInfo.json)
required: true
schema:
$ref: "#/definitions/esr-system-info"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing esr-system-info
+ description: |
+ Update an existing esr-system-info
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionEsrSystemInfoListEsrSystemInfo
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: esr-system-info-id
+ in: path
+ description: Unique ID of esr system info.
+ required: true
+ type: string
+ example: __ESR-SYSTEM-INFO-ID__
+ - name: body
+ in: body
+ description: esr-system-info object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/esr-system-info"
delete:
tags:
- CloudInfrastructure
@@ -6197,16 +7995,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: esr-system-info-id
in: path
description: Unique ID of esr system info.
required: true
type: string
+ example: __ESR-SYSTEM-INFO-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -6226,7 +8027,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/esr-system-info-list"
+ $ref: "#/getDefinitions/esr-system-info-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -6235,11 +8036,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -6271,19 +8074,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: vip-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __VIP-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionVipIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -6308,16 +8114,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: vip-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __VIP-IPV4-ADDRESS__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/vip-ipv4-address-list/{vip-ipv4-address}:
get:
tags:
@@ -6332,7 +8141,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vip-ipv4-address-list"
+ $ref: "#/getDefinitions/vip-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -6341,16 +8150,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: vip-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __VIP-IPV4-ADDRESS__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -6381,7 +8193,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing vip-ipv4-address-list
- description: create or update an existing vip-ipv4-address-list
+ description: |
+ Create or update an existing vip-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionVipIpv4AddressList
consumes:
- application/json
@@ -6398,22 +8213,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: vip-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __VIP-IPV4-ADDRESS__
- name: body
in: body
- description: vip-ipv4-address-list object that needs to be created or updated
+ description: vip-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionVipIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/vip-ipv4-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing vip-ipv4-address-list
+ description: |
+ Update an existing vip-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionVipIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: vip-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __VIP-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: vip-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vip-ipv4-address-list"
delete:
tags:
- CloudInfrastructure
@@ -6435,16 +8304,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: vip-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __VIP-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -6471,19 +8343,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: vip-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __VIP-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionVipIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -6508,16 +8383,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: vip-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __VIP-IPV6-ADDRESS__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/vip-ipv6-address-list/{vip-ipv6-address}:
get:
tags:
@@ -6532,7 +8410,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vip-ipv6-address-list"
+ $ref: "#/getDefinitions/vip-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -6541,16 +8419,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: vip-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __VIP-IPV6-ADDRESS__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -6581,7 +8462,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing vip-ipv6-address-list
- description: create or update an existing vip-ipv6-address-list
+ description: |
+ Create or update an existing vip-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionVipIpv6AddressList
consumes:
- application/json
@@ -6598,22 +8482,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: vip-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __VIP-IPV6-ADDRESS__
- name: body
in: body
- description: vip-ipv6-address-list object that needs to be created or updated
+ description: vip-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegionVipIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/vip-ipv6-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing vip-ipv6-address-list
+ description: |
+ Update an existing vip-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionVipIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: vip-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __VIP-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: vip-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vip-ipv6-address-list"
delete:
tags:
- CloudInfrastructure
@@ -6635,16 +8573,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: vip-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __VIP-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -6664,7 +8605,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/cloud-region"
+ $ref: "#/getDefinitions/cloud-region"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -6673,11 +8614,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -6692,7 +8635,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing cloud-region
- description: create or update an existing cloud-region
+ description: |
+ Create or update an existing cloud-region.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegion
consumes:
- application/json
@@ -6709,17 +8655,64 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: body
in: body
- description: cloud-region object that needs to be created or updated
+ description: cloud-region object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureCloudRegionsCloudRegion.json)
required: true
schema:
$ref: "#/definitions/cloud-region"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing cloud-region
+ description: |
+ Update an existing cloud-region
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegion
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: body
+ in: body
+ description: cloud-region object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/cloud-region"
delete:
tags:
- CloudInfrastructure
@@ -6741,11 +8734,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -6765,7 +8760,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/cloud-regions"
+ $ref: "#/getDefinitions/cloud-regions"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/cloud-infrastructure/network-profiles/network-profile/{nm-profile-name}/relationship-list/relationship:
@@ -6789,9 +8784,10 @@ paths:
description: Unique name of network profile.
required: true
type: string
+ example: __NM-PROFILE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureNetworkProfilesNetworkProfile.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -6816,6 +8812,7 @@ paths:
description: Unique name of network profile.
required: true
type: string
+ example: __NM-PROFILE-NAME__
/cloud-infrastructure/network-profiles/network-profile/{nm-profile-name}:
get:
tags:
@@ -6830,7 +8827,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/network-profile"
+ $ref: "#/getDefinitions/network-profile"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -6839,11 +8836,15 @@ paths:
description: Unique name of network profile.
required: true
type: string
+ example: __NM-PROFILE-NAME__
put:
tags:
- CloudInfrastructure
summary: create or update an existing network-profile
- description: create or update an existing network-profile
+ description: |
+ Create or update an existing network-profile.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureNetworkProfilesNetworkProfile
consumes:
- application/json
@@ -6860,12 +8861,52 @@ paths:
description: Unique name of network profile.
required: true
type: string
+ example: __NM-PROFILE-NAME__
- name: body
in: body
- description: network-profile object that needs to be created or updated
+ description: network-profile object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureNetworkProfilesNetworkProfile.json)
required: true
schema:
$ref: "#/definitions/network-profile"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing network-profile
+ description: |
+ Update an existing network-profile
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureNetworkProfilesNetworkProfile
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: nm-profile-name
+ in: path
+ description: Unique name of network profile.
+ required: true
+ type: string
+ example: __NM-PROFILE-NAME__
+ - name: body
+ in: body
+ description: network-profile object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/network-profile"
delete:
tags:
- CloudInfrastructure
@@ -6887,6 +8928,7 @@ paths:
description: Unique name of network profile.
required: true
type: string
+ example: __NM-PROFILE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -6906,7 +8948,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/network-profiles"
+ $ref: "#/getDefinitions/network-profiles"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/cloud-infrastructure/pservers/pserver/{hostname}/relationship-list/relationship:
@@ -6930,9 +8972,10 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserver.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -6957,6 +9000,7 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/relationship-list/relationship:
put:
tags:
@@ -6978,14 +9022,16 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -7010,11 +9056,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/sriov-pfs/sriov-pf/{pf-pci-id}/relationship-list/relationship:
put:
tags:
@@ -7036,19 +9084,22 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pf-pci-id
in: path
description: Identifier for the sriov-pf
required: true
type: string
+ example: __PF-PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceSriovPfsSriovPf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -7073,16 +9124,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pf-pci-id
in: path
description: Identifier for the sriov-pf
required: true
type: string
+ example: __PF-PCI-ID__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/sriov-pfs/sriov-pf/{pf-pci-id}:
get:
tags:
@@ -7097,7 +9151,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-pf"
+ $ref: "#/getDefinitions/sriov-pf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -7106,16 +9160,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pf-pci-id
in: path
description: Identifier for the sriov-pf
required: true
type: string
+ example: __PF-PCI-ID__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -7144,7 +9201,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing sriov-pf
- description: create or update an existing sriov-pf
+ description: |
+ Create or update an existing sriov-pf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceSriovPfsSriovPf
consumes:
- application/json
@@ -7161,22 +9221,76 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pf-pci-id
in: path
description: Identifier for the sriov-pf
required: true
type: string
+ example: __PF-PCI-ID__
- name: body
in: body
- description: sriov-pf object that needs to be created or updated
+ description: sriov-pf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceSriovPfsSriovPf.json)
required: true
schema:
$ref: "#/definitions/sriov-pf"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing sriov-pf
+ description: |
+ Update an existing sriov-pf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceSriovPfsSriovPf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pf-pci-id
+ in: path
+ description: Identifier for the sriov-pf
+ required: true
+ type: string
+ example: __PF-PCI-ID__
+ - name: body
+ in: body
+ description: sriov-pf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-pf"
delete:
tags:
- CloudInfrastructure
@@ -7198,16 +9312,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pf-pci-id
in: path
description: Identifier for the sriov-pf
required: true
type: string
+ example: __PF-PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -7227,7 +9344,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-pfs"
+ $ref: "#/getDefinitions/sriov-pfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -7236,11 +9353,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -7286,24 +9405,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -7328,21 +9451,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -7364,29 +9491,34 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -7411,26 +9543,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -7445,7 +9582,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -7454,26 +9591,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -7544,7 +9686,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -7561,32 +9706,100 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- CloudInfrastructure
@@ -7608,26 +9821,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -7654,29 +9872,34 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -7701,26 +9924,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -7735,7 +9963,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -7744,26 +9972,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -7834,7 +10067,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -7851,32 +10087,100 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- CloudInfrastructure
@@ -7898,26 +10202,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -7937,7 +10246,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -7946,21 +10255,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -8015,7 +10328,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -8032,27 +10348,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- CloudInfrastructure
@@ -8074,21 +10451,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -8108,7 +10489,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -8117,16 +10498,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -8187,24 +10571,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -8229,21 +10617,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -8258,7 +10650,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -8267,21 +10659,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -8345,7 +10741,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -8362,27 +10761,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- CloudInfrastructure
@@ -8404,21 +10864,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -8438,7 +10902,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -8447,16 +10911,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -8517,19 +10984,22 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -8554,16 +11024,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -8585,24 +11058,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -8627,21 +11104,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -8656,7 +11137,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -8665,21 +11146,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -8739,7 +11224,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -8756,27 +11244,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- CloudInfrastructure
@@ -8798,21 +11347,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -8839,24 +11392,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -8881,21 +11438,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -8910,7 +11471,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -8919,21 +11480,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -8993,7 +11558,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -9010,27 +11578,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- CloudInfrastructure
@@ -9052,21 +11681,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -9086,7 +11719,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -9095,16 +11728,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -9148,7 +11784,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface
consumes:
- application/json
@@ -9165,22 +11804,76 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- CloudInfrastructure
@@ -9202,16 +11895,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -9231,7 +11927,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -9240,11 +11936,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -9283,7 +11981,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/p-interface"
+ $ref: "#/getDefinitions/p-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -9292,11 +11990,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -9325,7 +12025,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing p-interface
- description: create or update an existing p-interface
+ description: |
+ Create or update an existing p-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterface
consumes:
- application/json
@@ -9342,17 +12045,64 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: p-interface object that needs to be created or updated
+ description: p-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverPInterfacesPInterface.json)
required: true
schema:
$ref: "#/definitions/p-interface"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing p-interface
+ description: |
+ Update an existing p-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: p-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/p-interface"
delete:
tags:
- CloudInfrastructure
@@ -9374,11 +12124,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -9398,7 +12150,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/p-interfaces"
+ $ref: "#/getDefinitions/p-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -9407,6 +12159,7 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -9447,14 +12200,16 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -9479,11 +12234,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -9505,24 +12262,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -9547,21 +12308,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -9583,29 +12348,34 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -9630,26 +12400,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -9664,7 +12439,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -9673,26 +12448,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -9768,7 +12548,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -9785,32 +12568,100 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- CloudInfrastructure
@@ -9832,26 +12683,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -9878,29 +12734,34 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -9925,26 +12786,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -9959,7 +12825,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -9968,26 +12834,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -10063,7 +12934,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -10080,32 +12954,100 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- CloudInfrastructure
@@ -10127,26 +13069,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -10166,7 +13113,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -10175,21 +13122,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -10249,7 +13200,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -10266,27 +13220,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- CloudInfrastructure
@@ -10308,21 +13323,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -10342,7 +13361,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -10351,16 +13370,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -10426,24 +13448,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -10468,21 +13494,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -10497,7 +13527,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -10506,21 +13536,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -10589,7 +13623,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -10606,27 +13643,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- CloudInfrastructure
@@ -10648,21 +13746,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -10682,7 +13784,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -10691,16 +13793,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -10766,19 +13871,22 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -10803,16 +13911,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -10834,24 +13945,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -10876,21 +13991,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -10905,7 +14024,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -10914,21 +14033,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -10993,7 +14116,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -11010,27 +14136,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- CloudInfrastructure
@@ -11052,21 +14239,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -11093,24 +14284,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -11135,21 +14330,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -11164,7 +14363,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -11173,21 +14372,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -11252,7 +14455,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -11269,27 +14475,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- CloudInfrastructure
@@ -11311,21 +14578,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -11345,7 +14616,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -11354,16 +14625,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -11412,7 +14686,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface
consumes:
- application/json
@@ -11429,22 +14706,76 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- CloudInfrastructure
@@ -11466,16 +14797,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -11495,7 +14829,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -11504,11 +14838,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -11552,7 +14888,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interface"
+ $ref: "#/getDefinitions/lag-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -11561,11 +14897,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -11599,7 +14937,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing lag-interface
- description: create or update an existing lag-interface
+ description: |
+ Create or update an existing lag-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterface
consumes:
- application/json
@@ -11616,17 +14957,64 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: lag-interface object that needs to be created or updated
+ description: lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserverLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/lag-interface"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing lag-interface
+ description: |
+ Update an existing lag-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: lag-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/lag-interface"
delete:
tags:
- CloudInfrastructure
@@ -11648,11 +15036,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -11672,7 +15062,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interfaces"
+ $ref: "#/getDefinitions/lag-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -11681,6 +15071,7 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -11714,7 +15105,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/pserver"
+ $ref: "#/getDefinitions/pserver"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -11723,6 +15114,7 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -11746,7 +15138,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing pserver
- description: create or update an existing pserver
+ description: |
+ Create or update an existing pserver.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserver
consumes:
- application/json
@@ -11763,12 +15158,52 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: body
in: body
- description: pserver object that needs to be created or updated
+ description: pserver object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructurePserversPserver.json)
required: true
schema:
$ref: "#/definitions/pserver"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing pserver
+ description: |
+ Update an existing pserver
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserver
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: body
+ in: body
+ description: pserver object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/pserver"
delete:
tags:
- CloudInfrastructure
@@ -11790,6 +15225,7 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -11809,7 +15245,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/pservers"
+ $ref: "#/getDefinitions/pservers"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}/relationship-list/relationship:
@@ -11833,9 +15269,10 @@ paths:
description: Unique ID of the vdc
required: true
type: string
+ example: __VDC-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureVirtualDataCentersVirtualDataCenter.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -11860,6 +15297,7 @@ paths:
description: Unique ID of the vdc
required: true
type: string
+ example: __VDC-ID__
/cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}:
get:
tags:
@@ -11874,7 +15312,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/virtual-data-center"
+ $ref: "#/getDefinitions/virtual-data-center"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -11883,6 +15321,7 @@ paths:
description: Unique ID of the vdc
required: true
type: string
+ example: __VDC-ID__
- name: vdc-name
in: query
description: Name of the virtual data center
@@ -11892,7 +15331,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing virtual-data-center
- description: create or update an existing virtual-data-center
+ description: |
+ Create or update an existing virtual-data-center.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureVirtualDataCentersVirtualDataCenter
consumes:
- application/json
@@ -11909,18 +15351,30 @@ paths:
description: Unique ID of the vdc
required: true
type: string
+ example: __VDC-ID__
- name: body
in: body
- description: virtual-data-center object that needs to be created or updated
+ description: virtual-data-center object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/CloudInfrastructureVirtualDataCentersVirtualDataCenter.json)
required: true
schema:
$ref: "#/definitions/virtual-data-center"
- delete:
+ patch:
tags:
- CloudInfrastructure
- summary: delete an existing virtual-data-center
- description: delete an existing virtual-data-center
- operationId: deleteCloudInfrastructureVirtualDataCentersVirtualDataCenter
+ summary: update an existing virtual-data-center
+ description: |
+ Update an existing virtual-data-center
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureVirtualDataCentersVirtualDataCenter
consumes:
- application/json
- application/xml
@@ -11936,960 +15390,19 @@ paths:
description: Unique ID of the vdc
required: true
type: string
- - name: resource-version
- in: query
- description: resource-version for concurrency
- required: true
- type: string
- /cloud-infrastructure/virtual-data-centers:
- get:
- tags:
- - CloudInfrastructure
- summary: returns virtual-data-centers
- description: returns virtual-data-centers
- operationId: getCloudInfrastructureVirtualDataCenters
- produces:
- - application/json
- - application/xml
- responses:
- "200":
- description: successful operation
- schema:
- $ref: "#/definitions/virtual-data-centers"
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- /external-system/esr-ems-list/esr-ems/{ems-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}/relationship-list/relationship:
- put:
- tags:
- - ExternalSystem
- summary: see node definition for valid relationships
- operationId: createOrUpdateExternalSystemEsrEmsListEsrEmsEsrSystemInfoListEsrSystemInfoRelationshipListRelationship
- consumes:
- - application/json
- - application/xml
- produces:
- - application/json
- - application/xml
- responses:
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: ems-id
- in: path
- description: Unique ID of EMS.
- required: true
- type: string
- - name: esr-system-info-id
- in: path
- description: Unique ID of esr system info.
- required: true
- type: string
- - name: body
- in: body
- description: relationship object that needs to be created or updated
- required: true
- schema:
- $ref: "#/definitions/relationship"
- delete:
- tags:
- - ExternalSystem
- summary: delete an existing relationship
- description: delete an existing relationship
- operationId: deleteExternalSystemEsrEmsListEsrEmsEsrSystemInfoListEsrSystemInfoRelationshipListRelationship
- consumes:
- - application/json
- - application/xml
- produces:
- - application/json
- - application/xml
- responses:
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: ems-id
- in: path
- description: Unique ID of EMS.
- required: true
- type: string
- - name: esr-system-info-id
- in: path
- description: Unique ID of esr system info.
- required: true
- type: string
- /external-system/esr-ems-list/esr-ems/{ems-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}:
- get:
- tags:
- - ExternalSystem
- summary: returns esr-system-info
- description: returns esr-system-info
- operationId: getExternalSystemEsrEmsListEsrEmsEsrSystemInfoListEsrSystemInfo
- produces:
- - application/json
- - application/xml
- responses:
- "200":
- description: successful operation
- schema:
- $ref: "#/definitions/esr-system-info"
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: ems-id
- in: path
- description: Unique ID of EMS.
- required: true
- type: string
- - name: esr-system-info-id
- in: path
- description: Unique ID of esr system info.
- required: true
- type: string
- - name: system-name
- in: query
- description: name of external system.
- required: false
- type: string
- - name: system-type
- in: query
- description: it could be vim/vnfm/thirdparty-sdnc/ems-resource/ems-performance/ems-alarm.
- required: false
- type: string
- put:
- tags:
- - ExternalSystem
- summary: create or update an existing esr-system-info
- description: create or update an existing esr-system-info
- operationId: createOrUpdateExternalSystemEsrEmsListEsrEmsEsrSystemInfoListEsrSystemInfo
- consumes:
- - application/json
- - application/xml
- produces:
- - application/json
- - application/xml
- responses:
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: ems-id
- in: path
- description: Unique ID of EMS.
- required: true
- type: string
- - name: esr-system-info-id
- in: path
- description: Unique ID of esr system info.
- required: true
- type: string
+ example: __VDC-ID__
- name: body
in: body
- description: esr-system-info object that needs to be created or updated
+ description: virtual-data-center object that needs to be created or updated.
required: true
schema:
- $ref: "#/definitions/esr-system-info"
+ $ref: "#/patchDefinitions/virtual-data-center"
delete:
tags:
- - ExternalSystem
- summary: delete an existing esr-system-info
- description: delete an existing esr-system-info
- operationId: deleteExternalSystemEsrEmsListEsrEmsEsrSystemInfoListEsrSystemInfo
- consumes:
- - application/json
- - application/xml
- produces:
- - application/json
- - application/xml
- responses:
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: ems-id
- in: path
- description: Unique ID of EMS.
- required: true
- type: string
- - name: esr-system-info-id
- in: path
- description: Unique ID of esr system info.
- required: true
- type: string
- - name: resource-version
- in: query
- description: resource-version for concurrency
- required: true
- type: string
- /external-system/esr-ems-list/esr-ems/{ems-id}/esr-system-info-list:
- get:
- tags:
- - ExternalSystem
- summary: returns esr-system-info-list
- description: returns esr-system-info-list
- operationId: getExternalSystemEsrEmsListEsrEmsEsrSystemInfoList
- produces:
- - application/json
- - application/xml
- responses:
- "200":
- description: successful operation
- schema:
- $ref: "#/definitions/esr-system-info-list"
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: ems-id
- in: path
- description: Unique ID of EMS.
- required: true
- type: string
- /external-system/esr-ems-list/esr-ems/{ems-id}/relationship-list/relationship:
- put:
- tags:
- - ExternalSystem
- summary: see node definition for valid relationships
- operationId: createOrUpdateExternalSystemEsrEmsListEsrEmsRelationshipListRelationship
- consumes:
- - application/json
- - application/xml
- produces:
- - application/json
- - application/xml
- responses:
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: ems-id
- in: path
- description: Unique ID of EMS.
- required: true
- type: string
- - name: body
- in: body
- description: relationship object that needs to be created or updated
- required: true
- schema:
- $ref: "#/definitions/relationship"
- delete:
- tags:
- - ExternalSystem
- summary: delete an existing relationship
- description: delete an existing relationship
- operationId: deleteExternalSystemEsrEmsListEsrEmsRelationshipListRelationship
- consumes:
- - application/json
- - application/xml
- produces:
- - application/json
- - application/xml
- responses:
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: ems-id
- in: path
- description: Unique ID of EMS.
- required: true
- type: string
- /external-system/esr-ems-list/esr-ems/{ems-id}:
- get:
- tags:
- - ExternalSystem
- summary: returns esr-ems
- description: returns esr-ems
- operationId: getExternalSystemEsrEmsListEsrEms
- produces:
- - application/json
- - application/xml
- responses:
- "200":
- description: successful operation
- schema:
- $ref: "#/definitions/esr-ems"
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: ems-id
- in: path
- description: Unique ID of EMS.
- required: true
- type: string
- put:
- tags:
- - ExternalSystem
- summary: create or update an existing esr-ems
- description: create or update an existing esr-ems
- operationId: createOrUpdateExternalSystemEsrEmsListEsrEms
- consumes:
- - application/json
- - application/xml
- produces:
- - application/json
- - application/xml
- responses:
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: ems-id
- in: path
- description: Unique ID of EMS.
- required: true
- type: string
- - name: body
- in: body
- description: esr-ems object that needs to be created or updated
- required: true
- schema:
- $ref: "#/definitions/esr-ems"
- delete:
- tags:
- - ExternalSystem
- summary: delete an existing esr-ems
- description: delete an existing esr-ems
- operationId: deleteExternalSystemEsrEmsListEsrEms
- consumes:
- - application/json
- - application/xml
- produces:
- - application/json
- - application/xml
- responses:
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: ems-id
- in: path
- description: Unique ID of EMS.
- required: true
- type: string
- - name: resource-version
- in: query
- description: resource-version for concurrency
- required: true
- type: string
- /external-system/esr-ems-list:
- get:
- tags:
- - ExternalSystem
- summary: returns esr-ems-list
- description: returns esr-ems-list
- operationId: getExternalSystemEsrEmsList
- produces:
- - application/json
- - application/xml
- responses:
- "200":
- description: successful operation
- schema:
- $ref: "#/definitions/esr-ems-list"
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- /external-system/esr-vnfm-list/esr-vnfm/{vnfm-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}/relationship-list/relationship:
- put:
- tags:
- - ExternalSystem
- summary: see node definition for valid relationships
- operationId: createOrUpdateExternalSystemEsrVnfmListEsrVnfmEsrSystemInfoListEsrSystemInfoRelationshipListRelationship
- consumes:
- - application/json
- - application/xml
- produces:
- - application/json
- - application/xml
- responses:
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: vnfm-id
- in: path
- description: Unique ID of VNFM.
- required: true
- type: string
- - name: esr-system-info-id
- in: path
- description: Unique ID of esr system info.
- required: true
- type: string
- - name: body
- in: body
- description: relationship object that needs to be created or updated
- required: true
- schema:
- $ref: "#/definitions/relationship"
- delete:
- tags:
- - ExternalSystem
- summary: delete an existing relationship
- description: delete an existing relationship
- operationId: deleteExternalSystemEsrVnfmListEsrVnfmEsrSystemInfoListEsrSystemInfoRelationshipListRelationship
- consumes:
- - application/json
- - application/xml
- produces:
- - application/json
- - application/xml
- responses:
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: vnfm-id
- in: path
- description: Unique ID of VNFM.
- required: true
- type: string
- - name: esr-system-info-id
- in: path
- description: Unique ID of esr system info.
- required: true
- type: string
- /external-system/esr-vnfm-list/esr-vnfm/{vnfm-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}:
- get:
- tags:
- - ExternalSystem
- summary: returns esr-system-info
- description: returns esr-system-info
- operationId: getExternalSystemEsrVnfmListEsrVnfmEsrSystemInfoListEsrSystemInfo
- produces:
- - application/json
- - application/xml
- responses:
- "200":
- description: successful operation
- schema:
- $ref: "#/definitions/esr-system-info"
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: vnfm-id
- in: path
- description: Unique ID of VNFM.
- required: true
- type: string
- - name: esr-system-info-id
- in: path
- description: Unique ID of esr system info.
- required: true
- type: string
- - name: system-name
- in: query
- description: name of external system.
- required: false
- type: string
- - name: system-type
- in: query
- description: it could be vim/vnfm/thirdparty-sdnc/ems-resource/ems-performance/ems-alarm.
- required: false
- type: string
- put:
- tags:
- - ExternalSystem
- summary: create or update an existing esr-system-info
- description: create or update an existing esr-system-info
- operationId: createOrUpdateExternalSystemEsrVnfmListEsrVnfmEsrSystemInfoListEsrSystemInfo
- consumes:
- - application/json
- - application/xml
- produces:
- - application/json
- - application/xml
- responses:
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: vnfm-id
- in: path
- description: Unique ID of VNFM.
- required: true
- type: string
- - name: esr-system-info-id
- in: path
- description: Unique ID of esr system info.
- required: true
- type: string
- - name: body
- in: body
- description: esr-system-info object that needs to be created or updated
- required: true
- schema:
- $ref: "#/definitions/esr-system-info"
- delete:
- tags:
- - ExternalSystem
- summary: delete an existing esr-system-info
- description: delete an existing esr-system-info
- operationId: deleteExternalSystemEsrVnfmListEsrVnfmEsrSystemInfoListEsrSystemInfo
- consumes:
- - application/json
- - application/xml
- produces:
- - application/json
- - application/xml
- responses:
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: vnfm-id
- in: path
- description: Unique ID of VNFM.
- required: true
- type: string
- - name: esr-system-info-id
- in: path
- description: Unique ID of esr system info.
- required: true
- type: string
- - name: resource-version
- in: query
- description: resource-version for concurrency
- required: true
- type: string
- /external-system/esr-vnfm-list/esr-vnfm/{vnfm-id}/esr-system-info-list:
- get:
- tags:
- - ExternalSystem
- summary: returns esr-system-info-list
- description: returns esr-system-info-list
- operationId: getExternalSystemEsrVnfmListEsrVnfmEsrSystemInfoList
- produces:
- - application/json
- - application/xml
- responses:
- "200":
- description: successful operation
- schema:
- $ref: "#/definitions/esr-system-info-list"
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: vnfm-id
- in: path
- description: Unique ID of VNFM.
- required: true
- type: string
- /external-system/esr-vnfm-list/esr-vnfm/{vnfm-id}/relationship-list/relationship:
- put:
- tags:
- - ExternalSystem
- summary: see node definition for valid relationships
- operationId: createOrUpdateExternalSystemEsrVnfmListEsrVnfmRelationshipListRelationship
- consumes:
- - application/json
- - application/xml
- produces:
- - application/json
- - application/xml
- responses:
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: vnfm-id
- in: path
- description: Unique ID of VNFM.
- required: true
- type: string
- - name: body
- in: body
- description: relationship object that needs to be created or updated
- required: true
- schema:
- $ref: "#/definitions/relationship"
- delete:
- tags:
- - ExternalSystem
- summary: delete an existing relationship
- description: delete an existing relationship
- operationId: deleteExternalSystemEsrVnfmListEsrVnfmRelationshipListRelationship
- consumes:
- - application/json
- - application/xml
- produces:
- - application/json
- - application/xml
- responses:
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: vnfm-id
- in: path
- description: Unique ID of VNFM.
- required: true
- type: string
- /external-system/esr-vnfm-list/esr-vnfm/{vnfm-id}:
- get:
- tags:
- - ExternalSystem
- summary: returns esr-vnfm
- description: returns esr-vnfm
- operationId: getExternalSystemEsrVnfmListEsrVnfm
- produces:
- - application/json
- - application/xml
- responses:
- "200":
- description: successful operation
- schema:
- $ref: "#/definitions/esr-vnfm"
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: vnfm-id
- in: path
- description: Unique ID of VNFM.
- required: true
- type: string
- put:
- tags:
- - ExternalSystem
- summary: create or update an existing esr-vnfm
- description: create or update an existing esr-vnfm
- operationId: createOrUpdateExternalSystemEsrVnfmListEsrVnfm
- consumes:
- - application/json
- - application/xml
- produces:
- - application/json
- - application/xml
- responses:
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: vnfm-id
- in: path
- description: Unique ID of VNFM.
- required: true
- type: string
- - name: body
- in: body
- description: esr-vnfm object that needs to be created or updated
- required: true
- schema:
- $ref: "#/definitions/esr-vnfm"
- delete:
- tags:
- - ExternalSystem
- summary: delete an existing esr-vnfm
- description: delete an existing esr-vnfm
- operationId: deleteExternalSystemEsrVnfmListEsrVnfm
- consumes:
- - application/json
- - application/xml
- produces:
- - application/json
- - application/xml
- responses:
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: vnfm-id
- in: path
- description: Unique ID of VNFM.
- required: true
- type: string
- - name: resource-version
- in: query
- description: resource-version for concurrency
- required: true
- type: string
- /external-system/esr-vnfm-list:
- get:
- tags:
- - ExternalSystem
- summary: returns esr-vnfm-list
- description: returns esr-vnfm-list
- operationId: getExternalSystemEsrVnfmList
- produces:
- - application/json
- - application/xml
- responses:
- "200":
- description: successful operation
- schema:
- $ref: "#/definitions/esr-vnfm-list"
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- /external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/{thirdparty-sdnc-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}/relationship-list/relationship:
- put:
- tags:
- - ExternalSystem
- summary: see node definition for valid relationships
- operationId: createOrUpdateExternalSystemEsrThirdpartySdncListEsrThirdpartySdncEsrSystemInfoListEsrSystemInfoRelationshipListRelationship
- consumes:
- - application/json
- - application/xml
- produces:
- - application/json
- - application/xml
- responses:
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: thirdparty-sdnc-id
- in: path
- description: Unique ID of SDNC.
- required: true
- type: string
- - name: esr-system-info-id
- in: path
- description: Unique ID of esr system info.
- required: true
- type: string
- - name: body
- in: body
- description: relationship object that needs to be created or updated
- required: true
- schema:
- $ref: "#/definitions/relationship"
- delete:
- tags:
- - ExternalSystem
- summary: delete an existing relationship
- description: delete an existing relationship
- operationId: deleteExternalSystemEsrThirdpartySdncListEsrThirdpartySdncEsrSystemInfoListEsrSystemInfoRelationshipListRelationship
- consumes:
- - application/json
- - application/xml
- produces:
- - application/json
- - application/xml
- responses:
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: thirdparty-sdnc-id
- in: path
- description: Unique ID of SDNC.
- required: true
- type: string
- - name: esr-system-info-id
- in: path
- description: Unique ID of esr system info.
- required: true
- type: string
- /external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/{thirdparty-sdnc-id}/esr-system-info-list/esr-system-info/{esr-system-info-id}:
- get:
- tags:
- - ExternalSystem
- summary: returns esr-system-info
- description: returns esr-system-info
- operationId: getExternalSystemEsrThirdpartySdncListEsrThirdpartySdncEsrSystemInfoListEsrSystemInfo
- produces:
- - application/json
- - application/xml
- responses:
- "200":
- description: successful operation
- schema:
- $ref: "#/definitions/esr-system-info"
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: thirdparty-sdnc-id
- in: path
- description: Unique ID of SDNC.
- required: true
- type: string
- - name: esr-system-info-id
- in: path
- description: Unique ID of esr system info.
- required: true
- type: string
- - name: system-name
- in: query
- description: name of external system.
- required: false
- type: string
- - name: system-type
- in: query
- description: it could be vim/vnfm/thirdparty-sdnc/ems-resource/ems-performance/ems-alarm.
- required: false
- type: string
- put:
- tags:
- - ExternalSystem
- summary: create or update an existing esr-system-info
- description: create or update an existing esr-system-info
- operationId: createOrUpdateExternalSystemEsrThirdpartySdncListEsrThirdpartySdncEsrSystemInfoListEsrSystemInfo
- consumes:
- - application/json
- - application/xml
- produces:
- - application/json
- - application/xml
- responses:
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: thirdparty-sdnc-id
- in: path
- description: Unique ID of SDNC.
- required: true
- type: string
- - name: esr-system-info-id
- in: path
- description: Unique ID of esr system info.
- required: true
- type: string
- - name: body
- in: body
- description: esr-system-info object that needs to be created or updated
- required: true
- schema:
- $ref: "#/definitions/esr-system-info"
- delete:
- tags:
- - ExternalSystem
- summary: delete an existing esr-system-info
- description: delete an existing esr-system-info
- operationId: deleteExternalSystemEsrThirdpartySdncListEsrThirdpartySdncEsrSystemInfoListEsrSystemInfo
- consumes:
- - application/json
- - application/xml
- produces:
- - application/json
- - application/xml
- responses:
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: thirdparty-sdnc-id
- in: path
- description: Unique ID of SDNC.
- required: true
- type: string
- - name: esr-system-info-id
- in: path
- description: Unique ID of esr system info.
- required: true
- type: string
- - name: resource-version
- in: query
- description: resource-version for concurrency
- required: true
- type: string
- /external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/{thirdparty-sdnc-id}/esr-system-info-list:
- get:
- tags:
- - ExternalSystem
- summary: returns esr-system-info-list
- description: returns esr-system-info-list
- operationId: getExternalSystemEsrThirdpartySdncListEsrThirdpartySdncEsrSystemInfoList
- produces:
- - application/json
- - application/xml
- responses:
- "200":
- description: successful operation
- schema:
- $ref: "#/definitions/esr-system-info-list"
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: thirdparty-sdnc-id
- in: path
- description: Unique ID of SDNC.
- required: true
- type: string
- /external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/{thirdparty-sdnc-id}/relationship-list/relationship:
- put:
- tags:
- - ExternalSystem
- summary: see node definition for valid relationships
- operationId: createOrUpdateExternalSystemEsrThirdpartySdncListEsrThirdpartySdncRelationshipListRelationship
- consumes:
- - application/json
- - application/xml
- produces:
- - application/json
- - application/xml
- responses:
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: thirdparty-sdnc-id
- in: path
- description: Unique ID of SDNC.
- required: true
- type: string
- - name: body
- in: body
- description: relationship object that needs to be created or updated
- required: true
- schema:
- $ref: "#/definitions/relationship"
- delete:
- tags:
- - ExternalSystem
- summary: delete an existing relationship
- description: delete an existing relationship
- operationId: deleteExternalSystemEsrThirdpartySdncListEsrThirdpartySdncRelationshipListRelationship
- consumes:
- - application/json
- - application/xml
- produces:
- - application/json
- - application/xml
- responses:
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: thirdparty-sdnc-id
- in: path
- description: Unique ID of SDNC.
- required: true
- type: string
- /external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/{thirdparty-sdnc-id}:
- get:
- tags:
- - ExternalSystem
- summary: returns esr-thirdparty-sdnc
- description: returns esr-thirdparty-sdnc
- operationId: getExternalSystemEsrThirdpartySdncListEsrThirdpartySdnc
- produces:
- - application/json
- - application/xml
- responses:
- "200":
- description: successful operation
- schema:
- $ref: "#/definitions/esr-thirdparty-sdnc"
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: thirdparty-sdnc-id
- in: path
- description: Unique ID of SDNC.
- required: true
- type: string
- put:
- tags:
- - ExternalSystem
- summary: create or update an existing esr-thirdparty-sdnc
- description: create or update an existing esr-thirdparty-sdnc
- operationId: createOrUpdateExternalSystemEsrThirdpartySdncListEsrThirdpartySdnc
- consumes:
- - application/json
- - application/xml
- produces:
- - application/json
- - application/xml
- responses:
- "default":
- description: Response codes found in [response codes](https://wiki.onap.org/).
- parameters:
- - name: thirdparty-sdnc-id
- in: path
- description: Unique ID of SDNC.
- required: true
- type: string
- - name: body
- in: body
- description: esr-thirdparty-sdnc object that needs to be created or updated
- required: true
- schema:
- $ref: "#/definitions/esr-thirdparty-sdnc"
- delete:
- tags:
- - ExternalSystem
- summary: delete an existing esr-thirdparty-sdnc
- description: delete an existing esr-thirdparty-sdnc
- operationId: deleteExternalSystemEsrThirdpartySdncListEsrThirdpartySdnc
+ - CloudInfrastructure
+ summary: delete an existing virtual-data-center
+ description: delete an existing virtual-data-center
+ operationId: deleteCloudInfrastructureVirtualDataCentersVirtualDataCenter
consumes:
- application/json
- application/xml
@@ -12900,23 +15413,24 @@ paths:
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
- - name: thirdparty-sdnc-id
+ - name: vdc-id
in: path
- description: Unique ID of SDNC.
+ description: Unique ID of the vdc
required: true
type: string
+ example: __VDC-ID__
- name: resource-version
in: query
description: resource-version for concurrency
required: true
type: string
- /external-system/esr-thirdparty-sdnc-list:
+ /cloud-infrastructure/virtual-data-centers:
get:
tags:
- - ExternalSystem
- summary: returns esr-thirdparty-sdnc-list
- description: returns esr-thirdparty-sdnc-list
- operationId: getExternalSystemEsrThirdpartySdncList
+ - CloudInfrastructure
+ summary: returns virtual-data-centers
+ description: returns virtual-data-centers
+ operationId: getCloudInfrastructureVirtualDataCenters
produces:
- application/json
- application/xml
@@ -12924,7 +15438,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/esr-thirdparty-sdnc-list"
+ $ref: "#/getDefinitions/virtual-data-centers"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/business/connectors/connector/{resource-instance-id}/relationship-list/relationship:
@@ -12948,9 +15462,10 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessConnectorsConnector.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -12975,6 +15490,7 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
/business/connectors/connector/{resource-instance-id}/metadata/metadatum/{metaname}:
get:
tags:
@@ -12989,7 +15505,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadatum"
+ $ref: "#/getDefinitions/metadatum"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -12998,10 +15514,12 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: model-invariant-id
in: query
description: the ASDC model id for this resource or service model.
@@ -13026,7 +15544,10 @@ paths:
tags:
- Business
summary: create or update an existing metadatum
- description: create or update an existing metadatum
+ description: |
+ Create or update an existing metadatum.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessConnectorsConnectorMetadataMetadatum
consumes:
- application/json
@@ -13043,16 +15564,62 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: body
in: body
- description: metadatum object that needs to be created or updated
+ description: metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessConnectorsConnectorMetadataMetadatum.json)
required: true
schema:
$ref: "#/definitions/metadatum"
+ patch:
+ tags:
+ - Business
+ summary: update an existing metadatum
+ description: |
+ Update an existing metadatum
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessConnectorsConnectorMetadataMetadatum
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: resource-instance-id
+ in: path
+ description: Unique id of resource instance.
+ required: true
+ type: string
+ example: __RESOURCE-INSTANCE-ID__
+ - name: metaname
+ in: path
+ required: true
+ type: string
+ example: __METANAME__
+ - name: body
+ in: body
+ description: metadatum object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/metadatum"
delete:
tags:
- Business
@@ -13074,10 +15641,12 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -13097,7 +15666,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadata"
+ $ref: "#/getDefinitions/metadata"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -13106,6 +15675,7 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: model-invariant-id
in: query
description: the ASDC model id for this resource or service model.
@@ -13140,7 +15710,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/connector"
+ $ref: "#/getDefinitions/connector"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -13149,6 +15719,7 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: model-invariant-id
in: query
description: the ASDC model id for this resource or service model.
@@ -13173,7 +15744,10 @@ paths:
tags:
- Business
summary: create or update an existing connector
- description: create or update an existing connector
+ description: |
+ Create or update an existing connector.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessConnectorsConnector
consumes:
- application/json
@@ -13190,12 +15764,52 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: body
in: body
- description: connector object that needs to be created or updated
+ description: connector object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessConnectorsConnector.json)
required: true
schema:
$ref: "#/definitions/connector"
+ patch:
+ tags:
+ - Business
+ summary: update an existing connector
+ description: |
+ Update an existing connector
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessConnectorsConnector
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: resource-instance-id
+ in: path
+ description: Unique id of resource instance.
+ required: true
+ type: string
+ example: __RESOURCE-INSTANCE-ID__
+ - name: body
+ in: body
+ description: connector object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/connector"
delete:
tags:
- Business
@@ -13217,6 +15831,7 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -13236,7 +15851,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/connectors"
+ $ref: "#/getDefinitions/connectors"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/relationship-list/relationship:
@@ -13260,19 +15875,22 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -13297,16 +15915,19 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/metadata/metadatum/{metaname}:
get:
tags:
@@ -13321,7 +15942,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadatum"
+ $ref: "#/getDefinitions/metadatum"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -13330,20 +15951,24 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -13403,7 +16028,10 @@ paths:
tags:
- Business
summary: create or update an existing metadatum
- description: create or update an existing metadatum
+ description: |
+ Create or update an existing metadatum.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceMetadataMetadatum
consumes:
- application/json
@@ -13420,26 +16048,86 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: body
in: body
- description: metadatum object that needs to be created or updated
+ description: metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceMetadataMetadatum.json)
required: true
schema:
$ref: "#/definitions/metadatum"
+ patch:
+ tags:
+ - Business
+ summary: update an existing metadatum
+ description: |
+ Update an existing metadatum
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceMetadataMetadatum
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: global-customer-id
+ in: path
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ required: true
+ type: string
+ example: __GLOBAL-CUSTOMER-ID__
+ - name: service-type
+ in: path
+ description: Value defined by orchestration to identify this service across ECOMP.
+ required: true
+ type: string
+ example: __SERVICE-TYPE__
+ - name: service-instance-id
+ in: path
+ description: Uniquely identifies this instance of a service
+ required: true
+ type: string
+ example: __SERVICE-INSTANCE-ID__
+ - name: metaname
+ in: path
+ required: true
+ type: string
+ example: __METANAME__
+ - name: body
+ in: body
+ description: metadatum object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/metadatum"
delete:
tags:
- Business
@@ -13461,20 +16149,24 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -13494,7 +16186,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadata"
+ $ref: "#/getDefinitions/metadata"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -13503,16 +16195,19 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -13589,29 +16284,34 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResourceTunnelXconnectsTunnelXconnect.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -13636,26 +16336,31 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/allotted-resources/allotted-resource/{id}/tunnel-xconnects/tunnel-xconnect/{id}:
get:
tags:
@@ -13670,7 +16375,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/tunnel-xconnect"
+ $ref: "#/getDefinitions/tunnel-xconnect"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -13679,26 +16384,31 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -13778,7 +16488,10 @@ paths:
tags:
- Business
summary: create or update an existing tunnel-xconnect
- description: create or update an existing tunnel-xconnect
+ description: |
+ Create or update an existing tunnel-xconnect.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResourceTunnelXconnectsTunnelXconnect
consumes:
- application/json
@@ -13795,32 +16508,100 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: body
in: body
- description: tunnel-xconnect object that needs to be created or updated
+ description: tunnel-xconnect object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResourceTunnelXconnectsTunnelXconnect.json)
required: true
schema:
$ref: "#/definitions/tunnel-xconnect"
+ patch:
+ tags:
+ - Business
+ summary: update an existing tunnel-xconnect
+ description: |
+ Update an existing tunnel-xconnect
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResourceTunnelXconnectsTunnelXconnect
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: global-customer-id
+ in: path
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ required: true
+ type: string
+ example: __GLOBAL-CUSTOMER-ID__
+ - name: service-type
+ in: path
+ description: Value defined by orchestration to identify this service across ECOMP.
+ required: true
+ type: string
+ example: __SERVICE-TYPE__
+ - name: service-instance-id
+ in: path
+ description: Uniquely identifies this instance of a service
+ required: true
+ type: string
+ example: __SERVICE-INSTANCE-ID__
+ - name: id
+ in: path
+ description: Allotted Resource id UUID assigned to this instance.
+ required: true
+ type: string
+ example: __ID__
+ - name: id
+ in: path
+ description: Allotted Resource id UUID assigned to this instance.
+ required: true
+ type: string
+ example: __ID__
+ - name: body
+ in: body
+ description: tunnel-xconnect object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/tunnel-xconnect"
delete:
tags:
- Business
@@ -13842,26 +16623,31 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -13881,7 +16667,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/tunnel-xconnects"
+ $ref: "#/getDefinitions/tunnel-xconnects"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -13890,21 +16676,25 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -14001,24 +16791,28 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResource.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -14043,21 +16837,25 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/allotted-resources/allotted-resource/{id}:
get:
tags:
@@ -14072,7 +16870,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/allotted-resource"
+ $ref: "#/getDefinitions/allotted-resource"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14081,21 +16879,25 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -14175,7 +16977,10 @@ paths:
tags:
- Business
summary: create or update an existing allotted-resource
- description: create or update an existing allotted-resource
+ description: |
+ Create or update an existing allotted-resource.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResource
consumes:
- application/json
@@ -14192,27 +16997,88 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: body
in: body
- description: allotted-resource object that needs to be created or updated
+ description: allotted-resource object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResource.json)
required: true
schema:
$ref: "#/definitions/allotted-resource"
+ patch:
+ tags:
+ - Business
+ summary: update an existing allotted-resource
+ description: |
+ Update an existing allotted-resource
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResource
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: global-customer-id
+ in: path
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ required: true
+ type: string
+ example: __GLOBAL-CUSTOMER-ID__
+ - name: service-type
+ in: path
+ description: Value defined by orchestration to identify this service across ECOMP.
+ required: true
+ type: string
+ example: __SERVICE-TYPE__
+ - name: service-instance-id
+ in: path
+ description: Uniquely identifies this instance of a service
+ required: true
+ type: string
+ example: __SERVICE-INSTANCE-ID__
+ - name: id
+ in: path
+ description: Allotted Resource id UUID assigned to this instance.
+ required: true
+ type: string
+ example: __ID__
+ - name: body
+ in: body
+ description: allotted-resource object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/allotted-resource"
delete:
tags:
- Business
@@ -14234,21 +17100,25 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -14268,7 +17138,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/allotted-resources"
+ $ref: "#/getDefinitions/allotted-resources"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14277,16 +17147,19 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -14356,7 +17229,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/service-instance"
+ $ref: "#/getDefinitions/service-instance"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14365,16 +17238,19 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -14434,7 +17310,10 @@ paths:
tags:
- Business
summary: create or update an existing service-instance
- description: create or update an existing service-instance
+ description: |
+ Create or update an existing service-instance.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance
consumes:
- application/json
@@ -14451,22 +17330,76 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: body
in: body
- description: service-instance object that needs to be created or updated
+ description: service-instance object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance.json)
required: true
schema:
$ref: "#/definitions/service-instance"
+ patch:
+ tags:
+ - Business
+ summary: update an existing service-instance
+ description: |
+ Update an existing service-instance
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: global-customer-id
+ in: path
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ required: true
+ type: string
+ example: __GLOBAL-CUSTOMER-ID__
+ - name: service-type
+ in: path
+ description: Value defined by orchestration to identify this service across ECOMP.
+ required: true
+ type: string
+ example: __SERVICE-TYPE__
+ - name: service-instance-id
+ in: path
+ description: Uniquely identifies this instance of a service
+ required: true
+ type: string
+ example: __SERVICE-INSTANCE-ID__
+ - name: body
+ in: body
+ description: service-instance object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/service-instance"
delete:
tags:
- Business
@@ -14488,16 +17421,19 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -14517,7 +17453,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/service-instances"
+ $ref: "#/getDefinitions/service-instances"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14526,11 +17462,13 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -14562,14 +17500,16 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessCustomersCustomerServiceSubscriptionsServiceSubscription.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -14594,11 +17534,13 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}:
get:
tags:
@@ -14613,7 +17555,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/service-subscription"
+ $ref: "#/getDefinitions/service-subscription"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14622,11 +17564,13 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -14641,7 +17585,10 @@ paths:
tags:
- Business
summary: create or update an existing service-subscription
- description: create or update an existing service-subscription
+ description: |
+ Create or update an existing service-subscription.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscription
consumes:
- application/json
@@ -14658,17 +17605,64 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: body
in: body
- description: service-subscription object that needs to be created or updated
+ description: service-subscription object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessCustomersCustomerServiceSubscriptionsServiceSubscription.json)
required: true
schema:
$ref: "#/definitions/service-subscription"
+ patch:
+ tags:
+ - Business
+ summary: update an existing service-subscription
+ description: |
+ Update an existing service-subscription
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscription
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: global-customer-id
+ in: path
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ required: true
+ type: string
+ example: __GLOBAL-CUSTOMER-ID__
+ - name: service-type
+ in: path
+ description: Value defined by orchestration to identify this service across ECOMP.
+ required: true
+ type: string
+ example: __SERVICE-TYPE__
+ - name: body
+ in: body
+ description: service-subscription object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/service-subscription"
delete:
tags:
- Business
@@ -14690,11 +17684,13 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -14714,7 +17710,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/service-subscriptions"
+ $ref: "#/getDefinitions/service-subscriptions"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14723,6 +17719,7 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -14754,9 +17751,10 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessCustomersCustomer.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -14781,6 +17779,7 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
/business/customers/customer/{global-customer-id}:
get:
tags:
@@ -14795,7 +17794,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/customer"
+ $ref: "#/getDefinitions/customer"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14804,6 +17803,7 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -14818,7 +17818,10 @@ paths:
tags:
- Business
summary: create or update an existing customer
- description: create or update an existing customer
+ description: |
+ Create or update an existing customer.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessCustomersCustomer
consumes:
- application/json
@@ -14835,12 +17838,52 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: body
in: body
- description: customer object that needs to be created or updated
+ description: customer object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessCustomersCustomer.json)
required: true
schema:
$ref: "#/definitions/customer"
+ patch:
+ tags:
+ - Business
+ summary: update an existing customer
+ description: |
+ Update an existing customer
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessCustomersCustomer
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: global-customer-id
+ in: path
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ required: true
+ type: string
+ example: __GLOBAL-CUSTOMER-ID__
+ - name: body
+ in: body
+ description: customer object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/customer"
delete:
tags:
- Business
@@ -14862,6 +17905,7 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -14881,7 +17925,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/customers"
+ $ref: "#/getDefinitions/customers"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/business/lines-of-business/line-of-business/{line-of-business-name}/relationship-list/relationship:
@@ -14905,9 +17949,10 @@ paths:
description: Name of the line-of-business (product)
required: true
type: string
+ example: __LINE-OF-BUSINESS-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessLinesOfBusinessLineOfBusiness.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -14932,6 +17977,7 @@ paths:
description: Name of the line-of-business (product)
required: true
type: string
+ example: __LINE-OF-BUSINESS-NAME__
/business/lines-of-business/line-of-business/{line-of-business-name}:
get:
tags:
@@ -14946,7 +17992,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/line-of-business"
+ $ref: "#/getDefinitions/line-of-business"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14955,11 +18001,15 @@ paths:
description: Name of the line-of-business (product)
required: true
type: string
+ example: __LINE-OF-BUSINESS-NAME__
put:
tags:
- Business
summary: create or update an existing line-of-business
- description: create or update an existing line-of-business
+ description: |
+ Create or update an existing line-of-business.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessLinesOfBusinessLineOfBusiness
consumes:
- application/json
@@ -14976,12 +18026,52 @@ paths:
description: Name of the line-of-business (product)
required: true
type: string
+ example: __LINE-OF-BUSINESS-NAME__
- name: body
in: body
- description: line-of-business object that needs to be created or updated
+ description: line-of-business object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessLinesOfBusinessLineOfBusiness.json)
required: true
schema:
$ref: "#/definitions/line-of-business"
+ patch:
+ tags:
+ - Business
+ summary: update an existing line-of-business
+ description: |
+ Update an existing line-of-business
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessLinesOfBusinessLineOfBusiness
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: line-of-business-name
+ in: path
+ description: Name of the line-of-business (product)
+ required: true
+ type: string
+ example: __LINE-OF-BUSINESS-NAME__
+ - name: body
+ in: body
+ description: line-of-business object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/line-of-business"
delete:
tags:
- Business
@@ -15003,6 +18093,7 @@ paths:
description: Name of the line-of-business (product)
required: true
type: string
+ example: __LINE-OF-BUSINESS-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -15022,7 +18113,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lines-of-business"
+ $ref: "#/getDefinitions/lines-of-business"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/business/owning-entities/owning-entity/{owning-entity-id}/relationship-list/relationship:
@@ -15046,9 +18137,10 @@ paths:
description: UUID of an owning entity
required: true
type: string
+ example: __OWNING-ENTITY-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessOwningEntitiesOwningEntity.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -15073,6 +18165,7 @@ paths:
description: UUID of an owning entity
required: true
type: string
+ example: __OWNING-ENTITY-ID__
/business/owning-entities/owning-entity/{owning-entity-id}:
get:
tags:
@@ -15087,7 +18180,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/owning-entity"
+ $ref: "#/getDefinitions/owning-entity"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -15096,11 +18189,15 @@ paths:
description: UUID of an owning entity
required: true
type: string
+ example: __OWNING-ENTITY-ID__
put:
tags:
- Business
summary: create or update an existing owning-entity
- description: create or update an existing owning-entity
+ description: |
+ Create or update an existing owning-entity.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessOwningEntitiesOwningEntity
consumes:
- application/json
@@ -15117,12 +18214,52 @@ paths:
description: UUID of an owning entity
required: true
type: string
+ example: __OWNING-ENTITY-ID__
- name: body
in: body
- description: owning-entity object that needs to be created or updated
+ description: owning-entity object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessOwningEntitiesOwningEntity.json)
required: true
schema:
$ref: "#/definitions/owning-entity"
+ patch:
+ tags:
+ - Business
+ summary: update an existing owning-entity
+ description: |
+ Update an existing owning-entity
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessOwningEntitiesOwningEntity
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: owning-entity-id
+ in: path
+ description: UUID of an owning entity
+ required: true
+ type: string
+ example: __OWNING-ENTITY-ID__
+ - name: body
+ in: body
+ description: owning-entity object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/owning-entity"
delete:
tags:
- Business
@@ -15144,6 +18281,7 @@ paths:
description: UUID of an owning entity
required: true
type: string
+ example: __OWNING-ENTITY-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -15163,7 +18301,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/owning-entities"
+ $ref: "#/getDefinitions/owning-entities"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/business/platforms/platform/{platform-name}/relationship-list/relationship:
@@ -15187,9 +18325,10 @@ paths:
description: Name of the platform
required: true
type: string
+ example: __PLATFORM-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessPlatformsPlatform.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -15214,6 +18353,7 @@ paths:
description: Name of the platform
required: true
type: string
+ example: __PLATFORM-NAME__
/business/platforms/platform/{platform-name}:
get:
tags:
@@ -15228,7 +18368,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/platform"
+ $ref: "#/getDefinitions/platform"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -15237,11 +18377,15 @@ paths:
description: Name of the platform
required: true
type: string
+ example: __PLATFORM-NAME__
put:
tags:
- Business
summary: create or update an existing platform
- description: create or update an existing platform
+ description: |
+ Create or update an existing platform.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessPlatformsPlatform
consumes:
- application/json
@@ -15258,12 +18402,52 @@ paths:
description: Name of the platform
required: true
type: string
+ example: __PLATFORM-NAME__
- name: body
in: body
- description: platform object that needs to be created or updated
+ description: platform object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessPlatformsPlatform.json)
required: true
schema:
$ref: "#/definitions/platform"
+ patch:
+ tags:
+ - Business
+ summary: update an existing platform
+ description: |
+ Update an existing platform
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessPlatformsPlatform
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: platform-name
+ in: path
+ description: Name of the platform
+ required: true
+ type: string
+ example: __PLATFORM-NAME__
+ - name: body
+ in: body
+ description: platform object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/platform"
delete:
tags:
- Business
@@ -15285,6 +18469,7 @@ paths:
description: Name of the platform
required: true
type: string
+ example: __PLATFORM-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -15304,7 +18489,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/platforms"
+ $ref: "#/getDefinitions/platforms"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/business/projects/project/{project-name}/relationship-list/relationship:
@@ -15328,9 +18513,10 @@ paths:
description: Name of the project deploying a service
required: true
type: string
+ example: __PROJECT-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessProjectsProject.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -15355,6 +18541,7 @@ paths:
description: Name of the project deploying a service
required: true
type: string
+ example: __PROJECT-NAME__
/business/projects/project/{project-name}:
get:
tags:
@@ -15369,7 +18556,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/project"
+ $ref: "#/getDefinitions/project"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -15378,11 +18565,15 @@ paths:
description: Name of the project deploying a service
required: true
type: string
+ example: __PROJECT-NAME__
put:
tags:
- Business
summary: create or update an existing project
- description: create or update an existing project
+ description: |
+ Create or update an existing project.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessProjectsProject
consumes:
- application/json
@@ -15399,12 +18590,52 @@ paths:
description: Name of the project deploying a service
required: true
type: string
+ example: __PROJECT-NAME__
- name: body
in: body
- description: project object that needs to be created or updated
+ description: project object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/BusinessProjectsProject.json)
required: true
schema:
$ref: "#/definitions/project"
+ patch:
+ tags:
+ - Business
+ summary: update an existing project
+ description: |
+ Update an existing project
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessProjectsProject
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: project-name
+ in: path
+ description: Name of the project deploying a service
+ required: true
+ type: string
+ example: __PROJECT-NAME__
+ - name: body
+ in: body
+ description: project object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/project"
delete:
tags:
- Business
@@ -15426,6 +18657,7 @@ paths:
description: Name of the project deploying a service
required: true
type: string
+ example: __PROJECT-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -15445,7 +18677,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/projects"
+ $ref: "#/getDefinitions/projects"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/service-design-and-creation/vnf-images/vnf-image/{vnf-image-uuid}/relationship-list/relationship:
@@ -15469,9 +18701,10 @@ paths:
description: Unique ID of this asset
required: true
type: string
+ example: __VNF-IMAGE-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationVnfImagesVnfImage.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -15496,6 +18729,7 @@ paths:
description: Unique ID of this asset
required: true
type: string
+ example: __VNF-IMAGE-UUID__
/service-design-and-creation/vnf-images/vnf-image/{vnf-image-uuid}:
get:
tags:
@@ -15510,7 +18744,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vnf-image"
+ $ref: "#/getDefinitions/vnf-image"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -15519,6 +18753,7 @@ paths:
description: Unique ID of this asset
required: true
type: string
+ example: __VNF-IMAGE-UUID__
- name: application
in: query
description: The application that the image instantiates.
@@ -15538,7 +18773,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing vnf-image
- description: create or update an existing vnf-image
+ description: |
+ Create or update an existing vnf-image.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationVnfImagesVnfImage
consumes:
- application/json
@@ -15555,12 +18793,52 @@ paths:
description: Unique ID of this asset
required: true
type: string
+ example: __VNF-IMAGE-UUID__
- name: body
in: body
- description: vnf-image object that needs to be created or updated
+ description: vnf-image object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationVnfImagesVnfImage.json)
required: true
schema:
$ref: "#/definitions/vnf-image"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing vnf-image
+ description: |
+ Update an existing vnf-image
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationVnfImagesVnfImage
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-image-uuid
+ in: path
+ description: Unique ID of this asset
+ required: true
+ type: string
+ example: __VNF-IMAGE-UUID__
+ - name: body
+ in: body
+ description: vnf-image object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vnf-image"
delete:
tags:
- ServiceDesignAndCreation
@@ -15582,6 +18860,7 @@ paths:
description: Unique ID of this asset
required: true
type: string
+ example: __VNF-IMAGE-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -15601,7 +18880,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vnf-images"
+ $ref: "#/getDefinitions/vnf-images"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/service-design-and-creation/services/service/{service-id}/relationship-list/relationship:
@@ -15625,9 +18904,10 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationServicesService.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -15652,6 +18932,7 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-ID__
/service-design-and-creation/services/service/{service-id}:
get:
tags:
@@ -15666,7 +18947,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/service"
+ $ref: "#/getDefinitions/service"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -15675,6 +18956,7 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-ID__
- name: service-description
in: query
description: Description of the service
@@ -15684,7 +18966,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing service
- description: create or update an existing service
+ description: |
+ Create or update an existing service.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationServicesService
consumes:
- application/json
@@ -15701,12 +18986,52 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-ID__
- name: body
in: body
- description: service object that needs to be created or updated
+ description: service object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationServicesService.json)
required: true
schema:
$ref: "#/definitions/service"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing service
+ description: |
+ Update an existing service
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationServicesService
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: service-id
+ in: path
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ required: true
+ type: string
+ example: __SERVICE-ID__
+ - name: body
+ in: body
+ description: service object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/service"
delete:
tags:
- ServiceDesignAndCreation
@@ -15728,6 +19053,7 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -15747,7 +19073,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/services"
+ $ref: "#/getDefinitions/services"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/service-design-and-creation/service-capabilities/service-capability/{service-type}/{vnf-type}/relationship-list/relationship:
@@ -15771,14 +19097,16 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: vnf-type
in: path
description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
required: true
type: string
+ example: __VNF-TYPE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationServiceCapabilitiesServiceCapability.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -15803,11 +19131,13 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: vnf-type
in: path
description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
required: true
type: string
+ example: __VNF-TYPE__
/service-design-and-creation/service-capabilities/service-capability/{service-type}/{vnf-type}:
get:
tags:
@@ -15822,7 +19152,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/service-capability"
+ $ref: "#/getDefinitions/service-capability"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -15831,16 +19161,21 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: vnf-type
in: path
description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
required: true
type: string
+ example: __VNF-TYPE__
put:
tags:
- ServiceDesignAndCreation
summary: create or update an existing service-capability
- description: create or update an existing service-capability
+ description: |
+ Create or update an existing service-capability.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationServiceCapabilitiesServiceCapability
consumes:
- application/json
@@ -15857,17 +19192,64 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: vnf-type
in: path
description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
required: true
type: string
+ example: __VNF-TYPE__
- name: body
in: body
- description: service-capability object that needs to be created or updated
+ description: service-capability object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationServiceCapabilitiesServiceCapability.json)
required: true
schema:
$ref: "#/definitions/service-capability"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing service-capability
+ description: |
+ Update an existing service-capability
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationServiceCapabilitiesServiceCapability
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: service-type
+ in: path
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ required: true
+ type: string
+ example: __SERVICE-TYPE__
+ - name: vnf-type
+ in: path
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ required: true
+ type: string
+ example: __VNF-TYPE__
+ - name: body
+ in: body
+ description: service-capability object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/service-capability"
delete:
tags:
- ServiceDesignAndCreation
@@ -15889,11 +19271,13 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: vnf-type
in: path
description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
required: true
type: string
+ example: __VNF-TYPE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -15913,7 +19297,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/service-capabilities"
+ $ref: "#/getDefinitions/service-capabilities"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}/element-choice-sets/element-choice-set/{element-choice-set-uuid}/relationship-list/relationship:
@@ -15937,30 +19321,36 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: element-choice-set-uuid
in: path
required: true
type: string
+ example: __ELEMENT-CHOICE-SET-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -15985,27 +19375,33 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: element-choice-set-uuid
in: path
required: true
type: string
+ example: __ELEMENT-CHOICE-SET-UUID__
/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}/element-choice-sets/element-choice-set/{element-choice-set-uuid}:
get:
tags:
@@ -16020,7 +19416,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/element-choice-set"
+ $ref: "#/getDefinitions/element-choice-set"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -16029,27 +19425,33 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: element-choice-set-uuid
in: path
required: true
type: string
+ example: __ELEMENT-CHOICE-SET-UUID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -16069,7 +19471,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing element-choice-set
- description: create or update an existing element-choice-set
+ description: |
+ Create or update an existing element-choice-set.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet
consumes:
- application/json
@@ -16086,33 +19491,104 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: element-choice-set-uuid
in: path
required: true
type: string
+ example: __ELEMENT-CHOICE-SET-UUID__
- name: body
in: body
- description: element-choice-set object that needs to be created or updated
+ description: element-choice-set object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet.json)
required: true
schema:
$ref: "#/definitions/element-choice-set"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing element-choice-set
+ description: |
+ Update an existing element-choice-set
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: model-invariant-id
+ in: path
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-INVARIANT-ID__
+ - name: model-version-id
+ in: path
+ description: Unique identifier corresponding to one version of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-VERSION-ID__
+ - name: model-element-uuid
+ in: path
+ required: true
+ type: string
+ example: __MODEL-ELEMENT-UUID__
+ - name: model-constraint-uuid
+ in: path
+ required: true
+ type: string
+ example: __MODEL-CONSTRAINT-UUID__
+ - name: constrained-element-set-uuid
+ in: path
+ required: true
+ type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
+ - name: element-choice-set-uuid
+ in: path
+ required: true
+ type: string
+ example: __ELEMENT-CHOICE-SET-UUID__
+ - name: body
+ in: body
+ description: element-choice-set object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/element-choice-set"
delete:
tags:
- ServiceDesignAndCreation
@@ -16134,27 +19610,33 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: element-choice-set-uuid
in: path
required: true
type: string
+ example: __ELEMENT-CHOICE-SET-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -16174,7 +19656,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/element-choice-sets"
+ $ref: "#/getDefinitions/element-choice-sets"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -16183,23 +19665,28 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -16236,26 +19723,31 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -16280,23 +19772,28 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}:
get:
tags:
@@ -16311,7 +19808,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/constrained-element-set"
+ $ref: "#/getDefinitions/constrained-element-set"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -16320,23 +19817,28 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -16356,7 +19858,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing constrained-element-set
- description: create or update an existing constrained-element-set
+ description: |
+ Create or update an existing constrained-element-set.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet
consumes:
- application/json
@@ -16373,29 +19878,94 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: body
in: body
- description: constrained-element-set object that needs to be created or updated
+ description: constrained-element-set object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet.json)
required: true
schema:
$ref: "#/definitions/constrained-element-set"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing constrained-element-set
+ description: |
+ Update an existing constrained-element-set
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: model-invariant-id
+ in: path
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-INVARIANT-ID__
+ - name: model-version-id
+ in: path
+ description: Unique identifier corresponding to one version of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-VERSION-ID__
+ - name: model-element-uuid
+ in: path
+ required: true
+ type: string
+ example: __MODEL-ELEMENT-UUID__
+ - name: model-constraint-uuid
+ in: path
+ required: true
+ type: string
+ example: __MODEL-CONSTRAINT-UUID__
+ - name: constrained-element-set-uuid
+ in: path
+ required: true
+ type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
+ - name: body
+ in: body
+ description: constrained-element-set object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/constrained-element-set"
delete:
tags:
- ServiceDesignAndCreation
@@ -16417,23 +19987,28 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -16453,7 +20028,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/constrained-element-sets"
+ $ref: "#/getDefinitions/constrained-element-sets"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -16462,19 +20037,23 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -16504,7 +20083,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/model-constraint"
+ $ref: "#/getDefinitions/model-constraint"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -16513,19 +20092,23 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -16545,7 +20128,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing model-constraint
- description: create or update an existing model-constraint
+ description: |
+ Create or update an existing model-constraint.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraint
consumes:
- application/json
@@ -16562,25 +20148,84 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: body
in: body
- description: model-constraint object that needs to be created or updated
+ description: model-constraint object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraint.json)
required: true
schema:
$ref: "#/definitions/model-constraint"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing model-constraint
+ description: |
+ Update an existing model-constraint
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraint
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: model-invariant-id
+ in: path
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-INVARIANT-ID__
+ - name: model-version-id
+ in: path
+ description: Unique identifier corresponding to one version of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-VERSION-ID__
+ - name: model-element-uuid
+ in: path
+ required: true
+ type: string
+ example: __MODEL-ELEMENT-UUID__
+ - name: model-constraint-uuid
+ in: path
+ required: true
+ type: string
+ example: __MODEL-CONSTRAINT-UUID__
+ - name: body
+ in: body
+ description: model-constraint object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/model-constraint"
delete:
tags:
- ServiceDesignAndCreation
@@ -16602,19 +20247,23 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -16634,7 +20283,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/model-constraints"
+ $ref: "#/getDefinitions/model-constraints"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -16643,15 +20292,18 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -16688,18 +20340,21 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElement.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -16724,15 +20379,18 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}:
get:
tags:
@@ -16747,7 +20405,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/model-element"
+ $ref: "#/getDefinitions/model-element"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -16756,15 +20414,18 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -16784,7 +20445,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing model-element
- description: create or update an existing model-element
+ description: |
+ Create or update an existing model-element.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElement
consumes:
- application/json
@@ -16801,21 +20465,74 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: body
in: body
- description: model-element object that needs to be created or updated
+ description: model-element object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElement.json)
required: true
schema:
$ref: "#/definitions/model-element"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing model-element
+ description: |
+ Update an existing model-element
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElement
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: model-invariant-id
+ in: path
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-INVARIANT-ID__
+ - name: model-version-id
+ in: path
+ description: Unique identifier corresponding to one version of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-VERSION-ID__
+ - name: model-element-uuid
+ in: path
+ required: true
+ type: string
+ example: __MODEL-ELEMENT-UUID__
+ - name: body
+ in: body
+ description: model-element object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/model-element"
delete:
tags:
- ServiceDesignAndCreation
@@ -16837,15 +20554,18 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -16865,7 +20585,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/model-elements"
+ $ref: "#/getDefinitions/model-elements"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -16874,11 +20594,13 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -16908,7 +20630,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadatum"
+ $ref: "#/getDefinitions/metadatum"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -16917,15 +20639,18 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -16945,7 +20670,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing metadatum
- description: create or update an existing metadatum
+ description: |
+ Create or update an existing metadatum.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationModelsModelModelVersModelVerMetadataMetadatum
consumes:
- application/json
@@ -16962,21 +20690,74 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: body
in: body
- description: metadatum object that needs to be created or updated
+ description: metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationModelsModelModelVersModelVerMetadataMetadatum.json)
required: true
schema:
$ref: "#/definitions/metadatum"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing metadatum
+ description: |
+ Update an existing metadatum
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationModelsModelModelVersModelVerMetadataMetadatum
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: model-invariant-id
+ in: path
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-INVARIANT-ID__
+ - name: model-version-id
+ in: path
+ description: Unique identifier corresponding to one version of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-VERSION-ID__
+ - name: metaname
+ in: path
+ required: true
+ type: string
+ example: __METANAME__
+ - name: body
+ in: body
+ description: metadatum object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/metadatum"
delete:
tags:
- ServiceDesignAndCreation
@@ -16998,15 +20779,18 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -17026,7 +20810,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadata"
+ $ref: "#/getDefinitions/metadata"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -17035,11 +20819,13 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -17076,14 +20862,16 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationModelsModelModelVersModelVer.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -17108,11 +20896,13 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}:
get:
tags:
@@ -17127,7 +20917,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/model-ver"
+ $ref: "#/getDefinitions/model-ver"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -17136,11 +20926,13 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -17160,7 +20952,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing model-ver
- description: create or update an existing model-ver
+ description: |
+ Create or update an existing model-ver.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationModelsModelModelVersModelVer
consumes:
- application/json
@@ -17177,17 +20972,64 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: body
in: body
- description: model-ver object that needs to be created or updated
+ description: model-ver object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationModelsModelModelVersModelVer.json)
required: true
schema:
$ref: "#/definitions/model-ver"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing model-ver
+ description: |
+ Update an existing model-ver
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationModelsModelModelVersModelVer
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: model-invariant-id
+ in: path
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-INVARIANT-ID__
+ - name: model-version-id
+ in: path
+ description: Unique identifier corresponding to one version of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-VERSION-ID__
+ - name: body
+ in: body
+ description: model-ver object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/model-ver"
delete:
tags:
- ServiceDesignAndCreation
@@ -17209,11 +21051,13 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -17233,7 +21077,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/model-vers"
+ $ref: "#/getDefinitions/model-vers"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -17242,6 +21086,7 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -17268,9 +21113,10 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationModelsModel.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -17295,6 +21141,7 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
/service-design-and-creation/models/model/{model-invariant-id}:
get:
tags:
@@ -17309,7 +21156,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/model"
+ $ref: "#/getDefinitions/model"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -17318,6 +21165,7 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -17327,7 +21175,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing model
- description: create or update an existing model
+ description: |
+ Create or update an existing model.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationModelsModel
consumes:
- application/json
@@ -17344,12 +21195,52 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: body
in: body
- description: model object that needs to be created or updated
+ description: model object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationModelsModel.json)
required: true
schema:
$ref: "#/definitions/model"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing model
+ description: |
+ Update an existing model
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationModelsModel
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: model-invariant-id
+ in: path
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-INVARIANT-ID__
+ - name: body
+ in: body
+ description: model object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/model"
delete:
tags:
- ServiceDesignAndCreation
@@ -17371,6 +21262,7 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -17390,7 +21282,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/models"
+ $ref: "#/getDefinitions/models"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/related-lookups/related-lookup/{related-lookup-uuid}/relationship-list/relationship:
@@ -17413,17 +21305,20 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: related-lookup-uuid
in: path
required: true
type: string
+ example: __RELATED-LOOKUP-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -17447,14 +21342,17 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: related-lookup-uuid
in: path
required: true
type: string
+ example: __RELATED-LOOKUP-UUID__
/service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/related-lookups/related-lookup/{related-lookup-uuid}:
get:
tags:
@@ -17469,7 +21367,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/related-lookup"
+ $ref: "#/getDefinitions/related-lookup"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -17477,14 +21375,17 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: related-lookup-uuid
in: path
required: true
type: string
+ example: __RELATED-LOOKUP-UUID__
- name: named-query-name
in: query
required: false
@@ -17493,7 +21394,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing related-lookup
- description: create or update an existing related-lookup
+ description: |
+ Create or update an existing related-lookup.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup
consumes:
- application/json
@@ -17509,20 +21413,71 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: related-lookup-uuid
in: path
required: true
type: string
+ example: __RELATED-LOOKUP-UUID__
- name: body
in: body
- description: related-lookup object that needs to be created or updated
+ description: related-lookup object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup.json)
required: true
schema:
$ref: "#/definitions/related-lookup"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing related-lookup
+ description: |
+ Update an existing related-lookup
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: named-query-uuid
+ in: path
+ required: true
+ type: string
+ example: __NAMED-QUERY-UUID__
+ - name: named-query-element-uuid
+ in: path
+ required: true
+ type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
+ - name: related-lookup-uuid
+ in: path
+ required: true
+ type: string
+ example: __RELATED-LOOKUP-UUID__
+ - name: body
+ in: body
+ description: related-lookup object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/related-lookup"
delete:
tags:
- ServiceDesignAndCreation
@@ -17543,14 +21498,17 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: related-lookup-uuid
in: path
required: true
type: string
+ example: __RELATED-LOOKUP-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -17570,7 +21528,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/related-lookups"
+ $ref: "#/getDefinitions/related-lookups"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -17578,10 +21536,12 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: named-query-name
in: query
required: false
@@ -17600,7 +21560,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/property-constraint"
+ $ref: "#/getDefinitions/property-constraint"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -17608,14 +21568,17 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: property-constraint-uuid
in: path
required: true
type: string
+ example: __PROPERTY-CONSTRAINT-UUID__
- name: named-query-name
in: query
required: false
@@ -17624,7 +21587,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing property-constraint
- description: create or update an existing property-constraint
+ description: |
+ Create or update an existing property-constraint.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementPropertyConstraintsPropertyConstraint
consumes:
- application/json
@@ -17640,20 +21606,71 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: property-constraint-uuid
in: path
required: true
type: string
+ example: __PROPERTY-CONSTRAINT-UUID__
- name: body
in: body
- description: property-constraint object that needs to be created or updated
+ description: property-constraint object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementPropertyConstraintsPropertyConstraint.json)
required: true
schema:
$ref: "#/definitions/property-constraint"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing property-constraint
+ description: |
+ Update an existing property-constraint
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementPropertyConstraintsPropertyConstraint
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: named-query-uuid
+ in: path
+ required: true
+ type: string
+ example: __NAMED-QUERY-UUID__
+ - name: named-query-element-uuid
+ in: path
+ required: true
+ type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
+ - name: property-constraint-uuid
+ in: path
+ required: true
+ type: string
+ example: __PROPERTY-CONSTRAINT-UUID__
+ - name: body
+ in: body
+ description: property-constraint object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/property-constraint"
delete:
tags:
- ServiceDesignAndCreation
@@ -17674,14 +21691,17 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: property-constraint-uuid
in: path
required: true
type: string
+ example: __PROPERTY-CONSTRAINT-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -17701,7 +21721,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/property-constraints"
+ $ref: "#/getDefinitions/property-constraints"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -17709,10 +21729,12 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: named-query-name
in: query
required: false
@@ -17737,13 +21759,15 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -17767,10 +21791,12 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
/service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}:
get:
tags:
@@ -17785,7 +21811,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/named-query-element"
+ $ref: "#/getDefinitions/named-query-element"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -17793,10 +21819,12 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: named-query-name
in: query
required: false
@@ -17805,7 +21833,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing named-query-element
- description: create or update an existing named-query-element
+ description: |
+ Create or update an existing named-query-element.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement
consumes:
- application/json
@@ -17821,16 +21852,61 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: body
in: body
- description: named-query-element object that needs to be created or updated
+ description: named-query-element object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement.json)
required: true
schema:
$ref: "#/definitions/named-query-element"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing named-query-element
+ description: |
+ Update an existing named-query-element
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: named-query-uuid
+ in: path
+ required: true
+ type: string
+ example: __NAMED-QUERY-UUID__
+ - name: named-query-element-uuid
+ in: path
+ required: true
+ type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
+ - name: body
+ in: body
+ description: named-query-element object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/named-query-element"
delete:
tags:
- ServiceDesignAndCreation
@@ -17851,10 +21927,12 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -17874,7 +21952,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/named-query-elements"
+ $ref: "#/getDefinitions/named-query-elements"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -17882,6 +21960,7 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-name
in: query
required: false
@@ -17906,9 +21985,10 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationNamedQueriesNamedQuery.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -17932,6 +22012,7 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
/service-design-and-creation/named-queries/named-query/{named-query-uuid}:
get:
tags:
@@ -17946,7 +22027,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/named-query"
+ $ref: "#/getDefinitions/named-query"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -17954,6 +22035,7 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-name
in: query
required: false
@@ -17962,7 +22044,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing named-query
- description: create or update an existing named-query
+ description: |
+ Create or update an existing named-query.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationNamedQueriesNamedQuery
consumes:
- application/json
@@ -17978,12 +22063,51 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: body
in: body
- description: named-query object that needs to be created or updated
+ description: named-query object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/ServiceDesignAndCreationNamedQueriesNamedQuery.json)
required: true
schema:
$ref: "#/definitions/named-query"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing named-query
+ description: |
+ Update an existing named-query
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationNamedQueriesNamedQuery
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: named-query-uuid
+ in: path
+ required: true
+ type: string
+ example: __NAMED-QUERY-UUID__
+ - name: body
+ in: body
+ description: named-query object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/named-query"
delete:
tags:
- ServiceDesignAndCreation
@@ -18004,6 +22128,7 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -18023,7 +22148,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/named-queries"
+ $ref: "#/getDefinitions/named-queries"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/logical-links/logical-link/{link-name}/relationship-list/relationship:
@@ -18047,9 +22172,10 @@ paths:
description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkLogicalLinksLogicalLink.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -18074,6 +22200,7 @@ paths:
description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
required: true
type: string
+ example: __LINK-NAME__
/network/logical-links/logical-link/{link-name}:
get:
tags:
@@ -18088,7 +22215,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/logical-link"
+ $ref: "#/getDefinitions/logical-link"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -18097,6 +22224,7 @@ paths:
description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: model-invariant-id
in: query
description: the ASDC model id for this resource or service model.
@@ -18141,7 +22269,10 @@ paths:
tags:
- Network
summary: create or update an existing logical-link
- description: create or update an existing logical-link
+ description: |
+ Create or update an existing logical-link.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkLogicalLinksLogicalLink
consumes:
- application/json
@@ -18158,12 +22289,52 @@ paths:
description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: body
in: body
- description: logical-link object that needs to be created or updated
+ description: logical-link object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkLogicalLinksLogicalLink.json)
required: true
schema:
$ref: "#/definitions/logical-link"
+ patch:
+ tags:
+ - Network
+ summary: update an existing logical-link
+ description: |
+ Update an existing logical-link
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkLogicalLinksLogicalLink
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: link-name
+ in: path
+ description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
+ required: true
+ type: string
+ example: __LINK-NAME__
+ - name: body
+ in: body
+ description: logical-link object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/logical-link"
delete:
tags:
- Network
@@ -18185,6 +22356,7 @@ paths:
description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -18204,7 +22376,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/logical-links"
+ $ref: "#/getDefinitions/logical-links"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}/classes-of-service/class-of-service/{cos}/relationship-list/relationship:
@@ -18228,24 +22400,28 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: cos
in: path
description: unique identifier of probe
required: true
type: string
+ example: __COS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -18270,21 +22446,25 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: cos
in: path
description: unique identifier of probe
required: true
type: string
+ example: __COS__
/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}/classes-of-service/class-of-service/{cos}:
get:
tags:
@@ -18299,7 +22479,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/class-of-service"
+ $ref: "#/getDefinitions/class-of-service"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -18308,26 +22488,33 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: cos
in: path
description: unique identifier of probe
required: true
type: string
+ example: __COS__
put:
tags:
- Network
summary: create or update an existing class-of-service
- description: create or update an existing class-of-service
+ description: |
+ Create or update an existing class-of-service.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService
consumes:
- application/json
@@ -18344,27 +22531,88 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: cos
in: path
description: unique identifier of probe
required: true
type: string
+ example: __COS__
- name: body
in: body
- description: class-of-service object that needs to be created or updated
+ description: class-of-service object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService.json)
required: true
schema:
$ref: "#/definitions/class-of-service"
+ patch:
+ tags:
+ - Network
+ summary: update an existing class-of-service
+ description: |
+ Update an existing class-of-service
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: site-pair-set-id
+ in: path
+ description: Unique id of site pair set.
+ required: true
+ type: string
+ example: __SITE-PAIR-SET-ID__
+ - name: routing-instance-id
+ in: path
+ description: Unique id of routing instance
+ required: true
+ type: string
+ example: __ROUTING-INSTANCE-ID__
+ - name: site-pair-id
+ in: path
+ description: unique identifier of probe
+ required: true
+ type: string
+ example: __SITE-PAIR-ID__
+ - name: cos
+ in: path
+ description: unique identifier of probe
+ required: true
+ type: string
+ example: __COS__
+ - name: body
+ in: body
+ description: class-of-service object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/class-of-service"
delete:
tags:
- Network
@@ -18386,21 +22634,25 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: cos
in: path
description: unique identifier of probe
required: true
type: string
+ example: __COS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -18420,7 +22672,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/classes-of-service"
+ $ref: "#/getDefinitions/classes-of-service"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -18429,16 +22681,19 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}/relationship-list/relationship:
put:
tags:
@@ -18460,19 +22715,22 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -18497,16 +22755,19 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}:
get:
tags:
@@ -18521,7 +22782,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/site-pair"
+ $ref: "#/getDefinitions/site-pair"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -18530,21 +22791,27 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
put:
tags:
- Network
summary: create or update an existing site-pair
- description: create or update an existing site-pair
+ description: |
+ Create or update an existing site-pair.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair
consumes:
- application/json
@@ -18561,22 +22828,76 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: body
in: body
- description: site-pair object that needs to be created or updated
+ description: site-pair object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair.json)
required: true
schema:
$ref: "#/definitions/site-pair"
+ patch:
+ tags:
+ - Network
+ summary: update an existing site-pair
+ description: |
+ Update an existing site-pair
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: site-pair-set-id
+ in: path
+ description: Unique id of site pair set.
+ required: true
+ type: string
+ example: __SITE-PAIR-SET-ID__
+ - name: routing-instance-id
+ in: path
+ description: Unique id of routing instance
+ required: true
+ type: string
+ example: __ROUTING-INSTANCE-ID__
+ - name: site-pair-id
+ in: path
+ description: unique identifier of probe
+ required: true
+ type: string
+ example: __SITE-PAIR-ID__
+ - name: body
+ in: body
+ description: site-pair object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/site-pair"
delete:
tags:
- Network
@@ -18598,16 +22919,19 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -18627,7 +22951,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/site-pairs"
+ $ref: "#/getDefinitions/site-pairs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -18636,11 +22960,13 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/relationship-list/relationship:
put:
tags:
@@ -18662,14 +22988,16 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -18694,11 +23022,13 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}:
get:
tags:
@@ -18713,7 +23043,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/routing-instance"
+ $ref: "#/getDefinitions/routing-instance"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -18722,16 +23052,21 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
put:
tags:
- Network
summary: create or update an existing routing-instance
- description: create or update an existing routing-instance
+ description: |
+ Create or update an existing routing-instance.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance
consumes:
- application/json
@@ -18748,17 +23083,64 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: body
in: body
- description: routing-instance object that needs to be created or updated
+ description: routing-instance object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance.json)
required: true
schema:
$ref: "#/definitions/routing-instance"
+ patch:
+ tags:
+ - Network
+ summary: update an existing routing-instance
+ description: |
+ Update an existing routing-instance
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: site-pair-set-id
+ in: path
+ description: Unique id of site pair set.
+ required: true
+ type: string
+ example: __SITE-PAIR-SET-ID__
+ - name: routing-instance-id
+ in: path
+ description: Unique id of routing instance
+ required: true
+ type: string
+ example: __ROUTING-INSTANCE-ID__
+ - name: body
+ in: body
+ description: routing-instance object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/routing-instance"
delete:
tags:
- Network
@@ -18780,11 +23162,13 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -18804,7 +23188,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/routing-instances"
+ $ref: "#/getDefinitions/routing-instances"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -18813,6 +23197,7 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
/network/site-pair-sets/site-pair-set/{site-pair-set-id}/relationship-list/relationship:
put:
tags:
@@ -18834,9 +23219,10 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkSitePairSetsSitePairSet.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -18861,6 +23247,7 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
/network/site-pair-sets/site-pair-set/{site-pair-set-id}:
get:
tags:
@@ -18875,7 +23262,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/site-pair-set"
+ $ref: "#/getDefinitions/site-pair-set"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -18884,11 +23271,15 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
put:
tags:
- Network
summary: create or update an existing site-pair-set
- description: create or update an existing site-pair-set
+ description: |
+ Create or update an existing site-pair-set.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkSitePairSetsSitePairSet
consumes:
- application/json
@@ -18905,12 +23296,52 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: body
in: body
- description: site-pair-set object that needs to be created or updated
+ description: site-pair-set object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkSitePairSetsSitePairSet.json)
required: true
schema:
$ref: "#/definitions/site-pair-set"
+ patch:
+ tags:
+ - Network
+ summary: update an existing site-pair-set
+ description: |
+ Update an existing site-pair-set
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkSitePairSetsSitePairSet
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: site-pair-set-id
+ in: path
+ description: Unique id of site pair set.
+ required: true
+ type: string
+ example: __SITE-PAIR-SET-ID__
+ - name: body
+ in: body
+ description: site-pair-set object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/site-pair-set"
delete:
tags:
- Network
@@ -18932,6 +23363,7 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -18951,7 +23383,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/site-pair-sets"
+ $ref: "#/getDefinitions/site-pair-sets"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/vpn-bindings/vpn-binding/{vpn-id}/route-targets/route-target/{global-route-target}/{route-target-role}/relationship-list/relationship:
@@ -18975,19 +23407,22 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
- name: global-route-target
in: path
description: Number used to identify an RT, globally unique in the network
required: true
type: string
+ example: __GLOBAL-ROUTE-TARGET__
- name: route-target-role
in: path
description: Role assigned to this route target
required: true
type: string
+ example: __ROUTE-TARGET-ROLE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVpnBindingsVpnBindingRouteTargetsRouteTarget.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -19012,16 +23447,19 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
- name: global-route-target
in: path
description: Number used to identify an RT, globally unique in the network
required: true
type: string
+ example: __GLOBAL-ROUTE-TARGET__
- name: route-target-role
in: path
description: Role assigned to this route target
required: true
type: string
+ example: __ROUTE-TARGET-ROLE__
/network/vpn-bindings/vpn-binding/{vpn-id}/route-targets/route-target/{global-route-target}/{route-target-role}:
get:
tags:
@@ -19036,7 +23474,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/route-target"
+ $ref: "#/getDefinitions/route-target"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -19045,16 +23483,19 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
- name: global-route-target
in: path
description: Number used to identify an RT, globally unique in the network
required: true
type: string
+ example: __GLOBAL-ROUTE-TARGET__
- name: route-target-role
in: path
description: Role assigned to this route target
required: true
type: string
+ example: __ROUTE-TARGET-ROLE__
- name: vpn-name
in: query
description: VPN Name
@@ -19069,7 +23510,10 @@ paths:
tags:
- Network
summary: create or update an existing route-target
- description: create or update an existing route-target
+ description: |
+ Create or update an existing route-target.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVpnBindingsVpnBindingRouteTargetsRouteTarget
consumes:
- application/json
@@ -19086,22 +23530,76 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
- name: global-route-target
in: path
description: Number used to identify an RT, globally unique in the network
required: true
type: string
+ example: __GLOBAL-ROUTE-TARGET__
- name: route-target-role
in: path
description: Role assigned to this route target
required: true
type: string
+ example: __ROUTE-TARGET-ROLE__
- name: body
in: body
- description: route-target object that needs to be created or updated
+ description: route-target object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVpnBindingsVpnBindingRouteTargetsRouteTarget.json)
required: true
schema:
$ref: "#/definitions/route-target"
+ patch:
+ tags:
+ - Network
+ summary: update an existing route-target
+ description: |
+ Update an existing route-target
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVpnBindingsVpnBindingRouteTargetsRouteTarget
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vpn-id
+ in: path
+ description: VPN ID, globally unique within A&AI
+ required: true
+ type: string
+ example: __VPN-ID__
+ - name: global-route-target
+ in: path
+ description: Number used to identify an RT, globally unique in the network
+ required: true
+ type: string
+ example: __GLOBAL-ROUTE-TARGET__
+ - name: route-target-role
+ in: path
+ description: Role assigned to this route target
+ required: true
+ type: string
+ example: __ROUTE-TARGET-ROLE__
+ - name: body
+ in: body
+ description: route-target object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/route-target"
delete:
tags:
- Network
@@ -19123,16 +23621,19 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
- name: global-route-target
in: path
description: Number used to identify an RT, globally unique in the network
required: true
type: string
+ example: __GLOBAL-ROUTE-TARGET__
- name: route-target-role
in: path
description: Role assigned to this route target
required: true
type: string
+ example: __ROUTE-TARGET-ROLE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -19152,7 +23653,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/route-targets"
+ $ref: "#/getDefinitions/route-targets"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -19161,6 +23662,7 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
- name: vpn-name
in: query
description: VPN Name
@@ -19192,9 +23694,10 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVpnBindingsVpnBinding.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -19219,6 +23722,7 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
/network/vpn-bindings/vpn-binding/{vpn-id}:
get:
tags:
@@ -19233,7 +23737,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vpn-binding"
+ $ref: "#/getDefinitions/vpn-binding"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -19242,6 +23746,7 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
- name: vpn-name
in: query
description: VPN Name
@@ -19256,7 +23761,10 @@ paths:
tags:
- Network
summary: create or update an existing vpn-binding
- description: create or update an existing vpn-binding
+ description: |
+ Create or update an existing vpn-binding.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVpnBindingsVpnBinding
consumes:
- application/json
@@ -19273,12 +23781,52 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
- name: body
in: body
- description: vpn-binding object that needs to be created or updated
+ description: vpn-binding object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVpnBindingsVpnBinding.json)
required: true
schema:
$ref: "#/definitions/vpn-binding"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vpn-binding
+ description: |
+ Update an existing vpn-binding
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVpnBindingsVpnBinding
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vpn-id
+ in: path
+ description: VPN ID, globally unique within A&AI
+ required: true
+ type: string
+ example: __VPN-ID__
+ - name: body
+ in: body
+ description: vpn-binding object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vpn-binding"
delete:
tags:
- Network
@@ -19300,6 +23848,7 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -19319,7 +23868,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vpn-bindings"
+ $ref: "#/getDefinitions/vpn-bindings"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/vpls-pes/vpls-pe/{equipment-name}/relationship-list/relationship:
@@ -19342,9 +23891,10 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPe.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -19368,6 +23918,7 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/relationship-list/relationship:
put:
tags:
@@ -19388,14 +23939,16 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -19419,11 +23972,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/sriov-pfs/sriov-pf/{pf-pci-id}/relationship-list/relationship:
put:
tags:
@@ -19444,19 +23999,22 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pf-pci-id
in: path
description: Identifier for the sriov-pf
required: true
type: string
+ example: __PF-PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceSriovPfsSriovPf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -19480,16 +24038,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pf-pci-id
in: path
description: Identifier for the sriov-pf
required: true
type: string
+ example: __PF-PCI-ID__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/sriov-pfs/sriov-pf/{pf-pci-id}:
get:
tags:
@@ -19504,7 +24065,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-pf"
+ $ref: "#/getDefinitions/sriov-pf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -19512,16 +24073,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pf-pci-id
in: path
description: Identifier for the sriov-pf
required: true
type: string
+ example: __PF-PCI-ID__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -19536,7 +24100,10 @@ paths:
tags:
- Network
summary: create or update an existing sriov-pf
- description: create or update an existing sriov-pf
+ description: |
+ Create or update an existing sriov-pf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceSriovPfsSriovPf
consumes:
- application/json
@@ -19552,22 +24119,75 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pf-pci-id
in: path
description: Identifier for the sriov-pf
required: true
type: string
+ example: __PF-PCI-ID__
- name: body
in: body
- description: sriov-pf object that needs to be created or updated
+ description: sriov-pf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceSriovPfsSriovPf.json)
required: true
schema:
$ref: "#/definitions/sriov-pf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing sriov-pf
+ description: |
+ Update an existing sriov-pf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceSriovPfsSriovPf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pf-pci-id
+ in: path
+ description: Identifier for the sriov-pf
+ required: true
+ type: string
+ example: __PF-PCI-ID__
+ - name: body
+ in: body
+ description: sriov-pf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-pf"
delete:
tags:
- Network
@@ -19588,16 +24208,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pf-pci-id
in: path
description: Identifier for the sriov-pf
required: true
type: string
+ example: __PF-PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -19617,7 +24240,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-pfs"
+ $ref: "#/getDefinitions/sriov-pfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -19625,11 +24248,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -19660,24 +24285,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -19701,21 +24330,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -19736,29 +24369,34 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -19782,26 +24420,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -19816,7 +24459,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -19824,26 +24467,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -19900,7 +24548,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -19916,32 +24567,99 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -19962,26 +24680,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -20007,29 +24730,34 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -20053,26 +24781,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -20087,7 +24820,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -20095,26 +24828,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -20171,7 +24909,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -20187,32 +24928,99 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -20233,26 +25041,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -20272,7 +25085,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -20280,21 +25093,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -20335,7 +25152,10 @@ paths:
tags:
- Network
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -20351,27 +25171,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- Network
@@ -20392,21 +25272,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -20426,7 +25310,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -20434,16 +25318,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -20489,24 +25376,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -20530,21 +25421,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -20559,7 +25454,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -20567,21 +25462,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -20631,7 +25530,10 @@ paths:
tags:
- Network
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -20647,27 +25549,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- Network
@@ -20688,21 +25650,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -20722,7 +25688,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -20730,16 +25696,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -20785,19 +25754,22 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -20821,16 +25793,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -20851,24 +25826,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -20892,21 +25871,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -20921,7 +25904,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -20929,21 +25912,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -20989,7 +25976,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -21005,27 +25995,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -21046,21 +26096,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -21086,24 +26140,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -21127,21 +26185,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -21156,7 +26218,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -21164,21 +26226,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -21224,7 +26290,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -21240,27 +26309,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -21281,21 +26410,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -21315,7 +26448,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -21323,16 +26456,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -21362,7 +26498,10 @@ paths:
tags:
- Network
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface
consumes:
- application/json
@@ -21378,22 +26517,75 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- Network
@@ -21414,16 +26606,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -21443,7 +26638,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -21451,11 +26646,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -21480,7 +26677,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/p-interface"
+ $ref: "#/getDefinitions/p-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -21488,11 +26685,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -21507,7 +26706,10 @@ paths:
tags:
- Network
summary: create or update an existing p-interface
- description: create or update an existing p-interface
+ description: |
+ Create or update an existing p-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterface
consumes:
- application/json
@@ -21523,17 +26725,63 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: p-interface object that needs to be created or updated
+ description: p-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPePInterfacesPInterface.json)
required: true
schema:
$ref: "#/definitions/p-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing p-interface
+ description: |
+ Update an existing p-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: p-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/p-interface"
delete:
tags:
- Network
@@ -21554,11 +26802,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -21578,7 +26828,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/p-interfaces"
+ $ref: "#/getDefinitions/p-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -21586,6 +26836,7 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -21611,14 +26862,16 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -21642,11 +26895,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -21667,24 +26922,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -21708,21 +26967,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -21743,29 +27006,34 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -21789,26 +27057,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -21823,7 +27096,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -21831,26 +27104,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -21912,7 +27190,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -21928,32 +27209,99 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -21974,26 +27322,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -22019,29 +27372,34 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -22065,26 +27423,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -22099,7 +27462,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -22107,26 +27470,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -22188,7 +27556,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -22204,32 +27575,99 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -22250,26 +27688,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -22289,7 +27732,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -22297,21 +27740,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -22357,7 +27804,10 @@ paths:
tags:
- Network
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -22373,27 +27823,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- Network
@@ -22414,21 +27924,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -22448,7 +27962,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -22456,16 +27970,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -22516,24 +28033,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -22557,21 +28078,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -22586,7 +28111,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -22594,21 +28119,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -22663,7 +28192,10 @@ paths:
tags:
- Network
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -22679,27 +28211,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- Network
@@ -22720,21 +28312,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -22754,7 +28350,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -22762,16 +28358,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -22822,19 +28421,22 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -22858,16 +28460,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -22888,24 +28493,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -22929,21 +28538,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -22958,7 +28571,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -22966,21 +28579,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -23031,7 +28648,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -23047,27 +28667,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -23088,21 +28768,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -23128,24 +28812,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -23169,21 +28857,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -23198,7 +28890,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -23206,21 +28898,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -23271,7 +28967,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -23287,27 +28986,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -23328,21 +29087,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -23362,7 +29125,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -23370,16 +29133,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -23414,7 +29180,10 @@ paths:
tags:
- Network
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface
consumes:
- application/json
@@ -23430,22 +29199,75 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- Network
@@ -23466,16 +29288,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -23495,7 +29320,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -23503,11 +29328,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -23537,7 +29364,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interface"
+ $ref: "#/getDefinitions/lag-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -23545,11 +29372,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -23569,7 +29398,10 @@ paths:
tags:
- Network
summary: create or update an existing lag-interface
- description: create or update an existing lag-interface
+ description: |
+ Create or update an existing lag-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterface
consumes:
- application/json
@@ -23585,17 +29417,63 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: lag-interface object that needs to be created or updated
+ description: lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPeLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/lag-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing lag-interface
+ description: |
+ Update an existing lag-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: lag-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/lag-interface"
delete:
tags:
- Network
@@ -23616,11 +29494,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -23640,7 +29520,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interfaces"
+ $ref: "#/getDefinitions/lag-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -23648,6 +29528,7 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -23667,7 +29548,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vpls-pe"
+ $ref: "#/getDefinitions/vpls-pe"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -23675,6 +29556,7 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -23684,7 +29566,10 @@ paths:
tags:
- Network
summary: create or update an existing vpls-pe
- description: create or update an existing vpls-pe
+ description: |
+ Create or update an existing vpls-pe.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPe
consumes:
- application/json
@@ -23700,12 +29585,51 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: body
in: body
- description: vpls-pe object that needs to be created or updated
+ description: vpls-pe object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVplsPesVplsPe.json)
required: true
schema:
$ref: "#/definitions/vpls-pe"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vpls-pe
+ description: |
+ Update an existing vpls-pe
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPe
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: body
+ in: body
+ description: vpls-pe object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vpls-pe"
delete:
tags:
- Network
@@ -23726,6 +29650,7 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -23745,7 +29670,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vpls-pes"
+ $ref: "#/getDefinitions/vpls-pes"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/multicast-configurations/multicast-configuration/{multicast-configuration-id}/relationship-list/relationship:
@@ -23769,9 +29694,10 @@ paths:
description: Unique id of multicast configuration.
required: true
type: string
+ example: __MULTICAST-CONFIGURATION-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkMulticastConfigurationsMulticastConfiguration.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -23796,6 +29722,7 @@ paths:
description: Unique id of multicast configuration.
required: true
type: string
+ example: __MULTICAST-CONFIGURATION-ID__
/network/multicast-configurations/multicast-configuration/{multicast-configuration-id}:
get:
tags:
@@ -23810,7 +29737,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/multicast-configuration"
+ $ref: "#/getDefinitions/multicast-configuration"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -23819,11 +29746,15 @@ paths:
description: Unique id of multicast configuration.
required: true
type: string
+ example: __MULTICAST-CONFIGURATION-ID__
put:
tags:
- Network
summary: create or update an existing multicast-configuration
- description: create or update an existing multicast-configuration
+ description: |
+ Create or update an existing multicast-configuration.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkMulticastConfigurationsMulticastConfiguration
consumes:
- application/json
@@ -23840,12 +29771,52 @@ paths:
description: Unique id of multicast configuration.
required: true
type: string
+ example: __MULTICAST-CONFIGURATION-ID__
- name: body
in: body
- description: multicast-configuration object that needs to be created or updated
+ description: multicast-configuration object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkMulticastConfigurationsMulticastConfiguration.json)
required: true
schema:
$ref: "#/definitions/multicast-configuration"
+ patch:
+ tags:
+ - Network
+ summary: update an existing multicast-configuration
+ description: |
+ Update an existing multicast-configuration
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkMulticastConfigurationsMulticastConfiguration
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: multicast-configuration-id
+ in: path
+ description: Unique id of multicast configuration.
+ required: true
+ type: string
+ example: __MULTICAST-CONFIGURATION-ID__
+ - name: body
+ in: body
+ description: multicast-configuration object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/multicast-configuration"
delete:
tags:
- Network
@@ -23867,6 +29838,7 @@ paths:
description: Unique id of multicast configuration.
required: true
type: string
+ example: __MULTICAST-CONFIGURATION-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -23886,7 +29858,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/multicast-configurations"
+ $ref: "#/getDefinitions/multicast-configurations"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}/cvlan-tags/cvlan-tag-entry/{cvlan-tag}/relationship-list/relationship:
@@ -23910,20 +29882,23 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: cvlan-tag
in: path
description: See mis-na-virtualization-platform.yang
required: true
type: integer
format: int64
+ example: __CVLAN-TAG__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -23948,17 +29923,20 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: cvlan-tag
in: path
description: See mis-na-virtualization-platform.yang
required: true
type: integer
format: int64
+ example: __CVLAN-TAG__
/network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}/cvlan-tags/cvlan-tag-entry/{cvlan-tag}:
get:
tags:
@@ -23973,7 +29951,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/cvlan-tag-entry"
+ $ref: "#/getDefinitions/cvlan-tag-entry"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -23982,17 +29960,20 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: cvlan-tag
in: path
description: See mis-na-virtualization-platform.yang
required: true
type: integer
format: int64
+ example: __CVLAN-TAG__
- name: vnf-name
in: query
description: Name of VNF.
@@ -24052,7 +30033,10 @@ paths:
tags:
- Network
summary: create or update an existing cvlan-tag-entry
- description: create or update an existing cvlan-tag-entry
+ description: |
+ Create or update an existing cvlan-tag-entry.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry
consumes:
- application/json
@@ -24069,23 +30053,78 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: cvlan-tag
in: path
description: See mis-na-virtualization-platform.yang
required: true
type: integer
format: int64
+ example: __CVLAN-TAG__
- name: body
in: body
- description: cvlan-tag-entry object that needs to be created or updated
+ description: cvlan-tag-entry object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry.json)
required: true
schema:
$ref: "#/definitions/cvlan-tag-entry"
+ patch:
+ tags:
+ - Network
+ summary: update an existing cvlan-tag-entry
+ description: |
+ Update an existing cvlan-tag-entry
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-id
+ in: path
+ description: Unique ID of the interface
+ required: true
+ type: string
+ example: __INTERFACE-ID__
+ - name: cvlan-tag
+ in: path
+ description: See mis-na-virtualization-platform.yang
+ required: true
+ type: integer
+ format: int64
+ example: __CVLAN-TAG__
+ - name: body
+ in: body
+ description: cvlan-tag-entry object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/cvlan-tag-entry"
delete:
tags:
- Network
@@ -24107,17 +30146,20 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: cvlan-tag
in: path
description: See mis-na-virtualization-platform.yang
required: true
type: integer
format: int64
+ example: __CVLAN-TAG__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -24137,7 +30179,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/cvlan-tags"
+ $ref: "#/getDefinitions/cvlan-tags"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -24146,11 +30188,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -24227,14 +30271,16 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVcesVcePortGroupsPortGroup.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -24259,11 +30305,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
/network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}:
get:
tags:
@@ -24278,7 +30326,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/port-group"
+ $ref: "#/getDefinitions/port-group"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -24287,11 +30335,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -24351,7 +30401,10 @@ paths:
tags:
- Network
summary: create or update an existing port-group
- description: create or update an existing port-group
+ description: |
+ Create or update an existing port-group.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVcesVcePortGroupsPortGroup
consumes:
- application/json
@@ -24368,17 +30421,64 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: body
in: body
- description: port-group object that needs to be created or updated
+ description: port-group object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVcesVcePortGroupsPortGroup.json)
required: true
schema:
$ref: "#/definitions/port-group"
+ patch:
+ tags:
+ - Network
+ summary: update an existing port-group
+ description: |
+ Update an existing port-group
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVcesVcePortGroupsPortGroup
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-id
+ in: path
+ description: Unique ID of the interface
+ required: true
+ type: string
+ example: __INTERFACE-ID__
+ - name: body
+ in: body
+ description: port-group object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/port-group"
delete:
tags:
- Network
@@ -24400,11 +30500,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -24424,7 +30526,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/port-groups"
+ $ref: "#/getDefinitions/port-groups"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -24433,6 +30535,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -24494,19 +30597,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the license group the resource belongs to, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of a license resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVcesVceLicensesLicense.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -24531,16 +30637,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the license group the resource belongs to, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of a license resource.
required: true
type: string
+ example: __RESOURCE-UUID__
/network/vces/vce/{vnf-id}/licenses/license/{group-uuid}/{resource-uuid}:
get:
tags:
@@ -24555,7 +30664,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/license"
+ $ref: "#/getDefinitions/license"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -24564,16 +30673,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the license group the resource belongs to, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of a license resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -24618,7 +30730,10 @@ paths:
tags:
- Network
summary: create or update an existing license
- description: create or update an existing license
+ description: |
+ Create or update an existing license.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVcesVceLicensesLicense
consumes:
- application/json
@@ -24635,22 +30750,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the license group the resource belongs to, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of a license resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: body
in: body
- description: license object that needs to be created or updated
+ description: license object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVcesVceLicensesLicense.json)
required: true
schema:
$ref: "#/definitions/license"
+ patch:
+ tags:
+ - Network
+ summary: update an existing license
+ description: |
+ Update an existing license
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVcesVceLicensesLicense
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: group-uuid
+ in: path
+ description: Unique ID for the license group the resource belongs to, should be uuid.
+ required: true
+ type: string
+ example: __GROUP-UUID__
+ - name: resource-uuid
+ in: path
+ description: Unique ID of a license resource.
+ required: true
+ type: string
+ example: __RESOURCE-UUID__
+ - name: body
+ in: body
+ description: license object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/license"
delete:
tags:
- Network
@@ -24672,16 +30841,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the license group the resource belongs to, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of a license resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -24701,7 +30873,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/licenses"
+ $ref: "#/getDefinitions/licenses"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -24710,6 +30882,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -24771,19 +30944,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the entitlement group the resource comes from, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of an entitlement resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVcesVceEntitlementsEntitlement.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -24808,16 +30984,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the entitlement group the resource comes from, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of an entitlement resource.
required: true
type: string
+ example: __RESOURCE-UUID__
/network/vces/vce/{vnf-id}/entitlements/entitlement/{group-uuid}/{resource-uuid}:
get:
tags:
@@ -24832,7 +31011,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/entitlement"
+ $ref: "#/getDefinitions/entitlement"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -24841,16 +31020,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the entitlement group the resource comes from, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of an entitlement resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -24895,7 +31077,10 @@ paths:
tags:
- Network
summary: create or update an existing entitlement
- description: create or update an existing entitlement
+ description: |
+ Create or update an existing entitlement.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVcesVceEntitlementsEntitlement
consumes:
- application/json
@@ -24912,22 +31097,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the entitlement group the resource comes from, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of an entitlement resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: body
in: body
- description: entitlement object that needs to be created or updated
+ description: entitlement object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVcesVceEntitlementsEntitlement.json)
required: true
schema:
$ref: "#/definitions/entitlement"
+ patch:
+ tags:
+ - Network
+ summary: update an existing entitlement
+ description: |
+ Update an existing entitlement
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVcesVceEntitlementsEntitlement
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: group-uuid
+ in: path
+ description: Unique ID for the entitlement group the resource comes from, should be uuid.
+ required: true
+ type: string
+ example: __GROUP-UUID__
+ - name: resource-uuid
+ in: path
+ description: Unique ID of an entitlement resource.
+ required: true
+ type: string
+ example: __RESOURCE-UUID__
+ - name: body
+ in: body
+ description: entitlement object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/entitlement"
delete:
tags:
- Network
@@ -24949,16 +31188,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the entitlement group the resource comes from, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of an entitlement resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -24978,7 +31220,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/entitlements"
+ $ref: "#/getDefinitions/entitlements"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -24987,6 +31229,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -25048,9 +31291,10 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVcesVce.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -25075,6 +31319,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
/network/vces/vce/{vnf-id}:
get:
tags:
@@ -25089,7 +31334,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vce"
+ $ref: "#/getDefinitions/vce"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -25098,6 +31343,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -25142,7 +31388,10 @@ paths:
tags:
- Network
summary: create or update an existing vce
- description: create or update an existing vce
+ description: |
+ Create or update an existing vce.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVcesVce
consumes:
- application/json
@@ -25159,12 +31408,52 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: body
in: body
- description: vce object that needs to be created or updated
+ description: vce object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVcesVce.json)
required: true
schema:
$ref: "#/definitions/vce"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vce
+ description: |
+ Update an existing vce
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVcesVce
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: body
+ in: body
+ description: vce object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vce"
delete:
tags:
- Network
@@ -25186,6 +31475,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -25205,7 +31495,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vces"
+ $ref: "#/getDefinitions/vces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/vnfcs/vnfc/{vnfc-name}/relationship-list/relationship:
@@ -25229,9 +31519,10 @@ paths:
description: Unique ID of vnfc.
required: true
type: string
+ example: __VNFC-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVnfcsVnfc.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -25256,6 +31547,7 @@ paths:
description: Unique ID of vnfc.
required: true
type: string
+ example: __VNFC-NAME__
/network/vnfcs/vnfc/{vnfc-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -25277,14 +31569,16 @@ paths:
description: Unique ID of vnfc.
required: true
type: string
+ example: __VNFC-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVnfcsVnfcL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -25309,11 +31603,13 @@ paths:
description: Unique ID of vnfc.
required: true
type: string
+ example: __VNFC-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/vnfcs/vnfc/{vnfc-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -25328,7 +31624,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -25337,11 +31633,13 @@ paths:
description: Unique ID of vnfc.
required: true
type: string
+ example: __VNFC-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: nfc-naming-code
in: query
description: Short code that is used in naming instances of the item being modeled
@@ -25405,7 +31703,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVnfcsVnfcL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -25422,17 +31723,64 @@ paths:
description: Unique ID of vnfc.
required: true
type: string
+ example: __VNFC-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVnfcsVnfcL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVnfcsVnfcL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnfc-name
+ in: path
+ description: Unique ID of vnfc.
+ required: true
+ type: string
+ example: __VNFC-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -25454,11 +31802,13 @@ paths:
description: Unique ID of vnfc.
required: true
type: string
+ example: __VNFC-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -25485,14 +31835,16 @@ paths:
description: Unique ID of vnfc.
required: true
type: string
+ example: __VNFC-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVnfcsVnfcL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -25517,11 +31869,13 @@ paths:
description: Unique ID of vnfc.
required: true
type: string
+ example: __VNFC-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/vnfcs/vnfc/{vnfc-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -25536,7 +31890,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -25545,11 +31899,13 @@ paths:
description: Unique ID of vnfc.
required: true
type: string
+ example: __VNFC-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: nfc-naming-code
in: query
description: Short code that is used in naming instances of the item being modeled
@@ -25613,7 +31969,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVnfcsVnfcL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -25630,17 +31989,64 @@ paths:
description: Unique ID of vnfc.
required: true
type: string
+ example: __VNFC-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVnfcsVnfcL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVnfcsVnfcL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnfc-name
+ in: path
+ description: Unique ID of vnfc.
+ required: true
+ type: string
+ example: __VNFC-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -25662,11 +32068,13 @@ paths:
description: Unique ID of vnfc.
required: true
type: string
+ example: __VNFC-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -25686,7 +32094,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vnfc"
+ $ref: "#/getDefinitions/vnfc"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -25695,6 +32103,7 @@ paths:
description: Unique ID of vnfc.
required: true
type: string
+ example: __VNFC-NAME__
- name: nfc-naming-code
in: query
description: Short code that is used in naming instances of the item being modeled
@@ -25742,7 +32151,10 @@ paths:
tags:
- Network
summary: create or update an existing vnfc
- description: create or update an existing vnfc
+ description: |
+ Create or update an existing vnfc.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVnfcsVnfc
consumes:
- application/json
@@ -25759,12 +32171,52 @@ paths:
description: Unique ID of vnfc.
required: true
type: string
+ example: __VNFC-NAME__
- name: body
in: body
- description: vnfc object that needs to be created or updated
+ description: vnfc object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkVnfcsVnfc.json)
required: true
schema:
$ref: "#/definitions/vnfc"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vnfc
+ description: |
+ Update an existing vnfc
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVnfcsVnfc
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnfc-name
+ in: path
+ description: Unique ID of vnfc.
+ required: true
+ type: string
+ example: __VNFC-NAME__
+ - name: body
+ in: body
+ description: vnfc object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vnfc"
delete:
tags:
- Network
@@ -25786,6 +32238,7 @@ paths:
description: Unique ID of vnfc.
required: true
type: string
+ example: __VNFC-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -25805,7 +32258,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vnfcs"
+ $ref: "#/getDefinitions/vnfcs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/l3-networks/l3-network/{network-id}/subnets/subnet/{subnet-id}/host-routes/host-route/{host-route-id}/relationship-list/relationship:
@@ -25829,19 +32282,22 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: subnet-id
in: path
description: Subnet ID, should be UUID.
required: true
type: string
+ example: __SUBNET-ID__
- name: host-route-id
in: path
description: host-route id
required: true
type: string
+ example: __HOST-ROUTE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkL3NetworksL3NetworkSubnetsSubnetHostRoutesHostRoute.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -25866,16 +32322,19 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: subnet-id
in: path
description: Subnet ID, should be UUID.
required: true
type: string
+ example: __SUBNET-ID__
- name: host-route-id
in: path
description: host-route id
required: true
type: string
+ example: __HOST-ROUTE-ID__
/network/l3-networks/l3-network/{network-id}/subnets/subnet/{subnet-id}/host-routes/host-route/{host-route-id}:
get:
tags:
@@ -25890,7 +32349,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/host-route"
+ $ref: "#/getDefinitions/host-route"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -25899,16 +32358,19 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: subnet-id
in: path
description: Subnet ID, should be UUID.
required: true
type: string
+ example: __SUBNET-ID__
- name: host-route-id
in: path
description: host-route id
required: true
type: string
+ example: __HOST-ROUTE-ID__
- name: network-name
in: query
description: Name of the network, governed by some naming convention..
@@ -25963,7 +32425,10 @@ paths:
tags:
- Network
summary: create or update an existing host-route
- description: create or update an existing host-route
+ description: |
+ Create or update an existing host-route.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkL3NetworksL3NetworkSubnetsSubnetHostRoutesHostRoute
consumes:
- application/json
@@ -25980,22 +32445,76 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: subnet-id
in: path
description: Subnet ID, should be UUID.
required: true
type: string
+ example: __SUBNET-ID__
- name: host-route-id
in: path
description: host-route id
required: true
type: string
+ example: __HOST-ROUTE-ID__
- name: body
in: body
- description: host-route object that needs to be created or updated
+ description: host-route object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkL3NetworksL3NetworkSubnetsSubnetHostRoutesHostRoute.json)
required: true
schema:
$ref: "#/definitions/host-route"
+ patch:
+ tags:
+ - Network
+ summary: update an existing host-route
+ description: |
+ Update an existing host-route
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkL3NetworksL3NetworkSubnetsSubnetHostRoutesHostRoute
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: network-id
+ in: path
+ description: Network ID, should be uuid. Unique across A&AI.
+ required: true
+ type: string
+ example: __NETWORK-ID__
+ - name: subnet-id
+ in: path
+ description: Subnet ID, should be UUID.
+ required: true
+ type: string
+ example: __SUBNET-ID__
+ - name: host-route-id
+ in: path
+ description: host-route id
+ required: true
+ type: string
+ example: __HOST-ROUTE-ID__
+ - name: body
+ in: body
+ description: host-route object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/host-route"
delete:
tags:
- Network
@@ -26017,16 +32536,19 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: subnet-id
in: path
description: Subnet ID, should be UUID.
required: true
type: string
+ example: __SUBNET-ID__
- name: host-route-id
in: path
description: host-route id
required: true
type: string
+ example: __HOST-ROUTE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -26046,7 +32568,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/host-routes"
+ $ref: "#/getDefinitions/host-routes"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -26055,11 +32577,13 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: subnet-id
in: path
description: Subnet ID, should be UUID.
required: true
type: string
+ example: __SUBNET-ID__
- name: network-name
in: query
description: Name of the network, governed by some naming convention..
@@ -26131,14 +32655,16 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: subnet-id
in: path
description: Subnet ID, should be UUID.
required: true
type: string
+ example: __SUBNET-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkL3NetworksL3NetworkSubnetsSubnet.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -26163,11 +32689,13 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: subnet-id
in: path
description: Subnet ID, should be UUID.
required: true
type: string
+ example: __SUBNET-ID__
/network/l3-networks/l3-network/{network-id}/subnets/subnet/{subnet-id}:
get:
tags:
@@ -26182,7 +32710,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/subnet"
+ $ref: "#/getDefinitions/subnet"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -26191,11 +32719,13 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: subnet-id
in: path
description: Subnet ID, should be UUID.
required: true
type: string
+ example: __SUBNET-ID__
- name: network-name
in: query
description: Name of the network, governed by some naming convention..
@@ -26250,7 +32780,10 @@ paths:
tags:
- Network
summary: create or update an existing subnet
- description: create or update an existing subnet
+ description: |
+ Create or update an existing subnet.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkL3NetworksL3NetworkSubnetsSubnet
consumes:
- application/json
@@ -26267,17 +32800,64 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: subnet-id
in: path
description: Subnet ID, should be UUID.
required: true
type: string
+ example: __SUBNET-ID__
- name: body
in: body
- description: subnet object that needs to be created or updated
+ description: subnet object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkL3NetworksL3NetworkSubnetsSubnet.json)
required: true
schema:
$ref: "#/definitions/subnet"
+ patch:
+ tags:
+ - Network
+ summary: update an existing subnet
+ description: |
+ Update an existing subnet
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkL3NetworksL3NetworkSubnetsSubnet
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: network-id
+ in: path
+ description: Network ID, should be uuid. Unique across A&AI.
+ required: true
+ type: string
+ example: __NETWORK-ID__
+ - name: subnet-id
+ in: path
+ description: Subnet ID, should be UUID.
+ required: true
+ type: string
+ example: __SUBNET-ID__
+ - name: body
+ in: body
+ description: subnet object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/subnet"
delete:
tags:
- Network
@@ -26299,11 +32879,13 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: subnet-id
in: path
description: Subnet ID, should be UUID.
required: true
type: string
+ example: __SUBNET-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -26323,7 +32905,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/subnets"
+ $ref: "#/getDefinitions/subnets"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -26332,6 +32914,7 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: network-name
in: query
description: Name of the network, governed by some naming convention..
@@ -26398,15 +32981,17 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: vlan-id-inner
in: path
description: id.
required: true
type: integer
format: int64
+ example: __VLAN-ID-INNER__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -26431,12 +33016,14 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: vlan-id-inner
in: path
description: id.
required: true
type: integer
format: int64
+ example: __VLAN-ID-INNER__
/network/l3-networks/l3-network/{network-id}/ctag-assignments/ctag-assignment/{vlan-id-inner}:
get:
tags:
@@ -26451,7 +33038,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/ctag-assignment"
+ $ref: "#/getDefinitions/ctag-assignment"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -26460,12 +33047,14 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: vlan-id-inner
in: path
description: id.
required: true
type: integer
format: int64
+ example: __VLAN-ID-INNER__
- name: network-name
in: query
description: Name of the network, governed by some naming convention..
@@ -26515,7 +33104,10 @@ paths:
tags:
- Network
summary: create or update an existing ctag-assignment
- description: create or update an existing ctag-assignment
+ description: |
+ Create or update an existing ctag-assignment.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment
consumes:
- application/json
@@ -26532,18 +33124,66 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: vlan-id-inner
in: path
description: id.
required: true
type: integer
format: int64
+ example: __VLAN-ID-INNER__
- name: body
in: body
- description: ctag-assignment object that needs to be created or updated
+ description: ctag-assignment object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment.json)
required: true
schema:
$ref: "#/definitions/ctag-assignment"
+ patch:
+ tags:
+ - Network
+ summary: update an existing ctag-assignment
+ description: |
+ Update an existing ctag-assignment
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: network-id
+ in: path
+ description: Network ID, should be uuid. Unique across A&AI.
+ required: true
+ type: string
+ example: __NETWORK-ID__
+ - name: vlan-id-inner
+ in: path
+ description: id.
+ required: true
+ type: integer
+ format: int64
+ example: __VLAN-ID-INNER__
+ - name: body
+ in: body
+ description: ctag-assignment object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/ctag-assignment"
delete:
tags:
- Network
@@ -26565,12 +33205,14 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: vlan-id-inner
in: path
description: id.
required: true
type: integer
format: int64
+ example: __VLAN-ID-INNER__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -26590,7 +33232,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/ctag-assignments"
+ $ref: "#/getDefinitions/ctag-assignments"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -26599,6 +33241,7 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: network-name
in: query
description: Name of the network, governed by some naming convention..
@@ -26665,14 +33308,16 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: segmentation-id
in: path
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __SEGMENTATION-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -26697,11 +33342,13 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: segmentation-id
in: path
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __SEGMENTATION-ID__
/network/l3-networks/l3-network/{network-id}/segmentation-assignments/segmentation-assignment/{segmentation-id}:
get:
tags:
@@ -26716,7 +33363,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/segmentation-assignment"
+ $ref: "#/getDefinitions/segmentation-assignment"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -26725,11 +33372,13 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: segmentation-id
in: path
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __SEGMENTATION-ID__
- name: network-name
in: query
description: Name of the network, governed by some naming convention..
@@ -26779,7 +33428,10 @@ paths:
tags:
- Network
summary: create or update an existing segmentation-assignment
- description: create or update an existing segmentation-assignment
+ description: |
+ Create or update an existing segmentation-assignment.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment
consumes:
- application/json
@@ -26796,17 +33448,64 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: segmentation-id
in: path
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __SEGMENTATION-ID__
- name: body
in: body
- description: segmentation-assignment object that needs to be created or updated
+ description: segmentation-assignment object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment.json)
required: true
schema:
$ref: "#/definitions/segmentation-assignment"
+ patch:
+ tags:
+ - Network
+ summary: update an existing segmentation-assignment
+ description: |
+ Update an existing segmentation-assignment
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: network-id
+ in: path
+ description: Network ID, should be uuid. Unique across A&AI.
+ required: true
+ type: string
+ example: __NETWORK-ID__
+ - name: segmentation-id
+ in: path
+ description: Route Table Reference id, UUID assigned to this instance.
+ required: true
+ type: string
+ example: __SEGMENTATION-ID__
+ - name: body
+ in: body
+ description: segmentation-assignment object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/segmentation-assignment"
delete:
tags:
- Network
@@ -26828,11 +33527,13 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: segmentation-id
in: path
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __SEGMENTATION-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -26852,7 +33553,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/segmentation-assignments"
+ $ref: "#/getDefinitions/segmentation-assignments"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -26861,6 +33562,7 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: network-name
in: query
description: Name of the network, governed by some naming convention..
@@ -26927,9 +33629,10 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkL3NetworksL3Network.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -26954,6 +33657,7 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
/network/l3-networks/l3-network/{network-id}:
get:
tags:
@@ -26968,7 +33672,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-network"
+ $ref: "#/getDefinitions/l3-network"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -26977,6 +33681,7 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: network-name
in: query
description: Name of the network, governed by some naming convention..
@@ -27026,7 +33731,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-network
- description: create or update an existing l3-network
+ description: |
+ Create or update an existing l3-network.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkL3NetworksL3Network
consumes:
- application/json
@@ -27043,12 +33751,52 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: body
in: body
- description: l3-network object that needs to be created or updated
+ description: l3-network object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkL3NetworksL3Network.json)
required: true
schema:
$ref: "#/definitions/l3-network"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-network
+ description: |
+ Update an existing l3-network
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkL3NetworksL3Network
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: network-id
+ in: path
+ description: Network ID, should be uuid. Unique across A&AI.
+ required: true
+ type: string
+ example: __NETWORK-ID__
+ - name: body
+ in: body
+ description: l3-network object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-network"
delete:
tags:
- Network
@@ -27070,6 +33818,7 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -27089,7 +33838,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-networks"
+ $ref: "#/getDefinitions/l3-networks"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/network-policies/network-policy/{network-policy-id}/relationship-list/relationship:
@@ -27113,9 +33862,10 @@ paths:
description: UUID representing unique key to this instance
required: true
type: string
+ example: __NETWORK-POLICY-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNetworkPoliciesNetworkPolicy.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -27140,6 +33890,7 @@ paths:
description: UUID representing unique key to this instance
required: true
type: string
+ example: __NETWORK-POLICY-ID__
/network/network-policies/network-policy/{network-policy-id}:
get:
tags:
@@ -27154,7 +33905,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/network-policy"
+ $ref: "#/getDefinitions/network-policy"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -27163,6 +33914,7 @@ paths:
description: UUID representing unique key to this instance
required: true
type: string
+ example: __NETWORK-POLICY-ID__
- name: network-policy-fqdn
in: query
description: Contrail FQDN for the policy
@@ -27172,7 +33924,10 @@ paths:
tags:
- Network
summary: create or update an existing network-policy
- description: create or update an existing network-policy
+ description: |
+ Create or update an existing network-policy.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNetworkPoliciesNetworkPolicy
consumes:
- application/json
@@ -27189,12 +33944,52 @@ paths:
description: UUID representing unique key to this instance
required: true
type: string
+ example: __NETWORK-POLICY-ID__
- name: body
in: body
- description: network-policy object that needs to be created or updated
+ description: network-policy object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNetworkPoliciesNetworkPolicy.json)
required: true
schema:
$ref: "#/definitions/network-policy"
+ patch:
+ tags:
+ - Network
+ summary: update an existing network-policy
+ description: |
+ Update an existing network-policy
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNetworkPoliciesNetworkPolicy
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: network-policy-id
+ in: path
+ description: UUID representing unique key to this instance
+ required: true
+ type: string
+ example: __NETWORK-POLICY-ID__
+ - name: body
+ in: body
+ description: network-policy object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/network-policy"
delete:
tags:
- Network
@@ -27216,6 +34011,7 @@ paths:
description: UUID representing unique key to this instance
required: true
type: string
+ example: __NETWORK-POLICY-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -27235,7 +34031,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/network-policies"
+ $ref: "#/getDefinitions/network-policies"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/generic-vnfs/generic-vnf/{vnf-id}/relationship-list/relationship:
@@ -27259,9 +34055,10 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -27286,6 +34083,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -27307,19 +34105,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -27344,16 +34145,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -27375,24 +34179,28 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -27417,21 +34225,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -27446,7 +34258,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -27455,21 +34267,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -27599,7 +34415,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -27616,27 +34435,88 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -27658,21 +34538,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -27699,24 +34583,28 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -27741,21 +34629,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -27770,7 +34662,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -27779,21 +34671,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -27923,7 +34819,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -27940,27 +34839,88 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -27982,21 +34942,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -28016,7 +34980,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -28025,16 +34989,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: vnf-name
in: query
description: Name of VNF.
@@ -28148,7 +35115,10 @@ paths:
tags:
- Network
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -28165,22 +35135,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- Network
@@ -28202,16 +35226,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -28231,7 +35258,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -28240,11 +35267,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -28364,19 +35393,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -28401,16 +35433,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -28425,7 +35460,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -28434,16 +35469,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -28566,7 +35604,10 @@ paths:
tags:
- Network
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -28583,22 +35624,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- Network
@@ -28620,16 +35715,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -28649,7 +35747,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -28658,11 +35756,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -28782,14 +35882,16 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -28814,11 +35916,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -28840,19 +35944,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -28877,16 +35984,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -28901,7 +36011,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -28910,16 +36020,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -29038,7 +36151,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -29055,22 +36171,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -29092,16 +36262,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -29128,19 +36301,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -29165,16 +36341,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -29189,7 +36368,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -29198,16 +36377,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -29326,7 +36508,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -29343,22 +36528,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -29380,16 +36619,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -29409,7 +36651,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -29418,11 +36660,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -29525,7 +36769,10 @@ paths:
tags:
- Network
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterface
consumes:
- application/json
@@ -29542,17 +36789,64 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- Network
@@ -29574,11 +36868,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -29598,7 +36894,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -29607,6 +36903,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -29711,14 +37008,16 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -29743,11 +37042,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -29769,24 +37070,28 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -29811,21 +37116,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -29847,29 +37156,34 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -29894,26 +37208,31 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -29928,7 +37247,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -29937,26 +37256,31 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -30096,7 +37420,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -30113,32 +37440,100 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -30160,26 +37555,31 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -30206,29 +37606,34 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -30253,26 +37658,31 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -30287,7 +37697,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -30296,26 +37706,31 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -30455,7 +37870,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -30472,32 +37890,100 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -30519,26 +38005,31 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -30558,7 +38049,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -30567,21 +38058,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: vnf-name
in: query
description: Name of VNF.
@@ -30705,7 +38200,10 @@ paths:
tags:
- Network
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -30722,27 +38220,88 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- Network
@@ -30764,21 +38323,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -30798,7 +38361,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -30807,16 +38370,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -30946,24 +38512,28 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -30988,21 +38558,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -31017,7 +38591,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -31026,21 +38600,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -31173,7 +38751,10 @@ paths:
tags:
- Network
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -31190,27 +38771,88 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- Network
@@ -31232,21 +38874,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -31266,7 +38912,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -31275,16 +38921,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -31414,19 +39063,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -31451,16 +39103,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -31482,24 +39137,28 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -31524,21 +39183,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -31553,7 +39216,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -31562,21 +39225,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -31705,7 +39372,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -31722,27 +39392,88 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -31764,21 +39495,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -31805,24 +39540,28 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -31847,21 +39586,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -31876,7 +39619,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -31885,21 +39628,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -32028,7 +39775,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -32045,27 +39795,88 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -32087,21 +39898,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -32121,7 +39936,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -32130,16 +39945,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -32252,7 +40070,10 @@ paths:
tags:
- Network
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface
consumes:
- application/json
@@ -32269,22 +40090,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- Network
@@ -32306,16 +40181,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -32335,7 +40213,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -32344,11 +40222,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -32456,7 +40336,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interface"
+ $ref: "#/getDefinitions/lag-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -32465,11 +40345,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -32567,7 +40449,10 @@ paths:
tags:
- Network
summary: create or update an existing lag-interface
- description: create or update an existing lag-interface
+ description: |
+ Create or update an existing lag-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterface
consumes:
- application/json
@@ -32584,17 +40469,64 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: lag-interface object that needs to be created or updated
+ description: lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/lag-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing lag-interface
+ description: |
+ Update an existing lag-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: lag-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/lag-interface"
delete:
tags:
- Network
@@ -32616,11 +40548,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -32640,7 +40574,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interfaces"
+ $ref: "#/getDefinitions/lag-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -32649,6 +40583,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -32753,14 +40688,16 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vf-module-id
in: path
description: Unique ID of vf-module.
required: true
type: string
+ example: __VF-MODULE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfVfModulesVfModule.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -32785,11 +40722,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vf-module-id
in: path
description: Unique ID of vf-module.
required: true
type: string
+ example: __VF-MODULE-ID__
/network/generic-vnfs/generic-vnf/{vnf-id}/vf-modules/vf-module/{vf-module-id}:
get:
tags:
@@ -32804,7 +40743,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vf-module"
+ $ref: "#/getDefinitions/vf-module"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -32813,11 +40752,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vf-module-id
in: path
description: Unique ID of vf-module.
required: true
type: string
+ example: __VF-MODULE-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -32940,7 +40881,10 @@ paths:
tags:
- Network
summary: create or update an existing vf-module
- description: create or update an existing vf-module
+ description: |
+ Create or update an existing vf-module.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfVfModulesVfModule
consumes:
- application/json
@@ -32957,17 +40901,64 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vf-module-id
in: path
description: Unique ID of vf-module.
required: true
type: string
+ example: __VF-MODULE-ID__
- name: body
in: body
- description: vf-module object that needs to be created or updated
+ description: vf-module object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfVfModulesVfModule.json)
required: true
schema:
$ref: "#/definitions/vf-module"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vf-module
+ description: |
+ Update an existing vf-module
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfVfModulesVfModule
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: vf-module-id
+ in: path
+ description: Unique ID of vf-module.
+ required: true
+ type: string
+ example: __VF-MODULE-ID__
+ - name: body
+ in: body
+ description: vf-module object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vf-module"
delete:
tags:
- Network
@@ -32989,11 +40980,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vf-module-id
in: path
description: Unique ID of vf-module.
required: true
type: string
+ example: __VF-MODULE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -33013,7 +41006,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vf-modules"
+ $ref: "#/getDefinitions/vf-modules"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -33022,6 +41015,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -33126,19 +41120,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the license group the resource belongs to, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of a license resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLicensesLicense.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -33163,16 +41160,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the license group the resource belongs to, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of a license resource.
required: true
type: string
+ example: __RESOURCE-UUID__
/network/generic-vnfs/generic-vnf/{vnf-id}/licenses/license/{group-uuid}/{resource-uuid}:
get:
tags:
@@ -33187,7 +41187,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/license"
+ $ref: "#/getDefinitions/license"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -33196,16 +41196,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the license group the resource belongs to, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of a license resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -33293,7 +41296,10 @@ paths:
tags:
- Network
summary: create or update an existing license
- description: create or update an existing license
+ description: |
+ Create or update an existing license.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLicensesLicense
consumes:
- application/json
@@ -33310,22 +41316,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the license group the resource belongs to, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of a license resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: body
in: body
- description: license object that needs to be created or updated
+ description: license object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfLicensesLicense.json)
required: true
schema:
$ref: "#/definitions/license"
+ patch:
+ tags:
+ - Network
+ summary: update an existing license
+ description: |
+ Update an existing license
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLicensesLicense
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: group-uuid
+ in: path
+ description: Unique ID for the license group the resource belongs to, should be uuid.
+ required: true
+ type: string
+ example: __GROUP-UUID__
+ - name: resource-uuid
+ in: path
+ description: Unique ID of a license resource.
+ required: true
+ type: string
+ example: __RESOURCE-UUID__
+ - name: body
+ in: body
+ description: license object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/license"
delete:
tags:
- Network
@@ -33347,16 +41407,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the license group the resource belongs to, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of a license resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -33376,7 +41439,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/licenses"
+ $ref: "#/getDefinitions/licenses"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -33385,6 +41448,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -33489,19 +41553,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the entitlement group the resource comes from, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of an entitlement resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfEntitlementsEntitlement.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -33526,16 +41593,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the entitlement group the resource comes from, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of an entitlement resource.
required: true
type: string
+ example: __RESOURCE-UUID__
/network/generic-vnfs/generic-vnf/{vnf-id}/entitlements/entitlement/{group-uuid}/{resource-uuid}:
get:
tags:
@@ -33550,7 +41620,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/entitlement"
+ $ref: "#/getDefinitions/entitlement"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -33559,16 +41629,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the entitlement group the resource comes from, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of an entitlement resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -33656,7 +41729,10 @@ paths:
tags:
- Network
summary: create or update an existing entitlement
- description: create or update an existing entitlement
+ description: |
+ Create or update an existing entitlement.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfEntitlementsEntitlement
consumes:
- application/json
@@ -33673,22 +41749,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the entitlement group the resource comes from, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of an entitlement resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: body
in: body
- description: entitlement object that needs to be created or updated
+ description: entitlement object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnfEntitlementsEntitlement.json)
required: true
schema:
$ref: "#/definitions/entitlement"
+ patch:
+ tags:
+ - Network
+ summary: update an existing entitlement
+ description: |
+ Update an existing entitlement
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfEntitlementsEntitlement
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: group-uuid
+ in: path
+ description: Unique ID for the entitlement group the resource comes from, should be uuid.
+ required: true
+ type: string
+ example: __GROUP-UUID__
+ - name: resource-uuid
+ in: path
+ description: Unique ID of an entitlement resource.
+ required: true
+ type: string
+ example: __RESOURCE-UUID__
+ - name: body
+ in: body
+ description: entitlement object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/entitlement"
delete:
tags:
- Network
@@ -33710,16 +41840,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the entitlement group the resource comes from, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of an entitlement resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -33739,7 +41872,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/entitlements"
+ $ref: "#/getDefinitions/entitlements"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -33748,6 +41881,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -33845,7 +41979,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/generic-vnf"
+ $ref: "#/getDefinitions/generic-vnf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -33854,6 +41988,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -33941,7 +42076,10 @@ paths:
tags:
- Network
summary: create or update an existing generic-vnf
- description: create or update an existing generic-vnf
+ description: |
+ Create or update an existing generic-vnf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnf
consumes:
- application/json
@@ -33958,12 +42096,52 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: body
in: body
- description: generic-vnf object that needs to be created or updated
+ description: generic-vnf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkGenericVnfsGenericVnf.json)
required: true
schema:
$ref: "#/definitions/generic-vnf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing generic-vnf
+ description: |
+ Update an existing generic-vnf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: body
+ in: body
+ description: generic-vnf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/generic-vnf"
delete:
tags:
- Network
@@ -33985,6 +42163,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -34004,7 +42183,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/generic-vnfs"
+ $ref: "#/getDefinitions/generic-vnfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/lag-links/lag-link/{link-name}/relationship-list/relationship:
@@ -34028,9 +42207,10 @@ paths:
description: Alphabetical concatenation of lag-interface names
required: true
type: string
+ example: __LINK-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkLagLinksLagLink.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -34055,6 +42235,7 @@ paths:
description: Alphabetical concatenation of lag-interface names
required: true
type: string
+ example: __LINK-NAME__
/network/lag-links/lag-link/{link-name}:
get:
tags:
@@ -34069,7 +42250,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-link"
+ $ref: "#/getDefinitions/lag-link"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -34078,11 +42259,15 @@ paths:
description: Alphabetical concatenation of lag-interface names
required: true
type: string
+ example: __LINK-NAME__
put:
tags:
- Network
summary: create or update an existing lag-link
- description: create or update an existing lag-link
+ description: |
+ Create or update an existing lag-link.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkLagLinksLagLink
consumes:
- application/json
@@ -34099,12 +42284,52 @@ paths:
description: Alphabetical concatenation of lag-interface names
required: true
type: string
+ example: __LINK-NAME__
- name: body
in: body
- description: lag-link object that needs to be created or updated
+ description: lag-link object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkLagLinksLagLink.json)
required: true
schema:
$ref: "#/definitions/lag-link"
+ patch:
+ tags:
+ - Network
+ summary: update an existing lag-link
+ description: |
+ Update an existing lag-link
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkLagLinksLagLink
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: link-name
+ in: path
+ description: Alphabetical concatenation of lag-interface names
+ required: true
+ type: string
+ example: __LINK-NAME__
+ - name: body
+ in: body
+ description: lag-link object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/lag-link"
delete:
tags:
- Network
@@ -34126,6 +42351,7 @@ paths:
description: Alphabetical concatenation of lag-interface names
required: true
type: string
+ example: __LINK-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -34145,7 +42371,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-links"
+ $ref: "#/getDefinitions/lag-links"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/newvces/newvce/{vnf-id2}/relationship-list/relationship:
@@ -34169,9 +42395,10 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvce.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -34196,6 +42423,7 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -34217,19 +42445,22 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -34254,16 +42485,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -34285,24 +42519,28 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -34327,21 +42565,25 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -34356,7 +42598,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -34365,21 +42607,25 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -34451,7 +42697,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -34468,27 +42717,88 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -34510,21 +42820,25 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -34551,24 +42865,28 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -34593,21 +42911,25 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -34622,7 +42944,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -34631,21 +42953,25 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -34717,7 +43043,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -34734,27 +43063,88 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -34776,21 +43166,25 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -34810,7 +43204,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -34819,16 +43213,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: vnf-name
in: query
description: Name of VNF.
@@ -34884,7 +43281,10 @@ paths:
tags:
- Network
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -34901,22 +43301,76 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- Network
@@ -34938,16 +43392,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -34967,7 +43424,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -34976,11 +43433,13 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -35042,19 +43501,22 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -35079,16 +43541,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -35103,7 +43568,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -35112,16 +43577,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -35186,7 +43654,10 @@ paths:
tags:
- Network
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -35203,22 +43674,76 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- Network
@@ -35240,16 +43765,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -35269,7 +43797,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -35278,11 +43806,13 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -35344,14 +43874,16 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -35376,11 +43908,13 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -35402,19 +43936,22 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -35439,16 +43976,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -35463,7 +44003,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -35472,16 +44012,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -35542,7 +44085,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -35559,22 +44105,76 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -35596,16 +44196,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -35632,19 +44235,22 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -35669,16 +44275,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -35693,7 +44302,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -35702,16 +44311,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -35772,7 +44384,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -35789,22 +44404,76 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -35826,16 +44495,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -35855,7 +44527,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -35864,11 +44536,13 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -35913,7 +44587,10 @@ paths:
tags:
- Network
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterface
consumes:
- application/json
@@ -35930,17 +44607,64 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- Network
@@ -35962,11 +44686,13 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -35986,7 +44712,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -35995,6 +44721,7 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: vnf-name
in: query
description: Name of VNF.
@@ -36034,7 +44761,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/newvce"
+ $ref: "#/getDefinitions/newvce"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -36043,6 +44770,7 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: vnf-name
in: query
description: Name of VNF.
@@ -36072,7 +44800,10 @@ paths:
tags:
- Network
summary: create or update an existing newvce
- description: create or update an existing newvce
+ description: |
+ Create or update an existing newvce.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvce
consumes:
- application/json
@@ -36089,12 +44820,52 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: body
in: body
- description: newvce object that needs to be created or updated
+ description: newvce object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkNewvcesNewvce.json)
required: true
schema:
$ref: "#/definitions/newvce"
+ patch:
+ tags:
+ - Network
+ summary: update an existing newvce
+ description: |
+ Update an existing newvce
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvce
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: body
+ in: body
+ description: newvce object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/newvce"
delete:
tags:
- Network
@@ -36116,6 +44887,7 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -36135,7 +44907,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/newvces"
+ $ref: "#/getDefinitions/newvces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/pnfs/pnf/{pnf-name}/relationship-list/relationship:
@@ -36159,9 +44931,10 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -36186,6 +44959,7 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/relationship-list/relationship:
put:
tags:
@@ -36207,14 +44981,16 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -36239,11 +45015,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/sriov-pfs/sriov-pf/{pf-pci-id}/relationship-list/relationship:
put:
tags:
@@ -36265,19 +45043,22 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pf-pci-id
in: path
description: Identifier for the sriov-pf
required: true
type: string
+ example: __PF-PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceSriovPfsSriovPf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -36302,16 +45083,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pf-pci-id
in: path
description: Identifier for the sriov-pf
required: true
type: string
+ example: __PF-PCI-ID__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/sriov-pfs/sriov-pf/{pf-pci-id}:
get:
tags:
@@ -36326,7 +45110,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-pf"
+ $ref: "#/getDefinitions/sriov-pf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -36335,16 +45119,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pf-pci-id
in: path
description: Identifier for the sriov-pf
required: true
type: string
+ example: __PF-PCI-ID__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -36359,7 +45146,10 @@ paths:
tags:
- Network
summary: create or update an existing sriov-pf
- description: create or update an existing sriov-pf
+ description: |
+ Create or update an existing sriov-pf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceSriovPfsSriovPf
consumes:
- application/json
@@ -36376,22 +45166,76 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pf-pci-id
in: path
description: Identifier for the sriov-pf
required: true
type: string
+ example: __PF-PCI-ID__
- name: body
in: body
- description: sriov-pf object that needs to be created or updated
+ description: sriov-pf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceSriovPfsSriovPf.json)
required: true
schema:
$ref: "#/definitions/sriov-pf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing sriov-pf
+ description: |
+ Update an existing sriov-pf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceSriovPfsSriovPf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pf-pci-id
+ in: path
+ description: Identifier for the sriov-pf
+ required: true
+ type: string
+ example: __PF-PCI-ID__
+ - name: body
+ in: body
+ description: sriov-pf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-pf"
delete:
tags:
- Network
@@ -36413,16 +45257,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pf-pci-id
in: path
description: Identifier for the sriov-pf
required: true
type: string
+ example: __PF-PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -36442,7 +45289,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-pfs"
+ $ref: "#/getDefinitions/sriov-pfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -36451,11 +45298,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -36487,24 +45336,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -36529,21 +45382,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -36565,29 +45422,34 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -36612,26 +45474,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -36646,7 +45513,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -36655,26 +45522,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -36731,7 +45603,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -36748,32 +45623,100 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -36795,26 +45738,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -36841,29 +45789,34 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -36888,26 +45841,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -36922,7 +45880,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -36931,26 +45889,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -37007,7 +45970,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -37024,32 +45990,100 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -37071,26 +46105,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -37110,7 +46149,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -37119,21 +46158,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -37174,7 +46217,10 @@ paths:
tags:
- Network
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -37191,27 +46237,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- Network
@@ -37233,21 +46340,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -37267,7 +46378,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -37276,16 +46387,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -37332,24 +46446,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -37374,21 +46492,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -37403,7 +46525,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -37412,21 +46534,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -37476,7 +46602,10 @@ paths:
tags:
- Network
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -37493,27 +46622,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- Network
@@ -37535,21 +46725,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -37569,7 +46763,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -37578,16 +46772,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -37634,19 +46831,22 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -37671,16 +46871,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -37702,24 +46905,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -37744,21 +46951,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -37773,7 +46984,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -37782,21 +46993,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -37842,7 +47057,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -37859,27 +47077,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -37901,21 +47180,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -37942,24 +47225,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -37984,21 +47271,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -38013,7 +47304,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -38022,21 +47313,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -38082,7 +47377,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -38099,27 +47397,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -38141,21 +47500,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -38175,7 +47538,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -38184,16 +47547,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -38223,7 +47589,10 @@ paths:
tags:
- Network
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface
consumes:
- application/json
@@ -38240,22 +47609,76 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- Network
@@ -38277,16 +47700,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -38306,7 +47732,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -38315,11 +47741,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -38344,7 +47772,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/p-interface"
+ $ref: "#/getDefinitions/p-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -38353,11 +47781,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -38372,7 +47802,10 @@ paths:
tags:
- Network
summary: create or update an existing p-interface
- description: create or update an existing p-interface
+ description: |
+ Create or update an existing p-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterface
consumes:
- application/json
@@ -38389,17 +47822,64 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: p-interface object that needs to be created or updated
+ description: p-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfPInterfacesPInterface.json)
required: true
schema:
$ref: "#/definitions/p-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing p-interface
+ description: |
+ Update an existing p-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: p-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/p-interface"
delete:
tags:
- Network
@@ -38421,11 +47901,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -38445,7 +47927,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/p-interfaces"
+ $ref: "#/getDefinitions/p-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -38454,6 +47936,7 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -38480,14 +47963,16 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -38512,11 +47997,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -38538,24 +48025,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -38580,21 +48071,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -38616,29 +48111,34 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -38663,26 +48163,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -38697,7 +48202,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -38706,26 +48211,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -38787,7 +48297,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -38804,32 +48317,100 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -38851,26 +48432,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -38897,29 +48483,34 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -38944,26 +48535,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -38978,7 +48574,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -38987,26 +48583,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -39068,7 +48669,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -39085,32 +48689,100 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -39132,26 +48804,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -39171,7 +48848,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -39180,21 +48857,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -39240,7 +48921,10 @@ paths:
tags:
- Network
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -39257,27 +48941,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- Network
@@ -39299,21 +49044,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -39333,7 +49082,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -39342,16 +49091,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -39403,24 +49155,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -39445,21 +49201,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -39474,7 +49234,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -39483,21 +49243,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -39552,7 +49316,10 @@ paths:
tags:
- Network
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -39569,27 +49336,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- Network
@@ -39611,21 +49439,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -39645,7 +49477,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -39654,16 +49486,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -39715,19 +49550,22 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -39752,16 +49590,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -39783,24 +49624,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -39825,21 +49670,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -39854,7 +49703,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -39863,21 +49712,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -39928,7 +49781,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -39945,27 +49801,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -39987,21 +49904,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -40028,24 +49949,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -40070,21 +49995,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -40099,7 +50028,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -40108,21 +50037,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -40173,7 +50106,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -40190,27 +50126,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -40232,21 +50229,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -40266,7 +50267,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -40275,16 +50276,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -40319,7 +50323,10 @@ paths:
tags:
- Network
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface
consumes:
- application/json
@@ -40336,22 +50343,76 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- Network
@@ -40373,16 +50434,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -40402,7 +50466,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -40411,11 +50475,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -40445,7 +50511,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interface"
+ $ref: "#/getDefinitions/lag-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -40454,11 +50520,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -40478,7 +50546,10 @@ paths:
tags:
- Network
summary: create or update an existing lag-interface
- description: create or update an existing lag-interface
+ description: |
+ Create or update an existing lag-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterface
consumes:
- application/json
@@ -40495,17 +50566,64 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: lag-interface object that needs to be created or updated
+ description: lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnfLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/lag-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing lag-interface
+ description: |
+ Update an existing lag-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: lag-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/lag-interface"
delete:
tags:
- Network
@@ -40527,11 +50645,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -40551,7 +50671,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interfaces"
+ $ref: "#/getDefinitions/lag-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -40560,6 +50680,7 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -40579,7 +50700,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/pnf"
+ $ref: "#/getDefinitions/pnf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -40588,6 +50709,7 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -40597,7 +50719,10 @@ paths:
tags:
- Network
summary: create or update an existing pnf
- description: create or update an existing pnf
+ description: |
+ Create or update an existing pnf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnf
consumes:
- application/json
@@ -40614,12 +50739,52 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: body
in: body
- description: pnf object that needs to be created or updated
+ description: pnf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPnfsPnf.json)
required: true
schema:
$ref: "#/definitions/pnf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing pnf
+ description: |
+ Update an existing pnf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: body
+ in: body
+ description: pnf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/pnf"
delete:
tags:
- Network
@@ -40641,6 +50806,7 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -40660,7 +50826,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/pnfs"
+ $ref: "#/getDefinitions/pnfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/physical-links/physical-link/{link-name}/relationship-list/relationship:
@@ -40684,9 +50850,10 @@ paths:
description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPhysicalLinksPhysicalLink.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -40711,6 +50878,7 @@ paths:
description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
required: true
type: string
+ example: __LINK-NAME__
/network/physical-links/physical-link/{link-name}:
get:
tags:
@@ -40725,7 +50893,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/physical-link"
+ $ref: "#/getDefinitions/physical-link"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -40734,6 +50902,7 @@ paths:
description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: circuit-id
in: query
description: Circuit it
@@ -40743,7 +50912,10 @@ paths:
tags:
- Network
summary: create or update an existing physical-link
- description: create or update an existing physical-link
+ description: |
+ Create or update an existing physical-link.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPhysicalLinksPhysicalLink
consumes:
- application/json
@@ -40760,12 +50932,52 @@ paths:
description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: body
in: body
- description: physical-link object that needs to be created or updated
+ description: physical-link object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkPhysicalLinksPhysicalLink.json)
required: true
schema:
$ref: "#/definitions/physical-link"
+ patch:
+ tags:
+ - Network
+ summary: update an existing physical-link
+ description: |
+ Update an existing physical-link
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPhysicalLinksPhysicalLink
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: link-name
+ in: path
+ description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
+ required: true
+ type: string
+ example: __LINK-NAME__
+ - name: body
+ in: body
+ description: physical-link object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/physical-link"
delete:
tags:
- Network
@@ -40787,6 +50999,7 @@ paths:
description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -40806,7 +51019,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/physical-links"
+ $ref: "#/getDefinitions/physical-links"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}/relationship-list/relationship:
@@ -40830,9 +51043,10 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkIpsecConfigurationsIpsecConfiguration.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -40857,6 +51071,7 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
/network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}/vig-servers/vig-server/{vig-address-type}/relationship-list/relationship:
put:
tags:
@@ -40878,14 +51093,16 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: vig-address-type
in: path
description: indicates whether the VIG is for AVPN or INTERNET
required: true
type: string
+ example: __VIG-ADDRESS-TYPE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -40910,11 +51127,13 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: vig-address-type
in: path
description: indicates whether the VIG is for AVPN or INTERNET
required: true
type: string
+ example: __VIG-ADDRESS-TYPE__
/network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}/vig-servers/vig-server/{vig-address-type}:
get:
tags:
@@ -40929,7 +51148,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vig-server"
+ $ref: "#/getDefinitions/vig-server"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -40938,16 +51157,21 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: vig-address-type
in: path
description: indicates whether the VIG is for AVPN or INTERNET
required: true
type: string
+ example: __VIG-ADDRESS-TYPE__
put:
tags:
- Network
summary: create or update an existing vig-server
- description: create or update an existing vig-server
+ description: |
+ Create or update an existing vig-server.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer
consumes:
- application/json
@@ -40964,17 +51188,64 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: vig-address-type
in: path
description: indicates whether the VIG is for AVPN or INTERNET
required: true
type: string
+ example: __VIG-ADDRESS-TYPE__
- name: body
in: body
- description: vig-server object that needs to be created or updated
+ description: vig-server object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer.json)
required: true
schema:
$ref: "#/definitions/vig-server"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vig-server
+ description: |
+ Update an existing vig-server
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: ipsec-configuration-id
+ in: path
+ description: UUID of this configuration
+ required: true
+ type: string
+ example: __IPSEC-CONFIGURATION-ID__
+ - name: vig-address-type
+ in: path
+ description: indicates whether the VIG is for AVPN or INTERNET
+ required: true
+ type: string
+ example: __VIG-ADDRESS-TYPE__
+ - name: body
+ in: body
+ description: vig-server object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vig-server"
delete:
tags:
- Network
@@ -40996,11 +51267,13 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: vig-address-type
in: path
description: indicates whether the VIG is for AVPN or INTERNET
required: true
type: string
+ example: __VIG-ADDRESS-TYPE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -41020,7 +51293,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vig-servers"
+ $ref: "#/getDefinitions/vig-servers"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -41029,6 +51302,7 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
/network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}:
get:
tags:
@@ -41043,7 +51317,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/ipsec-configuration"
+ $ref: "#/getDefinitions/ipsec-configuration"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -41052,11 +51326,15 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
put:
tags:
- Network
summary: create or update an existing ipsec-configuration
- description: create or update an existing ipsec-configuration
+ description: |
+ Create or update an existing ipsec-configuration.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkIpsecConfigurationsIpsecConfiguration
consumes:
- application/json
@@ -41073,12 +51351,52 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: body
in: body
- description: ipsec-configuration object that needs to be created or updated
+ description: ipsec-configuration object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkIpsecConfigurationsIpsecConfiguration.json)
required: true
schema:
$ref: "#/definitions/ipsec-configuration"
+ patch:
+ tags:
+ - Network
+ summary: update an existing ipsec-configuration
+ description: |
+ Update an existing ipsec-configuration
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkIpsecConfigurationsIpsecConfiguration
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: ipsec-configuration-id
+ in: path
+ description: UUID of this configuration
+ required: true
+ type: string
+ example: __IPSEC-CONFIGURATION-ID__
+ - name: body
+ in: body
+ description: ipsec-configuration object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/ipsec-configuration"
delete:
tags:
- Network
@@ -41100,6 +51418,7 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -41119,7 +51438,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/ipsec-configurations"
+ $ref: "#/getDefinitions/ipsec-configurations"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/route-table-references/route-table-reference/{route-table-reference-id}/relationship-list/relationship:
@@ -41143,9 +51462,10 @@ paths:
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __ROUTE-TABLE-REFERENCE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkRouteTableReferencesRouteTableReference.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -41170,6 +51490,7 @@ paths:
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __ROUTE-TABLE-REFERENCE-ID__
/network/route-table-references/route-table-reference/{route-table-reference-id}:
get:
tags:
@@ -41184,7 +51505,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/route-table-reference"
+ $ref: "#/getDefinitions/route-table-reference"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -41193,6 +51514,7 @@ paths:
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __ROUTE-TABLE-REFERENCE-ID__
- name: route-table-reference-fqdn
in: query
description: FQDN entry in the route table.
@@ -41202,7 +51524,10 @@ paths:
tags:
- Network
summary: create or update an existing route-table-reference
- description: create or update an existing route-table-reference
+ description: |
+ Create or update an existing route-table-reference.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkRouteTableReferencesRouteTableReference
consumes:
- application/json
@@ -41219,12 +51544,52 @@ paths:
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __ROUTE-TABLE-REFERENCE-ID__
- name: body
in: body
- description: route-table-reference object that needs to be created or updated
+ description: route-table-reference object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkRouteTableReferencesRouteTableReference.json)
required: true
schema:
$ref: "#/definitions/route-table-reference"
+ patch:
+ tags:
+ - Network
+ summary: update an existing route-table-reference
+ description: |
+ Update an existing route-table-reference
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkRouteTableReferencesRouteTableReference
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: route-table-reference-id
+ in: path
+ description: Route Table Reference id, UUID assigned to this instance.
+ required: true
+ type: string
+ example: __ROUTE-TABLE-REFERENCE-ID__
+ - name: body
+ in: body
+ description: route-table-reference object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/route-table-reference"
delete:
tags:
- Network
@@ -41246,6 +51611,7 @@ paths:
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __ROUTE-TABLE-REFERENCE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -41265,7 +51631,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/route-table-references"
+ $ref: "#/getDefinitions/route-table-references"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/instance-groups/instance-group/{id}/relationship-list/relationship:
@@ -41289,9 +51655,10 @@ paths:
description: Instance Group ID, UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkInstanceGroupsInstanceGroup.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -41316,6 +51683,7 @@ paths:
description: Instance Group ID, UUID assigned to this instance.
required: true
type: string
+ example: __ID__
/network/instance-groups/instance-group/{id}:
get:
tags:
@@ -41330,7 +51698,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/instance-group"
+ $ref: "#/getDefinitions/instance-group"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -41339,6 +51707,7 @@ paths:
description: Instance Group ID, UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: description
in: query
description: Descriptive text to help identify the usage of this instance-group
@@ -41358,7 +51727,10 @@ paths:
tags:
- Network
summary: create or update an existing instance-group
- description: create or update an existing instance-group
+ description: |
+ Create or update an existing instance-group.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkInstanceGroupsInstanceGroup
consumes:
- application/json
@@ -41375,12 +51747,52 @@ paths:
description: Instance Group ID, UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: body
in: body
- description: instance-group object that needs to be created or updated
+ description: instance-group object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkInstanceGroupsInstanceGroup.json)
required: true
schema:
$ref: "#/definitions/instance-group"
+ patch:
+ tags:
+ - Network
+ summary: update an existing instance-group
+ description: |
+ Update an existing instance-group
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkInstanceGroupsInstanceGroup
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: id
+ in: path
+ description: Instance Group ID, UUID assigned to this instance.
+ required: true
+ type: string
+ example: __ID__
+ - name: body
+ in: body
+ description: instance-group object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/instance-group"
delete:
tags:
- Network
@@ -41402,6 +51814,7 @@ paths:
description: Instance Group ID, UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -41421,7 +51834,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/instance-groups"
+ $ref: "#/getDefinitions/instance-groups"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/zones/zone/{zone-id}/relationship-list/relationship:
@@ -41445,9 +51858,10 @@ paths:
description: Code assigned by AIC to the zone
required: true
type: string
+ example: __ZONE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkZonesZone.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -41472,6 +51886,7 @@ paths:
description: Code assigned by AIC to the zone
required: true
type: string
+ example: __ZONE-ID__
/network/zones/zone/{zone-id}:
get:
tags:
@@ -41486,7 +51901,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/zone"
+ $ref: "#/getDefinitions/zone"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -41495,6 +51910,7 @@ paths:
description: Code assigned by AIC to the zone
required: true
type: string
+ example: __ZONE-ID__
- name: design-type
in: query
description: Design of zone [Medium/Large?]
@@ -41509,7 +51925,10 @@ paths:
tags:
- Network
summary: create or update an existing zone
- description: create or update an existing zone
+ description: |
+ Create or update an existing zone.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkZonesZone
consumes:
- application/json
@@ -41526,12 +51945,52 @@ paths:
description: Code assigned by AIC to the zone
required: true
type: string
+ example: __ZONE-ID__
- name: body
in: body
- description: zone object that needs to be created or updated
+ description: zone object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkZonesZone.json)
required: true
schema:
$ref: "#/definitions/zone"
+ patch:
+ tags:
+ - Network
+ summary: update an existing zone
+ description: |
+ Update an existing zone
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkZonesZone
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: zone-id
+ in: path
+ description: Code assigned by AIC to the zone
+ required: true
+ type: string
+ example: __ZONE-ID__
+ - name: body
+ in: body
+ description: zone object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/zone"
delete:
tags:
- Network
@@ -41553,6 +52012,7 @@ paths:
description: Code assigned by AIC to the zone
required: true
type: string
+ example: __ZONE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -41572,24 +52032,413 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/zones"
+ $ref: "#/getDefinitions/zones"
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ /network/configurations/configuration/{configuration-id}/relationship-list/relationship:
+ put:
+ tags:
+ - Network
+ summary: see node definition for valid relationships
+ operationId: createOrUpdateNetworkConfigurationsConfigurationRelationshipListRelationship
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: configuration-id
+ in: path
+ description: UUID assigned to configuration.
+ required: true
+ type: string
+ example: __CONFIGURATION-ID__
+ - name: body
+ in: body
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkConfigurationsConfiguration.json)
+ required: true
+ schema:
+ $ref: "#/definitions/relationship"
+ delete:
+ tags:
+ - Network
+ summary: delete an existing relationship
+ description: delete an existing relationship
+ operationId: deleteNetworkConfigurationsConfigurationRelationshipListRelationship
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: configuration-id
+ in: path
+ description: UUID assigned to configuration.
+ required: true
+ type: string
+ example: __CONFIGURATION-ID__
+ /network/configurations/configuration/{configuration-id}/metadata/metadatum/{metaname}:
+ get:
+ tags:
+ - Network
+ summary: returns metadatum
+ description: returns metadatum
+ operationId: getNetworkConfigurationsConfigurationMetadataMetadatum
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "200":
+ description: successful operation
+ schema:
+ $ref: "#/getDefinitions/metadatum"
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: configuration-id
+ in: path
+ description: UUID assigned to configuration.
+ required: true
+ type: string
+ example: __CONFIGURATION-ID__
+ - name: metaname
+ in: path
+ required: true
+ type: string
+ example: __METANAME__
+ - name: model-invariant-id
+ in: query
+ description: the ASDC model id for this resource or service model.
+ required: false
+ type: string
+ - name: model-version-id
+ in: query
+ description: the ASDC model version for this resource or service model.
+ required: false
+ type: string
+ put:
+ tags:
+ - Network
+ summary: create or update an existing metadatum
+ description: |
+ Create or update an existing metadatum.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
+ operationId: createOrUpdateNetworkConfigurationsConfigurationMetadataMetadatum
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: configuration-id
+ in: path
+ description: UUID assigned to configuration.
+ required: true
+ type: string
+ example: __CONFIGURATION-ID__
+ - name: metaname
+ in: path
+ required: true
+ type: string
+ example: __METANAME__
+ - name: body
+ in: body
+ description: metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkConfigurationsConfigurationMetadataMetadatum.json)
+ required: true
+ schema:
+ $ref: "#/definitions/metadatum"
+ patch:
+ tags:
+ - Network
+ summary: update an existing metadatum
+ description: |
+ Update an existing metadatum
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkConfigurationsConfigurationMetadataMetadatum
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: configuration-id
+ in: path
+ description: UUID assigned to configuration.
+ required: true
+ type: string
+ example: __CONFIGURATION-ID__
+ - name: metaname
+ in: path
+ required: true
+ type: string
+ example: __METANAME__
+ - name: body
+ in: body
+ description: metadatum object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/metadatum"
+ delete:
+ tags:
+ - Network
+ summary: delete an existing metadatum
+ description: delete an existing metadatum
+ operationId: deleteNetworkConfigurationsConfigurationMetadataMetadatum
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: configuration-id
+ in: path
+ description: UUID assigned to configuration.
+ required: true
+ type: string
+ example: __CONFIGURATION-ID__
+ - name: metaname
+ in: path
+ required: true
+ type: string
+ example: __METANAME__
+ - name: resource-version
+ in: query
+ description: resource-version for concurrency
+ required: true
+ type: string
+ /network/configurations/configuration/{configuration-id}/metadata:
+ get:
+ tags:
+ - Network
+ summary: returns metadata
+ description: returns metadata
+ operationId: getNetworkConfigurationsConfigurationMetadata
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "200":
+ description: successful operation
+ schema:
+ $ref: "#/getDefinitions/metadata"
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: configuration-id
+ in: path
+ description: UUID assigned to configuration.
+ required: true
+ type: string
+ example: __CONFIGURATION-ID__
+ - name: model-invariant-id
+ in: query
+ description: the ASDC model id for this resource or service model.
+ required: false
+ type: string
+ - name: model-version-id
+ in: query
+ description: the ASDC model version for this resource or service model.
+ required: false
+ type: string
+ /network/configurations/configuration/{configuration-id}:
+ get:
+ tags:
+ - Network
+ summary: returns configuration
+ description: returns configuration
+ operationId: getNetworkConfigurationsConfiguration
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "200":
+ description: successful operation
+ schema:
+ $ref: "#/getDefinitions/configuration"
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: configuration-id
+ in: path
+ description: UUID assigned to configuration.
+ required: true
+ type: string
+ example: __CONFIGURATION-ID__
+ - name: model-invariant-id
+ in: query
+ description: the ASDC model id for this resource or service model.
+ required: false
+ type: string
+ - name: model-version-id
+ in: query
+ description: the ASDC model version for this resource or service model.
+ required: false
+ type: string
+ put:
+ tags:
+ - Network
+ summary: create or update an existing configuration
+ description: |
+ Create or update an existing configuration.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
+ operationId: createOrUpdateNetworkConfigurationsConfiguration
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: configuration-id
+ in: path
+ description: UUID assigned to configuration.
+ required: true
+ type: string
+ example: __CONFIGURATION-ID__
+ - name: body
+ in: body
+ description: configuration object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v11/NetworkConfigurationsConfiguration.json)
+ required: true
+ schema:
+ $ref: "#/definitions/configuration"
+ patch:
+ tags:
+ - Network
+ summary: update an existing configuration
+ description: |
+ Update an existing configuration
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkConfigurationsConfiguration
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: configuration-id
+ in: path
+ description: UUID assigned to configuration.
+ required: true
+ type: string
+ example: __CONFIGURATION-ID__
+ - name: body
+ in: body
+ description: configuration object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/configuration"
+ delete:
+ tags:
+ - Network
+ summary: delete an existing configuration
+ description: delete an existing configuration
+ operationId: deleteNetworkConfigurationsConfiguration
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: configuration-id
+ in: path
+ description: UUID assigned to configuration.
+ required: true
+ type: string
+ example: __CONFIGURATION-ID__
+ - name: resource-version
+ in: query
+ description: resource-version for concurrency
+ required: true
+ type: string
+ /network/configurations:
+ get:
+ tags:
+ - Network
+ summary: returns configurations
+ description: returns configurations
+ operationId: getNetworkConfigurations
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "200":
+ description: successful operation
+ schema:
+ $ref: "#/getDefinitions/configurations"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
definitions:
- search:
+ aai-internal:
properties:
- edge-tag-query-result:
- type: object
- $ref: "#/definitions/edge-tag-query-result"
- edge-tag-query-request:
- type: object
- $ref: "#/definitions/edge-tag-query-request"
- search-results:
- type: object
- $ref: "#/definitions/search-results"
- sdn-zone-response:
- type: object
- $ref: "#/definitions/sdn-zone-response"
+ property-name:
+ type: string
+ property-value:
+ type: string
+ action:
+ properties:
+ action-type:
+ type: string
+ action-data:
+ type: array
+ items:
+ $ref: "#/definitions/action-data"
+ action-data:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
actions:
description: |
APIs that are more action related than REST (e.g., notify, update).
@@ -41600,101 +52449,348 @@ definitions:
notify:
type: object
$ref: "#/definitions/notify"
- relationship-data:
+ allotted-resource:
+ description: |
+ Represents a slice or partial piece of a resource that gets separately allotted
+ ###### Related Nodes
+ - TO allotted-resource( allotted-resource tosca.relationships.network.BindsTo allotted-resource, ONE2ONE)
+ - TO generic-vnf( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY)
+ - TO instance-group( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO l3-network( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY)
+ - TO l-interface( allotted-resource org.onap.relationships.inventory.Uses l-interface, ONE2MANY)
+ - TO network-policy( allotted-resource org.onap.relationships.inventory.Uses network-policy, ONE2ONE)
+ - TO vlan( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY)
+ - TO vpn-binding( allotted-resource org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2MANY)
+ - TO service-instance( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM tunnel-xconnect( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)
+ - FROM configuration( configuration org.onap.relationships.inventory.Uses allotted-resource, ONE2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY)
+ - FROM allotted-resource( allotted-resource tosca.relationships.network.BindsTo allotted-resource, ONE2ONE)
+ - ALLOTTED-RESOURCE is DELETED when these are DELETED TUNNEL-XCONNECT
required:
- - relationship-key
- - relationship-value
+ - id
properties:
- relationship-key:
+ id:
type: string
- description: A keyword provided by A&AI to indicate an attribute.
- relationship-value:
+ description: Allotted Resource id UUID assigned to this instance.
+ description:
type: string
- description: Value of the attribute.
- related-to-property:
- properties:
- property-key:
+ description: The descriptive information assigned to this allotted resource instance
+ selflink:
type: string
- description: Key part of a key/value pair
- property-value:
+ description: Link back to more information in the controller
+ model-invariant-id:
type: string
- description: Value part of a key/value pair
- relationship:
- properties:
- related-to:
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
type: string
- description: A keyword provided by A&AI to indicate type of node.
- related-link:
+ description: the ASDC model version for this resource or service model.
+ persona-model-version:
type: string
- description: URL to the object in A&AI.
- relationship-data:
+ description: the ASDC model version for this resource or service model.
+ resource-version:
+ type: string
+ description: Concurrency value
+ orchestration-status:
+ type: string
+ description: Orchestration status
+ operational-status:
+ type: string
+ description: Indicator for whether the resource is considered operational
+ type:
+ type: string
+ description: Generic description of the type of allotted resource.
+ role:
+ type: string
+ description: role in the network that this resource will be providing.
+ tunnel-xconnects:
type: array
- items:
- $ref: "#/definitions/relationship-data"
- related-to-property:
+ items:
+ $ref: "#/definitions/tunnel-xconnect"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ allotted-resources:
+ description: |
+ This object is used to store slices of services being offered
+ properties:
+ allotted-resource:
type: array
items:
- $ref: "#/definitions/related-to-property"
- relationship-list:
+ $ref: "#/definitions/allotted-resource"
+ availability-zone:
+ description: |
+ Availability zone, a collection of compute hosts/pservers
+ ###### Related Nodes
+ - TO complex( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO service-capability( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - TO cloud-region( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM ctag-pool( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM dvs-switch( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - FROM pserver( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)
+ - FROM vce( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - AVAILABILITY-ZONE cannot be deleted if linked to CTAG-POOL,DVS-SWITCH,GENERIC-VNF,PSERVER,VCE
+ required:
+ - availability-zone-name
+ - hypervisor-type
properties:
- relationship:
+ availability-zone-name:
+ type: string
+ description: Name of the availability zone. Unique across a cloud region
+ hypervisor-type:
+ type: string
+ description: Type of hypervisor. Source of truth should define valid values.
+ operational-status:
+ type: string
+ description: State that indicates whether the availability zone should be used, etc. Source of truth should define valid values.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ availability-zones:
+ description: |
+ Collection of availability zones
+ properties:
+ availability-zone:
type: array
items:
+ $ref: "#/definitions/availability-zone"
+ az-and-dvs-switches:
+ properties:
+ dvs-switches:
+ type: object
+ $ref: "#/definitions/dvs-switches"
+ availability-zone:
+ type: object
+ $ref: "#/definitions/availability-zone"
+ business:
+ description: |
+ Namespace for business related constructs
+ properties:
+ connectors:
+ type: array
+ items:
+ $ref: "#/definitions/connector"
+ customers:
+ type: array
+ items:
+ $ref: "#/definitions/customer"
+ lines-of-business:
+ type: array
+ items:
+ $ref: "#/definitions/line-of-business"
+ owning-entities:
+ type: array
+ items:
+ $ref: "#/definitions/owning-entity"
+ platforms:
+ type: array
+ items:
+ $ref: "#/definitions/platform"
+ projects:
+ type: array
+ items:
+ $ref: "#/definitions/project"
+ class-of-service:
+ description: |
+ ###### Related Nodes
+ - TO site-pair( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)
+ required:
+ - cos
+ properties:
+ cos:
+ type: string
+ description: unique identifier of probe
+ probe-id:
+ type: string
+ description: identifier of probe
+ probe-type:
+ type: string
+ description: type of probe
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
$ref: "#/definitions/relationship"
- ctag-pool:
+ classes-of-service:
description: |
- A collection of C tags (vlan tags) grouped for a specific purpose.
+ class-of-service of probe
+ properties:
+ class-of-service:
+ type: array
+ items:
+ $ref: "#/definitions/class-of-service"
+ cloud-infrastructure:
+ description: |
+ Namespace for cloud infrastructure.
+ properties:
+ complexes:
+ type: array
+ items:
+ $ref: "#/definitions/complex"
+ cloud-regions:
+ type: array
+ items:
+ $ref: "#/definitions/cloud-region"
+ network-profiles:
+ type: array
+ items:
+ $ref: "#/definitions/network-profile"
+ pservers:
+ type: array
+ items:
+ $ref: "#/definitions/pserver"
+ virtual-data-centers:
+ type: array
+ items:
+ $ref: "#/definitions/virtual-data-center"
+ cloud-region:
+ description: |
+ cloud-region designates an installation of a cloud cluster or region or instantiation.
###### Related Nodes
- - TO availability-zone (Many2Many)
- - FROM complex (is composed of ctag-pool)
- - FROM vpls-pe
- - FROM generic-vnf
+ - TO esr-system-info (CHILD of cloud-region, cloud-region has esr-system-info, One2Many)
+ - TO complex( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO l3-network( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO zone( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM dvs-switch( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM flavor( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM group-assignment( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM image( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM snapshot( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM vip-ipv4-address-list( vip-ipv4-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM vip-ipv6-address-list( vip-ipv6-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM volume-group( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn cloud-region, MANY2MANY)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)
+ - CLOUD-REGION cannot be deleted if linked to DVS-SWITCH,FLAVOR,GROUP-ASSIGNMENT,IMAGE,OAM-NETWORK,SNAPSHOT,TENANT,VIP-IPV4-ADDRESS-LIST,VIP-IPV6-ADDRESS-LIST,VOLUME-GROUP
+ - CLOUD-REGION is DELETED when these are DELETED AVAILABILITY-ZONE
+ - CLOUD-REGION deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
required:
- - target-pe
- - availability-zone-name
- - ctag-pool-purpose
+ - cloud-owner
+ - cloud-region-id
+ - sriov-automation
properties:
- target-pe:
+ cloud-owner:
type: string
- description: The Target provider edge router
- availability-zone-name:
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ cloud-region-id:
type: string
- description: Name of the availability zone
- ctag-pool-purpose:
+ description: Identifier used by the vendor for the region. Second part of composite key
+ cloud-type:
type: string
- description: Describes what the intended purpose of this pool is.
- ctag-values:
+ description: Type of the cloud (e.g., openstack)
+ owner-defined-type:
type: string
- description: Comma separated list of ctags
+ description: Cloud-owner defined type indicator (e.g., dcp, lcp)
+ cloud-region-version:
+ type: string
+ description: Software version employed at the site. NOTE - THIS FIELD IS NOT KEPT UP TO DATE.
+ identity-url:
+ type: string
+ description: URL of the keystone identity service
+ cloud-zone:
+ type: string
+ description: Zone where the cloud is homed. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
+ complex-name:
+ type: string
+ description: complex name for cloud-region instance. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
+ sriov-automation:
+ type: boolean
+ cloud-extra-info:
+ type: string
+ description: ESR inputs extra information about the VIM or Cloud which will be decoded by MultiVIM.
+ cloud-epa-caps:
+ type: string
+ description: MultiVIM will discover and expose EPA capabilities.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ volume-groups:
+ type: array
+ items:
+ $ref: "#/definitions/volume-group"
+ tenants:
+ type: array
+ items:
+ $ref: "#/definitions/tenant"
+ flavors:
+ type: array
+ items:
+ $ref: "#/definitions/flavor"
+ group-assignments:
+ type: array
+ items:
+ $ref: "#/definitions/group-assignment"
+ snapshots:
+ type: array
+ items:
+ $ref: "#/definitions/snapshot"
+ images:
+ type: array
+ items:
+ $ref: "#/definitions/image"
+ dvs-switches:
+ type: array
+ items:
+ $ref: "#/definitions/dvs-switch"
+ oam-networks:
+ type: array
+ items:
+ $ref: "#/definitions/oam-network"
+ availability-zones:
+ type: array
+ items:
+ $ref: "#/definitions/availability-zone"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- ctag-pools:
+ esr-system-info-list:
+ type: array
+ items:
+ $ref: "#/definitions/esr-system-info"
+ vip-ipv4-address-list:
+ type: array
+ items:
+ $ref: "#/definitions/vip-ipv4-address-list"
+ vip-ipv6-address-list:
+ type: array
+ items:
+ $ref: "#/definitions/vip-ipv6-address-list"
+ cloud-regions:
properties:
- ctag-pool:
+ cloud-region:
type: array
items:
- $ref: "#/definitions/ctag-pool"
+ $ref: "#/definitions/cloud-region"
complex:
description: |
Collection of physical locations that can house cloud-regions.
###### Related Nodes
- - TO ctag-pool (comprises complex, Many2Many)
- - TO l3-network (Many2Many)
- - FROM availability-zone
- - FROM cloud-region
- - FROM oam-network
- - FROM pserver
- - FROM pnf
- - FROM vce
- - FROM vpls-pe
- - FROM volume-group
- - FROM zone
- - FROM generic-vnf
+ - TO l3-network( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM ctag-pool( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)
+ - FROM pnf( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM vce( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)
+ - FROM volume-group( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM vpls-pe( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM zone( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - COMPLEX cannot be deleted if linked to AVAILABILITY-ZONE,CLOUD-REGION,GENERIC-VNF,OAM-NETWORK,PNF,PSERVER,VCE,VOLUME-GROUP,VPLS-PE,ZONE
+ - COMPLEX is DELETED when these are DELETED CTAG-POOL
required:
- physical-location-id
- physical-location-type
@@ -41760,41 +52856,59 @@ definitions:
type: array
items:
$ref: "#/definitions/complex"
- volume-group:
+ configuration:
description: |
- Persistent block-level storage.
+ Port Mirror Configuration.
###### Related Nodes
- - TO complex (Many2Many)
- - TO tenant (Many2Many)
- - FROM cloud-region (is composed of volume-group)
- - FROM vf-module
- - FROM generic-vnf
+ - TO allotted-resource( configuration org.onap.relationships.inventory.Uses allotted-resource, ONE2ONE)
+ - TO logical-link( configuration org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo configuration, MANY2ONE)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses configuration, ONE2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses configuration, ONE2MANY)
+ - CONFIGURATION is DELETED when these are DELETED METADATUM
+ - CONFIGURATION deletion means associated objects of these types are also DELETED:ALLOTTED-RESOURCE,LOGICAL-LINK
required:
- - volume-group-id
- - volume-group-name
- - vnf-type
+ - configuration-id
+ - configuration-type
+ - configuration-sub-type
+ - orchestration-status
+ - operational-status
+ - configuration-selflink
+ - model-customization-id
properties:
- volume-group-id:
+ configuration-id:
type: string
- description: Unique ID of volume-group.
- volume-group-name:
+ description: UUID assigned to configuration.
+ management-option:
type: string
- description: Name of the volume group.
- heat-stack-id:
+ description: Indicates the entity that will manage this feature. Could be an organization or the name of the application as well.
+ configuration-name:
type: string
- description: Heat stack id corresponding to this volume-group
- vnf-type:
+ description: Name of the configuration.
+ configuration-type:
type: string
- description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ description: port-mirroring-configuration.
+ configuration-sub-type:
+ type: string
+ description: vprobe, pprobe.
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
orchestration-status:
type: string
- description: Orchestration status of this volume-group
- model-customization-id:
+ description: Orchestration status of the configuration.
+ operational-status:
type: string
- description: captures the id of all the configuration used to customize the resource for the service.
- vf-module-model-customization-id:
+ description: Indicator for whether the resource is considered operational.
+ configuration-selflink:
type: string
- description: helps relate the volume group to the vf-module whose components will require the volume group
+ description: URL to endpoint where AAI can get more details from SDN-GC.
+ model-customization-id:
+ type: string
+ description: id of the configuration used to customize the resource
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
@@ -41802,478 +52916,640 @@ definitions:
type: array
items:
$ref: "#/definitions/relationship"
- volume-groups:
+ metadata:
+ type: array
+ items:
+ $ref: "#/definitions/metadatum"
+ configurations:
description: |
- Collection of persistent block-level storage.
+ Collection of configurations
properties:
- volume-group:
+ configuration:
type: array
items:
- $ref: "#/definitions/volume-group"
- volume:
+ $ref: "#/definitions/configuration"
+ connector:
description: |
- Ephemeral Block storage volume.
+ Collection of resource instances used to connect a variety of disparate inventory widgets
###### Related Nodes
- - FROM vserver (is composed of volume)
+ - TO virtual-data-center( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)
+ - CONNECTOR is DELETED when these are DELETED METADATUM
required:
- - volume-id
- - volume-selflink
+ - resource-instance-id
properties:
- volume-id:
- type: string
- description: Unique ID of block storage volume relative to the vserver.
- volume-selflink:
+ resource-instance-id:
type: string
- description: URL to endpoint where AAI can get more details
+ description: Unique id of resource instance.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- volumes:
+ metadata:
+ type: array
+ items:
+ $ref: "#/definitions/metadatum"
+ connectors:
description: |
- Collection of ephemeral Block storage volumes.
+ Collection of resource instances used to connect a variety of disparate inventory widgets
properties:
- volume:
+ connector:
type: array
items:
- $ref: "#/definitions/volume"
- l3-interface-ipv4-address-list:
+ $ref: "#/definitions/connector"
+ constrained-element-set:
description: |
- IPv4 Address Range
+ This is how we would capture constraints defining allowed sets of elements.
###### Related Nodes
- - TO instance-group (Many2Many)
- - TO l3-network (Many2Many)
- - TO subnet (Many2Many)
- - TO vnfc (is composed of l3-interface-ipv4-address-list, Many2One)
- - FROM l-interface (is composed of l3-interface-ipv4-address-list)
- - FROM vlan (is composed of l3-interface-ipv4-address-list)
+ - TO model-constraint( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)
+ - TO model-element( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM element-choice-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)
+ - CONSTRAINED-ELEMENT-SET is DELETED when these are DELETED ELEMENT-CHOICE-SET
required:
- - l3-interface-ipv4-address
+ - constrained-element-set-uuid
+ - constraint-type
+ - check-type
properties:
- l3-interface-ipv4-address:
+ constrained-element-set-uuid:
type: string
- description: IP address
- l3-interface-ipv4-prefix-length:
- type: integer
- format: int64
- description: Prefix length, 32 for single address
- vlan-id-inner:
- type: integer
- format: int64
- description: Inner VLAN tag
- vlan-id-outer:
- type: integer
- format: int64
- description: Outer VLAN tag
- is-floating:
- type: boolean
- description: Indicator of fixed or floating address
- resource-version:
+ constraint-type:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- neutron-network-id:
+ check-type:
type: string
- description: Neutron network id of the interface that address belongs to
- neutron-subnet-id:
+ resource-version:
type: string
- description: Neutron id of subnet that address belongs to
+ element-choice-sets:
+ type: array
+ items:
+ $ref: "#/definitions/element-choice-set"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- l3-interface-ipv6-address-list:
+ constrained-element-sets:
+ properties:
+ constrained-element-set:
+ type: array
+ items:
+ $ref: "#/definitions/constrained-element-set"
+ ctag-assignment:
description: |
- IPv6 Address Range
###### Related Nodes
- - TO instance-group (Many2Many)
- - TO l3-network (Many2Many)
- - TO subnet (Many2Many)
- - TO vnfc (is composed of l3-interface-ipv6-address-list, Many2One)
- - FROM l-interface (is composed of l3-interface-ipv6-address-list)
- - FROM vlan (is composed of l3-interface-ipv6-address-list)
+ - TO l3-network( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses ctag-assignment, ONE2MANY)
required:
- - l3-interface-ipv6-address
+ - vlan-id-inner
properties:
- l3-interface-ipv6-address:
- type: string
- description: IP address
- l3-interface-ipv6-prefix-length:
- type: integer
- format: int64
- description: Prefix length, 128 for single address
vlan-id-inner:
type: integer
format: int64
- description: Inner VLAN tag
- vlan-id-outer:
- type: integer
- format: int64
- description: Outer VLAN tag
- is-floating:
- type: boolean
- description: Indicator of fixed or floating address
+ description: id.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- neutron-network-id:
- type: string
- description: Neutron network id of the interface that address belongs to
- neutron-subnet-id:
- type: string
- description: Neutron id of subnet that address belongs to
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- vlan:
+ ctag-assignments:
+ properties:
+ ctag-assignment:
+ type: array
+ items:
+ $ref: "#/definitions/ctag-assignment"
+ ctag-pool:
description: |
- Definition of vlan
+ A collection of C tags (vlan tags) grouped for a specific purpose.
###### Related Nodes
- - TO l3-interface-ipv4-address-list (comprises vlan, Many2Many)
- - TO l3-interface-ipv6-address-list (comprises vlan, Many2Many)
- - TO multicast-configuration (Many2Many)
- - TO logical-link (Many2Many)
- - FROM l-interface (is composed of vlan)
- - FROM service-instance
- - FROM allotted-resource
+ - TO complex( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)
+ - TO availability-zone( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)
+ - FROM vpls-pe( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)
required:
- - vlan-interface
- - in-maint
- - is-ip-unnumbered
+ - target-pe
+ - availability-zone-name
+ - ctag-pool-purpose
properties:
- vlan-interface:
+ target-pe:
type: string
- description: String that identifies the interface
- vlan-id-inner:
- type: integer
- format: int64
- description: Inner VLAN tag
- vlan-id-outer:
- type: integer
- format: int64
- description: Outer VLAN tag
- resource-version:
+ description: The Target provider edge router
+ availability-zone-name:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- speed-value:
+ description: Name of the availability zone
+ ctag-pool-purpose:
type: string
- description: Captures the numeric part of the speed
- speed-units:
+ description: Describes what the intended purpose of this pool is.
+ ctag-values:
type: string
- description: Captures the units corresponding to the speed
- vlan-description:
+ description: Comma separated list of ctags
+ resource-version:
type: string
- description: Used to describe (the service associated with) the vlan
- backdoor-connection:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ ctag-pools:
+ properties:
+ ctag-pool:
+ type: array
+ items:
+ $ref: "#/definitions/ctag-pool"
+ customer:
+ description: |
+ customer identifiers to provide linkage back to BSS information.
+ ###### Related Nodes
+ - FROM service-subscription( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)
+ - CUSTOMER is DELETED when these are DELETED SERVICE-SUBSCRIPTION
+ required:
+ - global-customer-id
+ - subscriber-name
+ - subscriber-type
+ properties:
+ global-customer-id:
type: string
- description: Whether customer is going to use this VLAN for backdoor connection to another customer premise device.
- vpn-key:
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ subscriber-name:
type: string
- description: This indicates the customers VPN ID associated with this vlan
- orchestration-status:
+ description: Subscriber name, an alternate way to retrieve a customer.
+ subscriber-type:
type: string
- description: Status of a vnf's vlan interface, on which the customer circuit resides, mastered by SDN-C.
- in-maint:
- type: boolean
- prov-status:
+ description: Subscriber type, a way to provide VID with only the INFRA customers.
+ resource-version:
type: string
- description: Prov Status of the VLAN configuration related to a logical interface. Valid values [PREPROV/NVTPROV/PROV].
- is-ip-unnumbered:
- type: boolean
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ service-subscriptions:
+ type: array
+ items:
+ $ref: "#/definitions/service-subscription"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- l3-interface-ipv4-address-list:
+ customers:
+ description: |
+ Collection of customer identifiers to provide linkage back to BSS information.
+ properties:
+ customer:
type: array
items:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
- l3-interface-ipv6-address-list:
+ $ref: "#/definitions/customer"
+ cvlan-tag-entry:
+ required:
+ - cvlan-tag
+ properties:
+ cvlan-tag:
+ type: integer
+ format: int64
+ description: See mis-na-virtualization-platform.yang
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
- items:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
- vlans:
+ items:
+ $ref: "#/definitions/relationship"
+ cvlan-tags:
properties:
- vlan:
+ cvlan-tag-entry:
type: array
items:
- $ref: "#/definitions/vlan"
- sriov-vf:
+ $ref: "#/definitions/cvlan-tag-entry"
+ dvs-switch:
description: |
- SR-IOV Virtual Function (not to be confused with virtual network function)
+ Digital virtual switch metadata, used by SDN-C to configure VCEs. A&AI needs to receive this data from the PO deployment team and administer it using the provisioningTool.sh into A&AI.
###### Related Nodes
- - TO sriov-pf (Many2One)
- - FROM l-interface (is composed of sriov-vf)
+ - TO cloud-region( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO availability-zone( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
required:
- - pci-id
+ - switch-name
+ - vcenter-url
properties:
- pci-id:
- type: string
- description: PCI ID used to identify the sriov-vf
- vf-vlan-filter:
- type: string
- description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM.
- vf-mac-filter:
- type: string
- description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM.
- vf-vlan-strip:
- type: boolean
- description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM.
- vf-vlan-anti-spoof-check:
- type: boolean
- description: This option ensures anti VLAN spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
- vf-mac-anti-spoof-check:
- type: boolean
- description: This option ensures anti MAC spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
- vf-mirrors:
+ switch-name:
type: string
- description: This option defines the set of Mirror objects which essentially mirrors the traffic from source to set of collector VNF Ports.
- vf-broadcast-allow:
- type: boolean
- description: This option, if set to true, sets the VF in promiscuous mode and allows all broadcast traffic to reach the VM
- vf-unknown-multicast-allow:
- type: boolean
- description: This option, if set to true, sets the VF in promiscuous mode and allows unknown multicast traffic to reach the VM
- vf-unknown-unicast-allow:
- type: boolean
- description: This option, if set to true, sets the VF in promiscuous mode and allows unknown unicast traffic to reach the VM
- vf-insert-stag:
- type: boolean
- description: This option, if set to true, instructs to insert outer tag after traffic comes out of VM.
- vf-link-status:
+ description: DVS switch name
+ vcenter-url:
type: string
- description: This option is used to set the link status. Valid values as of 1607 are on, off, and auto.
+ description: URL used to reach the vcenter
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- neutron-network-id:
- type: string
- description: Neutron network id of the interface
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- sriov-vfs:
+ dvs-switches:
description: |
- Collection of SR-IOV Virtual Functions.
+ Collection of digital virtual switch metadata used for vmWare VCEs and GenericVnfs.
properties:
- sriov-vf:
+ dvs-switch:
type: array
items:
- $ref: "#/definitions/sriov-vf"
- l-interface:
+ $ref: "#/definitions/dvs-switch"
+ edge-prop-names:
description: |
- Logical interfaces, e.g., a vnic.
- ###### Related Nodes
- - TO instance-group (Many2Many)
- - TO l3-interface-ipv4-address-list (comprises l-interface, Many2Many)
- - TO l3-interface-ipv6-address-list (comprises l-interface, Many2Many)
- - TO l-interface (comprises l-interface, One2Many)
- - TO logical-link (Many2Many)
- - TO vlan (comprises l-interface, Many2Many)
- - TO sriov-vf (comprises l-interface, One2One)
- - FROM generic-vnf (is composed of l-interface)
- - FROM lag-interface (is composed of l-interface)
- - FROM newvce (is composed of l-interface)
- - FROM p-interface (is composed of l-interface)
- - FROM vserver (is composed of l-interface)
- - FROM allotted-resource
- - FROM l-interface (is composed of l-interface)
- required:
- - interface-name
- - is-port-mirrored
- - in-maint
- - is-ip-unnumbered
+ Internal map to define the properties of an edge and interpret the map EdgeRules
properties:
- interface-name:
+ edgeLabel:
type: string
- description: Name given to the interface
- interface-role:
+ direction:
type: string
- description: E.g., CUSTOMER, UPLINK, etc.
- v6-wan-link-ip:
+ multiplicityRule:
type: string
- description: Questionably placed - v6 ip addr of this interface (is in vr-lan-interface from Mary B.
- selflink:
+ contains-other-v:
type: string
- description: URL to endpoint where AAI can get more details
- interface-id:
+ delete-other-v:
type: string
- description: ID of interface
- macaddr:
+ SVC-INFRA:
type: string
- description: MAC address for the interface
- network-name:
+ prevent-delete:
type: string
- description: Name of the network
- management-option:
+ edge-tag-query-request:
+ properties:
+ edge-tag:
type: string
- description: Whether A&AI should be managing this interface of not. Could have value like CUSTOMER
- interface-description:
+ result-detail:
type: string
- description: Human friendly text regarding this interface.
- is-port-mirrored:
- type: boolean
- resource-version:
+ start-node-type:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- in-maint:
- type: boolean
- prov-status:
+ start-node-filter:
+ type: array
+ items:
+ $ref: "#/definitions/start-node-filter"
+ include-node-filter:
+ type: array
+ items:
+ $ref: "#/definitions/include-node-filter"
+ secondary-filter:
+ type: array
+ items:
+ $ref: "#/definitions/secondary-filter"
+ edge-tag-query-result:
+ properties:
+ tagged-inventory-item-list:
+ type: array
+ items:
+ $ref: "#/definitions/tagged-inventory-item-list"
+ element-choice-set:
+ description: |
+ This is how we would capture constraints defining allowed sets of elements.
+ ###### Related Nodes
+ - TO constrained-element-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)
+ - ELEMENT-CHOICE-SET is DELETED when these are DELETED MODEL-ELEMENT
+ required:
+ - element-choice-set-uuid
+ - element-choice-set-name
+ properties:
+ element-choice-set-uuid:
type: string
- description: Prov Status of the logical interface. Valid values [PREPROV/NVTPROV/PROV].
- is-ip-unnumbered:
- type: boolean
- allowed-address-pairs:
+ element-choice-set-name:
type: string
- description: Freeform field for storing an ip address, list of ip addresses or a subnet block.
- vlans:
+ cardinality:
+ type: string
+ resource-version:
+ type: string
+ model-elements:
type: array
items:
- $ref: "#/definitions/vlan"
- sriov-vfs:
+ $ref: "#/definitions/model-element"
+ relationship-list:
type: array
items:
- $ref: "#/definitions/sriov-vf"
- l-interfaces:
+ $ref: "#/definitions/relationship"
+ element-choice-sets:
+ properties:
+ element-choice-set:
type: array
- items:
- $ref: "#/definitions/l-interface"
+ items:
+ $ref: "#/definitions/element-choice-set"
+ entitlement:
+ description: |
+ Metadata for entitlement group.
+ ###### Related Nodes
+ - TO generic-vnf( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vce( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ required:
+ - group-uuid
+ - resource-uuid
+ properties:
+ group-uuid:
+ type: string
+ description: Unique ID for the entitlement group the resource comes from, should be uuid.
+ resource-uuid:
+ type: string
+ description: Unique ID of an entitlement resource.
+ resource-version:
+ type: string
+ description: Concurrency value
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- l3-interface-ipv4-address-list:
- type: array
- items:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
- l3-interface-ipv6-address-list:
+ entitlements:
+ description: |
+ Entitlements, keyed by group-uuid and resource-uuid, related to license management
+ properties:
+ entitlement:
type: array
items:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
- l-interfaces:
+ $ref: "#/definitions/entitlement"
+ esr-ems:
description: |
- Collection of logical interfaces.
+ Persist EMS address information used by EMS driver.
+ ###### Related Nodes
+ - TO esr-system-info (CHILD of esr-ems, esr-ems has esr-system-info, One2Many)
+ - ESR-EMS deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
+ required:
+ - ems-id
properties:
- l-interface:
+ ems-id:
+ type: string
+ description: Unique ID of EMS.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ esr-system-info-list:
+ type: object
+ $ref: "#/definitions/esr-system-info-list"
+ relationship-list:
+ type: object
+ $ref: "#/definitions/relationship-list"
+ esr-ems-list:
+ properties:
+ esr-ems:
type: array
items:
- $ref: "#/definitions/l-interface"
- vserver:
+ $ref: "#/definitions/esr-ems"
+ esr-system-info:
description: |
- Virtual Servers, aka virtual machine or VM.
+ Persist common address information of external systems.
###### Related Nodes
- - TO flavor (Many2One)
- - TO image (Many2One)
- - TO l-interface (comprises vserver, Many2Many)
- - TO pserver (Many2One)
- - TO volume (comprises vserver, Many2Many)
- - TO vnfc (Many2Many)
- - TO snapshot (One2One)
- - TO vf-module (Many2One)
- - FROM generic-vnf
- - FROM tenant (is composed of vserver)
- - FROM vce
+ - FROM esr-ems (PARENT of esr-system-info, esr-ems has esr-system-info)
+ - FROM esr-vnfm (PARENT of esr-system-info, esr-vnfm has esr-system-info)
+ - FROM esr-thirdparty-sdnc (PARENT of esr-system-info, esr-thirdparty-sdnc has esr-system-info)
+ - FROM cloud-region (PARENT of esr-system-info, cloud-region has esr-system-info)
required:
- - vserver-id
- - vserver-name
- - vserver-selflink
- - in-maint
- - is-closed-loop-disabled
+ - esr-system-info-id
+ - user-name
+ - password
+ - system-type
properties:
- vserver-id:
+ esr-system-info-id:
type: string
- description: Unique identifier for this vserver relative to its tenant
- vserver-name:
+ description: Unique ID of esr system info.
+ system-name:
type: string
- description: Name of vserver
- vserver-name2:
+ description: name of external system.
+ type:
type: string
- description: Alternative name of vserver
- prov-status:
+ description: type of external systems.
+ vendor:
type: string
- description: Trigger for operational monitoring of this resource by Service Assurance systems.
- vserver-selflink:
+ description: vendor of external systems.
+ version:
type: string
- description: URL to endpoint where AAI can get more details
- in-maint:
+ description: version of external systems.
+ service-url:
+ type: string
+ description: url used to access external systems.
+ user-name:
+ type: string
+ description: username used to access external systems.
+ password:
+ type: string
+ description: password used to access external systems.
+ system-type:
+ type: string
+ description: it could be vim/vnfm/thirdparty-sdnc/ems-resource/ems-performance/ems-alarm.
+ protocol:
+ type: string
+ description: protocol of third party SDNC, for example netconf/snmp.
+ ssl-cacert:
+ type: string
+ description: ca file content if enabled ssl on auth-url.
+ ssl-insecure:
type: boolean
- is-closed-loop-disabled:
+ description: Whether to verify VIM's certificate.
+ ip-address:
+ type: string
+ description: service IP of ftp server.
+ port:
+ type: string
+ description: service port of ftp server.
+ cloud-domain:
+ type: string
+ description: domain info for authentication.
+ default-tenant:
+ type: string
+ description: default tenant of VIM.
+ passive:
type: boolean
+ description: ftp passive mode or not.
+ remote-path:
+ type: string
+ description: resource or performance data file path.
+ system-status:
+ type: string
+ description: the status of external system.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- volumes:
- type: array
- items:
- $ref: "#/definitions/volume"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- l-interfaces:
+ esr-system-info-list:
+ description: |
+ Collection of persistent block-level external system auth info.
+ properties:
+ esr-system-info:
type: array
- items:
- $ref: "#/definitions/l-interface"
- vservers:
+ items:
+ $ref: "#/definitions/esr-system-info"
+ esr-thirdparty-sdnc:
description: |
- Collection of virtual Servers, aka virtual machines or VMs.
+ Persist SDNC address information used by ONAP SDNC.
+ ###### Related Nodes
+ - TO esr-system-info (CHILD of esr-thirdparty-sdnc, esr-thirdparty-sdnc has esr-system-info, One2One)
+ - TO pnf( esr-thirdparty-sdnc has pnf, One2Many)
+ - ESR-THIRDPARTY-SDNC deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
+ required:
+ - thirdparty-sdnc-id
properties:
- vserver:
+ thirdparty-sdnc-id:
+ type: string
+ description: Unique ID of SDNC.
+ location:
+ type: string
+ description: used for DC type to indicate the location of SDNC, such as Core or Edge.
+ product-name:
+ type: string
+ description: password used to access SDNC server.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ esr-system-info-list:
+ type: object
+ $ref: "#/definitions/esr-system-info-list"
+ relationship-list:
+ type: object
+ $ref: "#/definitions/relationship-list"
+ esr-thirdparty-sdnc-list:
+ properties:
+ esr-thirdparty-sdnc:
type: array
items:
- $ref: "#/definitions/vserver"
- tenant:
+ $ref: "#/definitions/esr-thirdparty-sdnc"
+ esr-vnfm:
description: |
- Openstack tenant
+ Persist VNFM address information used by VF-C.
###### Related Nodes
- - TO l3-network (Many2Many)
- - TO service-subscription (Many2Many)
- - TO vserver (comprises tenant, One2Many)
- - FROM cloud-region (is composed of tenant)
- - FROM group-assignment
- - FROM volume-group
+ - TO esr-system-info (CHILD of esr-vnfm, esr-vnfm has esr-system-info, One2One)
+ - ESR-VNFM deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
required:
- - tenant-id
- - tenant-name
+ - vnfm-id
properties:
- tenant-id:
+ vnfm-id:
type: string
- description: Unique id relative to the cloud-region.
- tenant-name:
+ description: Unique ID of VNFM.
+ vim-id:
type: string
- description: Readable name of tenant
- tenant-context:
+ description: indecate the VIM to deploy VNF.
+ certificate-url:
type: string
- description: This field will store the tenant context.
+ description: certificate url of VNFM.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- vservers:
+ esr-system-info-list:
+ type: object
+ $ref: "#/definitions/esr-system-info-list"
+ relationship-list:
+ type: object
+ $ref: "#/definitions/relationship-list"
+ esr-vnfm-list:
+ properties:
+ esr-vnfm:
type: array
- items:
- $ref: "#/definitions/vserver"
+ items:
+ $ref: "#/definitions/esr-vnfm"
+ evc:
+ description: |
+ evc object is an optional child object of the Configuration object.
+ ###### Related Nodes
+ - TO configuration( evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)
+ required:
+ - evc-id
+ properties:
+ evc-id:
+ type: string
+ description: Unique/key field for the evc object
+ forwarding-path-topology:
+ type: string
+ description: Point-to-Point, Multi-Point
+ cir-value:
+ type: string
+ description: Commited Information Rate
+ cir-units:
+ type: string
+ description: CIR units
+ connection-diversity-group-id:
+ type: string
+ description: Diversity Group ID
+ service-hours:
+ type: string
+ description: formerly Performance Group
+ esp-evc-circuit-id:
+ type: string
+ description: EVC Circuit ID of ESP EVC
+ esp-evc-cir-value:
+ type: string
+ description: Committed Information Rate (For ESP)
+ esp-evc-cir-units:
+ type: string
+ description: CIR units (For ESP)
+ esp-itu-code:
+ type: string
+ description: Identifies ESP
+ collector-pop-clli:
+ type: string
+ description: Collector POP CLLI (from the hostname of the access pnf)
+ inter-connect-type-ingress:
+ type: string
+ description: Interconnect type on ingress side of EVC.
+ tagmode-access-ingress:
+ type: string
+ description: tagode for collector side of EVC
+ tagmode-access-egress:
+ type: string
+ description: tagMode for network side of EVC
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- tenants:
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ evcs:
+ properties:
+ evc:
+ type: array
+ items:
+ $ref: "#/definitions/evc"
+ external-system:
description: |
- Collection of openstack tenants.
+ Namespace for external system.
properties:
- tenant:
+ esr-ems-list:
+ type: object
+ $ref: "#/definitions/esr-ems-list"
+ esr-vnfm-list:
+ type: object
+ $ref: "#/definitions/esr-vnfm-list"
+ esr-thirdparty-sdnc-list:
+ type: object
+ $ref: "#/definitions/esr-thirdparty-sdnc-list"
+ extra-properties:
+ description: |
+ Extra properties for inventory item for response list
+ properties:
+ extra-property:
type: array
items:
- $ref: "#/definitions/tenant"
+ $ref: "#/definitions/extra-property"
+ extra-property:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
flavor:
description: |
Openstack flavor.
###### Related Nodes
- - FROM cloud-region (is composed of flavor)
- - FROM vserver
+ - TO cloud-region( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)
+ - FLAVOR cannot be deleted if linked to VSERVER
required:
- flavor-id
- flavor-name
@@ -42328,134 +53604,448 @@ definitions:
type: array
items:
$ref: "#/definitions/flavor"
- group-assignment:
+ forwarder:
description: |
- Openstack group-assignment used to store exclusivity groups (EG).
+ Entity describing a sequenced segment of forwarding path
###### Related Nodes
- - TO tenant (Many2Many)
- - TO pserver (One2Many)
- - FROM cloud-region (is composed of group-assignment)
+ - TO forwarding-path( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)
+ - TO l-interface( forwarder org.onap.relationships.inventory.ForwardsTo l-interface, MANY2ONE)
+ - TO configuration( forwarder org.onap.relationships.inventory.Uses configuration, ONE2ONE)
+ - TO lag-interface( forwarder org.onap.relationships.inventory.ForwardsTo lag-interface, MANY2ONE)
+ - TO p-interface( forwarder org.onap.relationships.inventory.ForwardsTo p-interface, MANY2ONE)
+ - FORWARDER deletion means associated objects of these types are also DELETED:CONFIGURATION
required:
- - group-id
- - group-type
- - group-name
+ - sequence
properties:
- group-id:
+ sequence:
+ type: integer
+ format: int32
+ description: Unique ID of this segmentation
+ forwarder-role:
type: string
- description: Group id, expected to be unique across cloud-region.
- group-type:
+ description: ingress, intermediate, egress
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ resource-version:
type: string
- description: Group type - the type of group this instance refers to
- group-name:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ forwarder-evc:
+ description: |
+ forwarder object is an optional child object of the Configuration object.
+ ###### Related Nodes
+ - TO configuration( forwarder-evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)
+ required:
+ - forwarder-evc-id
+ properties:
+ forwarder-evc-id:
type: string
- description: Group name - name assigned to the group
- group-description:
+ description: Key for forwarder-evc object
+ circuit-id:
type: string
- description: Group description - description of the group
- resource-version:
+ description: Circuit ID from customer/ESP/ingress end of EVC, or reference to beater circuit on gateway/network/egress end of EVC
+ ivlan:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ description: Internal VLAN.
+ svlan:
+ type: string
+ description: SVLAN value for ingress of egress forwarder.
+ cvlan:
+ type: string
+ description: CVLAN value for ingress of egress forwarder.
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- group-assignments:
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ forwarder-evcs:
+ properties:
+ forwarder-evc:
+ type: array
+ items:
+ $ref: "#/definitions/forwarder-evc"
+ forwarders:
+ properties:
+ forwarder:
+ type: array
+ items:
+ $ref: "#/definitions/forwarder"
+ forwarding-path:
description: |
- Collection of openstack group assignments
+ Entity that describes the sequenced forwarding path between interfaces of services or resources
+ ###### Related Nodes
+ - TO service-instance( forwarding-path org.onap.relationships.inventory.AppliesTo service-instance, MANY2ONE)
+ - TO configuration( forwarding-path org.onap.relationships.inventory.Uses configuration, ONE2ONE)
+ - FROM forwarder( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)
+ - FORWARDING-PATH is DELETED when these are DELETED FORWARDER
+ - FORWARDING-PATH deletion means associated objects of these types are also DELETED:CONFIGURATION
+ required:
+ - forwarding-path-id
+ - forwarding-path-name
properties:
- group-assignment:
+ forwarding-path-id:
+ type: string
+ description: Unique ID of this FP
+ forwarding-path-name:
+ type: string
+ description: Name of the FP
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ selflink:
+ type: string
+ description: the self link for this FP
+ forwarders:
+ type: array
+ items:
+ $ref: "#/definitions/forwarder"
+ forwarding-paths:
+ properties:
+ forwarding-path:
type: array
items:
- $ref: "#/definitions/group-assignment"
- snapshot:
+ $ref: "#/definitions/forwarding-path"
+ generic-vnf:
description: |
- Openstack snapshot
+ General purpose VNF
###### Related Nodes
- - FROM cloud-region (is composed of snapshot)
- - FROM vserver
+ - TO availability-zone( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - TO complex( generic-vnf org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)
+ - TO configuration( generic-vnf org.onap.relationships.inventory.Uses configuration, ONE2MANY)
+ - TO ctag-pool( generic-vnf org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)
+ - TO instance-group( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO ipsec-configuration( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)
+ - TO l3-network( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO license-key-resource( generic-vnf org.onap.relationships.inventory.Uses license-key-resource, MANY2MANY)
+ - TO pnf( generic-vnf tosca.relationships.HostedOn pnf, MANY2MANY)
+ - TO pserver( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)
+ - TO vnf-image( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)
+ - TO volume-group( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - TO vserver( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)
+ - TO virtual-data-center( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY)
+ - FROM entitlement( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM lag-interface( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM license( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM network-profile( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)
+ - FROM site-pair-set( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM line-of-business( line-of-business org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)
+ - FROM platform( platform org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)
+ - GENERIC-VNF is DELETED when these are DELETED ENTITLEMENT,VNFC,LAG-INTERFACE,LICENSE,L-INTERFACE,VF-MODULE
+ - GENERIC-VNF deletion means associated objects of these types are also DELETED:CONFIGURATION
required:
- - snapshot-id
+ - vnf-id
+ - vnf-instance-id
+ - vnf-name
+ - vnf-type
+ - vnf-package-name
+ - vnf-discriptor-name
+ - job-id
+ - in-maint
+ - is-closed-loop-disabled
properties:
- snapshot-id:
+ vnf-id:
type: string
- description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
- snapshot-name:
+ description: Unique id of VNF. This is unique across the graph.
+ vnf-instance-id:
type: string
- description: Snapshot name
- snapshot-architecture:
+ description: vnf instance id.
+ vnf-name:
type: string
- description: Operating system architecture
- snapshot-os-distro:
+ description: Name of VNF.
+ vnf-name2:
type: string
- description: The common name of the operating system distribution in lowercase
- snapshot-os-version:
+ description: Alternate name of VNF.
+ vnf-type:
type: string
- description: The operating system version as specified by the distributor.
- application:
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ service-id:
type: string
- description: The application that the image instantiates.
- application-vendor:
+ description: Unique identifier of service, does not necessarily map to ASDC service models. SOON TO BE DEPRECATED
+ regional-resource-zone:
type: string
- description: The vendor of the application.
- application-version:
+ description: Regional way of organizing pservers, source of truth should define values
+ prov-status:
type: string
- description: The version of the application.
- snapshot-selflink:
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ operational-status:
type: string
- description: URL to endpoint where AAI can get more details
- prev-snapshot-id:
+ description: Indicator for whether the resource is considered operational. Valid values are in-service-path and out-of-service-path.
+ license-key:
type: string
- description: This field contains the UUID of the previous snapshot (if any).
+ description: OBSOLETE - do not use
+ equipment-role:
+ type: string
+ description: Client should send valid enumerated value
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, used by MSO.
+ vnf-package-name:
+ type: string
+ vnf-discriptor-name:
+ type: string
+ description: vnf discriptor name
+ job-id:
+ type: string
+ description: job id corresponding to vnf
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ management-option:
+ type: string
+ description: identifier of managed by ATT or customer
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by generic-vnf.
+ ipv4-loopback0-address:
+ type: string
+ description: v4 Loopback0 address
+ nm-lan-v6-address:
+ type: string
+ description: v6 Loopback address
+ management-v6-address:
+ type: string
+ description: v6 management address
+ vcpu:
+ type: integer
+ format: int64
+ description: number of vcpus ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only by uCPE
+ vcpu-units:
+ type: string
+ description: units associated with vcpu, used for VNFs with no vservers/flavors, to be used only by uCPE
+ vmemory:
+ type: integer
+ format: int64
+ description: number of GB of memory ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only by uCPE
+ vmemory-units:
+ type: string
+ description: units associated with vmemory, used for VNFs with no vservers/flavors, to be used only by uCPE
+ vdisk:
+ type: integer
+ format: int64
+ description: number of vdisks ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only uCPE
+ vdisk-units:
+ type: string
+ description: units associated with vdisk, used for VNFs with no vservers/flavors, to be used only by uCPE
+ nshd:
+ type: integer
+ format: int64
+ description: number of associated SHD in vnf.
+ nvm:
+ type: integer
+ format: int64
+ description: number of vms in vnf.
+ nnet:
+ type: integer
+ format: int64
+ description: number of network in vnf.
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ summary-status:
+ type: string
+ description: details regarding the generic-vnf operation, PLEASE DISCONTINUE USE OF THIS FIELD.
+ encrypted-access-flag:
+ type: boolean
+ description: indicates whether generic-vnf access uses SSH
+ entitlement-assignment-group-uuid:
+ type: string
+ description: UUID of the Entitlement group used for licensing VNFs, OBSOLETE - See child relationships.
+ entitlement-resource-uuid:
+ type: string
+ description: UUID of the specific entitlement resource. OBSOLETE - See child relationships.
+ license-assignment-group-uuid:
+ type: string
+ description: UUID of the license assignment group. OBSOLETE - See child relationships.
+ license-key-uuid:
+ type: string
+ description: UUID of the actual license resource. OBSOLETE - See child relationships.
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ model-customization-id:
+ type: string
+ description: captures the id of all the configuration used to customize the resource for the service.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ as-number:
+ type: string
+ description: as-number of the VNF
+ regional-resource-subzone:
+ type: string
+ description: represents sub zone of the rr plane
+ nf-type:
+ type: string
+ description: Generic description of the type of NF
+ nf-function:
+ type: string
+ description: English description of Network function that the specific VNF deployment is providing
+ nf-role:
+ type: string
+ description: role in the network that this model will be providing
+ nf-naming-code:
+ type: string
+ description: string assigned to this model used for naming purposes
+ selflink:
+ type: string
+ description: Path to the controller object.
+ ipv4-oam-gateway-address:
+ type: string
+ description: Gateway address
+ ipv4-oam-gateway-address-prefix-length:
+ type: integer
+ format: int32
+ description: Prefix length for oam-address
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Temporary location for S-TAG to get to VCE
+ nm-profile-name:
+ type: string
+ description: Network Management profile of this VNF
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- snapshots:
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/l-interface"
+ lag-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/lag-interface"
+ vf-modules:
+ type: array
+ items:
+ $ref: "#/definitions/vf-module"
+ licenses:
+ type: array
+ items:
+ $ref: "#/definitions/license"
+ entitlements:
+ type: array
+ items:
+ $ref: "#/definitions/entitlement"
+ generic-vnfs:
description: |
- Collection of openstack snapshots
+ Collection of VNFs
properties:
- snapshot:
+ generic-vnf:
type: array
items:
- $ref: "#/definitions/snapshot"
- metadatum:
+ $ref: "#/definitions/generic-vnf"
+ group-assignment:
description: |
- Key/value pairs
+ Openstack group-assignment used to store exclusivity groups (EG).
###### Related Nodes
- - FROM configuration (is composed of metadatum)
- - FROM image (is composed of metadatum)
- - FROM model-ver (is composed of metadatum)
- - FROM service-instance (is composed of metadatum)
- - FROM connector (is composed of metadatum)
+ - TO cloud-region( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)
required:
- - metaname
- - metaval
+ - group-id
+ - group-type
+ - group-name
properties:
- metaname:
+ group-id:
type: string
- metaval:
+ description: Group id, expected to be unique across cloud-region.
+ group-type:
+ type: string
+ description: Group type - the type of group this instance refers to
+ group-name:
type: string
+ description: Group name - name assigned to the group
+ group-description:
+ type: string
+ description: Group description - description of the group
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- metadata:
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ group-assignments:
description: |
- Collection of metadatum (key/value pairs)
+ Collection of openstack group assignments
properties:
- metadatum:
+ group-assignment:
type: array
items:
- $ref: "#/definitions/metadatum"
+ $ref: "#/definitions/group-assignment"
+ host-route:
+ description: |
+ ###### Related Nodes
+ - TO subnet( host-route org.onap.relationships.inventory.BelongsTo subnet, MANY2ONE)
+ required:
+ - host-route-id
+ - route-prefix
+ - next-hop
+ properties:
+ host-route-id:
+ type: string
+ description: host-route id
+ route-prefix:
+ type: string
+ description: subnet prefix
+ next-hop:
+ type: string
+ description: Could be ip-address, hostname, or service-instance
+ next-hop-type:
+ type: string
+ description: Should be ip-address, hostname, or service-instance to match next-hop
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ host-routes:
+ properties:
+ host-route:
+ type: array
+ items:
+ $ref: "#/definitions/host-route"
image:
description: |
Openstack image.
###### Related Nodes
- - TO metadatum (comprises image, Many2Many)
- - FROM cloud-region (is composed of image)
- - FROM vserver
+ - TO cloud-region( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)
+ - IMAGE cannot be deleted if linked to VSERVER
+ - IMAGE is DELETED when these are DELETED METADATUM
required:
- image-id
- image-name
@@ -42509,106 +54099,224 @@ definitions:
type: array
items:
$ref: "#/definitions/image"
- dvs-switch:
+ include-node-filter:
+ properties:
+ include-node-type:
+ type: string
+ instance-filter:
description: |
- Digital virtual switch metadata, used by SDN-C to configure VCEs. A&AI needs to receive this data from the PO deployment team and administer it using the provisioningTool.sh into A&AI.
+ InstanceFilter for performing a named-query or model query
+ instance-filters:
+ description: |
+ InstanceFilters for performing a named-query or model query
+ properties:
+ instance-filter:
+ type: array
+ items:
+ $ref: "#/definitions/instance-filter"
+ instance-group:
+ description: |
+ General mechanism for grouping instances
###### Related Nodes
- - TO availability-zone (Many2Many)
- - FROM cloud-region (is composed of dvs-switch)
+ - TO model( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)
+ - FROM l3-network( l3-network org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM pnf( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM vip-ipv4-address-list( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM vip-ipv6-address-list( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
required:
- - switch-name
- - vcenter-url
+ - instance-group-role
+ - model-invariant-id
+ - model-version-id
+ - id
+ - description
+ - type
properties:
- switch-name:
+ instance-group-role:
type: string
- description: DVS switch name
- vcenter-url:
+ description: role of the instance group.
+ model-invariant-id:
type: string
- description: URL used to reach the vcenter
+ description: ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: ASDC model version uid for this resource model.
+ id:
+ type: string
+ description: Instance Group ID, UUID assigned to this instance.
+ description:
+ type: string
+ description: Descriptive text to help identify the usage of this instance-group
+ type:
+ type: string
+ description: Only valid value today is lower case ha for high availability
+ sub-type:
+ type: string
+ description: Valid values for ha type are [geo-activeactive, geo-activestandby, local-activeactive, local-activestandby]
resource-version:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ description: Concurrency value
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- dvs-switches:
+ instance-groups:
description: |
- Collection of digital virtual switch metadata used for vmWare VCEs and GenericVnfs.
+ Collection of openstack route table references
properties:
- dvs-switch:
+ instance-group:
type: array
items:
- $ref: "#/definitions/dvs-switch"
- oam-network:
- description: |
- OAM network, to be deprecated shortly. Do not use for new purposes.
- ###### Related Nodes
- - TO complex (Many2Many)
- - TO service-capability (Many2Many)
- - FROM cloud-region (is composed of oam-network)
- required:
- - network-uuid
- - network-name
- - cvlan-tag
+ $ref: "#/definitions/instance-group"
+ inventory:
properties:
- network-uuid:
+ search:
+ type: object
+ $ref: "#/definitions/search"
+ actions:
+ type: object
+ $ref: "#/definitions/actions"
+ cloud-infrastructure:
+ type: object
+ $ref: "#/definitions/cloud-infrastructure"
+ external-system:
+ type: object
+ $ref: "#/definitions/external-system"
+ business:
+ type: object
+ $ref: "#/definitions/business"
+ service-design-and-creation:
+ type: object
+ $ref: "#/definitions/service-design-and-creation"
+ network:
+ type: object
+ $ref: "#/definitions/network"
+ aai-internal:
+ type: object
+ $ref: "#/definitions/aai-internal"
+ nodes:
+ type: array
+ items:
+ $ref: "#/definitions/aai-internal"
+ inventory-item:
+ properties:
+ inventory-item-type:
type: string
- description: UUID of the network. Unique across a cloud-region
- network-name:
+ inventory-item-link:
type: string
- description: Name of the network.
- cvlan-tag:
- type: integer
- format: int64
- description: cvlan-id
- ipv4-oam-gateway-address:
+ inventory-item-data:
+ type: array
+ items:
+ $ref: "#/definitions/inventory-item-data"
+ tagged-inventory-item-list:
+ type: array
+ items:
+ $ref: "#/definitions/tagged-inventory-item-list"
+ inventory-item-data:
+ properties:
+ property-name:
type: string
- description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
- ipv4-oam-gateway-address-prefix-length:
- type: integer
- format: int32
- description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
- resource-version:
+ property-value:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- relationship-list:
- type: array
- items:
- $ref: "#/definitions/relationship"
- oam-networks:
+ inventory-response-item:
description: |
- Collection of OAM networks, to be deprecated shortly. Do not use for new purposes.
+ Inventory item for response list
properties:
- oam-network:
+ model-name:
+ type: string
+ extra-properties:
+ type: object
+ $ref: "#/definitions/extra-properties"
+ inventory-response-items:
+ type: object
+ $ref: "#/definitions/inventory-response-items"
+ inventory-response-items:
+ description: |
+ Container for inventory items in response list
+ properties:
+ inventory-response-item:
type: array
items:
- $ref: "#/definitions/oam-network"
- availability-zone:
+ $ref: "#/definitions/inventory-response-item"
+ ipsec-configuration:
description: |
- Availability zone, a collection of compute hosts/pservers
+ IPSec configuration node will contain various configuration data for the NMTE VNF. This node will have an edge to the generic-vnf (vnf type = TE). Starting 1607, this data will be populated by SDN-C
###### Related Nodes
- - TO complex (Many2Many)
- - TO service-capability (Many2Many)
- - FROM cloud-region (is composed of availability-zone)
- - FROM ctag-pool
- - FROM dvs-switch
- - FROM generic-vnf
- - FROM pserver
- - FROM vce
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)
+ - FROM vig-server( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)
+ - IPSEC-CONFIGURATION is DELETED when these are DELETED VIG-SERVER
required:
- - availability-zone-name
- - hypervisor-type
+ - ipsec-configuration-id
properties:
- availability-zone-name:
+ ipsec-configuration-id:
type: string
- description: Name of the availability zone. Unique across a cloud region
- hypervisor-type:
+ description: UUID of this configuration
+ requested-vig-address-type:
type: string
- description: Type of hypervisor. Source of truth should define valid values.
- operational-status:
+ description: Indicate the type of VIG server like AVPN, INTERNET, BOTH
+ requested-encryption-strength:
type: string
- description: State that indicates whether the availability zone should be used, etc. Source of truth should define valid values.
+ description: Encryption values like 3des-cbc, des-cbc, aes-128-cbc, aes-192-cbc, aes-265-cbc
+ requested-dmz-type:
+ type: string
+ description: ATT can offer a shared DMZ or a DMZ specific to a customer
+ shared-dmz-network-address:
+ type: string
+ description: Network address of shared DMZ
+ requested-customer-name:
+ type: string
+ description: If the DMZ is a custom DMZ, this field will indicate the customer information
+ ike-version:
+ type: string
+ description: can be 1 or 2
+ ikev1-authentication:
+ type: string
+ description: Contains values like md5, sha1, sha256, sha384
+ ikev1-encryption:
+ type: string
+ description: Encyption values like 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
+ ikev1-dh-group:
+ type: string
+ description: Diffie-Hellman group like DH-GROUP2, DH-GROUP5, DH-GROUP14
+ ikev1-am-group-id:
+ type: string
+ description: Group name defined in VIG for clients using aggressive mode
+ ikev1-am-password:
+ type: string
+ description: pre-shared key for the above group name
+ ikev1-sa-lifetime:
+ type: string
+ description: Lifetime for IKEv1 SA
+ ipsec-authentication:
+ type: string
+ description: md5, sha1, sha256, sha384
+ ipsec-encryption:
+ type: string
+ description: 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
+ ipsec-sa-lifetime:
+ type: string
+ description: Life time for IPSec SA
+ ipsec-pfs:
+ type: string
+ description: enable PFS or not
+ xauth-userid:
+ type: string
+ description: user ID for xAuth, sm-user,ucpeHostName,nmteHostName
+ xauth-user-password:
+ type: string
+ description: Encrypted using the Juniper $9$ algorithm
+ dpd-interval:
+ type: string
+ description: The time between DPD probe
+ dpd-frequency:
+ type: string
+ description: Maximum number of DPD before claiming the tunnel is down
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
@@ -42616,115 +54324,139 @@ definitions:
type: array
items:
$ref: "#/definitions/relationship"
- availability-zones:
- description: |
- Collection of availability zones
+ vig-servers:
+ type: array
+ items:
+ $ref: "#/definitions/vig-server"
+ ipsec-configurations:
properties:
- availability-zone:
+ ipsec-configuration:
type: array
items:
- $ref: "#/definitions/availability-zone"
- esr-system-info:
+ $ref: "#/definitions/ipsec-configuration"
+ key-data:
+ properties:
+ key-name:
+ type: string
+ key-value:
+ type: string
+ l-interface:
description: |
- Persist common address information of external systems.
+ Logical interfaces, e.g., a vnic.
###### Related Nodes
- - FROM esr-ems (is composed of esr-system-info)
- - FROM esr-vnfm (is composed of esr-system-info)
- - FROM esr-thirdparty-sdnc (is composed of esr-system-info)
- - FROM cloud-region (is composed of esr-system-info)
+ - TO generic-vnf( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO lag-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)
+ - TO instance-group( l-interface org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO l-interface( l-interface org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - TO logical-link( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)
+ - TO newvce( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)
+ - TO p-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)
+ - TO vserver( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.Uses l-interface, ONE2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - FROM sriov-vf( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)
+ - FROM vlan( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - L-INTERFACE is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST,SRIOV-VF,VLAN
+ - L-INTERFACE deletion means associated objects of these types are also DELETED:LOGICAL-LINK
required:
- - esr-system-info-id
- - user-name
- - password
- - system-type
+ - interface-name
+ - is-port-mirrored
+ - in-maint
+ - is-ip-unnumbered
properties:
- esr-system-info-id:
- type: string
- description: Unique ID of esr system info.
- system-name:
- type: string
- description: name of external system.
- type:
+ interface-name:
type: string
- description: type of external systems.
- vendor:
+ description: Name given to the interface
+ interface-role:
type: string
- description: vendor of external systems.
- version:
+ description: E.g., CUSTOMER, UPLINK, etc.
+ v6-wan-link-ip:
type: string
- description: version of external systems.
- service-url:
+ description: Questionably placed - v6 ip addr of this interface (is in vr-lan-interface from Mary B.
+ selflink:
type: string
- description: url used to access external systems.
- user-name:
+ description: URL to endpoint where AAI can get more details
+ interface-id:
type: string
- description: username used to access external systems.
- password:
+ description: ID of interface
+ macaddr:
type: string
- description: password used to access external systems.
- system-type:
+ description: MAC address for the interface
+ network-name:
type: string
- description: it could be vim/vnfm/thirdparty-sdnc/ems-resource/ems-performance/ems-alarm.
- protocol:
+ description: Name of the network
+ management-option:
type: string
- description: protocol of third party SDNC, for example netconf/snmp.
- ssl-cacert:
+ description: Whether A&AI should be managing this interface of not. Could have value like CUSTOMER
+ interface-description:
type: string
- description: ca file content if enabled ssl on auth-url.
- ssl-insecure:
+ description: Human friendly text regarding this interface.
+ is-port-mirrored:
type: boolean
- description: Whether to verify VIM's certificate.
- ip-address:
- type: string
- description: service IP of ftp server.
- port:
- type: string
- description: service port of ftp server.
- cloud-domain:
- type: string
- description: domain info for authentication.
- default-tenant:
+ resource-version:
type: string
- description: default tenant of VIM.
- passive:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ in-maint:
type: boolean
- description: ftp passive mode or not.
- remote-path:
- type: string
- description: resource or performance data file path.
- system-status:
+ prov-status:
type: string
- description: the status of external system.
- resource-version:
+ description: Prov Status of the logical interface. Valid values [PREPROV/NVTPROV/PROV].
+ is-ip-unnumbered:
+ type: boolean
+ allowed-address-pairs:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ description: Freeform field for storing an ip address, list of ip addresses or a subnet block.
+ vlans:
+ type: array
+ items:
+ $ref: "#/definitions/vlan"
+ sriov-vfs:
+ type: array
+ items:
+ $ref: "#/definitions/sriov-vf"
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/l-interface"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- esr-system-info-list:
+ l3-interface-ipv4-address-list:
+ type: array
+ items:
+ $ref: "#/definitions/l3-interface-ipv4-address-list"
+ l3-interface-ipv6-address-list:
+ type: array
+ items:
+ $ref: "#/definitions/l3-interface-ipv6-address-list"
+ l-interfaces:
description: |
- Collection of persistent block-level external system auth info.
+ Collection of logical interfaces.
properties:
- esr-system-info:
+ l-interface:
type: array
items:
- $ref: "#/definitions/esr-system-info"
- vip-ipv4-address-list:
+ $ref: "#/definitions/l-interface"
+ l3-interface-ipv4-address-list:
description: |
IPv4 Address Range
###### Related Nodes
- - TO instance-group (Many2Many)
- - TO subnet (Many2Many)
- - FROM vnfc
- - FROM cloud-region (is composed of vip-ipv4-address-list)
+ - TO instance-group( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)
+ - TO l3-network( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - TO subnet( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - TO l-interface( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - TO vlan( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ - TO vnfc( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vnfc, MANY2ONE)
required:
- - vip-ipv4-address
+ - l3-interface-ipv4-address
properties:
- vip-ipv4-address:
+ l3-interface-ipv4-address:
type: string
description: IP address
- vip-ipv4-prefix-length:
+ l3-interface-ipv4-prefix-length:
type: integer
format: int64
description: Prefix length, 32 for single address
@@ -42752,21 +54484,23 @@ definitions:
type: array
items:
$ref: "#/definitions/relationship"
- vip-ipv6-address-list:
+ l3-interface-ipv6-address-list:
description: |
IPv6 Address Range
###### Related Nodes
- - TO instance-group (Many2Many)
- - TO subnet (Many2Many)
- - FROM vnfc
- - FROM cloud-region (is composed of vip-ipv6-address-list)
+ - TO instance-group( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)
+ - TO l3-network( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - TO subnet( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - TO l-interface( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - TO vlan( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ - TO vnfc( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vnfc, MANY2ONE)
required:
- - vip-ipv6-address
+ - l3-interface-ipv6-address
properties:
- vip-ipv6-address:
+ l3-interface-ipv6-address:
type: string
description: IP address
- vip-ipv6-prefix-length:
+ l3-interface-ipv6-prefix-length:
type: integer
format: int64
description: Prefix length, 128 for single address
@@ -42794,130 +54528,816 @@ definitions:
type: array
items:
$ref: "#/definitions/relationship"
- cloud-region:
+ l3-network:
description: |
- cloud-region designates an installation of a cloud cluster or region or instantiation.
+ Generic network definition
###### Related Nodes
- - TO esr-system-info (comprises cloud-region, One2Many)
- - TO complex (Many2One)
- - TO l3-network (Many2Many)
- - TO tenant (comprises cloud-region, One2Many)
- - TO image (comprises cloud-region, One2Many)
- - TO flavor (comprises cloud-region, One2Many)
- - TO availability-zone (comprises cloud-region, One2Many)
- - TO oam-network (comprises cloud-region, One2Many)
- - TO dvs-switch (comprises cloud-region, One2Many)
- - TO volume-group (comprises cloud-region, One2Many)
- - TO group-assignment (comprises cloud-region, One2Many)
- - TO snapshot (comprises cloud-region, One2Many)
- - TO zone (Many2One)
- - TO vip-ipv4-address-list (comprises cloud-region, One2Many)
- - TO vip-ipv6-address-list (comprises cloud-region, One2Many)
- - FROM pserver
- - FROM logical-link
+ - TO instance-group( l3-network org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO network-policy( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)
+ - TO route-table-reference( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)
+ - TO vpn-binding( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM complex( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - FROM ctag-assignment( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM segmentation-assignment( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)
+ - FROM subnet( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)
+ - L3-NETWORK is DELETED when these are DELETED CTAG-ASSIGNMENT,SEGMENTATION-ASSIGNMENT,SUBNET
required:
- - cloud-owner
- - cloud-region-id
- - sriov-automation
+ - network-id
+ - network-name
+ - is-bound-to-vpn
+ - is-provider-network
+ - is-shared-network
+ - is-external-network
properties:
- cloud-owner:
+ network-id:
type: string
- description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
- cloud-region-id:
+ description: Network ID, should be uuid. Unique across A&AI.
+ network-name:
type: string
- description: Identifier used by the vendor for the region. Second part of composite key
- cloud-type:
+ description: Name of the network, governed by some naming convention..
+ network-type:
type: string
- description: Type of the cloud (e.g., openstack)
- owner-defined-type:
+ description: Type of the network - who defines these values?
+ network-role:
type: string
- description: Cloud-owner defined type indicator (e.g., dcp, lcp)
- cloud-region-version:
+ description: Role the network plans - who defines these values?
+ network-technology:
type: string
- description: Software version employed at the site. NOTE - THIS FIELD IS NOT KEPT UP TO DATE.
- identity-url:
+ description: Network technology - who defines these values?
+ neutron-network-id:
type: string
- description: URL of the keystone identity service
- cloud-zone:
+ description: Neutron network id of this Interface
+ is-bound-to-vpn:
+ type: boolean
+ service-id:
type: string
- description: Zone where the cloud is homed. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
- complex-name:
+ description: Unique identifier of service from ASDC. Does not strictly map to ASDC services. SOON TO BE DEPRECATED
+ network-role-instance:
+ type: integer
+ format: int64
+ description: network role instance
+ resource-version:
type: string
- description: complex name for cloud-region instance. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
- sriov-automation:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ contrail-network-fqdn:
+ type: string
+ description: Contrail FQDN for the network
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ model-customization-id:
+ type: string
+ description: captures the id of all the configuration used to customize the resource for the service.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ physical-network-name:
+ type: string
+ description: Name associated with the physical network.
+ is-provider-network:
type: boolean
- cloud-extra-info:
+ is-shared-network:
+ type: boolean
+ is-external-network:
+ type: boolean
+ selflink:
type: string
- description: ESR inputs extra information about the VIM or Cloud which will be decoded by MultiVIM.
- cloud-epa-caps:
+ description: Path to the controller object.
+ operational-status:
type: string
- description: MultiVIM will discover and expose EPA capabilities.
+ description: Indicator for whether the resource is considered operational.
+ subnets:
+ type: array
+ items:
+ $ref: "#/definitions/subnet"
+ ctag-assignments:
+ type: array
+ items:
+ $ref: "#/definitions/ctag-assignment"
+ segmentation-assignments:
+ type: array
+ items:
+ $ref: "#/definitions/segmentation-assignment"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ description: Relates to tenant (or is it a child of tenant), complex, service, vpn-binding
+ l3-networks:
+ properties:
+ l3-network:
+ type: array
+ items:
+ $ref: "#/definitions/l3-network"
+ lag-interface:
+ description: |
+ Link aggregate interface
+ ###### Related Nodes
+ - TO generic-vnf( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO lag-link( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)
+ - TO logical-link( lag-interface org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - TO p-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)
+ - TO pnf( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - TO pserver( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - TO vpls-pe( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)
+ - LAG-INTERFACE is DELETED when these are DELETED L-INTERFACE
+ - LAG-INTERFACE deletion means associated objects of these types are also DELETED:LAG-LINK,LOGICAL-LINK
+ required:
+ - interface-name
+ - in-maint
+ properties:
+ interface-name:
+ type: string
+ description: Name that identifies the link aggregate interface
+ interface-description:
+ type: string
+ description: Human friendly text regarding this interface.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- volume-groups:
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ interface-id:
+ type: string
+ description: ID of interface
+ interface-role:
+ type: string
+ description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ in-maint:
+ type: boolean
+ relationship-list:
type: array
items:
- $ref: "#/definitions/volume-group"
- tenants:
+ $ref: "#/definitions/relationship"
+ l-interfaces:
type: array
items:
- $ref: "#/definitions/tenant"
- flavors:
+ $ref: "#/definitions/l-interface"
+ lag-interfaces:
+ description: |
+ Collection of link aggregate interfaces.
+ properties:
+ lag-interface:
+ type: array
+ items:
+ $ref: "#/definitions/lag-interface"
+ lag-link:
+ description: |
+ LAG links can connect lag-interfaces
+ ###### Related Nodes
+ - FROM lag-interface( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)
+ required:
+ - link-name
+ properties:
+ link-name:
+ type: string
+ description: Alphabetical concatenation of lag-interface names
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/flavor"
- group-assignments:
+ $ref: "#/definitions/relationship"
+ lag-links:
+ description: |
+ Collection of link aggregation connections
+ properties:
+ lag-link:
+ type: array
+ items:
+ $ref: "#/definitions/lag-link"
+ license:
+ description: |
+ Metadata for license group.
+ ###### Related Nodes
+ - TO generic-vnf( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vce( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ required:
+ - group-uuid
+ - resource-uuid
+ properties:
+ group-uuid:
+ type: string
+ description: Unique ID for the license group the resource belongs to, should be uuid.
+ resource-uuid:
+ type: string
+ description: Unique ID of a license resource.
+ resource-version:
+ type: string
+ description: Concurrency value
+ relationship-list:
type: array
items:
- $ref: "#/definitions/group-assignment"
- snapshots:
+ $ref: "#/definitions/relationship"
+ licenses:
+ description: |
+ Licenses to be allocated across resources, keyed by group-uuid and resource-uuid, related to license management
+ properties:
+ license:
+ type: array
+ items:
+ $ref: "#/definitions/license"
+ line-of-business:
+ description: |
+ describes a line-of-business
+ ###### Related Nodes
+ - TO generic-vnf( line-of-business org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)
+ required:
+ - line-of-business-name
+ properties:
+ line-of-business-name:
+ type: string
+ description: Name of the line-of-business (product)
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/snapshot"
- images:
+ $ref: "#/definitions/relationship"
+ lines-of-business:
+ description: |
+ Collection of lines-of-business
+ properties:
+ line-of-business:
+ type: array
+ items:
+ $ref: "#/definitions/line-of-business"
+ logical-link:
+ description: |
+ Logical links generally connect l-interfaces but are used to express logical connectivity between two points
+ ###### Related Nodes
+ - TO cloud-region( logical-link org.onap.relationships.inventory.LocatedIn cloud-region, MANY2MANY)
+ - TO generic-vnf( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)
+ - TO lag-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)
+ - TO logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - TO pnf( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)
+ - TO pserver( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)
+ - TO vpn-binding( logical-link org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - TO virtual-data-center( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM configuration( configuration org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - FROM lag-interface( lag-interface org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)
+ - FROM p-interface( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - FROM vlan( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ required:
+ - link-name
+ - in-maint
+ - link-type
+ properties:
+ link-name:
+ type: string
+ description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
+ in-maint:
+ type: boolean
+ link-type:
+ type: string
+ description: Type of logical link, e.g., evc
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ ip-version:
+ type: string
+ description: v4, v6, or ds for dual stack
+ routing-protocol:
+ type: string
+ description: For example, static or BGP
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ operational-status:
+ type: string
+ description: Indication of operational status of the logical link.
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+ link-role:
+ type: string
+ description: Indication of the network use of the logical link.
+ link-name2:
+ type: string
+ description: Alias or alternate name (CLCI or D1 name).
+ link-id:
+ type: string
+ description: UUID of the logical-link, SDNC generates this.
+ circuit-id:
+ type: string
+ description: Circuit id
+ purpose:
+ type: string
+ description: Reason for this entity, role it is playing
+ relationship-list:
type: array
items:
- $ref: "#/definitions/image"
- dvs-switches:
+ $ref: "#/definitions/relationship"
+ logical-links:
+ description: |
+ Collection of logical connections
+ properties:
+ logical-link:
+ type: array
+ items:
+ $ref: "#/definitions/logical-link"
+ metadata:
+ description: |
+ Collection of metadatum (key/value pairs)
+ properties:
+ metadatum:
+ type: array
+ items:
+ $ref: "#/definitions/metadatum"
+ metadatum:
+ description: |
+ Key/value pairs
+ ###### Related Nodes
+ - TO configuration( metadatum org.onap.relationships.inventory.BelongsTo configuration, MANY2ONE)
+ - TO connector( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)
+ - TO image( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)
+ - TO service-instance( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - TO model-ver( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ required:
+ - metaname
+ - metaval
+ properties:
+ metaname:
+ type: string
+ metaval:
+ type: string
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model:
+ description: |
+ Subgraph definition provided by ASDC to describe an inventory asset and its connections related to ASDC models, independent of version
+ ###### Related Nodes
+ - TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - FROM instance-group( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY)
+ - FROM model-ver( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - FROM named-query( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)
+ - MODEL cannot be deleted if linked to INSTANCE-GROUP,NAMED-QUERY,NAMED-QUERY-ELEMENT
+ - MODEL is DELETED when these are DELETED MODEL-VER
+ required:
+ - model-invariant-id
+ - model-type
+ properties:
+ model-invariant-id:
+ type: string
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ model-type:
+ type: string
+ description: Type of the model, e.g., service, resource, widget, etc.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-vers:
type: array
items:
- $ref: "#/definitions/dvs-switch"
- oam-networks:
+ $ref: "#/definitions/model-ver"
+ relationship-list:
type: array
items:
- $ref: "#/definitions/oam-network"
- availability-zones:
+ $ref: "#/definitions/relationship"
+ model-and-named-query-search:
+ description: |
+ ModelAndNamedQuerySearch holds query-parameters and instance-properties for performing a named-query or model query
+ properties:
+ query-parameters:
+ type: object
+ $ref: "#/definitions/query-parameters"
+ instance-filters:
+ type: object
+ $ref: "#/definitions/instance-filters"
+ secondary-filts:
+ type: object
+ $ref: "#/definitions/secondary-filts"
+ top-node-type:
+ type: string
+ secondary-filter-cut-point:
+ type: string
+ model-constraint:
+ description: |
+ This is how we would capture constraints defining allowed sets of elements.
+ ###### Related Nodes
+ - TO model-element( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)
+ - MODEL-CONSTRAINT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET
+ required:
+ - model-constraint-uuid
+ - constrained-element-set-uuid-to-replace
+ properties:
+ model-constraint-uuid:
+ type: string
+ constrained-element-set-uuid-to-replace:
+ type: string
+ constrained-element-sets:
type: array
items:
- $ref: "#/definitions/availability-zone"
+ $ref: "#/definitions/constrained-element-set"
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-constraints:
+ properties:
+ model-constraint:
+ type: array
+ items:
+ $ref: "#/definitions/model-constraint"
+ model-element:
+ description: |
+ Defines how other models combine to make up a higher-level model.
+ ###### Related Nodes
+ - TO element-choice-set( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)
+ - TO model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - TO model-ver( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE)
+ - TO model-ver( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM model-constraint( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - MODEL-ELEMENT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET,MODEL-CONSTRAINT
+ required:
+ - model-element-uuid
+ - new-data-del-flag
+ - cardinality
+ properties:
+ model-element-uuid:
+ type: string
+ new-data-del-flag:
+ type: string
+ description: Indicates whether this element was created as part of instantiation from this model
+ cardinality:
+ type: string
+ description: How many of this type of element are required/allowed
+ linkage-points:
+ type: string
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-elements:
+ type: array
+ items:
+ $ref: "#/definitions/model-element"
+ description: Defines how other models combine to make up a higher-level model
+ model-constraints:
+ type: array
+ items:
+ $ref: "#/definitions/model-constraint"
+ description: Describes new constraints on this model element that are not part of that model's definition
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- esr-system-info-list:
+ model-elements:
+ properties:
+ model-element:
+ type: array
+ items:
+ $ref: "#/definitions/model-element"
+ model-ver:
+ description: |
+ Subgraph definition provided by ASDC to describe a specific version of an inventory asset and its connections related to ASDC models
+ ###### Related Nodes
+ - TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - MODEL-VER cannot be deleted if linked to MODEL-ELEMENT
+ - MODEL-VER is DELETED when these are DELETED MODEL-ELEMENT,METADATUM
+ required:
+ - model-version-id
+ - model-name
+ - model-version
+ properties:
+ model-version-id:
+ type: string
+ description: Unique identifier corresponding to one version of a model in ASDC
+ model-name:
+ type: string
+ description: Name of the model, which can change from version to version.
+ model-version:
+ type: string
+ description: Version
+ model-description:
+ type: string
+ description: Description
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-elements:
type: array
items:
- $ref: "#/definitions/esr-system-info"
- vip-ipv4-address-list:
+ $ref: "#/definitions/model-element"
+ metadata:
+ type: array
+ items:
+ $ref: "#/definitions/metadatum"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ model-vers:
+ properties:
+ model-ver:
type: array
items:
- $ref: "#/definitions/vip-ipv4-address-list"
- vip-ipv6-address-list:
+ $ref: "#/definitions/model-ver"
+ models:
+ description: |
+ Collection of subgraph definitions provided by ASDC to describe the inventory assets and their connections related to ASDC models
+ properties:
+ model:
type: array
items:
- $ref: "#/definitions/vip-ipv6-address-list"
- cloud-regions:
+ $ref: "#/definitions/model"
+ multicast-configuration:
+ description: |
+ ###### Related Nodes
+ - FROM vlan( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)
+ required:
+ - multicast-configuration-id
+ - multicast-protocol
+ - rp-type
properties:
- cloud-region:
+ multicast-configuration-id:
+ type: string
+ description: Unique id of multicast configuration.
+ multicast-protocol:
+ type: string
+ description: protocol of multicast configuration
+ rp-type:
+ type: string
+ description: rp type of multicast configuration
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ multicast-configurations:
+ description: |
+ multicast configuration of generic-vnf ip-address
+ properties:
+ multicast-configuration:
type: array
items:
- $ref: "#/definitions/cloud-region"
+ $ref: "#/definitions/multicast-configuration"
+ named-queries:
+ properties:
+ named-query:
+ type: array
+ items:
+ $ref: "#/definitions/named-query"
+ named-query:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - TO model( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - NAMED-QUERY is DELETED when these are DELETED NAMED-QUERY-ELEMENT
+ required:
+ - named-query-uuid
+ - named-query-name
+ - named-query-version
+ properties:
+ named-query-uuid:
+ type: string
+ named-query-name:
+ type: string
+ named-query-version:
+ type: string
+ required-input-param:
+ type: string
+ description:
+ type: string
+ resource-version:
+ type: string
+ named-query-elements:
+ type: array
+ items:
+ $ref: "#/definitions/named-query-element"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ named-query-element:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - TO model( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)
+ - TO named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM property-constraint( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM related-lookup( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - NAMED-QUERY-ELEMENT is DELETED when these are DELETED PROPERTY-CONSTRAINT,RELATED-LOOKUP
+ required:
+ - named-query-element-uuid
+ properties:
+ named-query-element-uuid:
+ type: string
+ property-collect-list:
+ type: string
+ resource-version:
+ type: string
+ property-limit-desc:
+ type: string
+ do-not-output:
+ type: string
+ named-query-elements:
+ type: array
+ items:
+ $ref: "#/definitions/named-query-element"
+ related-lookups:
+ type: array
+ items:
+ $ref: "#/definitions/related-lookup"
+ property-constraints:
+ type: array
+ items:
+ $ref: "#/definitions/property-constraint"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ named-query-elements:
+ properties:
+ named-query-element:
+ type: array
+ items:
+ $ref: "#/definitions/named-query-element"
+ network:
+ description: |
+ Namespace for network inventory resources.
+ properties:
+ logical-links:
+ type: array
+ items:
+ $ref: "#/definitions/logical-link"
+ site-pair-sets:
+ type: array
+ items:
+ $ref: "#/definitions/site-pair-set"
+ vpn-bindings:
+ type: array
+ items:
+ $ref: "#/definitions/vpn-binding"
+ vpls-pes:
+ type: array
+ items:
+ $ref: "#/definitions/vpls-pe"
+ multicast-configurations:
+ type: array
+ items:
+ $ref: "#/definitions/multicast-configuration"
+ vces:
+ type: array
+ items:
+ $ref: "#/definitions/vce"
+ vnfcs:
+ type: array
+ items:
+ $ref: "#/definitions/vnfc"
+ l3-networks:
+ type: array
+ items:
+ $ref: "#/definitions/l3-network"
+ network-policies:
+ type: array
+ items:
+ $ref: "#/definitions/network-policy"
+ generic-vnfs:
+ type: array
+ items:
+ $ref: "#/definitions/generic-vnf"
+ lag-links:
+ type: array
+ items:
+ $ref: "#/definitions/lag-link"
+ newvces:
+ type: array
+ items:
+ $ref: "#/definitions/newvce"
+ pnfs:
+ type: array
+ items:
+ $ref: "#/definitions/pnf"
+ physical-links:
+ type: array
+ items:
+ $ref: "#/definitions/physical-link"
+ ipsec-configurations:
+ type: array
+ items:
+ $ref: "#/definitions/ipsec-configuration"
+ route-table-references:
+ type: array
+ items:
+ $ref: "#/definitions/route-table-reference"
+ instance-groups:
+ type: array
+ items:
+ $ref: "#/definitions/instance-group"
+ zones:
+ type: array
+ items:
+ $ref: "#/definitions/zone"
+ configurations:
+ type: array
+ items:
+ $ref: "#/definitions/configurations"
+ network-policies:
+ properties:
+ network-policy:
+ type: array
+ items:
+ $ref: "#/definitions/network-policy"
+ network-policy:
+ description: |
+ ###### Related Nodes
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.Uses network-policy, ONE2ONE)
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)
+ required:
+ - network-policy-id
+ properties:
+ network-policy-id:
+ type: string
+ description: UUID representing unique key to this instance
+ network-policy-fqdn:
+ type: string
+ description: Contrail FQDN for the policy
+ heat-stack-id:
+ type: string
+ description: ID for the openStack Heat instance
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
network-profile:
description: |
Network profile populated by SDN-GP for SNMP
###### Related Nodes
- - FROM generic-vnf
+ - TO generic-vnf( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
required:
- nm-profile-name
properties:
@@ -42942,18 +55362,155 @@ definitions:
type: array
items:
$ref: "#/definitions/network-profile"
- sriov-pf:
+ newvce:
description: |
- SR-IOV Physical Function
+ This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce.
###### Related Nodes
- - FROM p-interface (is composed of sriov-pf)
- - FROM sriov-vf
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)
+ - NEWVCE is DELETED when these are DELETED L-INTERFACE
required:
- - pf-pci-id
+ - vnf-id2
+ - vnf-name
+ - vnf-type
properties:
- pf-pci-id:
+ vnf-id2:
type: string
- description: Identifier for the sriov-pf
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ vnf-name:
+ type: string
+ description: Name of VNF.
+ vnf-name2:
+ type: string
+ description: Alternate name of VNF.
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+ operational-status:
+ type: string
+ description: Indicator for whether the resource is considered operational
+ license-key:
+ type: string
+ description: OBSOLETE - do not use
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address).
+ equipment-role:
+ type: string
+ description: Client should send valid enumerated value.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ ipv4-loopback0-address:
+ type: string
+ description: v4 Loopback0 address
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO.
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/l-interface"
+ newvces:
+ description: |
+ This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce.
+ properties:
+ newvce:
+ type: array
+ items:
+ $ref: "#/definitions/newvce"
+ notification-event:
+ properties:
+ cambria.partition:
+ type: string
+ notification-event-header:
+ type: object
+ $ref: "#/definitions/notification-event-header"
+ notification-event-header:
+ properties:
+ id:
+ type: string
+ timestamp:
+ type: string
+ source-name:
+ type: string
+ domain:
+ type: string
+ sequence-number:
+ type: string
+ severity:
+ type: string
+ event-type:
+ type: string
+ version:
+ type: string
+ action:
+ type: string
+ entity-type:
+ type: string
+ top-entity-type:
+ type: string
+ entity-link:
+ type: string
+ status:
+ type: string
+ notify:
+ required:
+ - event-id
+ properties:
+ event-id:
+ type: string
+ node-type:
+ type: string
+ event-trigger:
+ type: string
+ key-data:
+ type: array
+ items:
+ $ref: "#/definitions/key-data"
+ selflink:
+ type: string
+ oam-network:
+ description: |
+ OAM network, to be deprecated shortly. Do not use for new purposes.
+ ###### Related Nodes
+ - TO cloud-region( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO complex( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)
+ - TO service-capability( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ required:
+ - network-uuid
+ - network-name
+ - cvlan-tag
+ properties:
+ network-uuid:
+ type: string
+ description: UUID of the network. Unique across a cloud-region
+ network-name:
+ type: string
+ description: Name of the network.
+ cvlan-tag:
+ type: integer
+ format: int64
+ description: cvlan-id
+ ipv4-oam-gateway-address:
+ type: string
+ description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
+ ipv4-oam-gateway-address-prefix-length:
+ type: integer
+ format: int32
+ description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
@@ -42961,26 +55518,146 @@ definitions:
type: array
items:
$ref: "#/definitions/relationship"
- sriov-pfs:
+ oam-networks:
description: |
- Collection of SR-IOV Physical Functions.
+ Collection of OAM networks, to be deprecated shortly. Do not use for new purposes.
properties:
- sriov-pf:
+ oam-network:
type: array
items:
- $ref: "#/definitions/sriov-pf"
+ $ref: "#/definitions/oam-network"
+ operational-environment:
+ description: |
+ It is a logical partition of the cloud which allows to have multiple environments in the production AIC.
+ ###### Related Nodes
+ - TO operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)
+ - FROM operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)
+ required:
+ - operational-environment-id
+ - operational-environment-name
+ - operational-environment-type
+ - operational-environment-status
+ - tenant-context
+ - workload-context
+ properties:
+ operational-environment-id:
+ type: string
+ description: UUID of an operational environment
+ operational-environment-name:
+ type: string
+ description: Operational Environment name
+ operational-environment-type:
+ type: string
+ description: Operational Environment Type.
+ operational-environment-status:
+ type: string
+ description: Status
+ tenant-context:
+ type: string
+ description: Tenant Context.
+ workload-context:
+ type: string
+ description: Workload Context.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ operational-environments:
+ description: |
+ a logical partition of the cloud which allows to have multiple environments in the production AIC.
+ properties:
+ operational-environment:
+ type: array
+ items:
+ $ref: "#/definitions/operational-environment"
+ overloaded-model:
+ description: |
+ Allows for legacy POST of old-style and new-style models
+ required:
+ - model-invariant-id
+ - model-name-version-id
+ - model-type
+ - model-name
+ - model-id
+ - model-version
+ properties:
+ model-invariant-id:
+ type: string
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ model-name-version-id:
+ type: string
+ description: Unique identifier corresponding to one version of a model in ASDC
+ model-type:
+ type: string
+ description: Type of the model, e.g., service, resource, widget, etc.
+ model-name:
+ type: string
+ description: Name of the model, which can change from version to version.
+ model-id:
+ type: string
+ description: Invariant unique ID which does not change from version to version
+ model-version:
+ type: string
+ description: Version
+ model-description:
+ type: string
+ description: Description
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-vers:
+ type: object
+ $ref: "#/definitions/model-vers"
+ relationship-list:
+ type: object
+ $ref: "#/definitions/relationship-list"
+ owning-entities:
+ description: |
+ Collection of owning-entities
+ properties:
+ owning-entity:
+ type: array
+ items:
+ $ref: "#/definitions/owning-entity"
+ owning-entity:
+ description: |
+ describes an owning-entity
+ ###### Related Nodes
+ - FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo owning-entity, MANY2ONE)
+ required:
+ - owning-entity-id
+ - owning-entity-name
+ properties:
+ owning-entity-id:
+ type: string
+ description: UUID of an owning entity
+ owning-entity-name:
+ type: string
+ description: Owning entity name
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
p-interface:
description: |
Physical interface (e.g., nic)
###### Related Nodes
- - TO l-interface (comprises p-interface, Many2Many)
- - TO physical-link (Many2Many)
- - TO logical-link (Many2One)
- - TO sriov-pf (comprises p-interface, One2One)
- - FROM lag-interface
- - FROM pserver (is composed of p-interface)
- - FROM pnf (is composed of p-interface)
- - FROM vpls-pe (is composed of p-interface)
+ - TO logical-link( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)
+ - TO physical-link( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)
+ - TO pnf( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - TO pserver( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - TO vpls-pe( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM lag-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)
+ - FROM sriov-pf( sriov-pf org.onap.relationships.inventory.BelongsTo p-interface, ONE2ONE)
+ - P-INTERFACE is DELETED when these are DELETED L-INTERFACE,SRIOV-PF
+ - P-INTERFACE deletion means associated objects of these types are also DELETED:PHYSICAL-LINK
required:
- interface-name
- in-maint
@@ -43040,78 +55717,329 @@ definitions:
type: array
items:
$ref: "#/definitions/p-interface"
- lag-interface:
+ physical-link:
description: |
- Link aggregate interface
+ Collection of physical connections, typically between p-interfaces
###### Related Nodes
- - TO logical-link (Many2Many)
- - TO lag-link (Many2Many)
- - TO p-interface (Many2Many)
- - TO l-interface (comprises lag-interface, Many2Many)
- - FROM generic-vnf (is composed of lag-interface)
- - FROM pserver (is composed of lag-interface)
- - FROM pnf (is composed of lag-interface)
- - FROM vpls-pe (is composed of lag-interface)
+ - FROM p-interface( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)
required:
- - interface-name
+ - link-name
+ properties:
+ link-name:
+ type: string
+ description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ circuit-id:
+ type: string
+ description: Circuit it
+ dual-mode:
+ type: string
+ description: Dual access mode (e.g., primary, secondary
+ management-option:
+ type: string
+ description: To provide information on who manages this circuit. A&AI or 3rd party transport provider
+ service-provider-name:
+ type: string
+ description: Name of the service Provider on this link.
+ service-provider-bandwidth-up-value:
+ type: integer
+ format: int32
+ description: Upstream Bandwidth value agreed with the service provider
+ service-provider-bandwidth-up-units:
+ type: string
+ description: Units for the upstream BW value
+ service-provider-bandwidth-down-value:
+ type: integer
+ format: int32
+ description: Downstream Bandwidth value agreed with the service provider
+ service-provider-bandwidth-down-units:
+ type: string
+ description: Units for downstream BW value
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ physical-links:
+ description: |
+ Collection of physical connections, typically between p-interfaces
+ properties:
+ physical-link:
+ type: array
+ items:
+ $ref: "#/definitions/physical-link"
+ platform:
+ description: |
+ describes a platform
+ ###### Related Nodes
+ - TO generic-vnf( platform org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)
+ required:
+ - platform-name
+ properties:
+ platform-name:
+ type: string
+ description: Name of the platform
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ platforms:
+ description: |
+ Collection of platforms
+ properties:
+ platform:
+ type: array
+ items:
+ $ref: "#/definitions/platform"
+ pnf:
+ description: |
+ PNF represents a physical network function. typically equipment used in the D1 world. in 1607, this will be populated by SDN-C to represent a premises router that a uCPE connects to. But this can be used to represent any physical device that is not an AIC node or uCPE.
+ ###### Related Nodes
+ - TO complex( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO instance-group( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO zone( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM esr-thirdparty-sdnc( esr-thirdparty-sdnc has pnf, One2Many)
+ - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn pnf, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf pnf, ONE2MANY)
+ - PNF is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
+ required:
+ - pnf-name
- in-maint
properties:
- interface-name:
+ pnf-name:
type: string
- description: Name that identifies the link aggregate interface
- interface-description:
+ description: unique name of Physical Network Function.
+ pnf-name2:
type: string
- description: Human friendly text regarding this interface.
+ description: name of Physical Network Function.
+ pnf-name2-source:
+ type: string
+ description: source of name2
+ pnf-id:
+ type: string
+ description: id of pnf
+ equip-type:
+ type: string
+ description: Equipment type. Source of truth should define valid values.
+ equip-vendor:
+ type: string
+ description: Equipment vendor. Source of truth should define valid values.
+ equip-model:
+ type: string
+ description: Equipment model. Source of truth should define valid values.
+ management-option:
+ type: string
+ description: identifier of managed by ATT or customer
+ ipaddress-v4-oam:
+ type: string
+ description: ipv4-oam-address with new naming convention for IP addresses
+ sw-version:
+ type: string
+ description: sw-version is the version of SW for the hosted application on the PNF.
+ in-maint:
+ type: boolean
+ frame-id:
+ type: string
+ description: ID of the physical frame (relay rack) where pnf is installed.
+ serial-number:
+ type: string
+ description: Serial number of the device
+ ipaddress-v4-loopback-0:
+ type: string
+ description: IPV4 Loopback 0 address
+ ipaddress-v6-loopback-0:
+ type: string
+ description: IPV6 Loopback 0 address
+ ipaddress-v4-aim:
+ type: string
+ description: IPV4 AIM address
+ ipaddress-v6-aim:
+ type: string
+ description: IPV6 AIM address
+ ipaddress-v6-oam:
+ type: string
+ description: IPV6 OAM address
+ inv-status:
+ type: string
+ description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- speed-value:
+ prov-status:
type: string
- description: Captures the numeric part of the speed
- speed-units:
+ description: Prov Status of this device (not under canopi control) Valid values [PREPROV/NVTPROV/PROV]
+ nf-role:
type: string
- description: Captures the units corresponding to the speed
+ description: Nf Role is the role performed by this instance in the network.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ p-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/p-interface"
+ lag-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/lag-interface"
+ pnfs:
+ description: |
+ Collection of Physical Network Functions.
+ properties:
+ pnf:
+ type: array
+ items:
+ $ref: "#/definitions/pnf"
+ port-group:
+ description: |
+ Used to capture the network interfaces of this VCE
+ ###### Related Nodes
+ - TO vce( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM cvlan-tag( cvlan-tag org.onap.relationships.inventory.BelongsTo port-group, MANY2ONE)
+ - PORT-GROUP is DELETED when these are DELETED CVLAN-TAG
+ required:
+ - interface-id
+ - orchestration-status
+ properties:
interface-id:
type: string
- description: ID of interface
+ description: Unique ID of the interface
+ neutron-network-id:
+ type: string
+ description: Neutron network id of this Interface
+ neutron-network-name:
+ type: string
+ description: Neutron network name of this Interface
interface-role:
type: string
description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
- prov-status:
+ resource-version:
type: string
- description: Trigger for operational monitoring of this resource by Service Assurance systems.
- in-maint:
- type: boolean
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ port-group-id:
+ type: string
+ description: Unique ID for port group in vmware
+ port-group-name:
+ type: string
+ description: Likely to duplicate value of neutron network name
+ switch-name:
+ type: string
+ description: DVS or standard switch name (should be non-null for port groups associated with DVS)
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ cvlan-tags:
+ type: array
+ items:
+ $ref: "#/definitions/cvlan-tag-entry"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- l-interfaces:
+ port-groups:
+ properties:
+ port-group:
+ type: array
+ items:
+ $ref: "#/definitions/port-group"
+ project:
+ description: |
+ describes the project
+ ###### Related Nodes
+ - TO service-instance( project org.onap.relationships.inventory.Uses service-instance, ONE2MANY)
+ required:
+ - project-name
+ properties:
+ project-name:
+ type: string
+ description: Name of the project deploying a service
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/l-interface"
- lag-interfaces:
+ $ref: "#/definitions/relationship"
+ projects:
description: |
- Collection of link aggregate interfaces.
+ Collection of projects
properties:
- lag-interface:
+ project:
type: array
items:
- $ref: "#/definitions/lag-interface"
+ $ref: "#/definitions/project"
+ properties:
+ description: |
+ Property holder for query properties or instance properties
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ property-constraint:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query-element( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ required:
+ - property-constraint-uuid
+ - constraint-type
+ - property-name
+ - property-value
+ properties:
+ property-constraint-uuid:
+ type: string
+ constraint-type:
+ type: string
+ property-name:
+ type: string
+ property-value:
+ type: string
+ resource-version:
+ type: string
+ property-constraints:
+ properties:
+ property-constraint:
+ type: array
+ items:
+ $ref: "#/definitions/property-constraint"
pserver:
description: |
Compute host whose hostname must be unique and must exactly match what is sent as a relationship to a vserver.
###### Related Nodes
- - TO complex (Many2One)
- - TO cloud-region (Many2One)
- - TO availability-zone (Many2One)
- - TO lag-interface (comprises pserver, Many2Many)
- - TO p-interface (comprises pserver, Many2Many)
- - TO zone (Many2One)
- - FROM generic-vnf
- - FROM group-assignment
- - FROM vserver
- - FROM logical-link
+ - TO group-assignment( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)
+ - TO availability-zone( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)
+ - TO cloud-region( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)
+ - TO complex( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO zone( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - FROM vserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)
+ - PSERVER cannot be deleted if linked to GENERIC-VNF,LOGICAL-LINK,VSERVER
+ - PSERVER is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
+ - PSERVER cannot be deleted if linked to GROUP-ASSIGNMENT
required:
- hostname
- in-maint
@@ -43219,361 +56147,407 @@ definitions:
type: array
items:
$ref: "#/definitions/pserver"
- virtual-data-center:
+ query-parameters:
description: |
- Virtual organization of cloud infrastructure elements in a data center context
+ QueryParameters for performing a named-query or model query
+ properties:
+ named-query:
+ type: object
+ $ref: "#/definitions/named-query"
+ overloaded-model:
+ type: object
+ $ref: "#/definitions/overloaded-model"
+ related-lookup:
+ description: |
+ TBD
###### Related Nodes
- - TO generic-vnf (Many2Many)
- - TO logical-link (Many2Many)
- - FROM connector
+ - TO named-query-element( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
required:
- - vdc-id
- - vdc-name
+ - related-lookup-uuid
+ - source-node-type
+ - source-node-property
+ - target-node-type
+ - target-node-property
properties:
- vdc-id:
+ related-lookup-uuid:
type: string
- description: Unique ID of the vdc
- vdc-name:
+ source-node-type:
+ type: string
+ source-node-property:
+ type: string
+ target-node-type:
+ type: string
+ target-node-property:
+ type: string
+ property-collect-list:
type: string
- description: Name of the virtual data center
resource-version:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- virtual-data-centers:
- description: |
- Virtual organization of cloud infrastructure elements in a data center context
+ related-lookups:
properties:
- virtual-data-center:
+ related-lookup:
type: array
items:
- $ref: "#/definitions/virtual-data-center"
- cloud-infrastructure:
- description: |
- Namespace for cloud infrastructure.
+ $ref: "#/definitions/related-lookup"
+ related-to-property:
properties:
- complexes:
- type: array
- items:
- $ref: "#/definitions/complex"
- cloud-regions:
- type: array
- items:
- $ref: "#/definitions/cloud-region"
- network-profiles:
- type: array
- items:
- $ref: "#/definitions/network-profile"
- pservers:
+ property-key:
+ type: string
+ description: Key part of a key/value pair
+ property-value:
+ type: string
+ description: Value part of a key/value pair
+ relationship:
+ properties:
+ related-to:
+ type: string
+ description: A keyword provided by A&AI to indicate type of node.
+ related-link:
+ type: string
+ description: URL to the object in A&AI.
+ relationship-data:
type: array
- items:
- $ref: "#/definitions/pserver"
- virtual-data-centers:
+ items:
+ $ref: "#/definitions/relationship-data"
+ relationship-data:
+ required:
+ - relationship-key
+ - relationship-value
+ properties:
+ relationship-key:
+ type: string
+ description: A keyword provided by A&AI to indicate an attribute.
+ relationship-value:
+ type: string
+ description: Value of the attribute.
+ relationship-list:
+ properties:
+ relationship:
type: array
- items:
- $ref: "#/definitions/virtual-data-center"
- esr-ems:
+ items:
+ $ref: "#/definitions/relationship"
+ reserved-prop-names:
description: |
- Persist EMS address information used by EMS driver.
+ Internal map to define some reserved properties of a vertex
+ properties:
+ last-mod-source-of-truth:
+ type: string
+ aai-node-type:
+ type: string
+ aai-created-ts:
+ type: integer
+ format: int64
+ aai-unique-key:
+ type: string
+ aai-last-mod-ts:
+ type: integer
+ format: int64
+ source-of-truth:
+ type: string
+ aai-uri:
+ type: string
+ response-list:
+ description: |
+ Response container for the results of a named-query or model query
+ properties:
+ inventory-response-items:
+ type: object
+ $ref: "#/definitions/inventory-response-items"
+ result-data:
+ properties:
+ resource-type:
+ type: string
+ description: The specific type of node in the A&AI graph
+ resource-link:
+ type: string
+ description: The URL to the specific resource
+ route-table-reference:
+ description: |
+ Openstack route table reference.
###### Related Nodes
- - TO esr-system-info (comprises esr-ems, One2Many)
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)
required:
- - ems-id
+ - route-table-reference-id
+ - route-table-reference-fqdn
properties:
- ems-id:
+ route-table-reference-id:
type: string
- description: Unique ID of EMS.
+ description: Route Table Reference id, UUID assigned to this instance.
+ route-table-reference-fqdn:
+ type: string
+ description: FQDN entry in the route table.
resource-version:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- esr-system-info-list:
- type: array
- items:
- $ref: "#/definitions/esr-system-info"
+ description: Concurrency value
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- esr-ems-list:
+ route-table-references:
+ description: |
+ Collection of openstack route table references
properties:
- esr-ems:
+ route-table-reference:
type: array
items:
- $ref: "#/definitions/esr-ems"
- esr-vnfm:
+ $ref: "#/definitions/route-table-reference"
+ route-target:
description: |
- Persist VNFM address information used by VF-C.
+ Route target information
###### Related Nodes
- - TO esr-system-info (comprises esr-vnfm, One2One)
+ - TO vpn-binding( route-target org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2ONE)
required:
- - vnfm-id
+ - global-route-target
+ - route-target-role
properties:
- vnfm-id:
- type: string
- description: Unique ID of VNFM.
- vim-id:
+ global-route-target:
type: string
- description: indecate the VIM to deploy VNF.
- certificate-url:
+ description: Number used to identify an RT, globally unique in the network
+ route-target-role:
type: string
- description: certificate url of VNFM.
+ description: Role assigned to this route target
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- esr-system-info-list:
- type: array
- items:
- $ref: "#/definitions/esr-system-info"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- esr-vnfm-list:
+ route-targets:
+ description: |
+ Collection of route target information
properties:
- esr-vnfm:
+ route-target:
type: array
items:
- $ref: "#/definitions/esr-vnfm"
- esr-thirdparty-sdnc:
+ $ref: "#/definitions/route-target"
+ routing-instance:
description: |
- Persist SDNC address information used by ONAP SDNC.
###### Related Nodes
- - TO esr-system-info (comprises esr-thirdparty-sdnc, One2One)
- - TO pnf (One2Many)
+ - TO site-pair-set( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)
+ - FROM site-pair( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)
+ - ROUTING-INSTANCE is DELETED when these are DELETED SITE-PAIR
required:
- - thirdparty-sdnc-id
+ - routing-instance-id
properties:
- thirdparty-sdnc-id:
- type: string
- description: Unique ID of SDNC.
- location:
+ routing-instance-id:
type: string
- description: used for DC type to indicate the location of SDNC, such as Core or Edge.
- product-name:
+ description: Unique id of routing instance
+ rpm-owner:
type: string
- description: password used to access SDNC server.
+ description: rpm owner
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- esr-system-info-list:
+ site-pairs:
type: array
items:
- $ref: "#/definitions/esr-system-info"
+ $ref: "#/definitions/site-pair"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- esr-thirdparty-sdnc-list:
+ routing-instances:
+ description: |
+ set of probes related to generic-vnf routing instance
properties:
- esr-thirdparty-sdnc:
+ routing-instance:
type: array
items:
- $ref: "#/definitions/esr-thirdparty-sdnc"
- external-system:
- description: |
- Namespace for external system.
+ $ref: "#/definitions/routing-instance"
+ sdn-zone-response:
properties:
- esr-ems-list:
+ oam-networks:
+ type: object
+ $ref: "#/definitions/oam-networks"
+ az-and-dvs-switches:
type: array
- items:
- $ref: "#/definitions/esr-ems"
- esr-vnfm-list:
+ items:
+ $ref: "#/definitions/az-and-dvs-switches"
+ search:
+ properties:
+ edge-tag-query-result:
+ type: object
+ $ref: "#/definitions/edge-tag-query-result"
+ edge-tag-query-request:
+ type: object
+ $ref: "#/definitions/edge-tag-query-request"
+ search-results:
+ type: object
+ $ref: "#/definitions/search-results"
+ sdn-zone-response:
+ type: object
+ $ref: "#/definitions/sdn-zone-response"
+ search-results:
+ properties:
+ result-data:
type: array
- items:
- $ref: "#/definitions/esr-vnfm"
- esr-thirdparty-sdnc-list:
+ items:
+ $ref: "#/definitions/result-data"
+ secondary-filt:
+ description: |
+ SecondaryFilt for performing a named-query or model query
+ secondary-filter:
+ properties:
+ property-name:
+ type: string
+ filter-type:
+ type: string
+ property-value:
+ type: string
+ secondary-filts:
+ description: |
+ SecondaryFilts for performing a named-query or model query
+ properties:
+ secondary-filt:
type: array
- items:
- $ref: "#/definitions/esr-thirdparty-sdnc"
- connector:
+ items:
+ $ref: "#/definitions/secondary-filt"
+ segmentation-assignment:
description: |
- Collection of resource instances used to connect a variety of disparate inventory widgets
+ Openstack segmentation assignment.
###### Related Nodes
- - TO virtual-data-center (Many2Many)
- - TO metadatum (comprises connector, Many2Many)
- - FROM service-instance
+ - TO l3-network( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
required:
- - resource-instance-id
+ - segmentation-id
properties:
- resource-instance-id:
+ segmentation-id:
type: string
- description: Unique id of resource instance.
+ description: Route Table Reference id, UUID assigned to this instance.
resource-version:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- model-invariant-id:
- type: string
- description: the ASDC model id for this resource or service model.
- model-version-id:
- type: string
- description: the ASDC model version for this resource or service model.
- persona-model-version:
- type: string
- description: the ASDC model version for this resource or service model.
- widget-model-id:
- type: string
- description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
- widget-model-version:
- type: string
- description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ description: Concurrency value
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- metadata:
- type: array
- items:
- $ref: "#/definitions/metadatum"
- connectors:
+ segmentation-assignments:
description: |
- Collection of resource instances used to connect a variety of disparate inventory widgets
+ Collection of openstack segmentation assignments
properties:
- connector:
+ segmentation-assignment:
type: array
items:
- $ref: "#/definitions/connector"
- tunnel-xconnect:
+ $ref: "#/definitions/segmentation-assignment"
+ service:
description: |
- Represents the specifics of a tunnel cross connect piece of a resource that gets separately allotted
- ###### Related Nodes
- - FROM allotted-resource (is composed of tunnel-xconnect)
+ Stand-in for service model definitions. Likely to be deprecated in favor of models from ASDC. Does not strictly map to ASDC services.
required:
- - id
- - bandwidth-up-wan1
- - bandwidth-down-wan1
- - bandwidth-up-wan2
- - bandwidth-down-wan2
+ - service-id
+ - service-description
properties:
- id:
- type: string
- description: Allotted Resource id UUID assigned to this instance.
- bandwidth-up-wan1:
- type: string
- description: The WAN uplink bandwidth for WAN1
- bandwidth-down-wan1:
+ service-id:
type: string
- description: The WAN downlink bandwidth for WAN1
- bandwidth-up-wan2:
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ service-description:
type: string
- description: The WAN uplink bandwidth for WAN2
- bandwidth-down-wan2:
+ description: Description of the service
+ service-selflink:
type: string
- description: The WAN downlink bandwidth for WAN2
+ description: URL to endpoint where AAI can get more details
resource-version:
type: string
- description: Concurrency value
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ service-version:
+ type: string
+ description: service version
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- tunnel-xconnects:
+ service-capabilities:
description: |
- This object is used to store the specific tunnel cross connect aspects of an allotted resource
+ Collection of service capabilities.
properties:
- tunnel-xconnect:
+ service-capability:
type: array
items:
- $ref: "#/definitions/tunnel-xconnect"
- allotted-resource:
+ $ref: "#/definitions/service-capability"
+ service-capability:
description: |
- Represents a slice or partial piece of a resource that gets separately allotted
+ Early definition of server/resource pairings, likely to be replaced by models. No new use should be made of this.
###### Related Nodes
- - TO generic-vnf (Many2Many)
- - TO l3-network (Many2Many)
- - TO instance-group (Many2Many)
- - TO network-policy (One2One)
- - TO vlan (Many2Many)
- - TO l-interface (One2Many)
- - TO tunnel-xconnect (comprises allotted-resource, One2One)
- - TO vpn-binding (Many2Many)
- - TO allotted-resource (One2One)
- - FROM configuration
- - FROM service-instance (is composed of allotted-resource)
- - FROM service-instance
- - FROM allotted-resource
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - SERVICE-CAPABILITY cannot be deleted if linked to AVAILABILITY-ZONE,OAM-NETWORK
required:
- - id
+ - service-type
+ - vnf-type
properties:
- id:
- type: string
- description: Allotted Resource id UUID assigned to this instance.
- description:
- type: string
- description: The descriptive information assigned to this allotted resource instance
- selflink:
- type: string
- description: Link back to more information in the controller
- model-invariant-id:
- type: string
- description: the ASDC model id for this resource or service model.
- model-version-id:
+ service-type:
type: string
- description: the ASDC model version for this resource or service model.
- persona-model-version:
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ vnf-type:
type: string
- description: the ASDC model version for this resource or service model.
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
resource-version:
type: string
- description: Concurrency value
- orchestration-status:
- type: string
- description: Orchestration status
- operational-status:
- type: string
- description: Indicator for whether the resource is considered operational
- type:
- type: string
- description: Generic description of the type of allotted resource.
- role:
- type: string
- description: role in the network that this resource will be providing.
- tunnel-xconnects:
- type: array
- items:
- $ref: "#/definitions/tunnel-xconnect"
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- allotted-resources:
+ service-design-and-creation:
description: |
- This object is used to store slices of services being offered
+ Namespace for objects managed by ASDC
properties:
- allotted-resource:
+ vnf-images:
type: array
- items:
- $ref: "#/definitions/allotted-resource"
+ items:
+ $ref: "#/definitions/vnf-image"
+ services:
+ type: array
+ items:
+ $ref: "#/definitions/service"
+ service-capabilities:
+ type: array
+ items:
+ $ref: "#/definitions/service-capability"
+ models:
+ type: array
+ items:
+ $ref: "#/definitions/model"
+ named-queries:
+ type: array
+ items:
+ $ref: "#/definitions/named-query"
service-instance:
description: |
Instance of a service
###### Related Nodes
- - TO configuration (One2Many)
- - TO zone (Many2One)
- - TO cvlan-tag (Many2Many)
- - TO pnf (One2Many)
- - TO connector (Many2Many)
- - TO metadatum (comprises service-instance, Many2Many)
- - TO logical-link (Many2Many)
- - TO vlan (One2Many)
- - TO service-instance (One2Many)
- - TO ctag-assignment (One2Many)
- - TO instance-group (Many2Many)
- - TO allotted-resource (comprises service-instance, Many2Many)
- - TO allotted-resource (Many2Many)
- - FROM generic-vnf
- - FROM l3-network
- - FROM owning-entity
- - FROM project
- - FROM service-subscription (is composed of service-instance)
- - FROM vce
- - FROM service-instance
+ - TO generic-vnf( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)
+ - TO l3-network( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)
+ - TO owning-entity( service-instance org.onap.relationships.inventory.BelongsTo owning-entity, MANY2ONE)
+ - TO allotted-resource( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY)
+ - TO configuration( service-instance org.onap.relationships.inventory.Uses configuration, ONE2MANY)
+ - TO connector( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)
+ - TO ctag-assignment( service-instance org.onap.relationships.inventory.Uses ctag-assignment, ONE2MANY)
+ - TO cvlan-tag( service-instance org.onap.relationships.inventory.ComposedOf cvlan-tag, MANY2MANY)
+ - TO instance-group( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO logical-link( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - TO pnf( service-instance org.onap.relationships.inventory.ComposedOf pnf, ONE2MANY)
+ - TO service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)
+ - TO vlan( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)
+ - TO zone( service-instance org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - TO service-subscription( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)
+ - TO vce( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)
+ - FROM project( project org.onap.relationships.inventory.Uses service-instance, ONE2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)
+ - SERVICE-INSTANCE is DELETED when these are DELETED ALLOTTED-RESOURCE,METADATUM
+ - SERVICE-INSTANCE deletion means associated objects of these types are also DELETED:LOGICAL-LINK
required:
- service-instance-id
- service-type
- service-role
+ - created-at
+ - updated-at
+ - description
properties:
service-instance-id:
type: string
@@ -43593,6 +56567,15 @@ definitions:
workload-context:
type: string
description: This field will store the workload context assigned to the service-instance.
+ created-at:
+ type: string
+ description: create time of Network Service.
+ updated-at:
+ type: string
+ description: last update of Network Service.
+ description:
+ type: string
+ description: short description for service-instance.
model-invariant-id:
type: string
description: the ASDC model id for this resource or service model.
@@ -43662,9 +56645,10 @@ definitions:
description: |
Object that group service instances.
###### Related Nodes
- - TO service-instance (comprises service-subscription, Many2Many)
- - FROM customer (is composed of service-subscription)
- - FROM tenant
+ - TO customer( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)
+ - TO tenant( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)
+ - SERVICE-SUBSCRIPTION is DELETED when these are DELETED SERVICE-INSTANCE
required:
- service-type
properties:
@@ -43693,55 +56677,131 @@ definitions:
type: array
items:
$ref: "#/definitions/service-subscription"
- customer:
+ services:
+ description: |
+ Collection of service model definitions. Likely to be deprecated in favor of models from ASDC.
+ properties:
+ service:
+ type: array
+ items:
+ $ref: "#/definitions/service"
+ site-pair:
description: |
- customer identifiers to provide linkage back to BSS information.
###### Related Nodes
- - TO service-subscription (comprises customer, Many2Many)
+ - TO routing-instance( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)
+ - FROM class-of-service( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)
+ - SITE-PAIR is DELETED when these are DELETED CLASS-OF-SERVICE
required:
- - global-customer-id
- - subscriber-name
- - subscriber-type
+ - site-pair-id
properties:
- global-customer-id:
+ site-pair-id:
type: string
- description: Global customer id used across ECOMP to uniquely identify customer.
- subscriber-name:
+ description: unique identifier of probe
+ source-ip:
type: string
- description: Subscriber name, an alternate way to retrieve a customer.
- subscriber-type:
+ description: Prefix address
+ destination-ip:
type: string
- description: Subscriber type, a way to provide VID with only the INFRA customers.
+ description: Prefix address
+ ip-version:
+ type: string
+ description: ip version, v4, v6
+ destination-hostname:
+ type: string
+ description: Hostname of the destination equipment to which SLAs are measured against.
+ destination-equip-type:
+ type: string
+ description: The type of destinatination equipment. Could be Router, UCPE, etc.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- service-subscriptions:
+ classes-of-service:
type: array
items:
- $ref: "#/definitions/service-subscription"
+ $ref: "#/definitions/class-of-service"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- customers:
+ site-pair-set:
description: |
- Collection of customer identifiers to provide linkage back to BSS information.
+ Set of instances for probes used to measure service level agreements
+ ###### Related Nodes
+ - TO generic-vnf( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM routing-instance( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)
+ - SITE-PAIR-SET is DELETED when these are DELETED ROUTING-INSTANCE
+ required:
+ - site-pair-set-id
properties:
- customer:
+ site-pair-set-id:
+ type: string
+ description: Unique id of site pair set.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ routing-instances:
+ type: array
+ items:
+ $ref: "#/definitions/routing-instance"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ site-pair-sets:
+ description: |
+ Collection of sets of instances for probes related to generic-vnf
+ properties:
+ site-pair-set:
type: array
items:
- $ref: "#/definitions/customer"
- line-of-business:
+ $ref: "#/definitions/site-pair-set"
+ site-pairs:
description: |
- describes a line-of-business
+ probe within a set
+ properties:
+ site-pair:
+ type: array
+ items:
+ $ref: "#/definitions/site-pair"
+ snapshot:
+ description: |
+ Openstack snapshot
###### Related Nodes
- - TO generic-vnf (Many2Many)
+ - TO cloud-region( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)
required:
- - line-of-business-name
+ - snapshot-id
properties:
- line-of-business-name:
+ snapshot-id:
type: string
- description: Name of the line-of-business (product)
+ description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
+ snapshot-name:
+ type: string
+ description: Snapshot name
+ snapshot-architecture:
+ type: string
+ description: Operating system architecture
+ snapshot-os-distro:
+ type: string
+ description: The common name of the operating system distribution in lowercase
+ snapshot-os-version:
+ type: string
+ description: The operating system version as specified by the distributor.
+ application:
+ type: string
+ description: The application that the image instantiates.
+ application-vendor:
+ type: string
+ description: The vendor of the application.
+ application-version:
+ type: string
+ description: The version of the application.
+ snapshot-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ prev-snapshot-id:
+ type: string
+ description: This field contains the UUID of the previous snapshot (if any).
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
@@ -43749,129 +56809,704 @@ definitions:
type: array
items:
$ref: "#/definitions/relationship"
- lines-of-business:
+ snapshots:
description: |
- Collection of lines-of-business
+ Collection of openstack snapshots
properties:
- line-of-business:
+ snapshot:
type: array
items:
- $ref: "#/definitions/line-of-business"
- owning-entity:
+ $ref: "#/definitions/snapshot"
+ sriov-pf:
description: |
- describes an owning-entity
+ SR-IOV Physical Function
###### Related Nodes
- - TO service-instance (One2Many)
+ - TO p-interface( sriov-pf org.onap.relationships.inventory.BelongsTo p-interface, ONE2ONE)
+ - FROM sriov-vf( sriov-vf org.onap.relationships.inventory.Uses sriov-pf, MANY2ONE)
required:
- - owning-entity-id
- - owning-entity-name
+ - pf-pci-id
properties:
- owning-entity-id:
+ pf-pci-id:
type: string
- description: UUID of an owning entity
- owning-entity-name:
+ description: Identifier for the sriov-pf
+ resource-version:
type: string
- description: Owning entity name
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ sriov-pfs:
+ description: |
+ Collection of SR-IOV Physical Functions.
+ properties:
+ sriov-pf:
+ type: array
+ items:
+ $ref: "#/definitions/sriov-pf"
+ sriov-vf:
+ description: |
+ SR-IOV Virtual Function (not to be confused with virtual network function)
+ ###### Related Nodes
+ - TO l-interface( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)
+ - TO sriov-pf( sriov-vf org.onap.relationships.inventory.Uses sriov-pf, MANY2ONE)
+ required:
+ - pci-id
+ properties:
+ pci-id:
+ type: string
+ description: PCI ID used to identify the sriov-vf
+ vf-vlan-filter:
+ type: string
+ description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM.
+ vf-mac-filter:
+ type: string
+ description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM.
+ vf-vlan-strip:
+ type: boolean
+ description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM.
+ vf-vlan-anti-spoof-check:
+ type: boolean
+ description: This option ensures anti VLAN spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
+ vf-mac-anti-spoof-check:
+ type: boolean
+ description: This option ensures anti MAC spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
+ vf-mirrors:
+ type: string
+ description: This option defines the set of Mirror objects which essentially mirrors the traffic from source to set of collector VNF Ports.
+ vf-broadcast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows all broadcast traffic to reach the VM
+ vf-unknown-multicast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows unknown multicast traffic to reach the VM
+ vf-unknown-unicast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows unknown unicast traffic to reach the VM
+ vf-insert-stag:
+ type: boolean
+ description: This option, if set to true, instructs to insert outer tag after traffic comes out of VM.
+ vf-link-status:
+ type: string
+ description: This option is used to set the link status. Valid values as of 1607 are on, off, and auto.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
+ type: string
+ description: Neutron network id of the interface
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- owning-entities:
+ sriov-vfs:
description: |
- Collection of owning-entities
+ Collection of SR-IOV Virtual Functions.
properties:
- owning-entity:
+ sriov-vf:
type: array
items:
- $ref: "#/definitions/owning-entity"
- platform:
+ $ref: "#/definitions/sriov-vf"
+ start-node-filter:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ subnet:
description: |
- describes a platform
###### Related Nodes
- - TO generic-vnf (Many2Many)
+ - TO l3-network( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - FROM host-route( host-route org.onap.relationships.inventory.BelongsTo subnet, MANY2ONE)
+ - FROM vip-ipv4-address-list( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)
+ - FROM vip-ipv6-address-list( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)
+ - SUBNET cannot be deleted if linked to L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST,VIP-IPV4-ADDRESS-LIST,VIP-IPV6-ADDRESS-LIST
+ - SUBNET is DELETED when these are DELETED HOST-ROUTE
required:
- - platform-name
+ - subnet-id
+ - dhcp-enabled
properties:
- platform-name:
+ subnet-id:
type: string
- description: Name of the platform
+ description: Subnet ID, should be UUID.
+ subnet-name:
+ type: string
+ description: Name associated with the subnet.
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of this subnet
+ gateway-address:
+ type: string
+ description: gateway ip address
+ network-start-address:
+ type: string
+ description: network start address
+ cidr-mask:
+ type: string
+ description: cidr mask
+ ip-version:
+ type: string
+ description: ip version
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ dhcp-enabled:
+ type: boolean
+ dhcp-start:
+ type: string
+ description: the start address reserved for use by dhcp
+ dhcp-end:
+ type: string
+ description: the last address reserved for use by dhcp
+ subnet-role:
+ type: string
+ description: role of the subnet, referenced when assigning IPs
+ ip-assignment-direction:
+ type: string
+ description: ip address assignment direction of the subnet
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ subnet-sequence:
+ type: integer
+ format: int32
+ description: sequence of the subnet
+ host-routes:
+ type: array
+ items:
+ $ref: "#/definitions/host-route"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- platforms:
+ subnets:
+ properties:
+ subnet:
+ type: array
+ items:
+ $ref: "#/definitions/subnet"
+ tagged-inventory-item-list:
+ properties:
+ inventory-item:
+ type: array
+ items:
+ $ref: "#/definitions/inventory-item"
+ tenant:
description: |
- Collection of platforms
+ Openstack tenant
+ ###### Related Nodes
+ - TO cloud-region( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO group-assignment( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)
+ - TO l3-network( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO volume-group( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - FROM service-subscription( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)
+ - FROM vserver( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)
+ - TENANT cannot be deleted if linked to VSERVER
+ required:
+ - tenant-id
+ - tenant-name
properties:
- platform:
+ tenant-id:
+ type: string
+ description: Unique id relative to the cloud-region.
+ tenant-name:
+ type: string
+ description: Readable name of tenant
+ tenant-context:
+ type: string
+ description: This field will store the tenant context.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ vservers:
+ type: array
+ items:
+ $ref: "#/definitions/vserver"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ tenants:
+ description: |
+ Collection of openstack tenants.
+ properties:
+ tenant:
type: array
items:
- $ref: "#/definitions/platform"
- project:
+ $ref: "#/definitions/tenant"
+ tunnel-xconnect:
description: |
- describes the project
+ Represents the specifics of a tunnel cross connect piece of a resource that gets separately allotted
###### Related Nodes
- - TO service-instance (One2Many)
+ - TO allotted-resource( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)
required:
- - project-name
+ - id
+ - bandwidth-up-wan1
+ - bandwidth-down-wan1
+ - bandwidth-up-wan2
+ - bandwidth-down-wan2
properties:
- project-name:
+ id:
type: string
- description: Name of the project deploying a service
+ description: Allotted Resource id UUID assigned to this instance.
+ bandwidth-up-wan1:
+ type: string
+ description: The WAN uplink bandwidth for WAN1
+ bandwidth-down-wan1:
+ type: string
+ description: The WAN downlink bandwidth for WAN1
+ bandwidth-up-wan2:
+ type: string
+ description: The WAN uplink bandwidth for WAN2
+ bandwidth-down-wan2:
+ type: string
+ description: The WAN downlink bandwidth for WAN2
+ resource-version:
+ type: string
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ tunnel-xconnects:
+ description: |
+ This object is used to store the specific tunnel cross connect aspects of an allotted resource
+ properties:
+ tunnel-xconnect:
+ type: array
+ items:
+ $ref: "#/definitions/tunnel-xconnect"
+ update:
+ description: |
+ Serves a PATCH like function. Does not enforce concurrency control. Clear each usage with AAI team.
+ required:
+ - update-node-type
+ properties:
+ update-node-type:
+ type: string
+ update-node-key:
+ type: array
+ items:
+ $ref: "#/definitions/update-node-key"
+ update-node-uri:
+ type: string
+ action:
+ type: array
+ items:
+ $ref: "#/definitions/action"
+ update-node-key:
+ properties:
+ key-name:
+ type: string
+ key-value:
+ type: string
+ vce:
+ description: |
+ Virtual Customer Edge Router, used specifically for Gamma. This object is deprecated.
+ ###### Related Nodes
+ - TO availability-zone( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - TO complex( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)
+ - TO vserver( vce tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM entitlement( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM license( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM port-group( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)
+ - VCE is DELETED when these are DELETED ENTITLEMENT,LICENSE,PORT-GROUP
+ required:
+ - vnf-id
+ - vnf-name
+ - vnf-type
+ properties:
+ vnf-id:
+ type: string
+ description: Unique id of VNF. This is unique across the graph.
+ vnf-name:
+ type: string
+ description: Name of VNF.
+ vnf-name2:
+ type: string
+ description: Alternate name of VNF.
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ service-id:
+ type: string
+ description: Unique identifier of service, does not strictly map to ASDC services, SOON TO BE DEPRECATED.
+ regional-resource-zone:
+ type: string
+ description: Regional way of organizing pservers, source of truth should define values
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ operational-status:
+ type: string
+ description: Indicator for whether the resource is considered operational
+ license-key:
+ type: string
+ description: OBSOLETE - do not use
+ equipment-role:
+ type: string
+ description: Network role being played by this VNF
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ vpe-id:
+ type: string
+ description: Unique ID of VPE connected to this VCE.
+ v6-vce-wan-address:
+ type: string
+ description: Valid v6 IP address for the WAN Link on this router. Implied length of /64.
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure vce, also used for troubleshooting and is IP used for traps generated by VCE.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ ipv4-loopback0-address:
+ type: string
+ description: Loopback0 address
+ entitlement-resource-uuid:
+ type: string
+ description: OBSOLETE - see child relationships
+ port-groups:
+ type: array
+ items:
+ $ref: "#/definitions/port-group"
+ licenses:
+ type: array
+ items:
+ $ref: "#/definitions/license"
+ entitlements:
+ type: array
+ items:
+ $ref: "#/definitions/entitlement"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- projects:
+ vces:
description: |
- Collection of projects
+ Collection of Virtual Customer Edge Routers, used specifically for Gamma. This object is deprecated.
properties:
- project:
+ vce:
type: array
items:
- $ref: "#/definitions/project"
- business:
+ $ref: "#/definitions/vce"
+ vf-module:
description: |
- Namespace for business related constructs
+ a deployment unit of VNFCs
+ ###### Related Nodes
+ - TO generic-vnf( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO l3-network( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)
+ - TO vnfc( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)
+ - TO volume-group( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)
+ - TO vserver( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)
+ - VF-MODULE cannot be deleted if linked to VNFC
+ required:
+ - vf-module-id
+ - is-base-vf-module
properties:
- connectors:
+ vf-module-id:
+ type: string
+ description: Unique ID of vf-module.
+ vf-module-name:
+ type: string
+ description: Name of vf-module
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance.
+ orchestration-status:
+ type: string
+ description: orchestration status of this vf-module, mastered by MSO
+ is-base-vf-module:
+ type: boolean
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ model-customization-id:
+ type: string
+ description: captures the id of all the configuration used to customize the resource for the service.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ contrail-service-instance-fqdn:
+ type: string
+ description: the Contrail unique ID for a service-instance
+ module-index:
+ type: integer
+ format: int32
+ description: the index will track the number of modules of a given type that have been deployed in a VNF, starting with 0, and always choosing the lowest available digit
+ selflink:
+ type: string
+ description: Path to the controller object.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/connector"
- customers:
+ $ref: "#/definitions/relationship"
+ vf-modules:
+ description: |
+ Collection of vf-modules, a deployment unit of VNFCs
+ properties:
+ vf-module:
+ type: array
+ items:
+ $ref: "#/definitions/vf-module"
+ vig-server:
+ description: |
+ vig-server contains information about a vig server used for IPSec-configuration. Populated by SDN-C from 1607
+ ###### Related Nodes
+ - TO ipsec-configuration( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)
+ required:
+ - vig-address-type
+ properties:
+ vig-address-type:
+ type: string
+ description: indicates whether the VIG is for AVPN or INTERNET
+ ipaddress-v4-vig:
+ type: string
+ description: v4 IP of the vig server
+ ipaddress-v6-vig:
+ type: string
+ description: v6 IP of the vig server
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/customer"
- lines-of-business:
+ $ref: "#/definitions/relationship"
+ vig-servers:
+ properties:
+ vig-server:
+ type: array
+ items:
+ $ref: "#/definitions/vig-server"
+ vip-ipv4-address-list:
+ description: |
+ IPv4 Address Range
+ ###### Related Nodes
+ - TO cloud-region( vip-ipv4-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO instance-group( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO subnet( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv4-address-list, MANY2MANY)
+ required:
+ - vip-ipv4-address
+ properties:
+ vip-ipv4-address:
+ type: string
+ description: IP address
+ vip-ipv4-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 32 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
+ type: string
+ description: Neutron network id of the interface that address belongs to
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of subnet that address belongs to
+ relationship-list:
type: array
items:
- $ref: "#/definitions/line-of-business"
- owning-entities:
+ $ref: "#/definitions/relationship"
+ vip-ipv6-address-list:
+ description: |
+ IPv6 Address Range
+ ###### Related Nodes
+ - TO cloud-region( vip-ipv6-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO instance-group( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO subnet( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv6-address-list, MANY2MANY)
+ required:
+ - vip-ipv6-address
+ properties:
+ vip-ipv6-address:
+ type: string
+ description: IP address
+ vip-ipv6-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 128 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
+ type: string
+ description: Neutron network id of the interface that address belongs to
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of subnet that address belongs to
+ relationship-list:
type: array
items:
- $ref: "#/definitions/owning-entity"
- platforms:
+ $ref: "#/definitions/relationship"
+ virtual-data-center:
+ description: |
+ Virtual organization of cloud infrastructure elements in a data center context
+ ###### Related Nodes
+ - FROM connector( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ required:
+ - vdc-id
+ - vdc-name
+ properties:
+ vdc-id:
+ type: string
+ description: Unique ID of the vdc
+ vdc-name:
+ type: string
+ description: Name of the virtual data center
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/platform"
- projects:
+ $ref: "#/definitions/relationship"
+ virtual-data-centers:
+ description: |
+ Virtual organization of cloud infrastructure elements in a data center context
+ properties:
+ virtual-data-center:
+ type: array
+ items:
+ $ref: "#/definitions/virtual-data-center"
+ vlan:
+ description: |
+ Definition of vlan
+ ###### Related Nodes
+ - TO l-interface( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)
+ - TO logical-link( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - TO multicast-configuration( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ - VLAN is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST
+ - VLAN deletion means associated objects of these types are also DELETED:LOGICAL-LINK
+ required:
+ - vlan-interface
+ - in-maint
+ - is-ip-unnumbered
+ properties:
+ vlan-interface:
+ type: string
+ description: String that identifies the interface
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ vlan-description:
+ type: string
+ description: Used to describe (the service associated with) the vlan
+ backdoor-connection:
+ type: string
+ description: Whether customer is going to use this VLAN for backdoor connection to another customer premise device.
+ vpn-key:
+ type: string
+ description: This indicates the customers VPN ID associated with this vlan
+ orchestration-status:
+ type: string
+ description: Status of a vnf's vlan interface, on which the customer circuit resides, mastered by SDN-C.
+ in-maint:
+ type: boolean
+ prov-status:
+ type: string
+ description: Prov Status of the VLAN configuration related to a logical interface. Valid values [PREPROV/NVTPROV/PROV].
+ is-ip-unnumbered:
+ type: boolean
+ relationship-list:
type: array
items:
- $ref: "#/definitions/project"
+ $ref: "#/definitions/relationship"
+ l3-interface-ipv4-address-list:
+ type: array
+ items:
+ $ref: "#/definitions/l3-interface-ipv4-address-list"
+ l3-interface-ipv6-address-list:
+ type: array
+ items:
+ $ref: "#/definitions/l3-interface-ipv6-address-list"
+ vlans:
+ properties:
+ vlan:
+ type: array
+ items:
+ $ref: "#/definitions/vlan"
+ vnf:
+ description: |
+ Abstract vnf class
+ required:
+ - vnf-id
+ properties:
+ vnf-id:
+ type: string
+ description: Unique id of VNF. This is unique across the graph.
vnf-image:
description: |
Image object that pertain to a VNF that doesn't have associated vservers. This is a kludge.
###### Related Nodes
- - FROM generic-vnf
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)
+ - VNF-IMAGE cannot be deleted if linked to GENERIC-VNF
required:
- vnf-image-uuid
- application
@@ -43907,56 +57542,136 @@ definitions:
type: array
items:
$ref: "#/definitions/vnf-image"
- service:
+ vnfc:
description: |
- Stand-in for service model definitions. Likely to be deprecated in favor of models from ASDC. Does not strictly map to ASDC services.
+ ###### Related Nodes
+ - TO generic-vnf( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO instance-group( vnfc org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO vip-ipv4-address-list( vnfc org.onap.relationships.inventory.Uses vip-ipv4-address-list, MANY2MANY)
+ - TO vip-ipv6-address-list( vnfc org.onap.relationships.inventory.Uses vip-ipv6-address-list, MANY2MANY)
+ - TO vserver( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vnfc, MANY2ONE)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vnfc, MANY2ONE)
+ - VNFC is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST
required:
- - service-id
- - service-description
+ - vnfc-name
+ - nfc-naming-code
+ - nfc-function
+ - in-maint
+ - is-closed-loop-disabled
properties:
- service-id:
+ vnfc-name:
type: string
- description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
- service-description:
+ description: Unique ID of vnfc.
+ nfc-naming-code:
type: string
- description: Description of the service
- service-selflink:
+ description: Short code that is used in naming instances of the item being modeled
+ nfc-function:
type: string
- description: URL to endpoint where AAI can get more details
+ description: English description of function that the specific resource deployment is providing. Assigned as part of the customization of a resource in a service
+ prov-status:
+ type: string
+ description: prov status of this vnfc
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by APP-C
+ ipaddress-v4-oam-vip:
+ type: string
+ description: Oam V4 vip address of this vnfc
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
+ group-notation:
+ type: string
+ description: Group notation of VNFC
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- service-version:
- type: string
- description: service version
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- services:
+ l3-interface-ipv4-address-list:
+ type: array
+ items:
+ $ref: "#/definitions/l3-interface-ipv4-address-list"
+ l3-interface-ipv6-address-list:
+ type: array
+ items:
+ $ref: "#/definitions/l3-interface-ipv6-address-list"
+ vnfcs:
description: |
- Collection of service model definitions. Likely to be deprecated in favor of models from ASDC.
+ virtual network components associated with a vserver from application controller.
properties:
- service:
+ vnfc:
type: array
items:
- $ref: "#/definitions/service"
- service-capability:
+ $ref: "#/definitions/vnfc"
+ volume:
description: |
- Early definition of server/resource pairings, likely to be replaced by models. No new use should be made of this.
+ Ephemeral Block storage volume.
###### Related Nodes
- - FROM availability-zone
- - FROM oam-network
+ - FROM vserver (PARENT of volume, vserver tosca.relationships.AttachesTo volume)
required:
- - service-type
+ - volume-id
+ - volume-selflink
+ properties:
+ volume-id:
+ type: string
+ description: Unique ID of block storage volume relative to the vserver.
+ volume-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ volume-group:
+ description: |
+ Persistent block-level storage.
+ ###### Related Nodes
+ - TO cloud-region( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO complex( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ required:
+ - volume-group-id
+ - volume-group-name
- vnf-type
properties:
- service-type:
+ volume-group-id:
type: string
- description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ description: Unique ID of volume-group.
+ volume-group-name:
+ type: string
+ description: Name of the volume group.
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this volume-group
vnf-type:
type: string
description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ orchestration-status:
+ type: string
+ description: Orchestration status of this volume-group
+ model-customization-id:
+ type: string
+ description: captures the id of all the configuration used to customize the resource for the service.
+ vf-module-model-customization-id:
+ type: string
+ description: helps relate the volume group to the vf-module whose components will require the volume group
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
@@ -43964,53 +57679,637 @@ definitions:
type: array
items:
$ref: "#/definitions/relationship"
- service-capabilities:
+ volume-groups:
description: |
- Collection of service capabilities.
+ Collection of persistent block-level storage.
properties:
- service-capability:
+ volume-group:
type: array
items:
- $ref: "#/definitions/service-capability"
- element-choice-set:
+ $ref: "#/definitions/volume-group"
+ volumes:
description: |
- This is how we would capture constraints defining allowed sets of elements.
+ Collection of ephemeral Block storage volumes.
+ properties:
+ volume:
+ type: array
+ items:
+ $ref: "#/definitions/volume"
+ vpls-pe:
+ description: |
+ VPLS Provider Edge routers.
###### Related Nodes
- - TO model-element (comprises element-choice-set, One2Many)
- - FROM constrained-element-set (is composed of element-choice-set)
+ - TO complex( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO ctag-pool( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - VPLS-PE is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
required:
- - element-choice-set-uuid
- - element-choice-set-name
+ - equipment-name
properties:
- element-choice-set-uuid:
+ equipment-name:
type: string
- element-choice-set-name:
+ prov-status:
type: string
- cardinality:
+ description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+ ipv4-oam-address:
type: string
+ description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address).
+ equipment-role:
+ type: string
+ description: Client should send valid enumerated value, e.g., VPLS-PE.
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Temporary location for stag to get to VCE
resource-version:
type: string
- model-elements:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/model-element"
+ $ref: "#/definitions/relationship"
+ p-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/p-interface"
+ lag-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/lag-interface"
+ vpls-pes:
+ description: |
+ Collection of VPLS Provider Edge routers
+ properties:
+ vpls-pe:
+ type: array
+ items:
+ $ref: "#/definitions/vpls-pe"
+ vpn-binding:
+ description: |
+ VPN binding
+ ###### Related Nodes
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2MANY)
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - FROM route-target( route-target org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2ONE)
+ - VPN-BINDING cannot be deleted if linked to ALLOTTED-RESOURCE,L3-NETWORK,LOGICAL-LINK
+ - VPN-BINDING is DELETED when these are DELETED ROUTE-TARGET
+ required:
+ - vpn-id
+ - vpn-name
+ properties:
+ vpn-id:
+ type: string
+ description: VPN ID, globally unique within A&AI
+ vpn-name:
+ type: string
+ description: VPN Name
+ vpn-platform:
+ type: string
+ description: the platform associated with the VPN example AVPN, Mobility
+ vpn-type:
+ type: string
+ description: Type of the vpn, should be taken from enumerated/valid values
+ vpn-region:
+ type: string
+ description: region of customer vpn
+ customer-vpn-id:
+ type: string
+ description: id for this customer vpn
+ route-distinguisher:
+ type: string
+ description: Used to distinguish the distinct VPN routes of separate customers who connect to the provider in an MPLS network.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ route-targets:
+ type: array
+ items:
+ $ref: "#/definitions/route-target"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- element-choice-sets:
+ description: l3-networks relate to vpn-bindings
+ vpn-bindings:
properties:
- element-choice-set:
+ vpn-binding:
type: array
items:
- $ref: "#/definitions/element-choice-set"
+ $ref: "#/definitions/vpn-binding"
+ vserver:
+ description: |
+ Virtual Servers, aka virtual machine or VM.
+ ###### Related Nodes
+ - TO tenant( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)
+ - TO flavor( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)
+ - TO image( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)
+ - TO pserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)
+ - TO snapshot( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)
+ - TO volume (CHILD of vserver, vserver tosca.relationships.AttachesTo volume, ONE2MANY)
+ - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM vce( vce tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)
+ - FROM vnfc( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)
+ - VSERVER is DELETED when these are DELETED L-INTERFACE
+ - VSERVER deletion means associated objects of these types are also DELETED:VOLUME
+ required:
+ - vserver-id
+ - vserver-name
+ - vserver-selflink
+ - in-maint
+ - is-closed-loop-disabled
+ properties:
+ vserver-id:
+ type: string
+ description: Unique identifier for this vserver relative to its tenant
+ vserver-name:
+ type: string
+ description: Name of vserver
+ vserver-name2:
+ type: string
+ description: Alternative name of vserver
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ vserver-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ volumes:
+ type: array
+ items:
+ $ref: "#/definitions/volume"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/l-interface"
+ vservers:
+ description: |
+ Collection of virtual Servers, aka virtual machines or VMs.
+ properties:
+ vserver:
+ type: array
+ items:
+ $ref: "#/definitions/vserver"
+ zone:
+ description: |
+ A zone is a grouping of assets in a location homing to the same connections into the CBB
+ ###### Related Nodes
+ - TO complex( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM pnf( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ required:
+ - zone-id
+ - zone-name
+ - design-type
+ - zone-context
+ properties:
+ zone-id:
+ type: string
+ description: Code assigned by AIC to the zone
+ zone-name:
+ type: string
+ description: English name associated with the zone
+ design-type:
+ type: string
+ description: Design of zone [Medium/Large?]
+ zone-context:
+ type: string
+ description: Context of zone [production/test]
+ status:
+ type: string
+ description: Status of a zone.
+ resource-version:
+ type: string
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ zones:
+ description: |
+ Collection of zones
+ properties:
+ zone:
+ type: array
+ items:
+ $ref: "#/definitions/zone"
+patchDefinitions:
+ aai-internal:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ action:
+ properties:
+ action-type:
+ type: string
+ action-data:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/action-data"
+ action-data:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ actions:
+ description: |
+ APIs that are more action related than REST (e.g., notify, update).
+ properties:
+ update:
+ type: object
+ $ref: "#/patchDefinitions/update"
+ notify:
+ type: object
+ $ref: "#/patchDefinitions/notify"
+ allotted-resource:
+ description: |
+ Represents a slice or partial piece of a resource that gets separately allotted
+ ###### Related Nodes
+ - TO allotted-resource( allotted-resource tosca.relationships.network.BindsTo allotted-resource, ONE2ONE)
+ - TO generic-vnf( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY)
+ - TO instance-group( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO l3-network( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY)
+ - TO l-interface( allotted-resource org.onap.relationships.inventory.Uses l-interface, ONE2MANY)
+ - TO network-policy( allotted-resource org.onap.relationships.inventory.Uses network-policy, ONE2ONE)
+ - TO vlan( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY)
+ - TO vpn-binding( allotted-resource org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2MANY)
+ - TO service-instance( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM tunnel-xconnect( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)
+ - FROM configuration( configuration org.onap.relationships.inventory.Uses allotted-resource, ONE2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY)
+ - FROM allotted-resource( allotted-resource tosca.relationships.network.BindsTo allotted-resource, ONE2ONE)
+ - ALLOTTED-RESOURCE is DELETED when these are DELETED TUNNEL-XCONNECT
+ required:
+ - id
+ properties:
+ id:
+ type: string
+ description: Allotted Resource id UUID assigned to this instance.
+ description:
+ type: string
+ description: The descriptive information assigned to this allotted resource instance
+ selflink:
+ type: string
+ description: Link back to more information in the controller
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ allotted-resources:
+ description: |
+ This object is used to store slices of services being offered
+ properties:
+ allotted-resource:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/allotted-resource"
+ availability-zone:
+ description: |
+ Availability zone, a collection of compute hosts/pservers
+ ###### Related Nodes
+ - TO complex( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO service-capability( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - TO cloud-region( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM ctag-pool( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM dvs-switch( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - FROM pserver( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)
+ - FROM vce( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - AVAILABILITY-ZONE cannot be deleted if linked to CTAG-POOL,DVS-SWITCH,GENERIC-VNF,PSERVER,VCE
+ required:
+ - availability-zone-name
+ - hypervisor-type
+ properties:
+ availability-zone-name:
+ type: string
+ description: Name of the availability zone. Unique across a cloud region
+ hypervisor-type:
+ type: string
+ description: Type of hypervisor. Source of truth should define valid values.
+ operational-status:
+ type: string
+ description: State that indicates whether the availability zone should be used, etc. Source of truth should define valid values.
+ availability-zones:
+ description: |
+ Collection of availability zones
+ properties:
+ availability-zone:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/availability-zone"
+ az-and-dvs-switches:
+ properties:
+ dvs-switches:
+ type: object
+ $ref: "#/patchDefinitions/dvs-switches"
+ availability-zone:
+ type: object
+ $ref: "#/patchDefinitions/availability-zone"
+ business:
+ description: |
+ Namespace for business related constructs
+ properties:
+ connectors:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/connector"
+ customers:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/customer"
+ lines-of-business:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/line-of-business"
+ owning-entities:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/owning-entity"
+ platforms:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/platform"
+ projects:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/project"
+ class-of-service:
+ description: |
+ ###### Related Nodes
+ - TO site-pair( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)
+ required:
+ - cos
+ properties:
+ cos:
+ type: string
+ description: unique identifier of probe
+ probe-id:
+ type: string
+ description: identifier of probe
+ probe-type:
+ type: string
+ description: type of probe
+ classes-of-service:
+ description: |
+ class-of-service of probe
+ properties:
+ class-of-service:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/class-of-service"
+ cloud-infrastructure:
+ description: |
+ Namespace for cloud infrastructure.
+ properties:
+ complexes:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/complex"
+ cloud-regions:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/cloud-region"
+ network-profiles:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/network-profile"
+ pservers:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/pserver"
+ virtual-data-centers:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/virtual-data-center"
+ cloud-region:
+ description: |
+ cloud-region designates an installation of a cloud cluster or region or instantiation.
+ ###### Related Nodes
+ - TO esr-system-info (CHILD of cloud-region, cloud-region has esr-system-info, One2Many)
+ - TO complex( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO l3-network( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO zone( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM dvs-switch( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM flavor( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM group-assignment( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM image( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM snapshot( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM vip-ipv4-address-list( vip-ipv4-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM vip-ipv6-address-list( vip-ipv6-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM volume-group( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn cloud-region, MANY2MANY)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)
+ - CLOUD-REGION cannot be deleted if linked to DVS-SWITCH,FLAVOR,GROUP-ASSIGNMENT,IMAGE,OAM-NETWORK,SNAPSHOT,TENANT,VIP-IPV4-ADDRESS-LIST,VIP-IPV6-ADDRESS-LIST,VOLUME-GROUP
+ - CLOUD-REGION is DELETED when these are DELETED AVAILABILITY-ZONE
+ - CLOUD-REGION deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
+ required:
+ - cloud-owner
+ - cloud-region-id
+ - sriov-automation
+ properties:
+ cloud-owner:
+ type: string
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ cloud-region-id:
+ type: string
+ description: Identifier used by the vendor for the region. Second part of composite key
+ cloud-type:
+ type: string
+ description: Type of the cloud (e.g., openstack)
+ owner-defined-type:
+ type: string
+ description: Cloud-owner defined type indicator (e.g., dcp, lcp)
+ cloud-region-version:
+ type: string
+ description: Software version employed at the site. NOTE - THIS FIELD IS NOT KEPT UP TO DATE.
+ identity-url:
+ type: string
+ description: URL of the keystone identity service
+ cloud-zone:
+ type: string
+ description: Zone where the cloud is homed. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
+ complex-name:
+ type: string
+ description: complex name for cloud-region instance. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
+ sriov-automation:
+ type: boolean
+ cloud-extra-info:
+ type: string
+ description: ESR inputs extra information about the VIM or Cloud which will be decoded by MultiVIM.
+ cloud-epa-caps:
+ type: string
+ description: MultiVIM will discover and expose EPA capabilities.
+ cloud-regions:
+ properties:
+ cloud-region:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/cloud-region"
+ complex:
+ description: |
+ Collection of physical locations that can house cloud-regions.
+ ###### Related Nodes
+ - TO l3-network( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM ctag-pool( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)
+ - FROM pnf( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM vce( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)
+ - FROM volume-group( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM vpls-pe( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM zone( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - COMPLEX cannot be deleted if linked to AVAILABILITY-ZONE,CLOUD-REGION,GENERIC-VNF,OAM-NETWORK,PNF,PSERVER,VCE,VOLUME-GROUP,VPLS-PE,ZONE
+ - COMPLEX is DELETED when these are DELETED CTAG-POOL
+ required:
+ - physical-location-id
+ - physical-location-type
+ - street1
+ - city
+ - postal-code
+ - country
+ - region
+ properties:
+ physical-location-id:
+ type: string
+ description: Unique identifier for physical location, e.g., CLLI
+ data-center-code:
+ type: string
+ description: Data center code which can be an alternate way to identify a complex
+ complex-name:
+ type: string
+ description: Gamma complex name for LCP instance.
+ identity-url:
+ type: string
+ description: URL of the keystone identity service
+ complexes:
+ description: |
+ Collection of physical locations that can house cloud-regions.
+ properties:
+ complex:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/complex"
+ configuration:
+ description: |
+ Port Mirror Configuration.
+ ###### Related Nodes
+ - TO allotted-resource( configuration org.onap.relationships.inventory.Uses allotted-resource, ONE2ONE)
+ - TO logical-link( configuration org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo configuration, MANY2ONE)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses configuration, ONE2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses configuration, ONE2MANY)
+ - CONFIGURATION is DELETED when these are DELETED METADATUM
+ - CONFIGURATION deletion means associated objects of these types are also DELETED:ALLOTTED-RESOURCE,LOGICAL-LINK
+ required:
+ - configuration-id
+ - configuration-type
+ - configuration-sub-type
+ - orchestration-status
+ - operational-status
+ - configuration-selflink
+ - model-customization-id
+ properties:
+ configuration-id:
+ type: string
+ description: UUID assigned to configuration.
+ management-option:
+ type: string
+ description: Indicates the entity that will manage this feature. Could be an organization or the name of the application as well.
+ configuration-name:
+ type: string
+ description: Name of the configuration.
+ configuration-type:
+ type: string
+ description: port-mirroring-configuration.
+ configuration-sub-type:
+ type: string
+ description: vprobe, pprobe.
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ orchestration-status:
+ type: string
+ description: Orchestration status of the configuration.
+ operational-status:
+ type: string
+ description: Indicator for whether the resource is considered operational.
+ configuration-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details from SDN-GC.
+ model-customization-id:
+ type: string
+ description: id of the configuration used to customize the resource
+ configurations:
+ description: |
+ Collection of configurations
+ properties:
+ configuration:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/configuration"
+ connector:
+ description: |
+ Collection of resource instances used to connect a variety of disparate inventory widgets
+ ###### Related Nodes
+ - TO virtual-data-center( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)
+ - CONNECTOR is DELETED when these are DELETED METADATUM
+ required:
+ - resource-instance-id
+ properties:
+ resource-instance-id:
+ type: string
+ description: Unique id of resource instance.
+ connectors:
+ description: |
+ Collection of resource instances used to connect a variety of disparate inventory widgets
+ properties:
+ connector:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/connector"
constrained-element-set:
description: |
This is how we would capture constraints defining allowed sets of elements.
###### Related Nodes
- - TO element-choice-set (comprises constrained-element-set, One2Many)
- - FROM model-element (is composed of constrained-element-set)
- - FROM model-constraint (is composed of constrained-element-set)
+ - TO model-constraint( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)
+ - TO model-element( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM element-choice-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)
+ - CONSTRAINED-ELEMENT-SET is DELETED when these are DELETED ELEMENT-CHOICE-SET
required:
- constrained-element-set-uuid
- constraint-type
@@ -44022,28 +58321,1472 @@ definitions:
type: string
check-type:
type: string
- resource-version:
+ constrained-element-sets:
+ properties:
+ constrained-element-set:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/constrained-element-set"
+ ctag-assignment:
+ description: |
+ ###### Related Nodes
+ - TO l3-network( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses ctag-assignment, ONE2MANY)
+ required:
+ - vlan-id-inner
+ properties:
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: id.
+ ctag-assignments:
+ properties:
+ ctag-assignment:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/ctag-assignment"
+ ctag-pool:
+ description: |
+ A collection of C tags (vlan tags) grouped for a specific purpose.
+ ###### Related Nodes
+ - TO complex( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)
+ - TO availability-zone( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)
+ - FROM vpls-pe( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)
+ required:
+ - target-pe
+ - availability-zone-name
+ - ctag-pool-purpose
+ properties:
+ target-pe:
type: string
- element-choice-sets:
+ description: The Target provider edge router
+ availability-zone-name:
+ type: string
+ description: Name of the availability zone
+ ctag-pool-purpose:
+ type: string
+ description: Describes what the intended purpose of this pool is.
+ ctag-values:
+ type: string
+ description: Comma separated list of ctags
+ ctag-pools:
+ properties:
+ ctag-pool:
type: array
- items:
- $ref: "#/definitions/element-choice-set"
- relationship-list:
+ items:
+ $ref: "#/patchDefinitions/ctag-pool"
+ customer:
+ description: |
+ customer identifiers to provide linkage back to BSS information.
+ ###### Related Nodes
+ - FROM service-subscription( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)
+ - CUSTOMER is DELETED when these are DELETED SERVICE-SUBSCRIPTION
+ required:
+ - global-customer-id
+ - subscriber-name
+ - subscriber-type
+ properties:
+ global-customer-id:
+ type: string
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ subscriber-name:
+ type: string
+ description: Subscriber name, an alternate way to retrieve a customer.
+ subscriber-type:
+ type: string
+ description: Subscriber type, a way to provide VID with only the INFRA customers.
+ customers:
+ description: |
+ Collection of customer identifiers to provide linkage back to BSS information.
+ properties:
+ customer:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/customer"
+ cvlan-tag-entry:
+ required:
+ - cvlan-tag
+ properties:
+ cvlan-tag:
+ type: integer
+ format: int64
+ description: See mis-na-virtualization-platform.yang
+ cvlan-tags:
+ properties:
+ cvlan-tag-entry:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/cvlan-tag-entry"
+ dvs-switch:
+ description: |
+ Digital virtual switch metadata, used by SDN-C to configure VCEs. A&AI needs to receive this data from the PO deployment team and administer it using the provisioningTool.sh into A&AI.
+ ###### Related Nodes
+ - TO cloud-region( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO availability-zone( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ required:
+ - switch-name
+ - vcenter-url
+ properties:
+ switch-name:
+ type: string
+ description: DVS switch name
+ vcenter-url:
+ type: string
+ description: URL used to reach the vcenter
+ dvs-switches:
+ description: |
+ Collection of digital virtual switch metadata used for vmWare VCEs and GenericVnfs.
+ properties:
+ dvs-switch:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/dvs-switch"
+ edge-prop-names:
+ description: |
+ Internal map to define the properties of an edge and interpret the map EdgeRules
+ properties:
+ edgeLabel:
+ type: string
+ direction:
+ type: string
+ multiplicityRule:
+ type: string
+ contains-other-v:
+ type: string
+ delete-other-v:
+ type: string
+ SVC-INFRA:
+ type: string
+ prevent-delete:
+ type: string
+ edge-tag-query-request:
+ properties:
+ edge-tag:
+ type: string
+ result-detail:
+ type: string
+ start-node-type:
+ type: string
+ start-node-filter:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/start-node-filter"
+ include-node-filter:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/include-node-filter"
+ secondary-filter:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/secondary-filter"
+ edge-tag-query-result:
+ properties:
+ tagged-inventory-item-list:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/tagged-inventory-item-list"
+ element-choice-set:
+ description: |
+ This is how we would capture constraints defining allowed sets of elements.
+ ###### Related Nodes
+ - TO constrained-element-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)
+ - ELEMENT-CHOICE-SET is DELETED when these are DELETED MODEL-ELEMENT
+ required:
+ - element-choice-set-uuid
+ - element-choice-set-name
+ properties:
+ element-choice-set-uuid:
+ type: string
+ element-choice-set-name:
+ type: string
+ cardinality:
+ type: string
+ element-choice-sets:
+ properties:
+ element-choice-set:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/element-choice-set"
+ entitlement:
+ description: |
+ Metadata for entitlement group.
+ ###### Related Nodes
+ - TO generic-vnf( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vce( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ required:
+ - group-uuid
+ - resource-uuid
+ properties:
+ group-uuid:
+ type: string
+ description: Unique ID for the entitlement group the resource comes from, should be uuid.
+ resource-uuid:
+ type: string
+ description: Unique ID of an entitlement resource.
+ entitlements:
+ description: |
+ Entitlements, keyed by group-uuid and resource-uuid, related to license management
+ properties:
+ entitlement:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/entitlement"
+ esr-ems:
+ description: |
+ Persist EMS address information used by EMS driver.
+ ###### Related Nodes
+ - TO esr-system-info (CHILD of esr-ems, esr-ems has esr-system-info, One2Many)
+ - ESR-EMS deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
+ required:
+ - ems-id
+ properties:
+ ems-id:
+ type: string
+ description: Unique ID of EMS.
+ esr-ems-list:
+ properties:
+ esr-ems:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/esr-ems"
+ esr-system-info:
+ description: |
+ Persist common address information of external systems.
+ ###### Related Nodes
+ - FROM esr-ems (PARENT of esr-system-info, esr-ems has esr-system-info)
+ - FROM esr-vnfm (PARENT of esr-system-info, esr-vnfm has esr-system-info)
+ - FROM esr-thirdparty-sdnc (PARENT of esr-system-info, esr-thirdparty-sdnc has esr-system-info)
+ - FROM cloud-region (PARENT of esr-system-info, cloud-region has esr-system-info)
+ required:
+ - esr-system-info-id
+ - user-name
+ - password
+ - system-type
+ properties:
+ esr-system-info-id:
+ type: string
+ description: Unique ID of esr system info.
+ system-name:
+ type: string
+ description: name of external system.
+ type:
+ type: string
+ description: type of external systems.
+ vendor:
+ type: string
+ description: vendor of external systems.
+ version:
+ type: string
+ description: version of external systems.
+ service-url:
+ type: string
+ description: url used to access external systems.
+ user-name:
+ type: string
+ description: username used to access external systems.
+ password:
+ type: string
+ description: password used to access external systems.
+ system-type:
+ type: string
+ description: it could be vim/vnfm/thirdparty-sdnc/ems-resource/ems-performance/ems-alarm.
+ protocol:
+ type: string
+ description: protocol of third party SDNC, for example netconf/snmp.
+ ssl-cacert:
+ type: string
+ description: ca file content if enabled ssl on auth-url.
+ ssl-insecure:
+ type: boolean
+ description: Whether to verify VIM's certificate.
+ ip-address:
+ type: string
+ description: service IP of ftp server.
+ port:
+ type: string
+ description: service port of ftp server.
+ cloud-domain:
+ type: string
+ description: domain info for authentication.
+ default-tenant:
+ type: string
+ description: default tenant of VIM.
+ passive:
+ type: boolean
+ description: ftp passive mode or not.
+ remote-path:
+ type: string
+ description: resource or performance data file path.
+ system-status:
+ type: string
+ description: the status of external system.
+ esr-system-info-list:
+ description: |
+ Collection of persistent block-level external system auth info.
+ properties:
+ esr-system-info:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/esr-system-info"
+ esr-thirdparty-sdnc:
+ description: |
+ Persist SDNC address information used by ONAP SDNC.
+ ###### Related Nodes
+ - TO esr-system-info (CHILD of esr-thirdparty-sdnc, esr-thirdparty-sdnc has esr-system-info, One2One)
+ - TO pnf( esr-thirdparty-sdnc has pnf, One2Many)
+ - ESR-THIRDPARTY-SDNC deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
+ required:
+ - thirdparty-sdnc-id
+ properties:
+ thirdparty-sdnc-id:
+ type: string
+ description: Unique ID of SDNC.
+ location:
+ type: string
+ description: used for DC type to indicate the location of SDNC, such as Core or Edge.
+ product-name:
+ type: string
+ description: password used to access SDNC server.
+ esr-thirdparty-sdnc-list:
+ properties:
+ esr-thirdparty-sdnc:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/esr-thirdparty-sdnc"
+ esr-vnfm:
+ description: |
+ Persist VNFM address information used by VF-C.
+ ###### Related Nodes
+ - TO esr-system-info (CHILD of esr-vnfm, esr-vnfm has esr-system-info, One2One)
+ - ESR-VNFM deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
+ required:
+ - vnfm-id
+ properties:
+ vnfm-id:
+ type: string
+ description: Unique ID of VNFM.
+ vim-id:
+ type: string
+ description: indecate the VIM to deploy VNF.
+ certificate-url:
+ type: string
+ description: certificate url of VNFM.
+ esr-vnfm-list:
+ properties:
+ esr-vnfm:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/esr-vnfm"
+ evc:
+ description: |
+ evc object is an optional child object of the Configuration object.
+ ###### Related Nodes
+ - TO configuration( evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)
+ required:
+ - evc-id
+ properties:
+ evc-id:
+ type: string
+ description: Unique/key field for the evc object
+ forwarding-path-topology:
+ type: string
+ description: Point-to-Point, Multi-Point
+ cir-value:
+ type: string
+ description: Commited Information Rate
+ cir-units:
+ type: string
+ description: CIR units
+ connection-diversity-group-id:
+ type: string
+ description: Diversity Group ID
+ service-hours:
+ type: string
+ description: formerly Performance Group
+ esp-evc-circuit-id:
+ type: string
+ description: EVC Circuit ID of ESP EVC
+ esp-evc-cir-value:
+ type: string
+ description: Committed Information Rate (For ESP)
+ esp-evc-cir-units:
+ type: string
+ description: CIR units (For ESP)
+ esp-itu-code:
+ type: string
+ description: Identifies ESP
+ collector-pop-clli:
+ type: string
+ description: Collector POP CLLI (from the hostname of the access pnf)
+ inter-connect-type-ingress:
+ type: string
+ description: Interconnect type on ingress side of EVC.
+ tagmode-access-ingress:
+ type: string
+ description: tagode for collector side of EVC
+ tagmode-access-egress:
+ type: string
+ description: tagMode for network side of EVC
+ evcs:
+ properties:
+ evc:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/evc"
+ external-system:
+ description: |
+ Namespace for external system.
+ properties:
+ esr-ems-list:
+ type: object
+ $ref: "#/patchDefinitions/esr-ems-list"
+ esr-vnfm-list:
+ type: object
+ $ref: "#/patchDefinitions/esr-vnfm-list"
+ esr-thirdparty-sdnc-list:
+ type: object
+ $ref: "#/patchDefinitions/esr-thirdparty-sdnc-list"
+ extra-properties:
+ description: |
+ Extra properties for inventory item for response list
+ properties:
+ extra-property:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/extra-property"
+ extra-property:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ flavor:
+ description: |
+ Openstack flavor.
+ ###### Related Nodes
+ - TO cloud-region( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)
+ - FLAVOR cannot be deleted if linked to VSERVER
+ required:
+ - flavor-id
+ - flavor-name
+ - flavor-selflink
+ properties:
+ flavor-id:
+ type: string
+ description: Flavor id, expected to be unique across cloud-region.
+ flavor-name:
+ type: string
+ description: Flavor name
+ flavor-vcpus:
+ type: integer
+ format: int32
+ description: Number of CPUs
+ flavor-ram:
+ type: integer
+ format: int32
+ description: Amount of memory
+ flavor-disk:
+ type: integer
+ format: int32
+ description: Disk space
+ flavor-ephemeral:
+ type: integer
+ format: int32
+ description: Amount of ephemeral disk space
+ flavor-swap:
+ type: string
+ description: amount of swap space allocation
+ flavor-is-public:
+ type: boolean
+ description: whether flavor is available to all users or private to the tenant it was created in.
+ flavor-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ flavor-disabled:
+ type: boolean
+ description: Boolean as to whether this flavor is no longer enabled
+ flavors:
+ description: |
+ Collection of openstack flavors.
+ properties:
+ flavor:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/flavor"
+ forwarder:
+ description: |
+ Entity describing a sequenced segment of forwarding path
+ ###### Related Nodes
+ - TO forwarding-path( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)
+ - TO l-interface( forwarder org.onap.relationships.inventory.ForwardsTo l-interface, MANY2ONE)
+ - TO configuration( forwarder org.onap.relationships.inventory.Uses configuration, ONE2ONE)
+ - TO lag-interface( forwarder org.onap.relationships.inventory.ForwardsTo lag-interface, MANY2ONE)
+ - TO p-interface( forwarder org.onap.relationships.inventory.ForwardsTo p-interface, MANY2ONE)
+ - FORWARDER deletion means associated objects of these types are also DELETED:CONFIGURATION
+ required:
+ - sequence
+ properties:
+ sequence:
+ type: integer
+ format: int32
+ description: Unique ID of this segmentation
+ forwarder-role:
+ type: string
+ description: ingress, intermediate, egress
+ forwarder-evc:
+ description: |
+ forwarder object is an optional child object of the Configuration object.
+ ###### Related Nodes
+ - TO configuration( forwarder-evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)
+ required:
+ - forwarder-evc-id
+ properties:
+ forwarder-evc-id:
+ type: string
+ description: Key for forwarder-evc object
+ circuit-id:
+ type: string
+ description: Circuit ID from customer/ESP/ingress end of EVC, or reference to beater circuit on gateway/network/egress end of EVC
+ ivlan:
+ type: string
+ description: Internal VLAN.
+ svlan:
+ type: string
+ description: SVLAN value for ingress of egress forwarder.
+ cvlan:
+ type: string
+ description: CVLAN value for ingress of egress forwarder.
+ forwarder-evcs:
+ properties:
+ forwarder-evc:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/forwarder-evc"
+ forwarders:
+ properties:
+ forwarder:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/forwarder"
+ forwarding-path:
+ description: |
+ Entity that describes the sequenced forwarding path between interfaces of services or resources
+ ###### Related Nodes
+ - TO service-instance( forwarding-path org.onap.relationships.inventory.AppliesTo service-instance, MANY2ONE)
+ - TO configuration( forwarding-path org.onap.relationships.inventory.Uses configuration, ONE2ONE)
+ - FROM forwarder( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)
+ - FORWARDING-PATH is DELETED when these are DELETED FORWARDER
+ - FORWARDING-PATH deletion means associated objects of these types are also DELETED:CONFIGURATION
+ required:
+ - forwarding-path-id
+ - forwarding-path-name
+ properties:
+ forwarding-path-id:
+ type: string
+ description: Unique ID of this FP
+ forwarding-path-name:
+ type: string
+ description: Name of the FP
+ forwarding-paths:
+ properties:
+ forwarding-path:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/forwarding-path"
+ generic-vnf:
+ description: |
+ General purpose VNF
+ ###### Related Nodes
+ - TO availability-zone( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - TO complex( generic-vnf org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)
+ - TO configuration( generic-vnf org.onap.relationships.inventory.Uses configuration, ONE2MANY)
+ - TO ctag-pool( generic-vnf org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)
+ - TO instance-group( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO ipsec-configuration( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)
+ - TO l3-network( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO license-key-resource( generic-vnf org.onap.relationships.inventory.Uses license-key-resource, MANY2MANY)
+ - TO pnf( generic-vnf tosca.relationships.HostedOn pnf, MANY2MANY)
+ - TO pserver( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)
+ - TO vnf-image( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)
+ - TO volume-group( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - TO vserver( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)
+ - TO virtual-data-center( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY)
+ - FROM entitlement( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM lag-interface( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM license( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM network-profile( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)
+ - FROM site-pair-set( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM line-of-business( line-of-business org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)
+ - FROM platform( platform org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)
+ - GENERIC-VNF is DELETED when these are DELETED ENTITLEMENT,VNFC,LAG-INTERFACE,LICENSE,L-INTERFACE,VF-MODULE
+ - GENERIC-VNF deletion means associated objects of these types are also DELETED:CONFIGURATION
+ required:
+ - vnf-id
+ - vnf-instance-id
+ - vnf-name
+ - vnf-type
+ - vnf-package-name
+ - vnf-discriptor-name
+ - job-id
+ - in-maint
+ - is-closed-loop-disabled
+ properties:
+ vnf-id:
+ type: string
+ description: Unique id of VNF. This is unique across the graph.
+ vnf-instance-id:
+ type: string
+ description: vnf instance id.
+ vnf-name:
+ type: string
+ description: Name of VNF.
+ vnf-name2:
+ type: string
+ description: Alternate name of VNF.
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ service-id:
+ type: string
+ description: Unique identifier of service, does not necessarily map to ASDC service models. SOON TO BE DEPRECATED
+ regional-resource-zone:
+ type: string
+ description: Regional way of organizing pservers, source of truth should define values
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ operational-status:
+ type: string
+ description: Indicator for whether the resource is considered operational. Valid values are in-service-path and out-of-service-path.
+ license-key:
+ type: string
+ description: OBSOLETE - do not use
+ equipment-role:
+ type: string
+ description: Client should send valid enumerated value
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, used by MSO.
+ vnf-package-name:
+ type: string
+ vnf-discriptor-name:
+ type: string
+ description: vnf discriptor name
+ job-id:
+ type: string
+ description: job id corresponding to vnf
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ management-option:
+ type: string
+ description: identifier of managed by ATT or customer
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by generic-vnf.
+ ipv4-loopback0-address:
+ type: string
+ description: v4 Loopback0 address
+ nm-lan-v6-address:
+ type: string
+ description: v6 Loopback address
+ management-v6-address:
+ type: string
+ description: v6 management address
+ vcpu:
+ type: integer
+ format: int64
+ description: number of vcpus ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only by uCPE
+ vcpu-units:
+ type: string
+ description: units associated with vcpu, used for VNFs with no vservers/flavors, to be used only by uCPE
+ vmemory:
+ type: integer
+ format: int64
+ description: number of GB of memory ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only by uCPE
+ vmemory-units:
+ type: string
+ description: units associated with vmemory, used for VNFs with no vservers/flavors, to be used only by uCPE
+ vdisk:
+ type: integer
+ format: int64
+ description: number of vdisks ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only uCPE
+ vdisk-units:
+ type: string
+ description: units associated with vdisk, used for VNFs with no vservers/flavors, to be used only by uCPE
+ nshd:
+ type: integer
+ format: int64
+ description: number of associated SHD in vnf.
+ nvm:
+ type: integer
+ format: int64
+ description: number of vms in vnf.
+ nnet:
+ type: integer
+ format: int64
+ description: number of network in vnf.
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
+ generic-vnfs:
+ description: |
+ Collection of VNFs
+ properties:
+ generic-vnf:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/generic-vnf"
+ group-assignment:
+ description: |
+ Openstack group-assignment used to store exclusivity groups (EG).
+ ###### Related Nodes
+ - TO cloud-region( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)
+ required:
+ - group-id
+ - group-type
+ - group-name
+ properties:
+ group-id:
+ type: string
+ description: Group id, expected to be unique across cloud-region.
+ group-type:
+ type: string
+ description: Group type - the type of group this instance refers to
+ group-name:
+ type: string
+ description: Group name - name assigned to the group
+ group-description:
+ type: string
+ description: Group description - description of the group
+ group-assignments:
+ description: |
+ Collection of openstack group assignments
+ properties:
+ group-assignment:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/group-assignment"
+ host-route:
+ description: |
+ ###### Related Nodes
+ - TO subnet( host-route org.onap.relationships.inventory.BelongsTo subnet, MANY2ONE)
+ required:
+ - host-route-id
+ - route-prefix
+ - next-hop
+ properties:
+ host-route-id:
+ type: string
+ description: host-route id
+ route-prefix:
+ type: string
+ description: subnet prefix
+ next-hop:
+ type: string
+ description: Could be ip-address, hostname, or service-instance
+ next-hop-type:
+ type: string
+ description: Should be ip-address, hostname, or service-instance to match next-hop
+ host-routes:
+ properties:
+ host-route:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/host-route"
+ image:
+ description: |
+ Openstack image.
+ ###### Related Nodes
+ - TO cloud-region( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)
+ - IMAGE cannot be deleted if linked to VSERVER
+ - IMAGE is DELETED when these are DELETED METADATUM
+ required:
+ - image-id
+ - image-name
+ - image-os-distro
+ - image-os-version
+ - image-selflink
+ properties:
+ image-id:
+ type: string
+ description: Image id, expected to be unique across cloud region
+ image-name:
+ type: string
+ description: Image name
+ image-architecture:
+ type: string
+ description: Operating system architecture.
+ image-os-distro:
+ type: string
+ description: The common name of the operating system distribution in lowercase
+ image-os-version:
+ type: string
+ description: The operating system version as specified by the distributor.
+ application:
+ type: string
+ description: The application that the image instantiates.
+ application-vendor:
+ type: string
+ description: The vendor of the application.
+ application-version:
+ type: string
+ description: The version of the application.
+ image-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ images:
+ description: |
+ Collectio of Openstack images.
+ properties:
+ image:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/image"
+ include-node-filter:
+ properties:
+ include-node-type:
+ type: string
+ instance-filter:
+ description: |
+ InstanceFilter for performing a named-query or model query
+ instance-filters:
+ description: |
+ InstanceFilters for performing a named-query or model query
+ properties:
+ instance-filter:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/instance-filter"
+ instance-group:
+ description: |
+ General mechanism for grouping instances
+ ###### Related Nodes
+ - TO model( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)
+ - FROM l3-network( l3-network org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM pnf( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM vip-ipv4-address-list( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM vip-ipv6-address-list( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ required:
+ - instance-group-role
+ - model-invariant-id
+ - model-version-id
+ - id
+ - description
+ - type
+ properties:
+ instance-group-role:
+ type: string
+ description: role of the instance group.
+ model-invariant-id:
+ type: string
+ description: ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: ASDC model version uid for this resource model.
+ id:
+ type: string
+ description: Instance Group ID, UUID assigned to this instance.
+ description:
+ type: string
+ description: Descriptive text to help identify the usage of this instance-group
+ type:
+ type: string
+ description: Only valid value today is lower case ha for high availability
+ sub-type:
+ type: string
+ description: Valid values for ha type are [geo-activeactive, geo-activestandby, local-activeactive, local-activestandby]
+ instance-groups:
+ description: |
+ Collection of openstack route table references
+ properties:
+ instance-group:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/instance-group"
+ inventory:
+ properties:
+ search:
+ type: object
+ $ref: "#/patchDefinitions/search"
+ actions:
+ type: object
+ $ref: "#/patchDefinitions/actions"
+ cloud-infrastructure:
+ type: object
+ $ref: "#/patchDefinitions/cloud-infrastructure"
+ external-system:
+ type: object
+ $ref: "#/patchDefinitions/external-system"
+ business:
+ type: object
+ $ref: "#/patchDefinitions/business"
+ service-design-and-creation:
+ type: object
+ $ref: "#/patchDefinitions/service-design-and-creation"
+ network:
+ type: object
+ $ref: "#/patchDefinitions/network"
+ aai-internal:
+ type: object
+ $ref: "#/patchDefinitions/aai-internal"
+ nodes:
type: array
items:
- $ref: "#/definitions/relationship"
- constrained-element-sets:
+ $ref: "#/patchDefinitions/aai-internal"
+ inventory-item:
properties:
- constrained-element-set:
+ inventory-item-type:
+ type: string
+ inventory-item-link:
+ type: string
+ inventory-item-data:
type: array
items:
- $ref: "#/definitions/constrained-element-set"
+ $ref: "#/patchDefinitions/inventory-item-data"
+ tagged-inventory-item-list:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/tagged-inventory-item-list"
+ inventory-item-data:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ inventory-response-item:
+ description: |
+ Inventory item for response list
+ properties:
+ model-name:
+ type: string
+ extra-properties:
+ type: object
+ $ref: "#/patchDefinitions/extra-properties"
+ inventory-response-items:
+ type: object
+ $ref: "#/patchDefinitions/inventory-response-items"
+ inventory-response-items:
+ description: |
+ Container for inventory items in response list
+ properties:
+ inventory-response-item:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/inventory-response-item"
+ ipsec-configuration:
+ description: |
+ IPSec configuration node will contain various configuration data for the NMTE VNF. This node will have an edge to the generic-vnf (vnf type = TE). Starting 1607, this data will be populated by SDN-C
+ ###### Related Nodes
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)
+ - FROM vig-server( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)
+ - IPSEC-CONFIGURATION is DELETED when these are DELETED VIG-SERVER
+ required:
+ - ipsec-configuration-id
+ properties:
+ ipsec-configuration-id:
+ type: string
+ description: UUID of this configuration
+ requested-vig-address-type:
+ type: string
+ description: Indicate the type of VIG server like AVPN, INTERNET, BOTH
+ requested-encryption-strength:
+ type: string
+ description: Encryption values like 3des-cbc, des-cbc, aes-128-cbc, aes-192-cbc, aes-265-cbc
+ requested-dmz-type:
+ type: string
+ description: ATT can offer a shared DMZ or a DMZ specific to a customer
+ shared-dmz-network-address:
+ type: string
+ description: Network address of shared DMZ
+ requested-customer-name:
+ type: string
+ description: If the DMZ is a custom DMZ, this field will indicate the customer information
+ ike-version:
+ type: string
+ description: can be 1 or 2
+ ikev1-authentication:
+ type: string
+ description: Contains values like md5, sha1, sha256, sha384
+ ikev1-encryption:
+ type: string
+ description: Encyption values like 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
+ ikev1-dh-group:
+ type: string
+ description: Diffie-Hellman group like DH-GROUP2, DH-GROUP5, DH-GROUP14
+ ikev1-am-group-id:
+ type: string
+ description: Group name defined in VIG for clients using aggressive mode
+ ikev1-am-password:
+ type: string
+ description: pre-shared key for the above group name
+ ikev1-sa-lifetime:
+ type: string
+ description: Lifetime for IKEv1 SA
+ ipsec-authentication:
+ type: string
+ description: md5, sha1, sha256, sha384
+ ipsec-encryption:
+ type: string
+ description: 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
+ ipsec-sa-lifetime:
+ type: string
+ description: Life time for IPSec SA
+ ipsec-pfs:
+ type: string
+ description: enable PFS or not
+ xauth-userid:
+ type: string
+ description: user ID for xAuth, sm-user,ucpeHostName,nmteHostName
+ xauth-user-password:
+ type: string
+ description: Encrypted using the Juniper $9$ algorithm
+ dpd-interval:
+ type: string
+ description: The time between DPD probe
+ dpd-frequency:
+ type: string
+ description: Maximum number of DPD before claiming the tunnel is down
+ ipsec-configurations:
+ properties:
+ ipsec-configuration:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/ipsec-configuration"
+ key-data:
+ properties:
+ key-name:
+ type: string
+ key-value:
+ type: string
+ l-interface:
+ description: |
+ Logical interfaces, e.g., a vnic.
+ ###### Related Nodes
+ - TO generic-vnf( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO lag-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)
+ - TO instance-group( l-interface org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO l-interface( l-interface org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - TO logical-link( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)
+ - TO newvce( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)
+ - TO p-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)
+ - TO vserver( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.Uses l-interface, ONE2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - FROM sriov-vf( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)
+ - FROM vlan( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - L-INTERFACE is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST,SRIOV-VF,VLAN
+ - L-INTERFACE deletion means associated objects of these types are also DELETED:LOGICAL-LINK
+ required:
+ - interface-name
+ - is-port-mirrored
+ - in-maint
+ - is-ip-unnumbered
+ properties:
+ interface-name:
+ type: string
+ description: Name given to the interface
+ interface-role:
+ type: string
+ description: E.g., CUSTOMER, UPLINK, etc.
+ v6-wan-link-ip:
+ type: string
+ description: Questionably placed - v6 ip addr of this interface (is in vr-lan-interface from Mary B.
+ selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ interface-id:
+ type: string
+ description: ID of interface
+ macaddr:
+ type: string
+ description: MAC address for the interface
+ network-name:
+ type: string
+ description: Name of the network
+ management-option:
+ type: string
+ description: Whether A&AI should be managing this interface of not. Could have value like CUSTOMER
+ interface-description:
+ type: string
+ description: Human friendly text regarding this interface.
+ is-port-mirrored:
+ type: boolean
+ l-interfaces:
+ description: |
+ Collection of logical interfaces.
+ properties:
+ l-interface:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/l-interface"
+ l3-interface-ipv4-address-list:
+ description: |
+ IPv4 Address Range
+ ###### Related Nodes
+ - TO instance-group( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)
+ - TO l3-network( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - TO subnet( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - TO l-interface( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - TO vlan( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ - TO vnfc( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vnfc, MANY2ONE)
+ required:
+ - l3-interface-ipv4-address
+ properties:
+ l3-interface-ipv4-address:
+ type: string
+ description: IP address
+ l3-interface-ipv4-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 32 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ l3-interface-ipv6-address-list:
+ description: |
+ IPv6 Address Range
+ ###### Related Nodes
+ - TO instance-group( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)
+ - TO l3-network( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - TO subnet( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - TO l-interface( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - TO vlan( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ - TO vnfc( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vnfc, MANY2ONE)
+ required:
+ - l3-interface-ipv6-address
+ properties:
+ l3-interface-ipv6-address:
+ type: string
+ description: IP address
+ l3-interface-ipv6-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 128 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ l3-network:
+ description: |
+ Generic network definition
+ ###### Related Nodes
+ - TO instance-group( l3-network org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO network-policy( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)
+ - TO route-table-reference( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)
+ - TO vpn-binding( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM complex( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - FROM ctag-assignment( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM segmentation-assignment( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)
+ - FROM subnet( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)
+ - L3-NETWORK is DELETED when these are DELETED CTAG-ASSIGNMENT,SEGMENTATION-ASSIGNMENT,SUBNET
+ required:
+ - network-id
+ - network-name
+ - is-bound-to-vpn
+ - is-provider-network
+ - is-shared-network
+ - is-external-network
+ properties:
+ network-id:
+ type: string
+ description: Network ID, should be uuid. Unique across A&AI.
+ network-name:
+ type: string
+ description: Name of the network, governed by some naming convention..
+ network-type:
+ type: string
+ description: Type of the network - who defines these values?
+ network-role:
+ type: string
+ description: Role the network plans - who defines these values?
+ network-technology:
+ type: string
+ description: Network technology - who defines these values?
+ neutron-network-id:
+ type: string
+ description: Neutron network id of this Interface
+ is-bound-to-vpn:
+ type: boolean
+ service-id:
+ type: string
+ description: Unique identifier of service from ASDC. Does not strictly map to ASDC services. SOON TO BE DEPRECATED
+ network-role-instance:
+ type: integer
+ format: int64
+ description: network role instance
+ l3-networks:
+ properties:
+ l3-network:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/l3-network"
+ lag-interface:
+ description: |
+ Link aggregate interface
+ ###### Related Nodes
+ - TO generic-vnf( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO lag-link( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)
+ - TO logical-link( lag-interface org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - TO p-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)
+ - TO pnf( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - TO pserver( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - TO vpls-pe( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)
+ - LAG-INTERFACE is DELETED when these are DELETED L-INTERFACE
+ - LAG-INTERFACE deletion means associated objects of these types are also DELETED:LAG-LINK,LOGICAL-LINK
+ required:
+ - interface-name
+ - in-maint
+ properties:
+ interface-name:
+ type: string
+ description: Name that identifies the link aggregate interface
+ interface-description:
+ type: string
+ description: Human friendly text regarding this interface.
+ lag-interfaces:
+ description: |
+ Collection of link aggregate interfaces.
+ properties:
+ lag-interface:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/lag-interface"
+ lag-link:
+ description: |
+ LAG links can connect lag-interfaces
+ ###### Related Nodes
+ - FROM lag-interface( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)
+ required:
+ - link-name
+ properties:
+ link-name:
+ type: string
+ description: Alphabetical concatenation of lag-interface names
+ lag-links:
+ description: |
+ Collection of link aggregation connections
+ properties:
+ lag-link:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/lag-link"
+ license:
+ description: |
+ Metadata for license group.
+ ###### Related Nodes
+ - TO generic-vnf( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vce( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ required:
+ - group-uuid
+ - resource-uuid
+ properties:
+ group-uuid:
+ type: string
+ description: Unique ID for the license group the resource belongs to, should be uuid.
+ resource-uuid:
+ type: string
+ description: Unique ID of a license resource.
+ licenses:
+ description: |
+ Licenses to be allocated across resources, keyed by group-uuid and resource-uuid, related to license management
+ properties:
+ license:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/license"
+ line-of-business:
+ description: |
+ describes a line-of-business
+ ###### Related Nodes
+ - TO generic-vnf( line-of-business org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)
+ required:
+ - line-of-business-name
+ properties:
+ line-of-business-name:
+ type: string
+ description: Name of the line-of-business (product)
+ lines-of-business:
+ description: |
+ Collection of lines-of-business
+ properties:
+ line-of-business:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/line-of-business"
+ logical-link:
+ description: |
+ Logical links generally connect l-interfaces but are used to express logical connectivity between two points
+ ###### Related Nodes
+ - TO cloud-region( logical-link org.onap.relationships.inventory.LocatedIn cloud-region, MANY2MANY)
+ - TO generic-vnf( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)
+ - TO lag-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)
+ - TO logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - TO pnf( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)
+ - TO pserver( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)
+ - TO vpn-binding( logical-link org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - TO virtual-data-center( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM configuration( configuration org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - FROM lag-interface( lag-interface org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)
+ - FROM p-interface( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - FROM vlan( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ required:
+ - link-name
+ - in-maint
+ - link-type
+ properties:
+ link-name:
+ type: string
+ description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
+ in-maint:
+ type: boolean
+ link-type:
+ type: string
+ description: Type of logical link, e.g., evc
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ ip-version:
+ type: string
+ description: v4, v6, or ds for dual stack
+ routing-protocol:
+ type: string
+ description: For example, static or BGP
+ logical-links:
+ description: |
+ Collection of logical connections
+ properties:
+ logical-link:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/logical-link"
+ metadata:
+ description: |
+ Collection of metadatum (key/value pairs)
+ properties:
+ metadatum:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/metadatum"
+ metadatum:
+ description: |
+ Key/value pairs
+ ###### Related Nodes
+ - TO configuration( metadatum org.onap.relationships.inventory.BelongsTo configuration, MANY2ONE)
+ - TO connector( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)
+ - TO image( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)
+ - TO service-instance( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - TO model-ver( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ required:
+ - metaname
+ - metaval
+ properties:
+ metaname:
+ type: string
+ metaval:
+ type: string
+ model:
+ description: |
+ Subgraph definition provided by ASDC to describe an inventory asset and its connections related to ASDC models, independent of version
+ ###### Related Nodes
+ - TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - FROM instance-group( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY)
+ - FROM model-ver( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - FROM named-query( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)
+ - MODEL cannot be deleted if linked to INSTANCE-GROUP,NAMED-QUERY,NAMED-QUERY-ELEMENT
+ - MODEL is DELETED when these are DELETED MODEL-VER
+ required:
+ - model-invariant-id
+ - model-type
+ properties:
+ model-invariant-id:
+ type: string
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ model-type:
+ type: string
+ description: Type of the model, e.g., service, resource, widget, etc.
+ model-and-named-query-search:
+ description: |
+ ModelAndNamedQuerySearch holds query-parameters and instance-properties for performing a named-query or model query
+ properties:
+ query-parameters:
+ type: object
+ $ref: "#/patchDefinitions/query-parameters"
+ instance-filters:
+ type: object
+ $ref: "#/patchDefinitions/instance-filters"
+ secondary-filts:
+ type: object
+ $ref: "#/patchDefinitions/secondary-filts"
+ top-node-type:
+ type: string
+ secondary-filter-cut-point:
+ type: string
model-constraint:
description: |
This is how we would capture constraints defining allowed sets of elements.
###### Related Nodes
- - TO constrained-element-set (comprises model-constraint, One2Many)
- - FROM model-element (is composed of model-constraint)
+ - TO model-element( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)
+ - MODEL-CONSTRAINT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET
required:
- model-constraint-uuid
- constrained-element-set-uuid-to-replace
@@ -44055,27 +59798,25 @@ definitions:
constrained-element-sets:
type: array
items:
- $ref: "#/definitions/constrained-element-set"
- resource-version:
- type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ $ref: "#/patchDefinitions/constrained-element-set"
model-constraints:
properties:
model-constraint:
type: array
items:
- $ref: "#/definitions/model-constraint"
+ $ref: "#/patchDefinitions/model-constraint"
model-element:
description: |
Defines how other models combine to make up a higher-level model.
###### Related Nodes
- - TO model-ver (Many2One)
- - TO model-element (comprises model-element, One2Many)
- - TO model-constraint (comprises model-element, One2Many)
- - TO constrained-element-set (comprises model-element, One2Many)
- - FROM model-ver (is composed of model-element)
- - FROM element-choice-set (is composed of model-element)
- - FROM model-element (is composed of model-element)
+ - TO element-choice-set( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)
+ - TO model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - TO model-ver( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE)
+ - TO model-ver( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM model-constraint( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - MODEL-ELEMENT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET,MODEL-CONSTRAINT
required:
- model-element-uuid
- new-data-del-flag
@@ -44091,37 +59832,22 @@ definitions:
description: How many of this type of element are required/allowed
linkage-points:
type: string
- resource-version:
- type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- model-elements:
- type: array
- items:
- $ref: "#/definitions/model-element"
- description: Defines how other models combine to make up a higher-level model
- model-constraints:
- type: array
- items:
- $ref: "#/definitions/model-constraint"
- description: Describes new constraints on this model element that are not part of that model's definition
- relationship-list:
- type: array
- items:
- $ref: "#/definitions/relationship"
model-elements:
properties:
model-element:
type: array
items:
- $ref: "#/definitions/model-element"
+ $ref: "#/patchDefinitions/model-element"
model-ver:
description: |
Subgraph definition provided by ASDC to describe a specific version of an inventory asset and its connections related to ASDC models
###### Related Nodes
- - TO model-element (comprises model-ver, One2Many)
- - TO metadatum (comprises model-ver, One2Many)
- - FROM model (is composed of model-ver)
- - FROM model-element
+ - TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - MODEL-VER cannot be deleted if linked to MODEL-ELEMENT
+ - MODEL-VER is DELETED when these are DELETED MODEL-ELEMENT,METADATUM
required:
- model-version-id
- model-name
@@ -44139,105 +59865,719 @@ definitions:
model-description:
type: string
description: Description
- resource-version:
+ model-vers:
+ properties:
+ model-ver:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/model-ver"
+ models:
+ description: |
+ Collection of subgraph definitions provided by ASDC to describe the inventory assets and their connections related to ASDC models
+ properties:
+ model:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/model"
+ multicast-configuration:
+ description: |
+ ###### Related Nodes
+ - FROM vlan( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)
+ required:
+ - multicast-configuration-id
+ - multicast-protocol
+ - rp-type
+ properties:
+ multicast-configuration-id:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- model-elements:
+ description: Unique id of multicast configuration.
+ multicast-protocol:
+ type: string
+ description: protocol of multicast configuration
+ rp-type:
+ type: string
+ description: rp type of multicast configuration
+ multicast-configurations:
+ description: |
+ multicast configuration of generic-vnf ip-address
+ properties:
+ multicast-configuration:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/multicast-configuration"
+ named-queries:
+ properties:
+ named-query:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/named-query"
+ named-query:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - TO model( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - NAMED-QUERY is DELETED when these are DELETED NAMED-QUERY-ELEMENT
+ required:
+ - named-query-uuid
+ - named-query-name
+ - named-query-version
+ properties:
+ named-query-uuid:
+ type: string
+ named-query-name:
+ type: string
+ named-query-version:
+ type: string
+ required-input-param:
+ type: string
+ description:
+ type: string
+ named-query-element:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - TO model( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)
+ - TO named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM property-constraint( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM related-lookup( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - NAMED-QUERY-ELEMENT is DELETED when these are DELETED PROPERTY-CONSTRAINT,RELATED-LOOKUP
+ required:
+ - named-query-element-uuid
+ properties:
+ named-query-element-uuid:
+ type: string
+ property-collect-list:
+ type: string
+ named-query-elements:
+ properties:
+ named-query-element:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/named-query-element"
+ network:
+ description: |
+ Namespace for network inventory resources.
+ properties:
+ logical-links:
type: array
items:
- $ref: "#/definitions/model-element"
- metadata:
+ $ref: "#/patchDefinitions/logical-link"
+ site-pair-sets:
type: array
items:
- $ref: "#/definitions/metadatum"
- relationship-list:
+ $ref: "#/patchDefinitions/site-pair-set"
+ vpn-bindings:
type: array
items:
- $ref: "#/definitions/relationship"
- model-vers:
+ $ref: "#/patchDefinitions/vpn-binding"
+ vpls-pes:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vpls-pe"
+ multicast-configurations:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/multicast-configuration"
+ vces:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vce"
+ vnfcs:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vnfc"
+ l3-networks:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/l3-network"
+ network-policies:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/network-policy"
+ generic-vnfs:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/generic-vnf"
+ lag-links:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/lag-link"
+ newvces:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/newvce"
+ pnfs:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/pnf"
+ physical-links:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/physical-link"
+ ipsec-configurations:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/ipsec-configuration"
+ route-table-references:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/route-table-reference"
+ instance-groups:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/instance-group"
+ zones:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/zone"
+ configurations:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/configurations"
+ network-policies:
properties:
- model-ver:
+ network-policy:
type: array
items:
- $ref: "#/definitions/model-ver"
- model:
+ $ref: "#/patchDefinitions/network-policy"
+ network-policy:
description: |
- Subgraph definition provided by ASDC to describe an inventory asset and its connections related to ASDC models, independent of version
###### Related Nodes
- - TO model-ver (comprises model, One2Many)
- - FROM named-query
- - FROM named-query-element
- - FROM instance-group
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.Uses network-policy, ONE2ONE)
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)
+ required:
+ - network-policy-id
+ properties:
+ network-policy-id:
+ type: string
+ description: UUID representing unique key to this instance
+ network-policy-fqdn:
+ type: string
+ description: Contrail FQDN for the policy
+ heat-stack-id:
+ type: string
+ description: ID for the openStack Heat instance
+ network-profile:
+ description: |
+ Network profile populated by SDN-GP for SNMP
+ ###### Related Nodes
+ - TO generic-vnf( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ required:
+ - nm-profile-name
+ properties:
+ nm-profile-name:
+ type: string
+ description: Unique name of network profile.
+ community-string:
+ type: string
+ description: Encrypted SNMP community string
+ network-profiles:
+ description: |
+ Collection of network profiles
+ properties:
+ network-profile:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/network-profile"
+ newvce:
+ description: |
+ This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce.
+ ###### Related Nodes
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)
+ - NEWVCE is DELETED when these are DELETED L-INTERFACE
+ required:
+ - vnf-id2
+ - vnf-name
+ - vnf-type
+ properties:
+ vnf-id2:
+ type: string
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ vnf-name:
+ type: string
+ description: Name of VNF.
+ vnf-name2:
+ type: string
+ description: Alternate name of VNF.
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+ operational-status:
+ type: string
+ description: Indicator for whether the resource is considered operational
+ license-key:
+ type: string
+ description: OBSOLETE - do not use
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address).
+ equipment-role:
+ type: string
+ description: Client should send valid enumerated value.
+ newvces:
+ description: |
+ This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce.
+ properties:
+ newvce:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/newvce"
+ notification-event:
+ properties:
+ cambria.partition:
+ type: string
+ notification-event-header:
+ type: object
+ $ref: "#/patchDefinitions/notification-event-header"
+ notification-event-header:
+ properties:
+ id:
+ type: string
+ timestamp:
+ type: string
+ source-name:
+ type: string
+ domain:
+ type: string
+ sequence-number:
+ type: string
+ severity:
+ type: string
+ event-type:
+ type: string
+ version:
+ type: string
+ action:
+ type: string
+ entity-type:
+ type: string
+ top-entity-type:
+ type: string
+ entity-link:
+ type: string
+ status:
+ type: string
+ notify:
+ required:
+ - event-id
+ properties:
+ event-id:
+ type: string
+ node-type:
+ type: string
+ event-trigger:
+ type: string
+ key-data:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/key-data"
+ selflink:
+ type: string
+ oam-network:
+ description: |
+ OAM network, to be deprecated shortly. Do not use for new purposes.
+ ###### Related Nodes
+ - TO cloud-region( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO complex( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)
+ - TO service-capability( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ required:
+ - network-uuid
+ - network-name
+ - cvlan-tag
+ properties:
+ network-uuid:
+ type: string
+ description: UUID of the network. Unique across a cloud-region
+ network-name:
+ type: string
+ description: Name of the network.
+ cvlan-tag:
+ type: integer
+ format: int64
+ description: cvlan-id
+ ipv4-oam-gateway-address:
+ type: string
+ description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
+ ipv4-oam-gateway-address-prefix-length:
+ type: integer
+ format: int32
+ description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
+ oam-networks:
+ description: |
+ Collection of OAM networks, to be deprecated shortly. Do not use for new purposes.
+ properties:
+ oam-network:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/oam-network"
+ operational-environment:
+ description: |
+ It is a logical partition of the cloud which allows to have multiple environments in the production AIC.
+ ###### Related Nodes
+ - TO operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)
+ - FROM operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)
+ required:
+ - operational-environment-id
+ - operational-environment-name
+ - operational-environment-type
+ - operational-environment-status
+ - tenant-context
+ - workload-context
+ properties:
+ operational-environment-id:
+ type: string
+ description: UUID of an operational environment
+ operational-environment-name:
+ type: string
+ description: Operational Environment name
+ operational-environment-type:
+ type: string
+ description: Operational Environment Type.
+ operational-environment-status:
+ type: string
+ description: Status
+ tenant-context:
+ type: string
+ description: Tenant Context.
+ workload-context:
+ type: string
+ description: Workload Context.
+ operational-environments:
+ description: |
+ a logical partition of the cloud which allows to have multiple environments in the production AIC.
+ properties:
+ operational-environment:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/operational-environment"
+ overloaded-model:
+ description: |
+ Allows for legacy POST of old-style and new-style models
required:
- model-invariant-id
+ - model-name-version-id
- model-type
+ - model-name
+ - model-id
+ - model-version
properties:
model-invariant-id:
type: string
description: Unique identifier corresponding to the main definition of a model in ASDC
+ model-name-version-id:
+ type: string
+ description: Unique identifier corresponding to one version of a model in ASDC
model-type:
type: string
description: Type of the model, e.g., service, resource, widget, etc.
- resource-version:
+ model-name:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- model-vers:
+ description: Name of the model, which can change from version to version.
+ model-id:
+ type: string
+ description: Invariant unique ID which does not change from version to version
+ model-version:
+ type: string
+ description: Version
+ model-description:
+ type: string
+ description: Description
+ owning-entities:
+ description: |
+ Collection of owning-entities
+ properties:
+ owning-entity:
type: array
- items:
- $ref: "#/definitions/model-ver"
- relationship-list:
+ items:
+ $ref: "#/patchDefinitions/owning-entity"
+ owning-entity:
+ description: |
+ describes an owning-entity
+ ###### Related Nodes
+ - FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo owning-entity, MANY2ONE)
+ required:
+ - owning-entity-id
+ - owning-entity-name
+ properties:
+ owning-entity-id:
+ type: string
+ description: UUID of an owning entity
+ owning-entity-name:
+ type: string
+ description: Owning entity name
+ p-interface:
+ description: |
+ Physical interface (e.g., nic)
+ ###### Related Nodes
+ - TO logical-link( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)
+ - TO physical-link( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)
+ - TO pnf( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - TO pserver( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - TO vpls-pe( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM lag-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)
+ - FROM sriov-pf( sriov-pf org.onap.relationships.inventory.BelongsTo p-interface, ONE2ONE)
+ - P-INTERFACE is DELETED when these are DELETED L-INTERFACE,SRIOV-PF
+ - P-INTERFACE deletion means associated objects of these types are also DELETED:PHYSICAL-LINK
+ required:
+ - interface-name
+ - in-maint
+ properties:
+ interface-name:
+ type: string
+ description: Name that identifies the physical interface
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ port-description:
+ type: string
+ description: Nature of the services and connectivity on this port.
+ equipment-identifier:
+ type: string
+ description: CLEI or other specification for p-interface hardware.
+ interface-role:
+ type: string
+ description: Role specification for p-interface hardware.
+ interface-type:
+ type: string
+ description: Indicates the physical properties of the interface.
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ mac-addresss:
+ type: string
+ description: MAC Address of the p-interface.
+ p-interfaces:
+ description: |
+ Collection of physical interfaces.
+ properties:
+ p-interface:
type: array
- items:
- $ref: "#/definitions/relationship"
- models:
+ items:
+ $ref: "#/patchDefinitions/p-interface"
+ physical-link:
description: |
- Collection of subgraph definitions provided by ASDC to describe the inventory assets and their connections related to ASDC models
+ Collection of physical connections, typically between p-interfaces
+ ###### Related Nodes
+ - FROM p-interface( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)
+ required:
+ - link-name
properties:
- model:
+ link-name:
+ type: string
+ description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ circuit-id:
+ type: string
+ description: Circuit it
+ dual-mode:
+ type: string
+ description: Dual access mode (e.g., primary, secondary
+ management-option:
+ type: string
+ description: To provide information on who manages this circuit. A&AI or 3rd party transport provider
+ service-provider-name:
+ type: string
+ description: Name of the service Provider on this link.
+ service-provider-bandwidth-up-value:
+ type: integer
+ format: int32
+ description: Upstream Bandwidth value agreed with the service provider
+ service-provider-bandwidth-up-units:
+ type: string
+ description: Units for the upstream BW value
+ service-provider-bandwidth-down-value:
+ type: integer
+ format: int32
+ description: Downstream Bandwidth value agreed with the service provider
+ service-provider-bandwidth-down-units:
+ type: string
+ description: Units for downstream BW value
+ physical-links:
+ description: |
+ Collection of physical connections, typically between p-interfaces
+ properties:
+ physical-link:
type: array
items:
- $ref: "#/definitions/model"
- related-lookup:
+ $ref: "#/patchDefinitions/physical-link"
+ platform:
description: |
- TBD
+ describes a platform
###### Related Nodes
- - FROM named-query-element (is composed of related-lookup)
+ - TO generic-vnf( platform org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)
required:
- - related-lookup-uuid
- - source-node-type
- - source-node-property
- - target-node-type
- - target-node-property
+ - platform-name
properties:
- related-lookup-uuid:
+ platform-name:
type: string
- source-node-type:
+ description: Name of the platform
+ platforms:
+ description: |
+ Collection of platforms
+ properties:
+ platform:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/platform"
+ pnf:
+ description: |
+ PNF represents a physical network function. typically equipment used in the D1 world. in 1607, this will be populated by SDN-C to represent a premises router that a uCPE connects to. But this can be used to represent any physical device that is not an AIC node or uCPE.
+ ###### Related Nodes
+ - TO complex( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO instance-group( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO zone( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM esr-thirdparty-sdnc( esr-thirdparty-sdnc has pnf, One2Many)
+ - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn pnf, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf pnf, ONE2MANY)
+ - PNF is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
+ required:
+ - pnf-name
+ - in-maint
+ properties:
+ pnf-name:
type: string
- source-node-property:
+ description: unique name of Physical Network Function.
+ pnf-name2:
type: string
- target-node-type:
+ description: name of Physical Network Function.
+ pnf-name2-source:
type: string
- target-node-property:
+ description: source of name2
+ pnf-id:
type: string
- property-collect-list:
+ description: id of pnf
+ equip-type:
type: string
- resource-version:
+ description: Equipment type. Source of truth should define valid values.
+ equip-vendor:
type: string
- relationship-list:
+ description: Equipment vendor. Source of truth should define valid values.
+ equip-model:
+ type: string
+ description: Equipment model. Source of truth should define valid values.
+ management-option:
+ type: string
+ description: identifier of managed by ATT or customer
+ ipaddress-v4-oam:
+ type: string
+ description: ipv4-oam-address with new naming convention for IP addresses
+ sw-version:
+ type: string
+ description: sw-version is the version of SW for the hosted application on the PNF.
+ in-maint:
+ type: boolean
+ frame-id:
+ type: string
+ description: ID of the physical frame (relay rack) where pnf is installed.
+ serial-number:
+ type: string
+ description: Serial number of the device
+ ipaddress-v4-loopback-0:
+ type: string
+ description: IPV4 Loopback 0 address
+ ipaddress-v6-loopback-0:
+ type: string
+ description: IPV6 Loopback 0 address
+ ipaddress-v4-aim:
+ type: string
+ description: IPV4 AIM address
+ ipaddress-v6-aim:
+ type: string
+ description: IPV6 AIM address
+ ipaddress-v6-oam:
+ type: string
+ description: IPV6 OAM address
+ inv-status:
+ type: string
+ description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
+ pnfs:
+ description: |
+ Collection of Physical Network Functions.
+ properties:
+ pnf:
type: array
- items:
- $ref: "#/definitions/relationship"
- related-lookups:
+ items:
+ $ref: "#/patchDefinitions/pnf"
+ port-group:
+ description: |
+ Used to capture the network interfaces of this VCE
+ ###### Related Nodes
+ - TO vce( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM cvlan-tag( cvlan-tag org.onap.relationships.inventory.BelongsTo port-group, MANY2ONE)
+ - PORT-GROUP is DELETED when these are DELETED CVLAN-TAG
+ required:
+ - interface-id
+ - orchestration-status
properties:
- related-lookup:
+ interface-id:
+ type: string
+ description: Unique ID of the interface
+ neutron-network-id:
+ type: string
+ description: Neutron network id of this Interface
+ neutron-network-name:
+ type: string
+ description: Neutron network name of this Interface
+ interface-role:
+ type: string
+ description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
+ port-groups:
+ properties:
+ port-group:
type: array
items:
- $ref: "#/definitions/related-lookup"
+ $ref: "#/patchDefinitions/port-group"
+ project:
+ description: |
+ describes the project
+ ###### Related Nodes
+ - TO service-instance( project org.onap.relationships.inventory.Uses service-instance, ONE2MANY)
+ required:
+ - project-name
+ properties:
+ project-name:
+ type: string
+ description: Name of the project deploying a service
+ projects:
+ description: |
+ Collection of projects
+ properties:
+ project:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/project"
+ properties:
+ description: |
+ Property holder for query properties or instance properties
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
property-constraint:
description: |
TBD
###### Related Nodes
- - FROM named-query-element (is composed of property-constraint)
+ - TO named-query-element( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
required:
- property-constraint-uuid
- constraint-type
@@ -44252,96 +60592,393 @@ definitions:
type: string
property-value:
type: string
- resource-version:
- type: string
property-constraints:
properties:
property-constraint:
type: array
items:
- $ref: "#/definitions/property-constraint"
- named-query-element:
+ $ref: "#/patchDefinitions/property-constraint"
+ pserver:
description: |
- TBD
+ Compute host whose hostname must be unique and must exactly match what is sent as a relationship to a vserver.
###### Related Nodes
- - TO named-query-element (comprises named-query-element, Many2Many)
- - TO model (Many2One)
- - TO property-constraint (comprises named-query-element, One2Many)
- - TO related-lookup (comprises named-query-element, One2Many)
- - FROM named-query (is composed of named-query-element)
- - FROM named-query-element (is composed of named-query-element)
+ - TO group-assignment( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)
+ - TO availability-zone( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)
+ - TO cloud-region( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)
+ - TO complex( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO zone( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - FROM vserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)
+ - PSERVER cannot be deleted if linked to GENERIC-VNF,LOGICAL-LINK,VSERVER
+ - PSERVER is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
+ - PSERVER cannot be deleted if linked to GROUP-ASSIGNMENT
required:
- - named-query-element-uuid
+ - hostname
+ - in-maint
properties:
- named-query-element-uuid:
+ hostname:
type: string
- property-collect-list:
+ description: Value from executing hostname on the compute node.
+ ptnii-equip-name:
type: string
- resource-version:
+ description: PTNII name
+ number-of-cpus:
+ type: integer
+ format: int32
+ description: Number of cpus
+ disk-in-gigabytes:
+ type: integer
+ format: int32
+ description: Disk size, in GBs
+ ram-in-megabytes:
+ type: integer
+ format: int32
+ description: RAM size, in MBs
+ equip-type:
type: string
- property-limit-desc:
+ description: Equipment type. Source of truth should define valid values.
+ equip-vendor:
type: string
- do-not-output:
+ description: Equipment vendor. Source of truth should define valid values.
+ equip-model:
type: string
- named-query-elements:
+ description: Equipment model. Source of truth should define valid values.
+ fqdn:
+ type: string
+ description: Fully-qualified domain name
+ pserver-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ ipv4-oam-address:
+ type: string
+ description: Used to configure device, also used for troubleshooting and is IP used for traps generated by device.
+ serial-number:
+ type: string
+ description: Serial number, may be queried
+ ipaddress-v4-loopback-0:
+ type: string
+ description: IPV4 Loopback 0 address
+ ipaddress-v6-loopback-0:
+ type: string
+ description: IPV6 Loopback 0 address
+ ipaddress-v4-aim:
+ type: string
+ description: IPV4 AIM address
+ ipaddress-v6-aim:
+ type: string
+ description: IPV6 AIM address
+ ipaddress-v6-oam:
+ type: string
+ description: IPV6 OAM address
+ inv-status:
+ type: string
+ description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
+ pserver-id:
+ type: string
+ description: ID of Pserver
+ internet-topology:
+ type: string
+ description: internet topology of Pserver
+ in-maint:
+ type: boolean
+ pservers:
+ description: |
+ Collection of compute hosts.
+ properties:
+ pserver:
type: array
- items:
- $ref: "#/definitions/named-query-element"
- related-lookups:
+ items:
+ $ref: "#/patchDefinitions/pserver"
+ query-parameters:
+ description: |
+ QueryParameters for performing a named-query or model query
+ properties:
+ named-query:
+ type: object
+ $ref: "#/patchDefinitions/named-query"
+ overloaded-model:
+ type: object
+ $ref: "#/patchDefinitions/overloaded-model"
+ related-lookup:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query-element( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ required:
+ - related-lookup-uuid
+ - source-node-type
+ - source-node-property
+ - target-node-type
+ - target-node-property
+ properties:
+ related-lookup-uuid:
+ type: string
+ source-node-type:
+ type: string
+ source-node-property:
+ type: string
+ target-node-type:
+ type: string
+ target-node-property:
+ type: string
+ property-collect-list:
+ type: string
+ related-lookups:
+ properties:
+ related-lookup:
type: array
- items:
- $ref: "#/definitions/related-lookup"
- property-constraints:
+ items:
+ $ref: "#/patchDefinitions/related-lookup"
+ related-to-property:
+ properties:
+ property-key:
+ type: string
+ description: Key part of a key/value pair
+ property-value:
+ type: string
+ description: Value part of a key/value pair
+ relationship:
+ properties:
+ related-to:
+ type: string
+ description: A keyword provided by A&AI to indicate type of node.
+ related-link:
+ type: string
+ description: URL to the object in A&AI.
+ relationship-data:
type: array
- items:
- $ref: "#/definitions/property-constraint"
- relationship-list:
+ items:
+ $ref: "#/patchDefinitions/relationship-data"
+ related-to-property:
type: array
- items:
- $ref: "#/definitions/relationship"
- named-query-elements:
+ items:
+ $ref: "#/patchDefinitions/related-to-property"
+ relationship-data:
+ required:
+ - relationship-key
+ - relationship-value
properties:
- named-query-element:
+ relationship-key:
+ type: string
+ description: A keyword provided by A&AI to indicate an attribute.
+ relationship-value:
+ type: string
+ description: Value of the attribute.
+ reserved-prop-names:
+ description: |
+ Internal map to define some reserved properties of a vertex
+ properties:
+ last-mod-source-of-truth:
+ type: string
+ aai-node-type:
+ type: string
+ aai-created-ts:
+ type: integer
+ format: int64
+ aai-unique-key:
+ type: string
+ aai-last-mod-ts:
+ type: integer
+ format: int64
+ source-of-truth:
+ type: string
+ aai-uri:
+ type: string
+ response-list:
+ description: |
+ Response container for the results of a named-query or model query
+ properties:
+ inventory-response-items:
+ type: object
+ $ref: "#/patchDefinitions/inventory-response-items"
+ result-data:
+ properties:
+ resource-type:
+ type: string
+ description: The specific type of node in the A&AI graph
+ resource-link:
+ type: string
+ description: The URL to the specific resource
+ route-table-reference:
+ description: |
+ Openstack route table reference.
+ ###### Related Nodes
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)
+ required:
+ - route-table-reference-id
+ - route-table-reference-fqdn
+ properties:
+ route-table-reference-id:
+ type: string
+ description: Route Table Reference id, UUID assigned to this instance.
+ route-table-reference-fqdn:
+ type: string
+ description: FQDN entry in the route table.
+ route-table-references:
+ description: |
+ Collection of openstack route table references
+ properties:
+ route-table-reference:
type: array
items:
- $ref: "#/definitions/named-query-element"
- named-query:
+ $ref: "#/patchDefinitions/route-table-reference"
+ route-target:
description: |
- TBD
+ Route target information
###### Related Nodes
- - TO model (One2Many)
- - TO named-query-element (comprises named-query, One2One)
+ - TO vpn-binding( route-target org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2ONE)
required:
- - named-query-uuid
- - named-query-name
- - named-query-version
+ - global-route-target
+ - route-target-role
properties:
- named-query-uuid:
+ global-route-target:
type: string
- named-query-name:
+ description: Number used to identify an RT, globally unique in the network
+ route-target-role:
type: string
- named-query-version:
+ description: Role assigned to this route target
+ route-targets:
+ description: |
+ Collection of route target information
+ properties:
+ route-target:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/route-target"
+ routing-instance:
+ description: |
+ ###### Related Nodes
+ - TO site-pair-set( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)
+ - FROM site-pair( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)
+ - ROUTING-INSTANCE is DELETED when these are DELETED SITE-PAIR
+ required:
+ - routing-instance-id
+ properties:
+ routing-instance-id:
type: string
- required-input-param:
+ description: Unique id of routing instance
+ rpm-owner:
type: string
- description:
+ description: rpm owner
+ routing-instances:
+ description: |
+ set of probes related to generic-vnf routing instance
+ properties:
+ routing-instance:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/routing-instance"
+ sdn-zone-response:
+ properties:
+ oam-networks:
+ type: object
+ $ref: "#/patchDefinitions/oam-networks"
+ az-and-dvs-switches:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/az-and-dvs-switches"
+ search:
+ properties:
+ edge-tag-query-result:
+ type: object
+ $ref: "#/patchDefinitions/edge-tag-query-result"
+ edge-tag-query-request:
+ type: object
+ $ref: "#/patchDefinitions/edge-tag-query-request"
+ search-results:
+ type: object
+ $ref: "#/patchDefinitions/search-results"
+ sdn-zone-response:
+ type: object
+ $ref: "#/patchDefinitions/sdn-zone-response"
+ search-results:
+ properties:
+ result-data:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/result-data"
+ secondary-filt:
+ description: |
+ SecondaryFilt for performing a named-query or model query
+ secondary-filter:
+ properties:
+ property-name:
type: string
- resource-version:
+ filter-type:
type: string
- named-query-elements:
+ property-value:
+ type: string
+ secondary-filts:
+ description: |
+ SecondaryFilts for performing a named-query or model query
+ properties:
+ secondary-filt:
type: array
- items:
- $ref: "#/definitions/named-query-element"
- relationship-list:
+ items:
+ $ref: "#/patchDefinitions/secondary-filt"
+ segmentation-assignment:
+ description: |
+ Openstack segmentation assignment.
+ ###### Related Nodes
+ - TO l3-network( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ required:
+ - segmentation-id
+ properties:
+ segmentation-id:
+ type: string
+ description: Route Table Reference id, UUID assigned to this instance.
+ segmentation-assignments:
+ description: |
+ Collection of openstack segmentation assignments
+ properties:
+ segmentation-assignment:
type: array
- items:
- $ref: "#/definitions/relationship"
- named-queries:
+ items:
+ $ref: "#/patchDefinitions/segmentation-assignment"
+ service:
+ description: |
+ Stand-in for service model definitions. Likely to be deprecated in favor of models from ASDC. Does not strictly map to ASDC services.
+ required:
+ - service-id
+ - service-description
properties:
- named-query:
+ service-id:
+ type: string
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ service-description:
+ type: string
+ description: Description of the service
+ service-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ service-capabilities:
+ description: |
+ Collection of service capabilities.
+ properties:
+ service-capability:
type: array
items:
- $ref: "#/definitions/named-query"
+ $ref: "#/patchDefinitions/service-capability"
+ service-capability:
+ description: |
+ Early definition of server/resource pairings, likely to be replaced by models. No new use should be made of this.
+ ###### Related Nodes
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - SERVICE-CAPABILITY cannot be deleted if linked to AVAILABILITY-ZONE,OAM-NETWORK
+ required:
+ - service-type
+ - vnf-type
+ properties:
+ service-type:
+ type: string
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
service-design-and-creation:
description: |
Namespace for objects managed by ASDC
@@ -44349,70 +60986,84 @@ definitions:
vnf-images:
type: array
items:
- $ref: "#/definitions/vnf-image"
+ $ref: "#/patchDefinitions/vnf-image"
services:
type: array
items:
- $ref: "#/definitions/service"
+ $ref: "#/patchDefinitions/service"
service-capabilities:
type: array
items:
- $ref: "#/definitions/service-capability"
+ $ref: "#/patchDefinitions/service-capability"
models:
type: array
items:
- $ref: "#/definitions/model"
+ $ref: "#/patchDefinitions/model"
named-queries:
type: array
items:
- $ref: "#/definitions/named-query"
- logical-link:
+ $ref: "#/patchDefinitions/named-query"
+ service-instance:
description: |
- Logical links generally connect l-interfaces but are used to express logical connectivity between two points
+ Instance of a service
###### Related Nodes
- - TO lag-link (Many2Many)
- - TO pnf (Many2Many)
- - TO logical-link (One2Many)
- - TO generic-vnf (Many2Many)
- - TO pserver (Many2Many)
- - TO cloud-region (Many2Many)
- - TO vpn-binding (Many2Many)
- - FROM configuration
- - FROM l-interface
- - FROM lag-interface
- - FROM p-interface
- - FROM service-instance
- - FROM virtual-data-center
- - FROM vlan
- - FROM logical-link
+ - TO generic-vnf( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)
+ - TO l3-network( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)
+ - TO owning-entity( service-instance org.onap.relationships.inventory.BelongsTo owning-entity, MANY2ONE)
+ - TO allotted-resource( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY)
+ - TO configuration( service-instance org.onap.relationships.inventory.Uses configuration, ONE2MANY)
+ - TO connector( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)
+ - TO ctag-assignment( service-instance org.onap.relationships.inventory.Uses ctag-assignment, ONE2MANY)
+ - TO cvlan-tag( service-instance org.onap.relationships.inventory.ComposedOf cvlan-tag, MANY2MANY)
+ - TO instance-group( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO logical-link( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - TO pnf( service-instance org.onap.relationships.inventory.ComposedOf pnf, ONE2MANY)
+ - TO service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)
+ - TO vlan( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)
+ - TO zone( service-instance org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - TO service-subscription( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)
+ - TO vce( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)
+ - FROM project( project org.onap.relationships.inventory.Uses service-instance, ONE2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)
+ - SERVICE-INSTANCE is DELETED when these are DELETED ALLOTTED-RESOURCE,METADATUM
+ - SERVICE-INSTANCE deletion means associated objects of these types are also DELETED:LOGICAL-LINK
required:
- - link-name
- - in-maint
- - link-type
+ - service-instance-id
+ - service-type
+ - service-role
+ - created-at
+ - updated-at
+ - description
properties:
- link-name:
+ service-instance-id:
type: string
- description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
- in-maint:
- type: boolean
- link-type:
+ description: Uniquely identifies this instance of a service
+ service-instance-name:
type: string
- description: Type of logical link, e.g., evc
- speed-value:
+ description: This field will store a name assigned to the service-instance.
+ service-type:
type: string
- description: Captures the numeric part of the speed
- speed-units:
+ description: String capturing type of service.
+ service-role:
type: string
- description: Captures the units corresponding to the speed
- ip-version:
+ description: String capturing the service role.
+ environment-context:
type: string
- description: v4, v6, or ds for dual stack
- routing-protocol:
+ description: This field will store the environment context assigned to the service-instance.
+ workload-context:
type: string
- description: For example, static or BGP
- resource-version:
+ description: This field will store the workload context assigned to the service-instance.
+ created-at:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ description: create time of Network Service.
+ updated-at:
+ type: string
+ description: last update of Network Service.
+ description:
+ type: string
+ description: short description for service-instance.
model-invariant-id:
type: string
description: the ASDC model id for this resource or service model.
@@ -44428,75 +61079,74 @@ definitions:
widget-model-version:
type: string
description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
- operational-status:
+ bandwidth-total:
type: string
- description: Indication of operational status of the logical link.
- prov-status:
+ description: Indicates the total bandwidth to be used for this service.
+ bandwidth-up-wan1:
type: string
- description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
- link-role:
+ description: indicates the upstream bandwidth this service will use on the WAN1 port of the physical device.
+ bandwidth-down-wan1:
type: string
- description: Indication of the network use of the logical link.
- link-name2:
+ description: indicates the downstream bandwidth this service will use on the WAN1 port of the physical device.
+ bandwidth-up-wan2:
type: string
- description: Alias or alternate name (CLCI or D1 name).
- link-id:
+ description: indicates the upstream bandwidth this service will use on the WAN2 port of the physical device.
+ bandwidth-down-wan2:
type: string
- description: UUID of the logical-link, SDNC generates this.
- circuit-id:
+ description: indicates the downstream bandwidth this service will use on the WAN2 port of the physical device.
+ vhn-portal-url:
type: string
- description: Circuit id
- purpose:
+ description: URL customers will use to access the vHN Portal.
+ service-instance-location-id:
type: string
- description: Reason for this entity, role it is playing
- relationship-list:
- type: array
- items:
- $ref: "#/definitions/relationship"
- logical-links:
+ description: An identifier that customers assign to the location where this service is being used.
+ service-instances:
description: |
- Collection of logical connections
+ Collection of service instances
properties:
- logical-link:
+ service-instance:
type: array
items:
- $ref: "#/definitions/logical-link"
- class-of-service:
+ $ref: "#/patchDefinitions/service-instance"
+ service-subscription:
description: |
+ Object that group service instances.
###### Related Nodes
- - FROM site-pair (is composed of class-of-service)
+ - TO customer( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)
+ - TO tenant( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)
+ - SERVICE-SUBSCRIPTION is DELETED when these are DELETED SERVICE-INSTANCE
required:
- - cos
+ - service-type
properties:
- cos:
- type: string
- description: unique identifier of probe
- probe-id:
- type: string
- description: identifier of probe
- probe-type:
+ service-type:
type: string
- description: type of probe
- resource-version:
+ description: Value defined by orchestration to identify this service across ECOMP.
+ temp-ub-sub-account-id:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- relationship-list:
+ description: This property will be deleted from A&AI in the near future. Only stop gap solution.
+ service-subscriptions:
+ description: |
+ Collection of objects that group service instances.
+ properties:
+ service-subscription:
type: array
- items:
- $ref: "#/definitions/relationship"
- classes-of-service:
+ items:
+ $ref: "#/patchDefinitions/service-subscription"
+ services:
description: |
- class-of-service of probe
+ Collection of service model definitions. Likely to be deprecated in favor of models from ASDC.
properties:
- class-of-service:
+ service:
type: array
items:
- $ref: "#/definitions/class-of-service"
+ $ref: "#/patchDefinitions/service"
site-pair:
description: |
###### Related Nodes
- - TO class-of-service (comprises site-pair, Many2Many)
- - FROM routing-instance (is composed of site-pair)
+ - TO routing-instance( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)
+ - FROM class-of-service( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)
+ - SITE-PAIR is DELETED when these are DELETED CLASS-OF-SERVICE
required:
- site-pair-id
properties:
@@ -44518,17 +61168,27 @@ definitions:
destination-equip-type:
type: string
description: The type of destinatination equipment. Could be Router, UCPE, etc.
- resource-version:
+ site-pair-set:
+ description: |
+ Set of instances for probes used to measure service level agreements
+ ###### Related Nodes
+ - TO generic-vnf( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM routing-instance( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)
+ - SITE-PAIR-SET is DELETED when these are DELETED ROUTING-INSTANCE
+ required:
+ - site-pair-set-id
+ properties:
+ site-pair-set-id:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- classes-of-service:
- type: array
- items:
- $ref: "#/definitions/class-of-service"
- relationship-list:
+ description: Unique id of site pair set.
+ site-pair-sets:
+ description: |
+ Collection of sets of instances for probes related to generic-vnf
+ properties:
+ site-pair-set:
type: array
- items:
- $ref: "#/definitions/relationship"
+ items:
+ $ref: "#/patchDefinitions/site-pair-set"
site-pairs:
description: |
probe within a set
@@ -44536,109 +61196,751 @@ definitions:
site-pair:
type: array
items:
- $ref: "#/definitions/site-pair"
- routing-instance:
+ $ref: "#/patchDefinitions/site-pair"
+ snapshot:
description: |
+ Openstack snapshot
###### Related Nodes
- - TO site-pair (comprises routing-instance, Many2Many)
- - FROM site-pair-set (is composed of routing-instance)
+ - TO cloud-region( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)
required:
- - routing-instance-id
+ - snapshot-id
properties:
- routing-instance-id:
+ snapshot-id:
type: string
- description: Unique id of routing instance
- rpm-owner:
+ description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
+ snapshot-name:
type: string
- description: rpm owner
- resource-version:
+ description: Snapshot name
+ snapshot-architecture:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- site-pairs:
+ description: Operating system architecture
+ snapshot-os-distro:
+ type: string
+ description: The common name of the operating system distribution in lowercase
+ snapshot-os-version:
+ type: string
+ description: The operating system version as specified by the distributor.
+ application:
+ type: string
+ description: The application that the image instantiates.
+ application-vendor:
+ type: string
+ description: The vendor of the application.
+ application-version:
+ type: string
+ description: The version of the application.
+ snapshot-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ prev-snapshot-id:
+ type: string
+ description: This field contains the UUID of the previous snapshot (if any).
+ snapshots:
+ description: |
+ Collection of openstack snapshots
+ properties:
+ snapshot:
type: array
- items:
- $ref: "#/definitions/site-pair"
- relationship-list:
+ items:
+ $ref: "#/patchDefinitions/snapshot"
+ sriov-pf:
+ description: |
+ SR-IOV Physical Function
+ ###### Related Nodes
+ - TO p-interface( sriov-pf org.onap.relationships.inventory.BelongsTo p-interface, ONE2ONE)
+ - FROM sriov-vf( sriov-vf org.onap.relationships.inventory.Uses sriov-pf, MANY2ONE)
+ required:
+ - pf-pci-id
+ properties:
+ pf-pci-id:
+ type: string
+ description: Identifier for the sriov-pf
+ sriov-pfs:
+ description: |
+ Collection of SR-IOV Physical Functions.
+ properties:
+ sriov-pf:
type: array
- items:
- $ref: "#/definitions/relationship"
- routing-instances:
+ items:
+ $ref: "#/patchDefinitions/sriov-pf"
+ sriov-vf:
description: |
- set of probes related to generic-vnf routing instance
+ SR-IOV Virtual Function (not to be confused with virtual network function)
+ ###### Related Nodes
+ - TO l-interface( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)
+ - TO sriov-pf( sriov-vf org.onap.relationships.inventory.Uses sriov-pf, MANY2ONE)
+ required:
+ - pci-id
properties:
- routing-instance:
+ pci-id:
+ type: string
+ description: PCI ID used to identify the sriov-vf
+ vf-vlan-filter:
+ type: string
+ description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM.
+ vf-mac-filter:
+ type: string
+ description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM.
+ vf-vlan-strip:
+ type: boolean
+ description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM.
+ vf-vlan-anti-spoof-check:
+ type: boolean
+ description: This option ensures anti VLAN spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
+ vf-mac-anti-spoof-check:
+ type: boolean
+ description: This option ensures anti MAC spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
+ vf-mirrors:
+ type: string
+ description: This option defines the set of Mirror objects which essentially mirrors the traffic from source to set of collector VNF Ports.
+ vf-broadcast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows all broadcast traffic to reach the VM
+ vf-unknown-multicast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows unknown multicast traffic to reach the VM
+ vf-unknown-unicast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows unknown unicast traffic to reach the VM
+ vf-insert-stag:
+ type: boolean
+ description: This option, if set to true, instructs to insert outer tag after traffic comes out of VM.
+ vf-link-status:
+ type: string
+ description: This option is used to set the link status. Valid values as of 1607 are on, off, and auto.
+ sriov-vfs:
+ description: |
+ Collection of SR-IOV Virtual Functions.
+ properties:
+ sriov-vf:
type: array
items:
- $ref: "#/definitions/routing-instance"
- site-pair-set:
+ $ref: "#/patchDefinitions/sriov-vf"
+ start-node-filter:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ subnet:
description: |
- Set of instances for probes used to measure service level agreements
###### Related Nodes
- - TO routing-instance (comprises site-pair-set, Many2Many)
- - FROM generic-vnf
+ - TO l3-network( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - FROM host-route( host-route org.onap.relationships.inventory.BelongsTo subnet, MANY2ONE)
+ - FROM vip-ipv4-address-list( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)
+ - FROM vip-ipv6-address-list( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)
+ - SUBNET cannot be deleted if linked to L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST,VIP-IPV4-ADDRESS-LIST,VIP-IPV6-ADDRESS-LIST
+ - SUBNET is DELETED when these are DELETED HOST-ROUTE
required:
- - site-pair-set-id
+ - subnet-id
+ - dhcp-enabled
properties:
- site-pair-set-id:
+ subnet-id:
type: string
- description: Unique id of site pair set.
- resource-version:
+ description: Subnet ID, should be UUID.
+ subnet-name:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- routing-instances:
+ description: Name associated with the subnet.
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of this subnet
+ gateway-address:
+ type: string
+ description: gateway ip address
+ network-start-address:
+ type: string
+ description: network start address
+ cidr-mask:
+ type: string
+ description: cidr mask
+ ip-version:
+ type: string
+ description: ip version
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ dhcp-enabled:
+ type: boolean
+ dhcp-start:
+ type: string
+ description: the start address reserved for use by dhcp
+ dhcp-end:
+ type: string
+ description: the last address reserved for use by dhcp
+ subnet-role:
+ type: string
+ description: role of the subnet, referenced when assigning IPs
+ ip-assignment-direction:
+ type: string
+ description: ip address assignment direction of the subnet
+ subnets:
+ properties:
+ subnet:
type: array
- items:
- $ref: "#/definitions/routing-instance"
- relationship-list:
+ items:
+ $ref: "#/patchDefinitions/subnet"
+ tagged-inventory-item-list:
+ properties:
+ inventory-item:
type: array
- items:
- $ref: "#/definitions/relationship"
- site-pair-sets:
+ items:
+ $ref: "#/patchDefinitions/inventory-item"
+ tenant:
description: |
- Collection of sets of instances for probes related to generic-vnf
+ Openstack tenant
+ ###### Related Nodes
+ - TO cloud-region( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO group-assignment( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)
+ - TO l3-network( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO volume-group( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - FROM service-subscription( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)
+ - FROM vserver( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)
+ - TENANT cannot be deleted if linked to VSERVER
+ required:
+ - tenant-id
+ - tenant-name
properties:
- site-pair-set:
+ tenant-id:
+ type: string
+ description: Unique id relative to the cloud-region.
+ tenant-name:
+ type: string
+ description: Readable name of tenant
+ tenant-context:
+ type: string
+ description: This field will store the tenant context.
+ tenants:
+ description: |
+ Collection of openstack tenants.
+ properties:
+ tenant:
type: array
items:
- $ref: "#/definitions/site-pair-set"
- route-target:
+ $ref: "#/patchDefinitions/tenant"
+ tunnel-xconnect:
description: |
- Route target information
+ Represents the specifics of a tunnel cross connect piece of a resource that gets separately allotted
###### Related Nodes
- - FROM vpn-binding (is composed of route-target)
+ - TO allotted-resource( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)
required:
- - global-route-target
- - route-target-role
+ - id
+ - bandwidth-up-wan1
+ - bandwidth-down-wan1
+ - bandwidth-up-wan2
+ - bandwidth-down-wan2
properties:
- global-route-target:
+ id:
type: string
- description: Number used to identify an RT, globally unique in the network
- route-target-role:
+ description: Allotted Resource id UUID assigned to this instance.
+ bandwidth-up-wan1:
type: string
- description: Role assigned to this route target
- resource-version:
+ description: The WAN uplink bandwidth for WAN1
+ bandwidth-down-wan1:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- relationship-list:
+ description: The WAN downlink bandwidth for WAN1
+ bandwidth-up-wan2:
+ type: string
+ description: The WAN uplink bandwidth for WAN2
+ bandwidth-down-wan2:
+ type: string
+ description: The WAN downlink bandwidth for WAN2
+ tunnel-xconnects:
+ description: |
+ This object is used to store the specific tunnel cross connect aspects of an allotted resource
+ properties:
+ tunnel-xconnect:
type: array
- items:
- $ref: "#/definitions/relationship"
- route-targets:
+ items:
+ $ref: "#/patchDefinitions/tunnel-xconnect"
+ update:
description: |
- Collection of route target information
+ Serves a PATCH like function. Does not enforce concurrency control. Clear each usage with AAI team.
+ required:
+ - update-node-type
properties:
- route-target:
+ update-node-type:
+ type: string
+ update-node-key:
type: array
items:
- $ref: "#/definitions/route-target"
+ $ref: "#/patchDefinitions/update-node-key"
+ update-node-uri:
+ type: string
+ action:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/action"
+ update-node-key:
+ properties:
+ key-name:
+ type: string
+ key-value:
+ type: string
+ vce:
+ description: |
+ Virtual Customer Edge Router, used specifically for Gamma. This object is deprecated.
+ ###### Related Nodes
+ - TO availability-zone( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - TO complex( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)
+ - TO vserver( vce tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM entitlement( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM license( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM port-group( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)
+ - VCE is DELETED when these are DELETED ENTITLEMENT,LICENSE,PORT-GROUP
+ required:
+ - vnf-id
+ - vnf-name
+ - vnf-type
+ properties:
+ vnf-id:
+ type: string
+ description: Unique id of VNF. This is unique across the graph.
+ vnf-name:
+ type: string
+ description: Name of VNF.
+ vnf-name2:
+ type: string
+ description: Alternate name of VNF.
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ service-id:
+ type: string
+ description: Unique identifier of service, does not strictly map to ASDC services, SOON TO BE DEPRECATED.
+ regional-resource-zone:
+ type: string
+ description: Regional way of organizing pservers, source of truth should define values
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ operational-status:
+ type: string
+ description: Indicator for whether the resource is considered operational
+ license-key:
+ type: string
+ description: OBSOLETE - do not use
+ equipment-role:
+ type: string
+ description: Network role being played by this VNF
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ vpe-id:
+ type: string
+ description: Unique ID of VPE connected to this VCE.
+ v6-vce-wan-address:
+ type: string
+ description: Valid v6 IP address for the WAN Link on this router. Implied length of /64.
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure vce, also used for troubleshooting and is IP used for traps generated by VCE.
+ vces:
+ description: |
+ Collection of Virtual Customer Edge Routers, used specifically for Gamma. This object is deprecated.
+ properties:
+ vce:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vce"
+ vf-module:
+ description: |
+ a deployment unit of VNFCs
+ ###### Related Nodes
+ - TO generic-vnf( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO l3-network( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)
+ - TO vnfc( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)
+ - TO volume-group( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)
+ - TO vserver( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)
+ - VF-MODULE cannot be deleted if linked to VNFC
+ required:
+ - vf-module-id
+ - is-base-vf-module
+ properties:
+ vf-module-id:
+ type: string
+ description: Unique ID of vf-module.
+ vf-module-name:
+ type: string
+ description: Name of vf-module
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance.
+ orchestration-status:
+ type: string
+ description: orchestration status of this vf-module, mastered by MSO
+ is-base-vf-module:
+ type: boolean
+ vf-modules:
+ description: |
+ Collection of vf-modules, a deployment unit of VNFCs
+ properties:
+ vf-module:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vf-module"
+ vig-server:
+ description: |
+ vig-server contains information about a vig server used for IPSec-configuration. Populated by SDN-C from 1607
+ ###### Related Nodes
+ - TO ipsec-configuration( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)
+ required:
+ - vig-address-type
+ properties:
+ vig-address-type:
+ type: string
+ description: indicates whether the VIG is for AVPN or INTERNET
+ ipaddress-v4-vig:
+ type: string
+ description: v4 IP of the vig server
+ ipaddress-v6-vig:
+ type: string
+ description: v6 IP of the vig server
+ vig-servers:
+ properties:
+ vig-server:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vig-server"
+ vip-ipv4-address-list:
+ description: |
+ IPv4 Address Range
+ ###### Related Nodes
+ - TO cloud-region( vip-ipv4-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO instance-group( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO subnet( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv4-address-list, MANY2MANY)
+ required:
+ - vip-ipv4-address
+ properties:
+ vip-ipv4-address:
+ type: string
+ description: IP address
+ vip-ipv4-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 32 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ vip-ipv6-address-list:
+ description: |
+ IPv6 Address Range
+ ###### Related Nodes
+ - TO cloud-region( vip-ipv6-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO instance-group( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO subnet( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv6-address-list, MANY2MANY)
+ required:
+ - vip-ipv6-address
+ properties:
+ vip-ipv6-address:
+ type: string
+ description: IP address
+ vip-ipv6-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 128 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ virtual-data-center:
+ description: |
+ Virtual organization of cloud infrastructure elements in a data center context
+ ###### Related Nodes
+ - FROM connector( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ required:
+ - vdc-id
+ - vdc-name
+ properties:
+ vdc-id:
+ type: string
+ description: Unique ID of the vdc
+ vdc-name:
+ type: string
+ description: Name of the virtual data center
+ virtual-data-centers:
+ description: |
+ Virtual organization of cloud infrastructure elements in a data center context
+ properties:
+ virtual-data-center:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/virtual-data-center"
+ vlan:
+ description: |
+ Definition of vlan
+ ###### Related Nodes
+ - TO l-interface( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)
+ - TO logical-link( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - TO multicast-configuration( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ - VLAN is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST
+ - VLAN deletion means associated objects of these types are also DELETED:LOGICAL-LINK
+ required:
+ - vlan-interface
+ - in-maint
+ - is-ip-unnumbered
+ properties:
+ vlan-interface:
+ type: string
+ description: String that identifies the interface
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ vlans:
+ properties:
+ vlan:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vlan"
+ vnf:
+ description: |
+ Abstract vnf class
+ required:
+ - vnf-id
+ properties:
+ vnf-id:
+ type: string
+ description: Unique id of VNF. This is unique across the graph.
+ vnf-image:
+ description: |
+ Image object that pertain to a VNF that doesn't have associated vservers. This is a kludge.
+ ###### Related Nodes
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)
+ - VNF-IMAGE cannot be deleted if linked to GENERIC-VNF
+ required:
+ - vnf-image-uuid
+ - application
+ - application-vendor
+ properties:
+ vnf-image-uuid:
+ type: string
+ description: Unique ID of this asset
+ application:
+ type: string
+ description: The application that the image instantiates.
+ application-vendor:
+ type: string
+ description: The vendor of the application.
+ application-version:
+ type: string
+ description: The version of the application.
+ selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ vnf-images:
+ description: |
+ Collection of image objects that pertain to a VNF that doesn't have associated vservers. This is a kludge.
+ properties:
+ vnf-image:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vnf-image"
+ vnfc:
+ description: |
+ ###### Related Nodes
+ - TO generic-vnf( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO instance-group( vnfc org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO vip-ipv4-address-list( vnfc org.onap.relationships.inventory.Uses vip-ipv4-address-list, MANY2MANY)
+ - TO vip-ipv6-address-list( vnfc org.onap.relationships.inventory.Uses vip-ipv6-address-list, MANY2MANY)
+ - TO vserver( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vnfc, MANY2ONE)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vnfc, MANY2ONE)
+ - VNFC is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST
+ required:
+ - vnfc-name
+ - nfc-naming-code
+ - nfc-function
+ - in-maint
+ - is-closed-loop-disabled
+ properties:
+ vnfc-name:
+ type: string
+ description: Unique ID of vnfc.
+ nfc-naming-code:
+ type: string
+ description: Short code that is used in naming instances of the item being modeled
+ nfc-function:
+ type: string
+ description: English description of function that the specific resource deployment is providing. Assigned as part of the customization of a resource in a service
+ prov-status:
+ type: string
+ description: prov status of this vnfc
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by APP-C
+ ipaddress-v4-oam-vip:
+ type: string
+ description: Oam V4 vip address of this vnfc
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
+ group-notation:
+ type: string
+ description: Group notation of VNFC
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ vnfcs:
+ description: |
+ virtual network components associated with a vserver from application controller.
+ properties:
+ vnfc:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vnfc"
+ volume:
+ description: |
+ Ephemeral Block storage volume.
+ ###### Related Nodes
+ - FROM vserver (PARENT of volume, vserver tosca.relationships.AttachesTo volume)
+ required:
+ - volume-id
+ - volume-selflink
+ properties:
+ volume-id:
+ type: string
+ description: Unique ID of block storage volume relative to the vserver.
+ volume-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ volume-group:
+ description: |
+ Persistent block-level storage.
+ ###### Related Nodes
+ - TO cloud-region( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO complex( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ required:
+ - volume-group-id
+ - volume-group-name
+ - vnf-type
+ properties:
+ volume-group-id:
+ type: string
+ description: Unique ID of volume-group.
+ volume-group-name:
+ type: string
+ description: Name of the volume group.
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this volume-group
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ orchestration-status:
+ type: string
+ description: Orchestration status of this volume-group
+ model-customization-id:
+ type: string
+ description: captures the id of all the configuration used to customize the resource for the service.
+ vf-module-model-customization-id:
+ type: string
+ description: helps relate the volume group to the vf-module whose components will require the volume group
+ volume-groups:
+ description: |
+ Collection of persistent block-level storage.
+ properties:
+ volume-group:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/volume-group"
+ volumes:
+ description: |
+ Collection of ephemeral Block storage volumes.
+ properties:
+ volume:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/volume"
+ vpls-pe:
+ description: |
+ VPLS Provider Edge routers.
+ ###### Related Nodes
+ - TO complex( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO ctag-pool( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - VPLS-PE is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
+ required:
+ - equipment-name
+ properties:
+ equipment-name:
+ type: string
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address).
+ equipment-role:
+ type: string
+ description: Client should send valid enumerated value, e.g., VPLS-PE.
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Temporary location for stag to get to VCE
+ vpls-pes:
+ description: |
+ Collection of VPLS Provider Edge routers
+ properties:
+ vpls-pe:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vpls-pe"
vpn-binding:
description: |
VPN binding
###### Related Nodes
- - TO route-target (comprises vpn-binding, One2Many)
- - FROM l3-network
- - FROM logical-link
- - FROM allotted-resource
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2MANY)
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - FROM route-target( route-target org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2ONE)
+ - VPN-BINDING cannot be deleted if linked to ALLOTTED-RESOURCE,L3-NETWORK,LOGICAL-LINK
+ - VPN-BINDING is DELETED when these are DELETED ROUTE-TARGET
required:
- vpn-id
- vpn-name
@@ -44664,106 +61966,796 @@ definitions:
route-distinguisher:
type: string
description: Used to distinguish the distinct VPN routes of separate customers who connect to the provider in an MPLS network.
+ vpn-bindings:
+ properties:
+ vpn-binding:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vpn-binding"
+ vserver:
+ description: |
+ Virtual Servers, aka virtual machine or VM.
+ ###### Related Nodes
+ - TO tenant( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)
+ - TO flavor( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)
+ - TO image( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)
+ - TO pserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)
+ - TO snapshot( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)
+ - TO volume (CHILD of vserver, vserver tosca.relationships.AttachesTo volume, ONE2MANY)
+ - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM vce( vce tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)
+ - FROM vnfc( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)
+ - VSERVER is DELETED when these are DELETED L-INTERFACE
+ - VSERVER deletion means associated objects of these types are also DELETED:VOLUME
+ required:
+ - vserver-id
+ - vserver-name
+ - vserver-selflink
+ - in-maint
+ - is-closed-loop-disabled
+ properties:
+ vserver-id:
+ type: string
+ description: Unique identifier for this vserver relative to its tenant
+ vserver-name:
+ type: string
+ description: Name of vserver
+ vserver-name2:
+ type: string
+ description: Alternative name of vserver
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ vserver-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
+ vservers:
+ description: |
+ Collection of virtual Servers, aka virtual machines or VMs.
+ properties:
+ vserver:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vserver"
+ zone:
+ description: |
+ A zone is a grouping of assets in a location homing to the same connections into the CBB
+ ###### Related Nodes
+ - TO complex( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM pnf( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ required:
+ - zone-id
+ - zone-name
+ - design-type
+ - zone-context
+ properties:
+ zone-id:
+ type: string
+ description: Code assigned by AIC to the zone
+ zone-name:
+ type: string
+ description: English name associated with the zone
+ design-type:
+ type: string
+ description: Design of zone [Medium/Large?]
+ zone-context:
+ type: string
+ description: Context of zone [production/test]
+ status:
+ type: string
+ description: Status of a zone.
+ zones:
+ description: |
+ Collection of zones
+ properties:
+ zone:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/zone"
+getDefinitions:
+ aai-internal:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ action:
+ properties:
+ action-type:
+ type: string
+ action-data:
+ type: array
+ items:
+ $ref: "#/getDefinitions/action-data"
+ action-data:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ actions:
+ description: |
+ APIs that are more action related than REST (e.g., notify, update).
+ properties:
+ update:
+ type: object
+ $ref: "#/getDefinitions/update"
+ notify:
+ type: object
+ $ref: "#/getDefinitions/notify"
+ allotted-resource:
+ description: |
+ Represents a slice or partial piece of a resource that gets separately allotted
+ ###### Related Nodes
+ - TO allotted-resource( allotted-resource tosca.relationships.network.BindsTo allotted-resource, ONE2ONE)
+ - TO generic-vnf( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY)
+ - TO instance-group( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO l3-network( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY)
+ - TO l-interface( allotted-resource org.onap.relationships.inventory.Uses l-interface, ONE2MANY)
+ - TO network-policy( allotted-resource org.onap.relationships.inventory.Uses network-policy, ONE2ONE)
+ - TO vlan( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY)
+ - TO vpn-binding( allotted-resource org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2MANY)
+ - TO service-instance( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM tunnel-xconnect( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)
+ - FROM configuration( configuration org.onap.relationships.inventory.Uses allotted-resource, ONE2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY)
+ - FROM allotted-resource( allotted-resource tosca.relationships.network.BindsTo allotted-resource, ONE2ONE)
+ - ALLOTTED-RESOURCE is DELETED when these are DELETED TUNNEL-XCONNECT
+ required:
+ - id
+ properties:
+ id:
+ type: string
+ description: Allotted Resource id UUID assigned to this instance.
+ description:
+ type: string
+ description: The descriptive information assigned to this allotted resource instance
+ selflink:
+ type: string
+ description: Link back to more information in the controller
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ resource-version:
+ type: string
+ description: Concurrency value
+ orchestration-status:
+ type: string
+ description: Orchestration status
+ operational-status:
+ type: string
+ description: Indicator for whether the resource is considered operational
+ type:
+ type: string
+ description: Generic description of the type of allotted resource.
+ role:
+ type: string
+ description: role in the network that this resource will be providing.
+ tunnel-xconnects:
+ type: array
+ items:
+ $ref: "#/getDefinitions/tunnel-xconnect"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ allotted-resources:
+ description: |
+ This object is used to store slices of services being offered
+ properties:
+ allotted-resource:
+ type: array
+ items:
+ $ref: "#/getDefinitions/allotted-resource"
+ availability-zone:
+ description: |
+ Availability zone, a collection of compute hosts/pservers
+ ###### Related Nodes
+ - TO complex( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO service-capability( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - TO cloud-region( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM ctag-pool( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM dvs-switch( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - FROM pserver( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)
+ - FROM vce( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - AVAILABILITY-ZONE cannot be deleted if linked to CTAG-POOL,DVS-SWITCH,GENERIC-VNF,PSERVER,VCE
+ required:
+ - availability-zone-name
+ - hypervisor-type
+ properties:
+ availability-zone-name:
+ type: string
+ description: Name of the availability zone. Unique across a cloud region
+ hypervisor-type:
+ type: string
+ description: Type of hypervisor. Source of truth should define valid values.
+ operational-status:
+ type: string
+ description: State that indicates whether the availability zone should be used, etc. Source of truth should define valid values.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- route-targets:
+ relationship-list:
type: array
items:
- $ref: "#/definitions/route-target"
+ $ref: "#/getDefinitions/relationship"
+ availability-zones:
+ description: |
+ Collection of availability zones
+ properties:
+ availability-zone:
+ type: array
+ items:
+ $ref: "#/getDefinitions/availability-zone"
+ az-and-dvs-switches:
+ properties:
+ dvs-switches:
+ type: object
+ $ref: "#/getDefinitions/dvs-switches"
+ availability-zone:
+ type: object
+ $ref: "#/getDefinitions/availability-zone"
+ business:
+ description: |
+ Namespace for business related constructs
+ properties:
+ connectors:
+ type: array
+ items:
+ $ref: "#/getDefinitions/connector"
+ customers:
+ type: array
+ items:
+ $ref: "#/getDefinitions/customer"
+ lines-of-business:
+ type: array
+ items:
+ $ref: "#/getDefinitions/line-of-business"
+ owning-entities:
+ type: array
+ items:
+ $ref: "#/getDefinitions/owning-entity"
+ platforms:
+ type: array
+ items:
+ $ref: "#/getDefinitions/platform"
+ projects:
+ type: array
+ items:
+ $ref: "#/getDefinitions/project"
+ class-of-service:
+ description: |
+ ###### Related Nodes
+ - TO site-pair( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)
+ required:
+ - cos
+ properties:
+ cos:
+ type: string
+ description: unique identifier of probe
+ probe-id:
+ type: string
+ description: identifier of probe
+ probe-type:
+ type: string
+ description: type of probe
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- description: l3-networks relate to vpn-bindings
- vpn-bindings:
+ $ref: "#/getDefinitions/relationship"
+ classes-of-service:
+ description: |
+ class-of-service of probe
properties:
- vpn-binding:
+ class-of-service:
type: array
items:
- $ref: "#/definitions/vpn-binding"
- vpls-pe:
+ $ref: "#/getDefinitions/class-of-service"
+ cloud-infrastructure:
description: |
- VPLS Provider Edge routers.
+ Namespace for cloud infrastructure.
+ properties:
+ complexes:
+ type: array
+ items:
+ $ref: "#/getDefinitions/complex"
+ cloud-regions:
+ type: array
+ items:
+ $ref: "#/getDefinitions/cloud-region"
+ network-profiles:
+ type: array
+ items:
+ $ref: "#/getDefinitions/network-profile"
+ pservers:
+ type: array
+ items:
+ $ref: "#/getDefinitions/pserver"
+ virtual-data-centers:
+ type: array
+ items:
+ $ref: "#/getDefinitions/virtual-data-center"
+ cloud-region:
+ description: |
+ cloud-region designates an installation of a cloud cluster or region or instantiation.
###### Related Nodes
- - TO complex (Many2Many)
- - TO ctag-pool (Many2Many)
- - TO p-interface (comprises vpls-pe, Many2Many)
- - TO lag-interface (comprises vpls-pe, Many2Many)
+ - TO esr-system-info (CHILD of cloud-region, cloud-region has esr-system-info, One2Many)
+ - TO complex( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO l3-network( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO zone( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM dvs-switch( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM flavor( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM group-assignment( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM image( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM snapshot( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM vip-ipv4-address-list( vip-ipv4-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM vip-ipv6-address-list( vip-ipv6-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM volume-group( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn cloud-region, MANY2MANY)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)
+ - CLOUD-REGION cannot be deleted if linked to DVS-SWITCH,FLAVOR,GROUP-ASSIGNMENT,IMAGE,OAM-NETWORK,SNAPSHOT,TENANT,VIP-IPV4-ADDRESS-LIST,VIP-IPV6-ADDRESS-LIST,VOLUME-GROUP
+ - CLOUD-REGION is DELETED when these are DELETED AVAILABILITY-ZONE
+ - CLOUD-REGION deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
required:
- - equipment-name
+ - cloud-owner
+ - cloud-region-id
+ - sriov-automation
properties:
- equipment-name:
+ cloud-owner:
type: string
- prov-status:
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ cloud-region-id:
type: string
- description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
- ipv4-oam-address:
+ description: Identifier used by the vendor for the region. Second part of composite key
+ cloud-type:
type: string
- description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address).
- equipment-role:
+ description: Type of the cloud (e.g., openstack)
+ owner-defined-type:
type: string
- description: Client should send valid enumerated value, e.g., VPLS-PE.
- vlan-id-outer:
- type: integer
- format: int64
- description: Temporary location for stag to get to VCE
+ description: Cloud-owner defined type indicator (e.g., dcp, lcp)
+ cloud-region-version:
+ type: string
+ description: Software version employed at the site. NOTE - THIS FIELD IS NOT KEPT UP TO DATE.
+ identity-url:
+ type: string
+ description: URL of the keystone identity service
+ cloud-zone:
+ type: string
+ description: Zone where the cloud is homed. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
+ complex-name:
+ type: string
+ description: complex name for cloud-region instance. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
+ sriov-automation:
+ type: boolean
+ cloud-extra-info:
+ type: string
+ description: ESR inputs extra information about the VIM or Cloud which will be decoded by MultiVIM.
+ cloud-epa-caps:
+ type: string
+ description: MultiVIM will discover and expose EPA capabilities.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ volume-groups:
+ type: array
+ items:
+ $ref: "#/getDefinitions/volume-group"
+ tenants:
+ type: array
+ items:
+ $ref: "#/getDefinitions/tenant"
+ flavors:
+ type: array
+ items:
+ $ref: "#/getDefinitions/flavor"
+ group-assignments:
+ type: array
+ items:
+ $ref: "#/getDefinitions/group-assignment"
+ snapshots:
+ type: array
+ items:
+ $ref: "#/getDefinitions/snapshot"
+ images:
+ type: array
+ items:
+ $ref: "#/getDefinitions/image"
+ dvs-switches:
+ type: array
+ items:
+ $ref: "#/getDefinitions/dvs-switch"
+ oam-networks:
+ type: array
+ items:
+ $ref: "#/getDefinitions/oam-network"
+ availability-zones:
+ type: array
+ items:
+ $ref: "#/getDefinitions/availability-zone"
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- p-interfaces:
+ $ref: "#/getDefinitions/relationship"
+ esr-system-info-list:
type: array
items:
- $ref: "#/definitions/p-interface"
- lag-interfaces:
+ $ref: "#/getDefinitions/esr-system-info"
+ vip-ipv4-address-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vip-ipv4-address-list"
+ vip-ipv6-address-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vip-ipv6-address-list"
+ cloud-regions:
+ properties:
+ cloud-region:
+ type: array
+ items:
+ $ref: "#/getDefinitions/cloud-region"
+ complex:
+ description: |
+ Collection of physical locations that can house cloud-regions.
+ ###### Related Nodes
+ - TO l3-network( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM ctag-pool( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)
+ - FROM pnf( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM vce( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)
+ - FROM volume-group( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM vpls-pe( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM zone( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - COMPLEX cannot be deleted if linked to AVAILABILITY-ZONE,CLOUD-REGION,GENERIC-VNF,OAM-NETWORK,PNF,PSERVER,VCE,VOLUME-GROUP,VPLS-PE,ZONE
+ - COMPLEX is DELETED when these are DELETED CTAG-POOL
+ required:
+ - physical-location-id
+ - physical-location-type
+ - street1
+ - city
+ - postal-code
+ - country
+ - region
+ properties:
+ physical-location-id:
+ type: string
+ description: Unique identifier for physical location, e.g., CLLI
+ data-center-code:
+ type: string
+ description: Data center code which can be an alternate way to identify a complex
+ complex-name:
+ type: string
+ description: Gamma complex name for LCP instance.
+ identity-url:
+ type: string
+ description: URL of the keystone identity service
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ physical-location-type:
+ type: string
+ description: Type, e.g., central office, data center.
+ street1:
+ type: string
+ street2:
+ type: string
+ city:
+ type: string
+ state:
+ type: string
+ postal-code:
+ type: string
+ country:
+ type: string
+ region:
+ type: string
+ latitude:
+ type: string
+ longitude:
+ type: string
+ elevation:
+ type: string
+ lata:
+ type: string
+ ctag-pools:
type: array
items:
- $ref: "#/definitions/lag-interface"
- vpls-pes:
+ $ref: "#/getDefinitions/ctag-pool"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ complexes:
description: |
- Collection of VPLS Provider Edge routers
+ Collection of physical locations that can house cloud-regions.
properties:
- vpls-pe:
+ complex:
type: array
items:
- $ref: "#/definitions/vpls-pe"
- multicast-configuration:
+ $ref: "#/getDefinitions/complex"
+ configuration:
description: |
+ Port Mirror Configuration.
###### Related Nodes
- - FROM vlan
+ - TO allotted-resource( configuration org.onap.relationships.inventory.Uses allotted-resource, ONE2ONE)
+ - TO logical-link( configuration org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo configuration, MANY2ONE)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses configuration, ONE2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses configuration, ONE2MANY)
+ - CONFIGURATION is DELETED when these are DELETED METADATUM
+ - CONFIGURATION deletion means associated objects of these types are also DELETED:ALLOTTED-RESOURCE,LOGICAL-LINK
required:
- - multicast-configuration-id
- - multicast-protocol
- - rp-type
+ - configuration-id
+ - configuration-type
+ - configuration-sub-type
+ - orchestration-status
+ - operational-status
+ - configuration-selflink
+ - model-customization-id
properties:
- multicast-configuration-id:
+ configuration-id:
type: string
- description: Unique id of multicast configuration.
- multicast-protocol:
+ description: UUID assigned to configuration.
+ management-option:
type: string
- description: protocol of multicast configuration
- rp-type:
+ description: Indicates the entity that will manage this feature. Could be an organization or the name of the application as well.
+ configuration-name:
type: string
- description: rp type of multicast configuration
+ description: Name of the configuration.
+ configuration-type:
+ type: string
+ description: port-mirroring-configuration.
+ configuration-sub-type:
+ type: string
+ description: vprobe, pprobe.
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ orchestration-status:
+ type: string
+ description: Orchestration status of the configuration.
+ operational-status:
+ type: string
+ description: Indicator for whether the resource is considered operational.
+ configuration-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details from SDN-GC.
+ model-customization-id:
+ type: string
+ description: id of the configuration used to customize the resource
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- multicast-configurations:
+ $ref: "#/getDefinitions/relationship"
+ metadata:
+ type: array
+ items:
+ $ref: "#/getDefinitions/metadatum"
+ configurations:
description: |
- multicast configuration of generic-vnf ip-address
+ Collection of configurations
properties:
- multicast-configuration:
+ configuration:
type: array
items:
- $ref: "#/definitions/multicast-configuration"
+ $ref: "#/getDefinitions/configuration"
+ connector:
+ description: |
+ Collection of resource instances used to connect a variety of disparate inventory widgets
+ ###### Related Nodes
+ - TO virtual-data-center( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)
+ - CONNECTOR is DELETED when these are DELETED METADATUM
+ required:
+ - resource-instance-id
+ properties:
+ resource-instance-id:
+ type: string
+ description: Unique id of resource instance.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ metadata:
+ type: array
+ items:
+ $ref: "#/getDefinitions/metadatum"
+ connectors:
+ description: |
+ Collection of resource instances used to connect a variety of disparate inventory widgets
+ properties:
+ connector:
+ type: array
+ items:
+ $ref: "#/getDefinitions/connector"
+ constrained-element-set:
+ description: |
+ This is how we would capture constraints defining allowed sets of elements.
+ ###### Related Nodes
+ - TO model-constraint( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)
+ - TO model-element( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM element-choice-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)
+ - CONSTRAINED-ELEMENT-SET is DELETED when these are DELETED ELEMENT-CHOICE-SET
+ required:
+ - constrained-element-set-uuid
+ - constraint-type
+ - check-type
+ properties:
+ constrained-element-set-uuid:
+ type: string
+ constraint-type:
+ type: string
+ check-type:
+ type: string
+ resource-version:
+ type: string
+ element-choice-sets:
+ type: array
+ items:
+ $ref: "#/getDefinitions/element-choice-set"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ constrained-element-sets:
+ properties:
+ constrained-element-set:
+ type: array
+ items:
+ $ref: "#/getDefinitions/constrained-element-set"
+ ctag-assignment:
+ description: |
+ ###### Related Nodes
+ - TO l3-network( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses ctag-assignment, ONE2MANY)
+ required:
+ - vlan-id-inner
+ properties:
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: id.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ ctag-assignments:
+ properties:
+ ctag-assignment:
+ type: array
+ items:
+ $ref: "#/getDefinitions/ctag-assignment"
+ ctag-pool:
+ description: |
+ A collection of C tags (vlan tags) grouped for a specific purpose.
+ ###### Related Nodes
+ - TO complex( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)
+ - TO availability-zone( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)
+ - FROM vpls-pe( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)
+ required:
+ - target-pe
+ - availability-zone-name
+ - ctag-pool-purpose
+ properties:
+ target-pe:
+ type: string
+ description: The Target provider edge router
+ availability-zone-name:
+ type: string
+ description: Name of the availability zone
+ ctag-pool-purpose:
+ type: string
+ description: Describes what the intended purpose of this pool is.
+ ctag-values:
+ type: string
+ description: Comma separated list of ctags
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ ctag-pools:
+ properties:
+ ctag-pool:
+ type: array
+ items:
+ $ref: "#/getDefinitions/ctag-pool"
+ customer:
+ description: |
+ customer identifiers to provide linkage back to BSS information.
+ ###### Related Nodes
+ - FROM service-subscription( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)
+ - CUSTOMER is DELETED when these are DELETED SERVICE-SUBSCRIPTION
+ required:
+ - global-customer-id
+ - subscriber-name
+ - subscriber-type
+ properties:
+ global-customer-id:
+ type: string
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ subscriber-name:
+ type: string
+ description: Subscriber name, an alternate way to retrieve a customer.
+ subscriber-type:
+ type: string
+ description: Subscriber type, a way to provide VID with only the INFRA customers.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ service-subscriptions:
+ type: array
+ items:
+ $ref: "#/getDefinitions/service-subscription"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ customers:
+ description: |
+ Collection of customer identifiers to provide linkage back to BSS information.
+ properties:
+ customer:
+ type: array
+ items:
+ $ref: "#/getDefinitions/customer"
cvlan-tag-entry:
required:
- cvlan-tag
@@ -44778,107 +62770,127 @@ definitions:
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
+ $ref: "#/getDefinitions/relationship"
cvlan-tags:
properties:
cvlan-tag-entry:
type: array
items:
- $ref: "#/definitions/cvlan-tag-entry"
- port-group:
+ $ref: "#/getDefinitions/cvlan-tag-entry"
+ dvs-switch:
description: |
- Used to capture the network interfaces of this VCE
+ Digital virtual switch metadata, used by SDN-C to configure VCEs. A&AI needs to receive this data from the PO deployment team and administer it using the provisioningTool.sh into A&AI.
###### Related Nodes
- - TO cvlan-tag (comprises port-group, Many2Many)
- - FROM vce (is composed of port-group)
+ - TO cloud-region( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO availability-zone( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
required:
- - interface-id
- - orchestration-status
+ - switch-name
+ - vcenter-url
properties:
- interface-id:
- type: string
- description: Unique ID of the interface
- neutron-network-id:
- type: string
- description: Neutron network id of this Interface
- neutron-network-name:
+ switch-name:
type: string
- description: Neutron network name of this Interface
- interface-role:
+ description: DVS switch name
+ vcenter-url:
type: string
- description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
+ description: URL used to reach the vcenter
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- port-group-id:
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ dvs-switches:
+ description: |
+ Collection of digital virtual switch metadata used for vmWare VCEs and GenericVnfs.
+ properties:
+ dvs-switch:
+ type: array
+ items:
+ $ref: "#/getDefinitions/dvs-switch"
+ edge-prop-names:
+ description: |
+ Internal map to define the properties of an edge and interpret the map EdgeRules
+ properties:
+ edgeLabel:
type: string
- description: Unique ID for port group in vmware
- port-group-name:
+ direction:
type: string
- description: Likely to duplicate value of neutron network name
- switch-name:
+ multiplicityRule:
type: string
- description: DVS or standard switch name (should be non-null for port groups associated with DVS)
- orchestration-status:
+ contains-other-v:
type: string
- description: Orchestration status of this VNF, mastered by MSO
- heat-stack-id:
+ delete-other-v:
type: string
- description: Heat stack id corresponding to this instance, managed by MSO
- mso-catalog-key:
+ SVC-INFRA:
type: string
- description: Corresponds to the SDN-C catalog id used to configure this VCE
- cvlan-tags:
+ prevent-delete:
+ type: string
+ edge-tag-query-request:
+ properties:
+ edge-tag:
+ type: string
+ result-detail:
+ type: string
+ start-node-type:
+ type: string
+ start-node-filter:
type: array
- items:
- $ref: "#/definitions/cvlan-tag-entry"
- relationship-list:
+ items:
+ $ref: "#/getDefinitions/start-node-filter"
+ include-node-filter:
type: array
- items:
- $ref: "#/definitions/relationship"
- port-groups:
+ items:
+ $ref: "#/getDefinitions/include-node-filter"
+ secondary-filter:
+ type: array
+ items:
+ $ref: "#/getDefinitions/secondary-filter"
+ edge-tag-query-result:
properties:
- port-group:
+ tagged-inventory-item-list:
type: array
items:
- $ref: "#/definitions/port-group"
- license:
+ $ref: "#/getDefinitions/tagged-inventory-item-list"
+ element-choice-set:
description: |
- Metadata for license group.
+ This is how we would capture constraints defining allowed sets of elements.
###### Related Nodes
- - FROM generic-vnf (is composed of license)
- - FROM vce (is composed of license)
+ - TO constrained-element-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)
+ - ELEMENT-CHOICE-SET is DELETED when these are DELETED MODEL-ELEMENT
required:
- - group-uuid
- - resource-uuid
+ - element-choice-set-uuid
+ - element-choice-set-name
properties:
- group-uuid:
+ element-choice-set-uuid:
type: string
- description: Unique ID for the license group the resource belongs to, should be uuid.
- resource-uuid:
+ element-choice-set-name:
+ type: string
+ cardinality:
type: string
- description: Unique ID of a license resource.
resource-version:
type: string
- description: Concurrency value
+ model-elements:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model-element"
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- licenses:
- description: |
- Licenses to be allocated across resources, keyed by group-uuid and resource-uuid, related to license management
+ $ref: "#/getDefinitions/relationship"
+ element-choice-sets:
properties:
- license:
+ element-choice-set:
type: array
items:
- $ref: "#/definitions/license"
+ $ref: "#/getDefinitions/element-choice-set"
entitlement:
description: |
Metadata for entitlement group.
###### Related Nodes
- - FROM generic-vnf (is composed of entitlement)
- - FROM vce (is composed of entitlement)
+ - TO generic-vnf( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vce( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
required:
- group-uuid
- resource-uuid
@@ -44895,7 +62907,7 @@ definitions:
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
+ $ref: "#/getDefinitions/relationship"
entitlements:
description: |
Entitlements, keyed by group-uuid and resource-uuid, related to license management
@@ -44903,26 +62915,496 @@ definitions:
entitlement:
type: array
items:
- $ref: "#/definitions/entitlement"
- vce:
+ $ref: "#/getDefinitions/entitlement"
+ esr-ems:
description: |
- Virtual Customer Edge Router, used specifically for Gamma. This object is deprecated.
+ Persist EMS address information used by EMS driver.
+ ###### Related Nodes
+ - TO esr-system-info (CHILD of esr-ems, esr-ems has esr-system-info, One2Many)
+ - ESR-EMS deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
+ required:
+ - ems-id
+ properties:
+ ems-id:
+ type: string
+ description: Unique ID of EMS.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ esr-system-info-list:
+ type: object
+ $ref: "#/getDefinitions/esr-system-info-list"
+ relationship-list:
+ type: object
+ $ref: "#/getDefinitions/relationship-list"
+ esr-ems-list:
+ properties:
+ esr-ems:
+ type: array
+ items:
+ $ref: "#/getDefinitions/esr-ems"
+ esr-system-info:
+ description: |
+ Persist common address information of external systems.
+ ###### Related Nodes
+ - FROM esr-ems (PARENT of esr-system-info, esr-ems has esr-system-info)
+ - FROM esr-vnfm (PARENT of esr-system-info, esr-vnfm has esr-system-info)
+ - FROM esr-thirdparty-sdnc (PARENT of esr-system-info, esr-thirdparty-sdnc has esr-system-info)
+ - FROM cloud-region (PARENT of esr-system-info, cloud-region has esr-system-info)
+ required:
+ - esr-system-info-id
+ - user-name
+ - password
+ - system-type
+ properties:
+ esr-system-info-id:
+ type: string
+ description: Unique ID of esr system info.
+ system-name:
+ type: string
+ description: name of external system.
+ type:
+ type: string
+ description: type of external systems.
+ vendor:
+ type: string
+ description: vendor of external systems.
+ version:
+ type: string
+ description: version of external systems.
+ service-url:
+ type: string
+ description: url used to access external systems.
+ user-name:
+ type: string
+ description: username used to access external systems.
+ password:
+ type: string
+ description: password used to access external systems.
+ system-type:
+ type: string
+ description: it could be vim/vnfm/thirdparty-sdnc/ems-resource/ems-performance/ems-alarm.
+ protocol:
+ type: string
+ description: protocol of third party SDNC, for example netconf/snmp.
+ ssl-cacert:
+ type: string
+ description: ca file content if enabled ssl on auth-url.
+ ssl-insecure:
+ type: boolean
+ description: Whether to verify VIM's certificate.
+ ip-address:
+ type: string
+ description: service IP of ftp server.
+ port:
+ type: string
+ description: service port of ftp server.
+ cloud-domain:
+ type: string
+ description: domain info for authentication.
+ default-tenant:
+ type: string
+ description: default tenant of VIM.
+ passive:
+ type: boolean
+ description: ftp passive mode or not.
+ remote-path:
+ type: string
+ description: resource or performance data file path.
+ system-status:
+ type: string
+ description: the status of external system.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ esr-system-info-list:
+ description: |
+ Collection of persistent block-level external system auth info.
+ properties:
+ esr-system-info:
+ type: array
+ items:
+ $ref: "#/getDefinitions/esr-system-info"
+ esr-thirdparty-sdnc:
+ description: |
+ Persist SDNC address information used by ONAP SDNC.
+ ###### Related Nodes
+ - TO esr-system-info (CHILD of esr-thirdparty-sdnc, esr-thirdparty-sdnc has esr-system-info, One2One)
+ - TO pnf( esr-thirdparty-sdnc has pnf, One2Many)
+ - ESR-THIRDPARTY-SDNC deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
+ required:
+ - thirdparty-sdnc-id
+ properties:
+ thirdparty-sdnc-id:
+ type: string
+ description: Unique ID of SDNC.
+ location:
+ type: string
+ description: used for DC type to indicate the location of SDNC, such as Core or Edge.
+ product-name:
+ type: string
+ description: password used to access SDNC server.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ esr-system-info-list:
+ type: object
+ $ref: "#/getDefinitions/esr-system-info-list"
+ relationship-list:
+ type: object
+ $ref: "#/getDefinitions/relationship-list"
+ esr-thirdparty-sdnc-list:
+ properties:
+ esr-thirdparty-sdnc:
+ type: array
+ items:
+ $ref: "#/getDefinitions/esr-thirdparty-sdnc"
+ esr-vnfm:
+ description: |
+ Persist VNFM address information used by VF-C.
###### Related Nodes
- - TO availability-zone (Many2Many)
- - TO complex (Many2Many)
- - TO port-group (comprises vce, Many2Many)
- - TO vserver (Many2Many)
- - TO service-instance (Many2Many)
- - TO entitlement (comprises vce, One2Many)
- - TO license (comprises vce, One2Many)
+ - TO esr-system-info (CHILD of esr-vnfm, esr-vnfm has esr-system-info, One2One)
+ - ESR-VNFM deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
+ required:
+ - vnfm-id
+ properties:
+ vnfm-id:
+ type: string
+ description: Unique ID of VNFM.
+ vim-id:
+ type: string
+ description: indecate the VIM to deploy VNF.
+ certificate-url:
+ type: string
+ description: certificate url of VNFM.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ esr-system-info-list:
+ type: object
+ $ref: "#/getDefinitions/esr-system-info-list"
+ relationship-list:
+ type: object
+ $ref: "#/getDefinitions/relationship-list"
+ esr-vnfm-list:
+ properties:
+ esr-vnfm:
+ type: array
+ items:
+ $ref: "#/getDefinitions/esr-vnfm"
+ evc:
+ description: |
+ evc object is an optional child object of the Configuration object.
+ ###### Related Nodes
+ - TO configuration( evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)
+ required:
+ - evc-id
+ properties:
+ evc-id:
+ type: string
+ description: Unique/key field for the evc object
+ forwarding-path-topology:
+ type: string
+ description: Point-to-Point, Multi-Point
+ cir-value:
+ type: string
+ description: Commited Information Rate
+ cir-units:
+ type: string
+ description: CIR units
+ connection-diversity-group-id:
+ type: string
+ description: Diversity Group ID
+ service-hours:
+ type: string
+ description: formerly Performance Group
+ esp-evc-circuit-id:
+ type: string
+ description: EVC Circuit ID of ESP EVC
+ esp-evc-cir-value:
+ type: string
+ description: Committed Information Rate (For ESP)
+ esp-evc-cir-units:
+ type: string
+ description: CIR units (For ESP)
+ esp-itu-code:
+ type: string
+ description: Identifies ESP
+ collector-pop-clli:
+ type: string
+ description: Collector POP CLLI (from the hostname of the access pnf)
+ inter-connect-type-ingress:
+ type: string
+ description: Interconnect type on ingress side of EVC.
+ tagmode-access-ingress:
+ type: string
+ description: tagode for collector side of EVC
+ tagmode-access-egress:
+ type: string
+ description: tagMode for network side of EVC
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ evcs:
+ properties:
+ evc:
+ type: array
+ items:
+ $ref: "#/getDefinitions/evc"
+ external-system:
+ description: |
+ Namespace for external system.
+ properties:
+ esr-ems-list:
+ type: object
+ $ref: "#/getDefinitions/esr-ems-list"
+ esr-vnfm-list:
+ type: object
+ $ref: "#/getDefinitions/esr-vnfm-list"
+ esr-thirdparty-sdnc-list:
+ type: object
+ $ref: "#/getDefinitions/esr-thirdparty-sdnc-list"
+ extra-properties:
+ description: |
+ Extra properties for inventory item for response list
+ properties:
+ extra-property:
+ type: array
+ items:
+ $ref: "#/getDefinitions/extra-property"
+ extra-property:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ flavor:
+ description: |
+ Openstack flavor.
+ ###### Related Nodes
+ - TO cloud-region( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)
+ - FLAVOR cannot be deleted if linked to VSERVER
+ required:
+ - flavor-id
+ - flavor-name
+ - flavor-selflink
+ properties:
+ flavor-id:
+ type: string
+ description: Flavor id, expected to be unique across cloud-region.
+ flavor-name:
+ type: string
+ description: Flavor name
+ flavor-vcpus:
+ type: integer
+ format: int32
+ description: Number of CPUs
+ flavor-ram:
+ type: integer
+ format: int32
+ description: Amount of memory
+ flavor-disk:
+ type: integer
+ format: int32
+ description: Disk space
+ flavor-ephemeral:
+ type: integer
+ format: int32
+ description: Amount of ephemeral disk space
+ flavor-swap:
+ type: string
+ description: amount of swap space allocation
+ flavor-is-public:
+ type: boolean
+ description: whether flavor is available to all users or private to the tenant it was created in.
+ flavor-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ flavor-disabled:
+ type: boolean
+ description: Boolean as to whether this flavor is no longer enabled
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ flavors:
+ description: |
+ Collection of openstack flavors.
+ properties:
+ flavor:
+ type: array
+ items:
+ $ref: "#/getDefinitions/flavor"
+ forwarder:
+ description: |
+ Entity describing a sequenced segment of forwarding path
+ ###### Related Nodes
+ - TO forwarding-path( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)
+ - TO l-interface( forwarder org.onap.relationships.inventory.ForwardsTo l-interface, MANY2ONE)
+ - TO configuration( forwarder org.onap.relationships.inventory.Uses configuration, ONE2ONE)
+ - TO lag-interface( forwarder org.onap.relationships.inventory.ForwardsTo lag-interface, MANY2ONE)
+ - TO p-interface( forwarder org.onap.relationships.inventory.ForwardsTo p-interface, MANY2ONE)
+ - FORWARDER deletion means associated objects of these types are also DELETED:CONFIGURATION
+ required:
+ - sequence
+ properties:
+ sequence:
+ type: integer
+ format: int32
+ description: Unique ID of this segmentation
+ forwarder-role:
+ type: string
+ description: ingress, intermediate, egress
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ forwarder-evc:
+ description: |
+ forwarder object is an optional child object of the Configuration object.
+ ###### Related Nodes
+ - TO configuration( forwarder-evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)
+ required:
+ - forwarder-evc-id
+ properties:
+ forwarder-evc-id:
+ type: string
+ description: Key for forwarder-evc object
+ circuit-id:
+ type: string
+ description: Circuit ID from customer/ESP/ingress end of EVC, or reference to beater circuit on gateway/network/egress end of EVC
+ ivlan:
+ type: string
+ description: Internal VLAN.
+ svlan:
+ type: string
+ description: SVLAN value for ingress of egress forwarder.
+ cvlan:
+ type: string
+ description: CVLAN value for ingress of egress forwarder.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ forwarder-evcs:
+ properties:
+ forwarder-evc:
+ type: array
+ items:
+ $ref: "#/getDefinitions/forwarder-evc"
+ forwarders:
+ properties:
+ forwarder:
+ type: array
+ items:
+ $ref: "#/getDefinitions/forwarder"
+ forwarding-path:
+ description: |
+ Entity that describes the sequenced forwarding path between interfaces of services or resources
+ ###### Related Nodes
+ - TO service-instance( forwarding-path org.onap.relationships.inventory.AppliesTo service-instance, MANY2ONE)
+ - TO configuration( forwarding-path org.onap.relationships.inventory.Uses configuration, ONE2ONE)
+ - FROM forwarder( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)
+ - FORWARDING-PATH is DELETED when these are DELETED FORWARDER
+ - FORWARDING-PATH deletion means associated objects of these types are also DELETED:CONFIGURATION
+ required:
+ - forwarding-path-id
+ - forwarding-path-name
+ properties:
+ forwarding-path-id:
+ type: string
+ description: Unique ID of this FP
+ forwarding-path-name:
+ type: string
+ description: Name of the FP
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ selflink:
+ type: string
+ description: the self link for this FP
+ forwarders:
+ type: array
+ items:
+ $ref: "#/getDefinitions/forwarder"
+ forwarding-paths:
+ properties:
+ forwarding-path:
+ type: array
+ items:
+ $ref: "#/getDefinitions/forwarding-path"
+ generic-vnf:
+ description: |
+ General purpose VNF
+ ###### Related Nodes
+ - TO availability-zone( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - TO complex( generic-vnf org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)
+ - TO configuration( generic-vnf org.onap.relationships.inventory.Uses configuration, ONE2MANY)
+ - TO ctag-pool( generic-vnf org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)
+ - TO instance-group( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO ipsec-configuration( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)
+ - TO l3-network( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO license-key-resource( generic-vnf org.onap.relationships.inventory.Uses license-key-resource, MANY2MANY)
+ - TO pnf( generic-vnf tosca.relationships.HostedOn pnf, MANY2MANY)
+ - TO pserver( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)
+ - TO vnf-image( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)
+ - TO volume-group( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - TO vserver( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)
+ - TO virtual-data-center( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY)
+ - FROM entitlement( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM lag-interface( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM license( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM network-profile( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)
+ - FROM site-pair-set( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM line-of-business( line-of-business org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)
+ - FROM platform( platform org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)
+ - GENERIC-VNF is DELETED when these are DELETED ENTITLEMENT,VNFC,LAG-INTERFACE,LICENSE,L-INTERFACE,VF-MODULE
+ - GENERIC-VNF deletion means associated objects of these types are also DELETED:CONFIGURATION
required:
- vnf-id
+ - vnf-instance-id
- vnf-name
- vnf-type
+ - vnf-package-name
+ - vnf-discriptor-name
+ - job-id
+ - in-maint
+ - is-closed-loop-disabled
properties:
vnf-id:
type: string
description: Unique id of VNF. This is unique across the graph.
+ vnf-instance-id:
+ type: string
+ description: vnf instance id.
vnf-name:
type: string
description: Name of VNF.
@@ -44934,7 +63416,7 @@ definitions:
description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
service-id:
type: string
- description: Unique identifier of service, does not strictly map to ASDC services, SOON TO BE DEPRECATED.
+ description: Unique identifier of service, does not necessarily map to ASDC service models. SOON TO BE DEPRECATED
regional-resource-zone:
type: string
description: Regional way of organizing pservers, source of truth should define values
@@ -44943,140 +63425,231 @@ definitions:
description: Trigger for operational monitoring of this resource by Service Assurance systems.
operational-status:
type: string
- description: Indicator for whether the resource is considered operational
+ description: Indicator for whether the resource is considered operational. Valid values are in-service-path and out-of-service-path.
license-key:
type: string
description: OBSOLETE - do not use
equipment-role:
type: string
- description: Network role being played by this VNF
+ description: Client should send valid enumerated value
orchestration-status:
type: string
- description: Orchestration status of this VNF, mastered by MSO
+ description: Orchestration status of this VNF, used by MSO.
+ vnf-package-name:
+ type: string
+ vnf-discriptor-name:
+ type: string
+ description: vnf discriptor name
+ job-id:
+ type: string
+ description: job id corresponding to vnf
heat-stack-id:
type: string
description: Heat stack id corresponding to this instance, managed by MSO
mso-catalog-key:
type: string
description: Corresponds to the SDN-C catalog id used to configure this VCE
- vpe-id:
- type: string
- description: Unique ID of VPE connected to this VCE.
- v6-vce-wan-address:
+ management-option:
type: string
- description: Valid v6 IP address for the WAN Link on this router. Implied length of /64.
+ description: identifier of managed by ATT or customer
ipv4-oam-address:
type: string
- description: Address tail-f uses to configure vce, also used for troubleshooting and is IP used for traps generated by VCE.
+ description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by generic-vnf.
+ ipv4-loopback0-address:
+ type: string
+ description: v4 Loopback0 address
+ nm-lan-v6-address:
+ type: string
+ description: v6 Loopback address
+ management-v6-address:
+ type: string
+ description: v6 management address
+ vcpu:
+ type: integer
+ format: int64
+ description: number of vcpus ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only by uCPE
+ vcpu-units:
+ type: string
+ description: units associated with vcpu, used for VNFs with no vservers/flavors, to be used only by uCPE
+ vmemory:
+ type: integer
+ format: int64
+ description: number of GB of memory ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only by uCPE
+ vmemory-units:
+ type: string
+ description: units associated with vmemory, used for VNFs with no vservers/flavors, to be used only by uCPE
+ vdisk:
+ type: integer
+ format: int64
+ description: number of vdisks ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only uCPE
+ vdisk-units:
+ type: string
+ description: units associated with vdisk, used for VNFs with no vservers/flavors, to be used only by uCPE
+ nshd:
+ type: integer
+ format: int64
+ description: number of associated SHD in vnf.
+ nvm:
+ type: integer
+ format: int64
+ description: number of vms in vnf.
+ nnet:
+ type: integer
+ format: int64
+ description: number of network in vnf.
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- ipv4-loopback0-address:
+ summary-status:
type: string
- description: Loopback0 address
+ description: details regarding the generic-vnf operation, PLEASE DISCONTINUE USE OF THIS FIELD.
+ encrypted-access-flag:
+ type: boolean
+ description: indicates whether generic-vnf access uses SSH
+ entitlement-assignment-group-uuid:
+ type: string
+ description: UUID of the Entitlement group used for licensing VNFs, OBSOLETE - See child relationships.
entitlement-resource-uuid:
type: string
- description: OBSOLETE - see child relationships
- port-groups:
+ description: UUID of the specific entitlement resource. OBSOLETE - See child relationships.
+ license-assignment-group-uuid:
+ type: string
+ description: UUID of the license assignment group. OBSOLETE - See child relationships.
+ license-key-uuid:
+ type: string
+ description: UUID of the actual license resource. OBSOLETE - See child relationships.
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ model-customization-id:
+ type: string
+ description: captures the id of all the configuration used to customize the resource for the service.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ as-number:
+ type: string
+ description: as-number of the VNF
+ regional-resource-subzone:
+ type: string
+ description: represents sub zone of the rr plane
+ nf-type:
+ type: string
+ description: Generic description of the type of NF
+ nf-function:
+ type: string
+ description: English description of Network function that the specific VNF deployment is providing
+ nf-role:
+ type: string
+ description: role in the network that this model will be providing
+ nf-naming-code:
+ type: string
+ description: string assigned to this model used for naming purposes
+ selflink:
+ type: string
+ description: Path to the controller object.
+ ipv4-oam-gateway-address:
+ type: string
+ description: Gateway address
+ ipv4-oam-gateway-address-prefix-length:
+ type: integer
+ format: int32
+ description: Prefix length for oam-address
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Temporary location for S-TAG to get to VCE
+ nm-profile-name:
+ type: string
+ description: Network Management profile of this VNF
+ relationship-list:
type: array
items:
- $ref: "#/definitions/port-group"
- licenses:
+ $ref: "#/getDefinitions/relationship"
+ l-interfaces:
type: array
items:
- $ref: "#/definitions/license"
- entitlements:
+ $ref: "#/getDefinitions/l-interface"
+ lag-interfaces:
type: array
items:
- $ref: "#/definitions/entitlement"
- relationship-list:
+ $ref: "#/getDefinitions/lag-interface"
+ vf-modules:
type: array
items:
- $ref: "#/definitions/relationship"
- vces:
+ $ref: "#/getDefinitions/vf-module"
+ licenses:
+ type: array
+ items:
+ $ref: "#/getDefinitions/license"
+ entitlements:
+ type: array
+ items:
+ $ref: "#/getDefinitions/entitlement"
+ generic-vnfs:
description: |
- Collection of Virtual Customer Edge Routers, used specifically for Gamma. This object is deprecated.
+ Collection of VNFs
properties:
- vce:
+ generic-vnf:
type: array
items:
- $ref: "#/definitions/vce"
- vnfc:
+ $ref: "#/getDefinitions/generic-vnf"
+ group-assignment:
description: |
+ Openstack group-assignment used to store exclusivity groups (EG).
###### Related Nodes
- - TO instance-group (Many2Many)
- - TO vip-ipv4-address-list (Many2Many)
- - TO vip-ipv6-address-list (Many2Many)
- - FROM vserver
- - FROM vf-module
- - FROM generic-vnf
- - FROM l3-interface-ipv4-address-list (comprises vnfc)
- - FROM l3-interface-ipv6-address-list (comprises vnfc)
+ - TO cloud-region( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)
required:
- - vnfc-name
- - nfc-naming-code
- - nfc-function
- - in-maint
- - is-closed-loop-disabled
+ - group-id
+ - group-type
+ - group-name
properties:
- vnfc-name:
- type: string
- description: Unique ID of vnfc.
- nfc-naming-code:
- type: string
- description: Short code that is used in naming instances of the item being modeled
- nfc-function:
- type: string
- description: English description of function that the specific resource deployment is providing. Assigned as part of the customization of a resource in a service
- prov-status:
- type: string
- description: prov status of this vnfc
- orchestration-status:
- type: string
- description: Orchestration status of this VNF, mastered by APP-C
- ipaddress-v4-oam-vip:
+ group-id:
type: string
- description: Oam V4 vip address of this vnfc
- in-maint:
- type: boolean
- is-closed-loop-disabled:
- type: boolean
- group-notation:
+ description: Group id, expected to be unique across cloud-region.
+ group-type:
type: string
- description: Group notation of VNFC
- model-invariant-id:
+ description: Group type - the type of group this instance refers to
+ group-name:
type: string
- description: the ASDC model id for this resource or service model.
- model-version-id:
+ description: Group name - name assigned to the group
+ group-description:
type: string
- description: the ASDC model version for this resource or service model.
+ description: Group description - description of the group
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- l3-interface-ipv4-address-list:
- type: array
- items:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
- l3-interface-ipv6-address-list:
- type: array
- items:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
- vnfcs:
+ $ref: "#/getDefinitions/relationship"
+ group-assignments:
description: |
- virtual network components associated with a vserver from application controller.
+ Collection of openstack group assignments
properties:
- vnfc:
+ group-assignment:
type: array
items:
- $ref: "#/definitions/vnfc"
+ $ref: "#/getDefinitions/group-assignment"
host-route:
description: |
###### Related Nodes
- - FROM subnet (is composed of host-route)
+ - TO subnet( host-route org.onap.relationships.inventory.BelongsTo subnet, MANY2ONE)
required:
- host-route-id
- route-prefix
@@ -45100,156 +63673,525 @@ definitions:
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
+ $ref: "#/getDefinitions/relationship"
host-routes:
properties:
host-route:
type: array
items:
- $ref: "#/definitions/host-route"
- subnet:
+ $ref: "#/getDefinitions/host-route"
+ image:
description: |
+ Openstack image.
###### Related Nodes
- - TO host-route (comprises subnet, One2Many)
- - FROM l3-interface-ipv4-address-list
- - FROM l3-interface-ipv6-address-list
- - FROM l3-network (is composed of subnet)
- - FROM vip-ipv4-address-list
- - FROM vip-ipv6-address-list
+ - TO cloud-region( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)
+ - IMAGE cannot be deleted if linked to VSERVER
+ - IMAGE is DELETED when these are DELETED METADATUM
required:
- - subnet-id
- - dhcp-enabled
+ - image-id
+ - image-name
+ - image-os-distro
+ - image-os-version
+ - image-selflink
properties:
- subnet-id:
+ image-id:
type: string
- description: Subnet ID, should be UUID.
- subnet-name:
+ description: Image id, expected to be unique across cloud region
+ image-name:
type: string
- description: Name associated with the subnet.
- neutron-subnet-id:
+ description: Image name
+ image-architecture:
type: string
- description: Neutron id of this subnet
- gateway-address:
+ description: Operating system architecture.
+ image-os-distro:
type: string
- description: gateway ip address
- network-start-address:
+ description: The common name of the operating system distribution in lowercase
+ image-os-version:
type: string
- description: network start address
- cidr-mask:
+ description: The operating system version as specified by the distributor.
+ application:
type: string
- description: cidr mask
- ip-version:
+ description: The application that the image instantiates.
+ application-vendor:
type: string
- description: ip version
- orchestration-status:
+ description: The vendor of the application.
+ application-version:
type: string
- description: Orchestration status of this VNF, mastered by MSO
- dhcp-enabled:
- type: boolean
- dhcp-start:
+ description: The version of the application.
+ image-selflink:
type: string
- description: the start address reserved for use by dhcp
- dhcp-end:
+ description: URL to endpoint where AAI can get more details
+ resource-version:
type: string
- description: the last address reserved for use by dhcp
- subnet-role:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ metadata:
+ type: array
+ items:
+ $ref: "#/getDefinitions/metadatum"
+ images:
+ description: |
+ Collectio of Openstack images.
+ properties:
+ image:
+ type: array
+ items:
+ $ref: "#/getDefinitions/image"
+ include-node-filter:
+ properties:
+ include-node-type:
type: string
- description: role of the subnet, referenced when assigning IPs
- ip-assignment-direction:
+ instance-filter:
+ description: |
+ InstanceFilter for performing a named-query or model query
+ instance-filters:
+ description: |
+ InstanceFilters for performing a named-query or model query
+ properties:
+ instance-filter:
+ type: array
+ items:
+ $ref: "#/getDefinitions/instance-filter"
+ instance-group:
+ description: |
+ General mechanism for grouping instances
+ ###### Related Nodes
+ - TO model( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)
+ - FROM l3-network( l3-network org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM pnf( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM vip-ipv4-address-list( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM vip-ipv6-address-list( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ required:
+ - instance-group-role
+ - model-invariant-id
+ - model-version-id
+ - id
+ - description
+ - type
+ properties:
+ instance-group-role:
type: string
- description: ip address assignment direction of the subnet
+ description: role of the instance group.
+ model-invariant-id:
+ type: string
+ description: ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: ASDC model version uid for this resource model.
+ id:
+ type: string
+ description: Instance Group ID, UUID assigned to this instance.
+ description:
+ type: string
+ description: Descriptive text to help identify the usage of this instance-group
+ type:
+ type: string
+ description: Only valid value today is lower case ha for high availability
+ sub-type:
+ type: string
+ description: Valid values for ha type are [geo-activeactive, geo-activestandby, local-activeactive, local-activestandby]
resource-version:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- subnet-sequence:
- type: integer
- format: int32
- description: sequence of the subnet
- host-routes:
+ description: Concurrency value
+ relationship-list:
type: array
items:
- $ref: "#/definitions/host-route"
- relationship-list:
+ $ref: "#/getDefinitions/relationship"
+ instance-groups:
+ description: |
+ Collection of openstack route table references
+ properties:
+ instance-group:
+ type: array
+ items:
+ $ref: "#/getDefinitions/instance-group"
+ inventory:
+ properties:
+ search:
+ type: object
+ $ref: "#/getDefinitions/search"
+ actions:
+ type: object
+ $ref: "#/getDefinitions/actions"
+ cloud-infrastructure:
+ type: object
+ $ref: "#/getDefinitions/cloud-infrastructure"
+ external-system:
+ type: object
+ $ref: "#/getDefinitions/external-system"
+ business:
+ type: object
+ $ref: "#/getDefinitions/business"
+ service-design-and-creation:
+ type: object
+ $ref: "#/getDefinitions/service-design-and-creation"
+ network:
+ type: object
+ $ref: "#/getDefinitions/network"
+ aai-internal:
+ type: object
+ $ref: "#/getDefinitions/aai-internal"
+ nodes:
type: array
items:
- $ref: "#/definitions/relationship"
- subnets:
+ $ref: "#/getDefinitions/aai-internal"
+ inventory-item:
properties:
- subnet:
+ inventory-item-type:
+ type: string
+ inventory-item-link:
+ type: string
+ inventory-item-data:
type: array
items:
- $ref: "#/definitions/subnet"
- ctag-assignment:
+ $ref: "#/getDefinitions/inventory-item-data"
+ tagged-inventory-item-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/tagged-inventory-item-list"
+ inventory-item-data:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ inventory-response-item:
+ description: |
+ Inventory item for response list
+ properties:
+ model-name:
+ type: string
+ extra-properties:
+ type: object
+ $ref: "#/getDefinitions/extra-properties"
+ inventory-response-items:
+ type: object
+ $ref: "#/getDefinitions/inventory-response-items"
+ inventory-response-items:
description: |
+ Container for inventory items in response list
+ properties:
+ inventory-response-item:
+ type: array
+ items:
+ $ref: "#/getDefinitions/inventory-response-item"
+ ipsec-configuration:
+ description: |
+ IPSec configuration node will contain various configuration data for the NMTE VNF. This node will have an edge to the generic-vnf (vnf type = TE). Starting 1607, this data will be populated by SDN-C
###### Related Nodes
- - FROM l3-network (is composed of ctag-assignment)
- - FROM service-instance
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)
+ - FROM vig-server( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)
+ - IPSEC-CONFIGURATION is DELETED when these are DELETED VIG-SERVER
required:
- - vlan-id-inner
+ - ipsec-configuration-id
properties:
- vlan-id-inner:
- type: integer
- format: int64
- description: id.
+ ipsec-configuration-id:
+ type: string
+ description: UUID of this configuration
+ requested-vig-address-type:
+ type: string
+ description: Indicate the type of VIG server like AVPN, INTERNET, BOTH
+ requested-encryption-strength:
+ type: string
+ description: Encryption values like 3des-cbc, des-cbc, aes-128-cbc, aes-192-cbc, aes-265-cbc
+ requested-dmz-type:
+ type: string
+ description: ATT can offer a shared DMZ or a DMZ specific to a customer
+ shared-dmz-network-address:
+ type: string
+ description: Network address of shared DMZ
+ requested-customer-name:
+ type: string
+ description: If the DMZ is a custom DMZ, this field will indicate the customer information
+ ike-version:
+ type: string
+ description: can be 1 or 2
+ ikev1-authentication:
+ type: string
+ description: Contains values like md5, sha1, sha256, sha384
+ ikev1-encryption:
+ type: string
+ description: Encyption values like 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
+ ikev1-dh-group:
+ type: string
+ description: Diffie-Hellman group like DH-GROUP2, DH-GROUP5, DH-GROUP14
+ ikev1-am-group-id:
+ type: string
+ description: Group name defined in VIG for clients using aggressive mode
+ ikev1-am-password:
+ type: string
+ description: pre-shared key for the above group name
+ ikev1-sa-lifetime:
+ type: string
+ description: Lifetime for IKEv1 SA
+ ipsec-authentication:
+ type: string
+ description: md5, sha1, sha256, sha384
+ ipsec-encryption:
+ type: string
+ description: 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
+ ipsec-sa-lifetime:
+ type: string
+ description: Life time for IPSec SA
+ ipsec-pfs:
+ type: string
+ description: enable PFS or not
+ xauth-userid:
+ type: string
+ description: user ID for xAuth, sm-user,ucpeHostName,nmteHostName
+ xauth-user-password:
+ type: string
+ description: Encrypted using the Juniper $9$ algorithm
+ dpd-interval:
+ type: string
+ description: The time between DPD probe
+ dpd-frequency:
+ type: string
+ description: Maximum number of DPD before claiming the tunnel is down
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- ctag-assignments:
+ $ref: "#/getDefinitions/relationship"
+ vig-servers:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vig-server"
+ ipsec-configurations:
properties:
- ctag-assignment:
+ ipsec-configuration:
type: array
items:
- $ref: "#/definitions/ctag-assignment"
- segmentation-assignment:
+ $ref: "#/getDefinitions/ipsec-configuration"
+ key-data:
+ properties:
+ key-name:
+ type: string
+ key-value:
+ type: string
+ l-interface:
description: |
- Openstack segmentation assignment.
+ Logical interfaces, e.g., a vnic.
###### Related Nodes
- - FROM l3-network (is composed of segmentation-assignment)
+ - TO generic-vnf( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO lag-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)
+ - TO instance-group( l-interface org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO l-interface( l-interface org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - TO logical-link( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)
+ - TO newvce( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)
+ - TO p-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)
+ - TO vserver( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.Uses l-interface, ONE2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - FROM sriov-vf( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)
+ - FROM vlan( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - L-INTERFACE is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST,SRIOV-VF,VLAN
+ - L-INTERFACE deletion means associated objects of these types are also DELETED:LOGICAL-LINK
required:
- - segmentation-id
+ - interface-name
+ - is-port-mirrored
+ - in-maint
+ - is-ip-unnumbered
properties:
- segmentation-id:
+ interface-name:
type: string
- description: Route Table Reference id, UUID assigned to this instance.
+ description: Name given to the interface
+ interface-role:
+ type: string
+ description: E.g., CUSTOMER, UPLINK, etc.
+ v6-wan-link-ip:
+ type: string
+ description: Questionably placed - v6 ip addr of this interface (is in vr-lan-interface from Mary B.
+ selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ interface-id:
+ type: string
+ description: ID of interface
+ macaddr:
+ type: string
+ description: MAC address for the interface
+ network-name:
+ type: string
+ description: Name of the network
+ management-option:
+ type: string
+ description: Whether A&AI should be managing this interface of not. Could have value like CUSTOMER
+ interface-description:
+ type: string
+ description: Human friendly text regarding this interface.
+ is-port-mirrored:
+ type: boolean
resource-version:
type: string
- description: Concurrency value
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ in-maint:
+ type: boolean
+ prov-status:
+ type: string
+ description: Prov Status of the logical interface. Valid values [PREPROV/NVTPROV/PROV].
+ is-ip-unnumbered:
+ type: boolean
+ allowed-address-pairs:
+ type: string
+ description: Freeform field for storing an ip address, list of ip addresses or a subnet block.
+ vlans:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vlan"
+ sriov-vfs:
+ type: array
+ items:
+ $ref: "#/getDefinitions/sriov-vf"
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l-interface"
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- segmentation-assignments:
+ $ref: "#/getDefinitions/relationship"
+ l3-interface-ipv4-address-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
+ l3-interface-ipv6-address-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
+ l-interfaces:
description: |
- Collection of openstack segmentation assignments
+ Collection of logical interfaces.
properties:
- segmentation-assignment:
+ l-interface:
type: array
items:
- $ref: "#/definitions/segmentation-assignment"
+ $ref: "#/getDefinitions/l-interface"
+ l3-interface-ipv4-address-list:
+ description: |
+ IPv4 Address Range
+ ###### Related Nodes
+ - TO instance-group( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)
+ - TO l3-network( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - TO subnet( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - TO l-interface( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - TO vlan( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ - TO vnfc( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vnfc, MANY2ONE)
+ required:
+ - l3-interface-ipv4-address
+ properties:
+ l3-interface-ipv4-address:
+ type: string
+ description: IP address
+ l3-interface-ipv4-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 32 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
+ type: string
+ description: Neutron network id of the interface that address belongs to
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of subnet that address belongs to
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ l3-interface-ipv6-address-list:
+ description: |
+ IPv6 Address Range
+ ###### Related Nodes
+ - TO instance-group( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf instance-group, MANY2MANY)
+ - TO l3-network( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - TO subnet( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - TO l-interface( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - TO vlan( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ - TO vnfc( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vnfc, MANY2ONE)
+ required:
+ - l3-interface-ipv6-address
+ properties:
+ l3-interface-ipv6-address:
+ type: string
+ description: IP address
+ l3-interface-ipv6-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 128 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
+ type: string
+ description: Neutron network id of the interface that address belongs to
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of subnet that address belongs to
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
l3-network:
description: |
Generic network definition
###### Related Nodes
- - TO vpn-binding (Many2Many)
- - TO instance-group (Many2Many)
- - TO subnet (comprises l3-network, Many2Many)
- - TO service-instance (Many2Many)
- - TO ctag-assignment (comprises l3-network, Many2Many)
- - TO network-policy (Many2Many)
- - TO segmentation-assignment (comprises l3-network, One2Many)
- - TO route-table-reference (Many2Many)
- - FROM cloud-region
- - FROM complex
- - FROM generic-vnf
- - FROM l3-interface-ipv4-address-list
- - FROM l3-interface-ipv6-address-list
- - FROM tenant
- - FROM vf-module
- - FROM allotted-resource
+ - TO instance-group( l3-network org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO network-policy( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)
+ - TO route-table-reference( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)
+ - TO vpn-binding( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM complex( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - FROM ctag-assignment( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM segmentation-assignment( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)
+ - FROM subnet( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)
+ - L3-NETWORK is DELETED when these are DELETED CTAG-ASSIGNMENT,SEGMENTATION-ASSIGNMENT,SUBNET
required:
- network-id
- network-name
@@ -45336,83 +64278,214 @@ definitions:
subnets:
type: array
items:
- $ref: "#/definitions/subnet"
+ $ref: "#/getDefinitions/subnet"
ctag-assignments:
type: array
items:
- $ref: "#/definitions/ctag-assignment"
+ $ref: "#/getDefinitions/ctag-assignment"
segmentation-assignments:
type: array
items:
- $ref: "#/definitions/segmentation-assignment"
+ $ref: "#/getDefinitions/segmentation-assignment"
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
+ $ref: "#/getDefinitions/relationship"
description: Relates to tenant (or is it a child of tenant), complex, service, vpn-binding
l3-networks:
properties:
l3-network:
type: array
items:
- $ref: "#/definitions/l3-network"
- network-policy:
+ $ref: "#/getDefinitions/l3-network"
+ lag-interface:
description: |
+ Link aggregate interface
###### Related Nodes
- - FROM l3-network
- - FROM allotted-resource
+ - TO generic-vnf( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO lag-link( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)
+ - TO logical-link( lag-interface org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - TO p-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)
+ - TO pnf( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - TO pserver( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - TO vpls-pe( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)
+ - LAG-INTERFACE is DELETED when these are DELETED L-INTERFACE
+ - LAG-INTERFACE deletion means associated objects of these types are also DELETED:LAG-LINK,LOGICAL-LINK
required:
- - network-policy-id
+ - interface-name
+ - in-maint
properties:
- network-policy-id:
+ interface-name:
type: string
- description: UUID representing unique key to this instance
- network-policy-fqdn:
+ description: Name that identifies the link aggregate interface
+ interface-description:
type: string
- description: Contrail FQDN for the policy
- heat-stack-id:
+ description: Human friendly text regarding this interface.
+ resource-version:
type: string
- description: ID for the openStack Heat instance
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ interface-id:
+ type: string
+ description: ID of interface
+ interface-role:
+ type: string
+ description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ in-maint:
+ type: boolean
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l-interface"
+ lag-interfaces:
+ description: |
+ Collection of link aggregate interfaces.
+ properties:
+ lag-interface:
+ type: array
+ items:
+ $ref: "#/getDefinitions/lag-interface"
+ lag-link:
+ description: |
+ LAG links can connect lag-interfaces
+ ###### Related Nodes
+ - FROM lag-interface( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)
+ required:
+ - link-name
+ properties:
+ link-name:
+ type: string
+ description: Alphabetical concatenation of lag-interface names
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- network-policies:
+ $ref: "#/getDefinitions/relationship"
+ lag-links:
+ description: |
+ Collection of link aggregation connections
properties:
- network-policy:
+ lag-link:
type: array
items:
- $ref: "#/definitions/network-policy"
- vf-module:
+ $ref: "#/getDefinitions/lag-link"
+ license:
description: |
- a deployment unit of VNFCs
+ Metadata for license group.
###### Related Nodes
- - TO volume-group (One2One)
- - TO l3-network (Many2Many)
- - TO vnfc (One2Many)
- - FROM vserver
- - FROM generic-vnf (is composed of vf-module)
+ - TO generic-vnf( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vce( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
required:
- - vf-module-id
- - is-base-vf-module
+ - group-uuid
+ - resource-uuid
properties:
- vf-module-id:
+ group-uuid:
type: string
- description: Unique ID of vf-module.
- vf-module-name:
+ description: Unique ID for the license group the resource belongs to, should be uuid.
+ resource-uuid:
type: string
- description: Name of vf-module
- heat-stack-id:
+ description: Unique ID of a license resource.
+ resource-version:
type: string
- description: Heat stack id corresponding to this instance.
- orchestration-status:
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ licenses:
+ description: |
+ Licenses to be allocated across resources, keyed by group-uuid and resource-uuid, related to license management
+ properties:
+ license:
+ type: array
+ items:
+ $ref: "#/getDefinitions/license"
+ line-of-business:
+ description: |
+ describes a line-of-business
+ ###### Related Nodes
+ - TO generic-vnf( line-of-business org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)
+ required:
+ - line-of-business-name
+ properties:
+ line-of-business-name:
type: string
- description: orchestration status of this vf-module, mastered by MSO
- is-base-vf-module:
+ description: Name of the line-of-business (product)
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ lines-of-business:
+ description: |
+ Collection of lines-of-business
+ properties:
+ line-of-business:
+ type: array
+ items:
+ $ref: "#/getDefinitions/line-of-business"
+ logical-link:
+ description: |
+ Logical links generally connect l-interfaces but are used to express logical connectivity between two points
+ ###### Related Nodes
+ - TO cloud-region( logical-link org.onap.relationships.inventory.LocatedIn cloud-region, MANY2MANY)
+ - TO generic-vnf( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)
+ - TO lag-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)
+ - TO logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - TO pnf( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)
+ - TO pserver( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)
+ - TO vpn-binding( logical-link org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - TO virtual-data-center( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM configuration( configuration org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - FROM lag-interface( lag-interface org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)
+ - FROM p-interface( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - FROM vlan( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ required:
+ - link-name
+ - in-maint
+ - link-type
+ properties:
+ link-name:
+ type: string
+ description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
+ in-maint:
type: boolean
+ link-type:
+ type: string
+ description: Type of logical link, e.g., evc
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ ip-version:
+ type: string
+ description: v4, v6, or ds for dual stack
+ routing-protocol:
+ type: string
+ description: For example, static or BGP
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
@@ -45425,292 +64498,519 @@ definitions:
persona-model-version:
type: string
description: the ASDC model version for this resource or service model.
- model-customization-id:
- type: string
- description: captures the id of all the configuration used to customize the resource for the service.
widget-model-id:
type: string
description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
widget-model-version:
type: string
description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
- contrail-service-instance-fqdn:
+ operational-status:
type: string
- description: the Contrail unique ID for a service-instance
- module-index:
- type: integer
- format: int32
- description: the index will track the number of modules of a given type that have been deployed in a VNF, starting with 0, and always choosing the lowest available digit
- selflink:
+ description: Indication of operational status of the logical link.
+ prov-status:
type: string
- description: Path to the controller object.
+ description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+ link-role:
+ type: string
+ description: Indication of the network use of the logical link.
+ link-name2:
+ type: string
+ description: Alias or alternate name (CLCI or D1 name).
+ link-id:
+ type: string
+ description: UUID of the logical-link, SDNC generates this.
+ circuit-id:
+ type: string
+ description: Circuit id
+ purpose:
+ type: string
+ description: Reason for this entity, role it is playing
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- vf-modules:
+ $ref: "#/getDefinitions/relationship"
+ logical-links:
description: |
- Collection of vf-modules, a deployment unit of VNFCs
+ Collection of logical connections
properties:
- vf-module:
+ logical-link:
type: array
items:
- $ref: "#/definitions/vf-module"
- generic-vnf:
+ $ref: "#/getDefinitions/logical-link"
+ metadata:
description: |
- General purpose VNF
+ Collection of metadatum (key/value pairs)
+ properties:
+ metadatum:
+ type: array
+ items:
+ $ref: "#/getDefinitions/metadatum"
+ metadatum:
+ description: |
+ Key/value pairs
###### Related Nodes
- - TO license-key-resource (Many2Many)
- - TO l-interface (comprises generic-vnf, Many2Many)
- - TO availability-zone (Many2Many)
- - TO lag-interface (comprises generic-vnf, Many2Many)
- - TO l3-network (Many2Many)
- - TO pserver (Many2Many)
- - TO vnf-image (Many2One)
- - TO vserver (One2Many)
- - TO service-instance (Many2Many)
- - TO site-pair-set (Many2Many)
- - TO network-profile (Many2Many)
- - TO pnf (Many2Many)
- - TO ipsec-configuration (Many2One)
- - TO configuration (One2Many)
- - TO vf-module (comprises generic-vnf, One2Many)
- - TO volume-group (One2Many)
- - TO vnfc (One2Many)
- - TO instance-group (Many2Many)
- - TO entitlement (comprises generic-vnf, One2Many)
- - TO license (comprises generic-vnf, One2Many)
- - TO complex (Many2Many)
- - TO ctag-pool (Many2Many)
- - FROM line-of-business
- - FROM platform
- - FROM virtual-data-center
- - FROM logical-link
- - FROM allotted-resource
+ - TO configuration( metadatum org.onap.relationships.inventory.BelongsTo configuration, MANY2ONE)
+ - TO connector( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)
+ - TO image( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)
+ - TO service-instance( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - TO model-ver( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
required:
- - vnf-id
- - vnf-name
- - vnf-type
- - in-maint
- - is-closed-loop-disabled
+ - metaname
+ - metaval
properties:
- vnf-id:
- type: string
- description: Unique id of VNF. This is unique across the graph.
- vnf-name:
- type: string
- description: Name of VNF.
- vnf-name2:
- type: string
- description: Alternate name of VNF.
- vnf-type:
- type: string
- description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
- service-id:
- type: string
- description: Unique identifier of service, does not necessarily map to ASDC service models. SOON TO BE DEPRECATED
- regional-resource-zone:
- type: string
- description: Regional way of organizing pservers, source of truth should define values
- prov-status:
+ metaname:
type: string
- description: Trigger for operational monitoring of this resource by Service Assurance systems.
- operational-status:
+ metaval:
type: string
- description: Indicator for whether the resource is considered operational. Valid values are in-service-path and out-of-service-path.
- license-key:
+ resource-version:
type: string
- description: OBSOLETE - do not use
- equipment-role:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model:
+ description: |
+ Subgraph definition provided by ASDC to describe an inventory asset and its connections related to ASDC models, independent of version
+ ###### Related Nodes
+ - TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - FROM instance-group( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY)
+ - FROM model-ver( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - FROM named-query( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)
+ - MODEL cannot be deleted if linked to INSTANCE-GROUP,NAMED-QUERY,NAMED-QUERY-ELEMENT
+ - MODEL is DELETED when these are DELETED MODEL-VER
+ required:
+ - model-invariant-id
+ - model-type
+ properties:
+ model-invariant-id:
type: string
- description: Client should send valid enumerated value
- orchestration-status:
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ model-type:
type: string
- description: Orchestration status of this VNF, used by MSO.
- heat-stack-id:
+ description: Type of the model, e.g., service, resource, widget, etc.
+ resource-version:
type: string
- description: Heat stack id corresponding to this instance, managed by MSO
- mso-catalog-key:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-vers:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model-ver"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ model-and-named-query-search:
+ description: |
+ ModelAndNamedQuerySearch holds query-parameters and instance-properties for performing a named-query or model query
+ properties:
+ query-parameters:
+ type: object
+ $ref: "#/getDefinitions/query-parameters"
+ instance-filters:
+ type: object
+ $ref: "#/getDefinitions/instance-filters"
+ secondary-filts:
+ type: object
+ $ref: "#/getDefinitions/secondary-filts"
+ top-node-type:
type: string
- description: Corresponds to the SDN-C catalog id used to configure this VCE
- management-option:
+ secondary-filter-cut-point:
type: string
- description: identifier of managed by ATT or customer
- ipv4-oam-address:
+ model-constraint:
+ description: |
+ This is how we would capture constraints defining allowed sets of elements.
+ ###### Related Nodes
+ - TO model-element( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)
+ - MODEL-CONSTRAINT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET
+ required:
+ - model-constraint-uuid
+ - constrained-element-set-uuid-to-replace
+ properties:
+ model-constraint-uuid:
type: string
- description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by generic-vnf.
- ipv4-loopback0-address:
+ constrained-element-set-uuid-to-replace:
type: string
- description: v4 Loopback0 address
- nm-lan-v6-address:
+ constrained-element-sets:
+ type: array
+ items:
+ $ref: "#/getDefinitions/constrained-element-set"
+ resource-version:
type: string
- description: v6 Loopback address
- management-v6-address:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-constraints:
+ properties:
+ model-constraint:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model-constraint"
+ model-element:
+ description: |
+ Defines how other models combine to make up a higher-level model.
+ ###### Related Nodes
+ - TO element-choice-set( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)
+ - TO model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - TO model-ver( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE)
+ - TO model-ver( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM model-constraint( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - MODEL-ELEMENT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET,MODEL-CONSTRAINT
+ required:
+ - model-element-uuid
+ - new-data-del-flag
+ - cardinality
+ properties:
+ model-element-uuid:
type: string
- description: v6 management address
- vcpu:
- type: integer
- format: int64
- description: number of vcpus ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only by uCPE
- vcpu-units:
+ new-data-del-flag:
type: string
- description: units associated with vcpu, used for VNFs with no vservers/flavors, to be used only by uCPE
- vmemory:
- type: integer
- format: int64
- description: number of GB of memory ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only by uCPE
- vmemory-units:
+ description: Indicates whether this element was created as part of instantiation from this model
+ cardinality:
type: string
- description: units associated with vmemory, used for VNFs with no vservers/flavors, to be used only by uCPE
- vdisk:
- type: integer
- format: int64
- description: number of vdisks ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only uCPE
- vdisk-units:
+ description: How many of this type of element are required/allowed
+ linkage-points:
type: string
- description: units associated with vdisk, used for VNFs with no vservers/flavors, to be used only by uCPE
- in-maint:
- type: boolean
- is-closed-loop-disabled:
- type: boolean
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- summary-status:
+ model-elements:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model-element"
+ description: Defines how other models combine to make up a higher-level model
+ model-constraints:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model-constraint"
+ description: Describes new constraints on this model element that are not part of that model's definition
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ model-elements:
+ properties:
+ model-element:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model-element"
+ model-ver:
+ description: |
+ Subgraph definition provided by ASDC to describe a specific version of an inventory asset and its connections related to ASDC models
+ ###### Related Nodes
+ - TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - MODEL-VER cannot be deleted if linked to MODEL-ELEMENT
+ - MODEL-VER is DELETED when these are DELETED MODEL-ELEMENT,METADATUM
+ required:
+ - model-version-id
+ - model-name
+ - model-version
+ properties:
+ model-version-id:
type: string
- description: details regarding the generic-vnf operation, PLEASE DISCONTINUE USE OF THIS FIELD.
- encrypted-access-flag:
- type: boolean
- description: indicates whether generic-vnf access uses SSH
- entitlement-assignment-group-uuid:
+ description: Unique identifier corresponding to one version of a model in ASDC
+ model-name:
type: string
- description: UUID of the Entitlement group used for licensing VNFs, OBSOLETE - See child relationships.
- entitlement-resource-uuid:
+ description: Name of the model, which can change from version to version.
+ model-version:
type: string
- description: UUID of the specific entitlement resource. OBSOLETE - See child relationships.
- license-assignment-group-uuid:
+ description: Version
+ model-description:
type: string
- description: UUID of the license assignment group. OBSOLETE - See child relationships.
- license-key-uuid:
+ description: Description
+ resource-version:
type: string
- description: UUID of the actual license resource. OBSOLETE - See child relationships.
- model-invariant-id:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-elements:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model-element"
+ metadata:
+ type: array
+ items:
+ $ref: "#/getDefinitions/metadatum"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ model-vers:
+ properties:
+ model-ver:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model-ver"
+ models:
+ description: |
+ Collection of subgraph definitions provided by ASDC to describe the inventory assets and their connections related to ASDC models
+ properties:
+ model:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model"
+ multicast-configuration:
+ description: |
+ ###### Related Nodes
+ - FROM vlan( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)
+ required:
+ - multicast-configuration-id
+ - multicast-protocol
+ - rp-type
+ properties:
+ multicast-configuration-id:
type: string
- description: the ASDC model id for this resource or service model.
- model-version-id:
+ description: Unique id of multicast configuration.
+ multicast-protocol:
type: string
- description: the ASDC model version for this resource or service model.
- persona-model-version:
+ description: protocol of multicast configuration
+ rp-type:
type: string
- description: the ASDC model version for this resource or service model.
- model-customization-id:
+ description: rp type of multicast configuration
+ resource-version:
type: string
- description: captures the id of all the configuration used to customize the resource for the service.
- widget-model-id:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ multicast-configurations:
+ description: |
+ multicast configuration of generic-vnf ip-address
+ properties:
+ multicast-configuration:
+ type: array
+ items:
+ $ref: "#/getDefinitions/multicast-configuration"
+ named-queries:
+ properties:
+ named-query:
+ type: array
+ items:
+ $ref: "#/getDefinitions/named-query"
+ named-query:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - TO model( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - NAMED-QUERY is DELETED when these are DELETED NAMED-QUERY-ELEMENT
+ required:
+ - named-query-uuid
+ - named-query-name
+ - named-query-version
+ properties:
+ named-query-uuid:
type: string
- description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
- widget-model-version:
+ named-query-name:
type: string
- description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
- as-number:
+ named-query-version:
type: string
- description: as-number of the VNF
- regional-resource-subzone:
+ required-input-param:
type: string
- description: represents sub zone of the rr plane
- nf-type:
+ description:
type: string
- description: Generic description of the type of NF
- nf-function:
+ resource-version:
type: string
- description: English description of Network function that the specific VNF deployment is providing
- nf-role:
+ named-query-elements:
+ type: array
+ items:
+ $ref: "#/getDefinitions/named-query-element"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ named-query-element:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - TO model( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)
+ - TO named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM property-constraint( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM related-lookup( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - NAMED-QUERY-ELEMENT is DELETED when these are DELETED PROPERTY-CONSTRAINT,RELATED-LOOKUP
+ required:
+ - named-query-element-uuid
+ properties:
+ named-query-element-uuid:
type: string
- description: role in the network that this model will be providing
- nf-naming-code:
+ property-collect-list:
type: string
- description: string assigned to this model used for naming purposes
- selflink:
+ resource-version:
type: string
- description: Path to the controller object.
- ipv4-oam-gateway-address:
+ property-limit-desc:
type: string
- description: Gateway address
- ipv4-oam-gateway-address-prefix-length:
- type: integer
- format: int32
- description: Prefix length for oam-address
- vlan-id-outer:
- type: integer
- format: int64
- description: Temporary location for S-TAG to get to VCE
- nm-profile-name:
+ do-not-output:
type: string
- description: Network Management profile of this VNF
+ named-query-elements:
+ type: array
+ items:
+ $ref: "#/getDefinitions/named-query-element"
+ related-lookups:
+ type: array
+ items:
+ $ref: "#/getDefinitions/related-lookup"
+ property-constraints:
+ type: array
+ items:
+ $ref: "#/getDefinitions/property-constraint"
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- l-interfaces:
+ $ref: "#/getDefinitions/relationship"
+ named-query-elements:
+ properties:
+ named-query-element:
+ type: array
+ items:
+ $ref: "#/getDefinitions/named-query-element"
+ network:
+ description: |
+ Namespace for network inventory resources.
+ properties:
+ logical-links:
type: array
items:
- $ref: "#/definitions/l-interface"
- lag-interfaces:
+ $ref: "#/getDefinitions/logical-link"
+ site-pair-sets:
type: array
items:
- $ref: "#/definitions/lag-interface"
- vf-modules:
+ $ref: "#/getDefinitions/site-pair-set"
+ vpn-bindings:
type: array
items:
- $ref: "#/definitions/vf-module"
- licenses:
+ $ref: "#/getDefinitions/vpn-binding"
+ vpls-pes:
type: array
items:
- $ref: "#/definitions/license"
- entitlements:
+ $ref: "#/getDefinitions/vpls-pe"
+ multicast-configurations:
type: array
items:
- $ref: "#/definitions/entitlement"
- generic-vnfs:
- description: |
- Collection of VNFs
+ $ref: "#/getDefinitions/multicast-configuration"
+ vces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vce"
+ vnfcs:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vnfc"
+ l3-networks:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l3-network"
+ network-policies:
+ type: array
+ items:
+ $ref: "#/getDefinitions/network-policy"
+ generic-vnfs:
+ type: array
+ items:
+ $ref: "#/getDefinitions/generic-vnf"
+ lag-links:
+ type: array
+ items:
+ $ref: "#/getDefinitions/lag-link"
+ newvces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/newvce"
+ pnfs:
+ type: array
+ items:
+ $ref: "#/getDefinitions/pnf"
+ physical-links:
+ type: array
+ items:
+ $ref: "#/getDefinitions/physical-link"
+ ipsec-configurations:
+ type: array
+ items:
+ $ref: "#/getDefinitions/ipsec-configuration"
+ route-table-references:
+ type: array
+ items:
+ $ref: "#/getDefinitions/route-table-reference"
+ instance-groups:
+ type: array
+ items:
+ $ref: "#/getDefinitions/instance-group"
+ zones:
+ type: array
+ items:
+ $ref: "#/getDefinitions/zone"
+ configurations:
+ type: array
+ items:
+ $ref: "#/getDefinitions/configurations"
+ network-policies:
properties:
- generic-vnf:
+ network-policy:
type: array
items:
- $ref: "#/definitions/generic-vnf"
- lag-link:
+ $ref: "#/getDefinitions/network-policy"
+ network-policy:
description: |
- LAG links can connect lag-interfaces
###### Related Nodes
- - FROM lag-interface
- - FROM logical-link
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.Uses network-policy, ONE2ONE)
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)
required:
- - link-name
+ - network-policy-id
properties:
- link-name:
+ network-policy-id:
type: string
- description: Alphabetical concatenation of lag-interface names
+ description: UUID representing unique key to this instance
+ network-policy-fqdn:
+ type: string
+ description: Contrail FQDN for the policy
+ heat-stack-id:
+ type: string
+ description: ID for the openStack Heat instance
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- lag-links:
+ $ref: "#/getDefinitions/relationship"
+ network-profile:
description: |
- Collection of link aggregation connections
+ Network profile populated by SDN-GP for SNMP
+ ###### Related Nodes
+ - TO generic-vnf( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ required:
+ - nm-profile-name
properties:
- lag-link:
+ nm-profile-name:
+ type: string
+ description: Unique name of network profile.
+ community-string:
+ type: string
+ description: Encrypted SNMP community string
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ network-profiles:
+ description: |
+ Collection of network profiles
+ properties:
+ network-profile:
type: array
items:
- $ref: "#/definitions/lag-link"
+ $ref: "#/getDefinitions/network-profile"
newvce:
description: |
This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce.
###### Related Nodes
- - TO l-interface (comprises newvce, Many2Many)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)
+ - NEWVCE is DELETED when these are DELETED L-INTERFACE
required:
- vnf-id2
- vnf-name
@@ -45761,11 +65061,11 @@ definitions:
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
+ $ref: "#/getDefinitions/relationship"
l-interfaces:
type: array
items:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
newvces:
description: |
This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce.
@@ -45773,20 +65073,391 @@ definitions:
newvce:
type: array
items:
- $ref: "#/definitions/newvce"
+ $ref: "#/getDefinitions/newvce"
+ notification-event:
+ properties:
+ cambria.partition:
+ type: string
+ notification-event-header:
+ type: object
+ $ref: "#/getDefinitions/notification-event-header"
+ notification-event-header:
+ properties:
+ id:
+ type: string
+ timestamp:
+ type: string
+ source-name:
+ type: string
+ domain:
+ type: string
+ sequence-number:
+ type: string
+ severity:
+ type: string
+ event-type:
+ type: string
+ version:
+ type: string
+ action:
+ type: string
+ entity-type:
+ type: string
+ top-entity-type:
+ type: string
+ entity-link:
+ type: string
+ status:
+ type: string
+ notify:
+ required:
+ - event-id
+ properties:
+ event-id:
+ type: string
+ node-type:
+ type: string
+ event-trigger:
+ type: string
+ key-data:
+ type: array
+ items:
+ $ref: "#/getDefinitions/key-data"
+ selflink:
+ type: string
+ oam-network:
+ description: |
+ OAM network, to be deprecated shortly. Do not use for new purposes.
+ ###### Related Nodes
+ - TO cloud-region( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO complex( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)
+ - TO service-capability( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ required:
+ - network-uuid
+ - network-name
+ - cvlan-tag
+ properties:
+ network-uuid:
+ type: string
+ description: UUID of the network. Unique across a cloud-region
+ network-name:
+ type: string
+ description: Name of the network.
+ cvlan-tag:
+ type: integer
+ format: int64
+ description: cvlan-id
+ ipv4-oam-gateway-address:
+ type: string
+ description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
+ ipv4-oam-gateway-address-prefix-length:
+ type: integer
+ format: int32
+ description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ oam-networks:
+ description: |
+ Collection of OAM networks, to be deprecated shortly. Do not use for new purposes.
+ properties:
+ oam-network:
+ type: array
+ items:
+ $ref: "#/getDefinitions/oam-network"
+ operational-environment:
+ description: |
+ It is a logical partition of the cloud which allows to have multiple environments in the production AIC.
+ ###### Related Nodes
+ - TO operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)
+ - FROM operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)
+ required:
+ - operational-environment-id
+ - operational-environment-name
+ - operational-environment-type
+ - operational-environment-status
+ - tenant-context
+ - workload-context
+ properties:
+ operational-environment-id:
+ type: string
+ description: UUID of an operational environment
+ operational-environment-name:
+ type: string
+ description: Operational Environment name
+ operational-environment-type:
+ type: string
+ description: Operational Environment Type.
+ operational-environment-status:
+ type: string
+ description: Status
+ tenant-context:
+ type: string
+ description: Tenant Context.
+ workload-context:
+ type: string
+ description: Workload Context.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ operational-environments:
+ description: |
+ a logical partition of the cloud which allows to have multiple environments in the production AIC.
+ properties:
+ operational-environment:
+ type: array
+ items:
+ $ref: "#/getDefinitions/operational-environment"
+ overloaded-model:
+ description: |
+ Allows for legacy POST of old-style and new-style models
+ required:
+ - model-invariant-id
+ - model-name-version-id
+ - model-type
+ - model-name
+ - model-id
+ - model-version
+ properties:
+ model-invariant-id:
+ type: string
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ model-name-version-id:
+ type: string
+ description: Unique identifier corresponding to one version of a model in ASDC
+ model-type:
+ type: string
+ description: Type of the model, e.g., service, resource, widget, etc.
+ model-name:
+ type: string
+ description: Name of the model, which can change from version to version.
+ model-id:
+ type: string
+ description: Invariant unique ID which does not change from version to version
+ model-version:
+ type: string
+ description: Version
+ model-description:
+ type: string
+ description: Description
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-vers:
+ type: object
+ $ref: "#/getDefinitions/model-vers"
+ relationship-list:
+ type: object
+ $ref: "#/getDefinitions/relationship-list"
+ owning-entities:
+ description: |
+ Collection of owning-entities
+ properties:
+ owning-entity:
+ type: array
+ items:
+ $ref: "#/getDefinitions/owning-entity"
+ owning-entity:
+ description: |
+ describes an owning-entity
+ ###### Related Nodes
+ - FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo owning-entity, MANY2ONE)
+ required:
+ - owning-entity-id
+ - owning-entity-name
+ properties:
+ owning-entity-id:
+ type: string
+ description: UUID of an owning entity
+ owning-entity-name:
+ type: string
+ description: Owning entity name
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ p-interface:
+ description: |
+ Physical interface (e.g., nic)
+ ###### Related Nodes
+ - TO logical-link( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)
+ - TO physical-link( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)
+ - TO pnf( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - TO pserver( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - TO vpls-pe( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM lag-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)
+ - FROM sriov-pf( sriov-pf org.onap.relationships.inventory.BelongsTo p-interface, ONE2ONE)
+ - P-INTERFACE is DELETED when these are DELETED L-INTERFACE,SRIOV-PF
+ - P-INTERFACE deletion means associated objects of these types are also DELETED:PHYSICAL-LINK
+ required:
+ - interface-name
+ - in-maint
+ properties:
+ interface-name:
+ type: string
+ description: Name that identifies the physical interface
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ port-description:
+ type: string
+ description: Nature of the services and connectivity on this port.
+ equipment-identifier:
+ type: string
+ description: CLEI or other specification for p-interface hardware.
+ interface-role:
+ type: string
+ description: Role specification for p-interface hardware.
+ interface-type:
+ type: string
+ description: Indicates the physical properties of the interface.
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ mac-addresss:
+ type: string
+ description: MAC Address of the p-interface.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ in-maint:
+ type: boolean
+ inv-status:
+ type: string
+ description: inventory status
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ sriov-pfs:
+ type: array
+ items:
+ $ref: "#/getDefinitions/sriov-pf"
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l-interface"
+ p-interfaces:
+ description: |
+ Collection of physical interfaces.
+ properties:
+ p-interface:
+ type: array
+ items:
+ $ref: "#/getDefinitions/p-interface"
+ physical-link:
+ description: |
+ Collection of physical connections, typically between p-interfaces
+ ###### Related Nodes
+ - FROM p-interface( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)
+ required:
+ - link-name
+ properties:
+ link-name:
+ type: string
+ description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ circuit-id:
+ type: string
+ description: Circuit it
+ dual-mode:
+ type: string
+ description: Dual access mode (e.g., primary, secondary
+ management-option:
+ type: string
+ description: To provide information on who manages this circuit. A&AI or 3rd party transport provider
+ service-provider-name:
+ type: string
+ description: Name of the service Provider on this link.
+ service-provider-bandwidth-up-value:
+ type: integer
+ format: int32
+ description: Upstream Bandwidth value agreed with the service provider
+ service-provider-bandwidth-up-units:
+ type: string
+ description: Units for the upstream BW value
+ service-provider-bandwidth-down-value:
+ type: integer
+ format: int32
+ description: Downstream Bandwidth value agreed with the service provider
+ service-provider-bandwidth-down-units:
+ type: string
+ description: Units for downstream BW value
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ physical-links:
+ description: |
+ Collection of physical connections, typically between p-interfaces
+ properties:
+ physical-link:
+ type: array
+ items:
+ $ref: "#/getDefinitions/physical-link"
+ platform:
+ description: |
+ describes a platform
+ ###### Related Nodes
+ - TO generic-vnf( platform org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)
+ required:
+ - platform-name
+ properties:
+ platform-name:
+ type: string
+ description: Name of the platform
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ platforms:
+ description: |
+ Collection of platforms
+ properties:
+ platform:
+ type: array
+ items:
+ $ref: "#/getDefinitions/platform"
pnf:
description: |
PNF represents a physical network function. typically equipment used in the D1 world. in 1607, this will be populated by SDN-C to represent a premises router that a uCPE connects to. But this can be used to represent any physical device that is not an AIC node or uCPE.
###### Related Nodes
- - TO p-interface (comprises pnf, Many2Many)
- - TO lag-interface (comprises pnf, One2Many)
- - TO complex (Many2One)
- - TO instance-group (Many2Many)
- - TO zone (Many2One)
- - FROM esr-thirdparty-sdnc
- - FROM generic-vnf
- - FROM logical-link
- - FROM service-instance
+ - TO complex( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO instance-group( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO zone( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM esr-thirdparty-sdnc( esr-thirdparty-sdnc has pnf, One2Many)
+ - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn pnf, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf pnf, ONE2MANY)
+ - PNF is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
required:
- pnf-name
- in-maint
@@ -45859,15 +65530,15 @@ definitions:
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
+ $ref: "#/getDefinitions/relationship"
p-interfaces:
type: array
items:
- $ref: "#/definitions/p-interface"
+ $ref: "#/getDefinitions/p-interface"
lag-interfaces:
type: array
items:
- $ref: "#/definitions/lag-interface"
+ $ref: "#/getDefinitions/lag-interface"
pnfs:
description: |
Collection of Physical Network Functions.
@@ -45875,189 +65546,377 @@ definitions:
pnf:
type: array
items:
- $ref: "#/definitions/pnf"
- physical-link:
+ $ref: "#/getDefinitions/pnf"
+ port-group:
description: |
- Collection of physical connections, typically between p-interfaces
+ Used to capture the network interfaces of this VCE
###### Related Nodes
- - FROM p-interface
+ - TO vce( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM cvlan-tag( cvlan-tag org.onap.relationships.inventory.BelongsTo port-group, MANY2ONE)
+ - PORT-GROUP is DELETED when these are DELETED CVLAN-TAG
required:
- - link-name
+ - interface-id
+ - orchestration-status
properties:
- link-name:
+ interface-id:
type: string
- description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
- speed-value:
+ description: Unique ID of the interface
+ neutron-network-id:
type: string
- description: Captures the numeric part of the speed
- speed-units:
+ description: Neutron network id of this Interface
+ neutron-network-name:
type: string
- description: Captures the units corresponding to the speed
- circuit-id:
+ description: Neutron network name of this Interface
+ interface-role:
type: string
- description: Circuit it
- dual-mode:
+ description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
+ resource-version:
type: string
- description: Dual access mode (e.g., primary, secondary
- management-option:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ port-group-id:
type: string
- description: To provide information on who manages this circuit. A&AI or 3rd party transport provider
- service-provider-name:
+ description: Unique ID for port group in vmware
+ port-group-name:
type: string
- description: Name of the service Provider on this link.
- service-provider-bandwidth-up-value:
- type: integer
- format: int32
- description: Upstream Bandwidth value agreed with the service provider
- service-provider-bandwidth-up-units:
+ description: Likely to duplicate value of neutron network name
+ switch-name:
type: string
- description: Units for the upstream BW value
- service-provider-bandwidth-down-value:
- type: integer
- format: int32
- description: Downstream Bandwidth value agreed with the service provider
- service-provider-bandwidth-down-units:
+ description: DVS or standard switch name (should be non-null for port groups associated with DVS)
+ orchestration-status:
type: string
- description: Units for downstream BW value
- resource-version:
+ description: Orchestration status of this VNF, mastered by MSO
+ heat-stack-id:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ cvlan-tags:
+ type: array
+ items:
+ $ref: "#/getDefinitions/cvlan-tag-entry"
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- physical-links:
- description: |
- Collection of physical connections, typically between p-interfaces
+ $ref: "#/getDefinitions/relationship"
+ port-groups:
properties:
- physical-link:
+ port-group:
type: array
items:
- $ref: "#/definitions/physical-link"
- vig-server:
+ $ref: "#/getDefinitions/port-group"
+ project:
description: |
- vig-server contains information about a vig server used for IPSec-configuration. Populated by SDN-C from 1607
+ describes the project
###### Related Nodes
- - FROM ipsec-configuration (is composed of vig-server)
+ - TO service-instance( project org.onap.relationships.inventory.Uses service-instance, ONE2MANY)
required:
- - vig-address-type
+ - project-name
properties:
- vig-address-type:
- type: string
- description: indicates whether the VIG is for AVPN or INTERNET
- ipaddress-v4-vig:
- type: string
- description: v4 IP of the vig server
- ipaddress-v6-vig:
+ project-name:
type: string
- description: v6 IP of the vig server
+ description: Name of the project deploying a service
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- vig-servers:
+ $ref: "#/getDefinitions/relationship"
+ projects:
+ description: |
+ Collection of projects
properties:
- vig-server:
+ project:
type: array
items:
- $ref: "#/definitions/vig-server"
- ipsec-configuration:
+ $ref: "#/getDefinitions/project"
+ properties:
description: |
- IPSec configuration node will contain various configuration data for the NMTE VNF. This node will have an edge to the generic-vnf (vnf type = TE). Starting 1607, this data will be populated by SDN-C
+ Property holder for query properties or instance properties
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ property-constraint:
+ description: |
+ TBD
###### Related Nodes
- - TO vig-server (comprises ipsec-configuration, One2Many)
- - FROM generic-vnf
+ - TO named-query-element( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
required:
- - ipsec-configuration-id
+ - property-constraint-uuid
+ - constraint-type
+ - property-name
+ - property-value
properties:
- ipsec-configuration-id:
+ property-constraint-uuid:
type: string
- description: UUID of this configuration
- requested-vig-address-type:
+ constraint-type:
type: string
- description: Indicate the type of VIG server like AVPN, INTERNET, BOTH
- requested-encryption-strength:
+ property-name:
type: string
- description: Encryption values like 3des-cbc, des-cbc, aes-128-cbc, aes-192-cbc, aes-265-cbc
- requested-dmz-type:
+ property-value:
type: string
- description: ATT can offer a shared DMZ or a DMZ specific to a customer
- shared-dmz-network-address:
+ resource-version:
type: string
- description: Network address of shared DMZ
- requested-customer-name:
+ property-constraints:
+ properties:
+ property-constraint:
+ type: array
+ items:
+ $ref: "#/getDefinitions/property-constraint"
+ pserver:
+ description: |
+ Compute host whose hostname must be unique and must exactly match what is sent as a relationship to a vserver.
+ ###### Related Nodes
+ - TO group-assignment( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)
+ - TO availability-zone( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)
+ - TO cloud-region( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)
+ - TO complex( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO zone( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - FROM vserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)
+ - PSERVER cannot be deleted if linked to GENERIC-VNF,LOGICAL-LINK,VSERVER
+ - PSERVER is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
+ - PSERVER cannot be deleted if linked to GROUP-ASSIGNMENT
+ required:
+ - hostname
+ - in-maint
+ properties:
+ hostname:
type: string
- description: If the DMZ is a custom DMZ, this field will indicate the customer information
- ike-version:
+ description: Value from executing hostname on the compute node.
+ ptnii-equip-name:
type: string
- description: can be 1 or 2
- ikev1-authentication:
+ description: PTNII name
+ number-of-cpus:
+ type: integer
+ format: int32
+ description: Number of cpus
+ disk-in-gigabytes:
+ type: integer
+ format: int32
+ description: Disk size, in GBs
+ ram-in-megabytes:
+ type: integer
+ format: int32
+ description: RAM size, in MBs
+ equip-type:
type: string
- description: Contains values like md5, sha1, sha256, sha384
- ikev1-encryption:
+ description: Equipment type. Source of truth should define valid values.
+ equip-vendor:
type: string
- description: Encyption values like 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
- ikev1-dh-group:
+ description: Equipment vendor. Source of truth should define valid values.
+ equip-model:
type: string
- description: Diffie-Hellman group like DH-GROUP2, DH-GROUP5, DH-GROUP14
- ikev1-am-group-id:
+ description: Equipment model. Source of truth should define valid values.
+ fqdn:
type: string
- description: Group name defined in VIG for clients using aggressive mode
- ikev1-am-password:
+ description: Fully-qualified domain name
+ pserver-selflink:
type: string
- description: pre-shared key for the above group name
- ikev1-sa-lifetime:
+ description: URL to endpoint where AAI can get more details
+ ipv4-oam-address:
type: string
- description: Lifetime for IKEv1 SA
- ipsec-authentication:
+ description: Used to configure device, also used for troubleshooting and is IP used for traps generated by device.
+ serial-number:
type: string
- description: md5, sha1, sha256, sha384
- ipsec-encryption:
+ description: Serial number, may be queried
+ ipaddress-v4-loopback-0:
type: string
- description: 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
- ipsec-sa-lifetime:
+ description: IPV4 Loopback 0 address
+ ipaddress-v6-loopback-0:
type: string
- description: Life time for IPSec SA
- ipsec-pfs:
+ description: IPV6 Loopback 0 address
+ ipaddress-v4-aim:
type: string
- description: enable PFS or not
- xauth-userid:
+ description: IPV4 AIM address
+ ipaddress-v6-aim:
type: string
- description: user ID for xAuth, sm-user,ucpeHostName,nmteHostName
- xauth-user-password:
+ description: IPV6 AIM address
+ ipaddress-v6-oam:
type: string
- description: Encrypted using the Juniper $9$ algorithm
- dpd-interval:
+ description: IPV6 OAM address
+ inv-status:
type: string
- description: The time between DPD probe
- dpd-frequency:
+ description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
+ pserver-id:
type: string
- description: Maximum number of DPD before claiming the tunnel is down
+ description: ID of Pserver
+ internet-topology:
+ type: string
+ description: internet topology of Pserver
+ in-maint:
+ type: boolean
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ pserver-name2:
+ type: string
+ description: alternative pserver name
+ purpose:
+ type: string
+ description: purpose of pserver
+ prov-status:
+ type: string
+ description: Prov Status of this device (not under canopi control) Valid values [PREPROV/NVTPROV/PROV]
+ management-option:
+ type: string
+ description: Indicates who owns and or manages the device.
+ host-profile:
+ type: string
+ description: The host profile that defines the configuration of the pserver.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- vig-servers:
+ $ref: "#/getDefinitions/relationship"
+ p-interfaces:
type: array
items:
- $ref: "#/definitions/vig-server"
- ipsec-configurations:
+ $ref: "#/getDefinitions/p-interface"
+ lag-interfaces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/lag-interface"
+ pservers:
+ description: |
+ Collection of compute hosts.
properties:
- ipsec-configuration:
+ pserver:
type: array
items:
- $ref: "#/definitions/ipsec-configuration"
+ $ref: "#/getDefinitions/pserver"
+ query-parameters:
+ description: |
+ QueryParameters for performing a named-query or model query
+ properties:
+ named-query:
+ type: object
+ $ref: "#/getDefinitions/named-query"
+ overloaded-model:
+ type: object
+ $ref: "#/getDefinitions/overloaded-model"
+ related-lookup:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query-element( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ required:
+ - related-lookup-uuid
+ - source-node-type
+ - source-node-property
+ - target-node-type
+ - target-node-property
+ properties:
+ related-lookup-uuid:
+ type: string
+ source-node-type:
+ type: string
+ source-node-property:
+ type: string
+ target-node-type:
+ type: string
+ target-node-property:
+ type: string
+ property-collect-list:
+ type: string
+ resource-version:
+ type: string
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ related-lookups:
+ properties:
+ related-lookup:
+ type: array
+ items:
+ $ref: "#/getDefinitions/related-lookup"
+ related-to-property:
+ properties:
+ property-key:
+ type: string
+ description: Key part of a key/value pair
+ property-value:
+ type: string
+ description: Value part of a key/value pair
+ relationship:
+ properties:
+ related-to:
+ type: string
+ description: A keyword provided by A&AI to indicate type of node.
+ related-link:
+ type: string
+ description: URL to the object in A&AI.
+ relationship-data:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship-data"
+ related-to-property:
+ type: array
+ items:
+ $ref: "#/getDefinitions/related-to-property"
+ relationship-data:
+ required:
+ - relationship-key
+ - relationship-value
+ properties:
+ relationship-key:
+ type: string
+ description: A keyword provided by A&AI to indicate an attribute.
+ relationship-value:
+ type: string
+ description: Value of the attribute.
+ relationship-list:
+ properties:
+ relationship:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ reserved-prop-names:
+ description: |
+ Internal map to define some reserved properties of a vertex
+ properties:
+ last-mod-source-of-truth:
+ type: string
+ aai-node-type:
+ type: string
+ aai-created-ts:
+ type: integer
+ format: int64
+ aai-unique-key:
+ type: string
+ aai-last-mod-ts:
+ type: integer
+ format: int64
+ source-of-truth:
+ type: string
+ aai-uri:
+ type: string
+ response-list:
+ description: |
+ Response container for the results of a named-query or model query
+ properties:
+ inventory-response-items:
+ type: object
+ $ref: "#/getDefinitions/inventory-response-items"
+ result-data:
+ properties:
+ resource-type:
+ type: string
+ description: The specific type of node in the A&AI graph
+ resource-link:
+ type: string
+ description: The URL to the specific resource
route-table-reference:
description: |
Openstack route table reference.
###### Related Nodes
- - FROM l3-network
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)
required:
- route-table-reference-id
- route-table-reference-fqdn
@@ -46074,7 +65933,7 @@ definitions:
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
+ $ref: "#/getDefinitions/relationship"
route-table-references:
description: |
Collection of openstack route table references
@@ -46082,319 +65941,790 @@ definitions:
route-table-reference:
type: array
items:
- $ref: "#/definitions/route-table-reference"
- instance-group:
+ $ref: "#/getDefinitions/route-table-reference"
+ route-target:
description: |
- General mechanism for grouping instances
+ Route target information
###### Related Nodes
- - TO model (Many2Many)
- - FROM l-interface
- - FROM vnfc
- - FROM l3-interface-ipv4-address-list
- - FROM l3-interface-ipv6-address-list
- - FROM l3-network
- - FROM pnf
- - FROM allotted-resource
- - FROM generic-vnf
- - FROM service-instance
- - FROM vip-ipv4-address-list
- - FROM vip-ipv6-address-list
+ - TO vpn-binding( route-target org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2ONE)
required:
- - instance-group-role
- - model-invariant-id
- - model-version-id
- - id
- - description
- - type
+ - global-route-target
+ - route-target-role
properties:
- instance-group-role:
- type: string
- description: role of the instance group.
- model-invariant-id:
- type: string
- description: ASDC model id for this resource or service model.
- model-version-id:
+ global-route-target:
type: string
- description: ASDC model version uid for this resource model.
- id:
+ description: Number used to identify an RT, globally unique in the network
+ route-target-role:
type: string
- description: Instance Group ID, UUID assigned to this instance.
- description:
+ description: Role assigned to this route target
+ resource-version:
type: string
- description: Descriptive text to help identify the usage of this instance-group
- type:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ route-targets:
+ description: |
+ Collection of route target information
+ properties:
+ route-target:
+ type: array
+ items:
+ $ref: "#/getDefinitions/route-target"
+ routing-instance:
+ description: |
+ ###### Related Nodes
+ - TO site-pair-set( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)
+ - FROM site-pair( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)
+ - ROUTING-INSTANCE is DELETED when these are DELETED SITE-PAIR
+ required:
+ - routing-instance-id
+ properties:
+ routing-instance-id:
type: string
- description: Only valid value today is lower case ha for high availability
- sub-type:
+ description: Unique id of routing instance
+ rpm-owner:
type: string
- description: Valid values for ha type are [geo-activeactive, geo-activestandby, local-activeactive, local-activestandby]
+ description: rpm owner
resource-version:
type: string
- description: Concurrency value
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ site-pairs:
+ type: array
+ items:
+ $ref: "#/getDefinitions/site-pair"
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- instance-groups:
+ $ref: "#/getDefinitions/relationship"
+ routing-instances:
description: |
- Collection of openstack route table references
+ set of probes related to generic-vnf routing instance
properties:
- instance-group:
+ routing-instance:
type: array
items:
- $ref: "#/definitions/instance-group"
- zone:
+ $ref: "#/getDefinitions/routing-instance"
+ sdn-zone-response:
+ properties:
+ oam-networks:
+ type: object
+ $ref: "#/getDefinitions/oam-networks"
+ az-and-dvs-switches:
+ type: array
+ items:
+ $ref: "#/getDefinitions/az-and-dvs-switches"
+ search:
+ properties:
+ edge-tag-query-result:
+ type: object
+ $ref: "#/getDefinitions/edge-tag-query-result"
+ edge-tag-query-request:
+ type: object
+ $ref: "#/getDefinitions/edge-tag-query-request"
+ search-results:
+ type: object
+ $ref: "#/getDefinitions/search-results"
+ sdn-zone-response:
+ type: object
+ $ref: "#/getDefinitions/sdn-zone-response"
+ search-results:
+ properties:
+ result-data:
+ type: array
+ items:
+ $ref: "#/getDefinitions/result-data"
+ secondary-filt:
description: |
- A zone is a grouping of assets in a location homing to the same connections into the CBB
+ SecondaryFilt for performing a named-query or model query
+ secondary-filter:
+ properties:
+ property-name:
+ type: string
+ filter-type:
+ type: string
+ property-value:
+ type: string
+ secondary-filts:
+ description: |
+ SecondaryFilts for performing a named-query or model query
+ properties:
+ secondary-filt:
+ type: array
+ items:
+ $ref: "#/getDefinitions/secondary-filt"
+ segmentation-assignment:
+ description: |
+ Openstack segmentation assignment.
###### Related Nodes
- - TO complex (Many2One)
- - FROM cloud-region
- - FROM pserver
- - FROM pnf
- - FROM service-instance
+ - TO l3-network( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
required:
- - zone-id
- - zone-name
- - design-type
- - zone-context
+ - segmentation-id
properties:
- zone-id:
+ segmentation-id:
type: string
- description: Code assigned by AIC to the zone
- zone-name:
+ description: Route Table Reference id, UUID assigned to this instance.
+ resource-version:
type: string
- description: English name associated with the zone
- design-type:
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ segmentation-assignments:
+ description: |
+ Collection of openstack segmentation assignments
+ properties:
+ segmentation-assignment:
+ type: array
+ items:
+ $ref: "#/getDefinitions/segmentation-assignment"
+ service:
+ description: |
+ Stand-in for service model definitions. Likely to be deprecated in favor of models from ASDC. Does not strictly map to ASDC services.
+ required:
+ - service-id
+ - service-description
+ properties:
+ service-id:
type: string
- description: Design of zone [Medium/Large?]
- zone-context:
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ service-description:
type: string
- description: Context of zone [production/test]
- status:
+ description: Description of the service
+ service-selflink:
type: string
- description: Status of a zone.
+ description: URL to endpoint where AAI can get more details
resource-version:
type: string
- description: Concurrency value
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ service-version:
+ type: string
+ description: service version
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- zones:
+ $ref: "#/getDefinitions/relationship"
+ service-capabilities:
description: |
- Collection of zones
+ Collection of service capabilities.
properties:
- zone:
+ service-capability:
type: array
items:
- $ref: "#/definitions/zone"
- network:
+ $ref: "#/getDefinitions/service-capability"
+ service-capability:
description: |
- Namespace for network inventory resources.
+ Early definition of server/resource pairings, likely to be replaced by models. No new use should be made of this.
+ ###### Related Nodes
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - SERVICE-CAPABILITY cannot be deleted if linked to AVAILABILITY-ZONE,OAM-NETWORK
+ required:
+ - service-type
+ - vnf-type
properties:
- logical-links:
+ service-type:
+ type: string
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/logical-link"
- site-pair-sets:
+ $ref: "#/getDefinitions/relationship"
+ service-design-and-creation:
+ description: |
+ Namespace for objects managed by ASDC
+ properties:
+ vnf-images:
type: array
items:
- $ref: "#/definitions/site-pair-set"
- vpn-bindings:
+ $ref: "#/getDefinitions/vnf-image"
+ services:
type: array
items:
- $ref: "#/definitions/vpn-binding"
- vpls-pes:
+ $ref: "#/getDefinitions/service"
+ service-capabilities:
type: array
items:
- $ref: "#/definitions/vpls-pe"
- multicast-configurations:
+ $ref: "#/getDefinitions/service-capability"
+ models:
type: array
items:
- $ref: "#/definitions/multicast-configuration"
- vces:
+ $ref: "#/getDefinitions/model"
+ named-queries:
type: array
items:
- $ref: "#/definitions/vce"
- vnfcs:
+ $ref: "#/getDefinitions/named-query"
+ service-instance:
+ description: |
+ Instance of a service
+ ###### Related Nodes
+ - TO generic-vnf( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)
+ - TO l3-network( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)
+ - TO owning-entity( service-instance org.onap.relationships.inventory.BelongsTo owning-entity, MANY2ONE)
+ - TO allotted-resource( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY)
+ - TO configuration( service-instance org.onap.relationships.inventory.Uses configuration, ONE2MANY)
+ - TO connector( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)
+ - TO ctag-assignment( service-instance org.onap.relationships.inventory.Uses ctag-assignment, ONE2MANY)
+ - TO cvlan-tag( service-instance org.onap.relationships.inventory.ComposedOf cvlan-tag, MANY2MANY)
+ - TO instance-group( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO logical-link( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - TO pnf( service-instance org.onap.relationships.inventory.ComposedOf pnf, ONE2MANY)
+ - TO service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)
+ - TO vlan( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)
+ - TO zone( service-instance org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - TO service-subscription( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)
+ - TO vce( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)
+ - FROM project( project org.onap.relationships.inventory.Uses service-instance, ONE2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)
+ - SERVICE-INSTANCE is DELETED when these are DELETED ALLOTTED-RESOURCE,METADATUM
+ - SERVICE-INSTANCE deletion means associated objects of these types are also DELETED:LOGICAL-LINK
+ required:
+ - service-instance-id
+ - service-type
+ - service-role
+ - created-at
+ - updated-at
+ - description
+ properties:
+ service-instance-id:
+ type: string
+ description: Uniquely identifies this instance of a service
+ service-instance-name:
+ type: string
+ description: This field will store a name assigned to the service-instance.
+ service-type:
+ type: string
+ description: String capturing type of service.
+ service-role:
+ type: string
+ description: String capturing the service role.
+ environment-context:
+ type: string
+ description: This field will store the environment context assigned to the service-instance.
+ workload-context:
+ type: string
+ description: This field will store the workload context assigned to the service-instance.
+ created-at:
+ type: string
+ description: create time of Network Service.
+ updated-at:
+ type: string
+ description: last update of Network Service.
+ description:
+ type: string
+ description: short description for service-instance.
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ bandwidth-total:
+ type: string
+ description: Indicates the total bandwidth to be used for this service.
+ bandwidth-up-wan1:
+ type: string
+ description: indicates the upstream bandwidth this service will use on the WAN1 port of the physical device.
+ bandwidth-down-wan1:
+ type: string
+ description: indicates the downstream bandwidth this service will use on the WAN1 port of the physical device.
+ bandwidth-up-wan2:
+ type: string
+ description: indicates the upstream bandwidth this service will use on the WAN2 port of the physical device.
+ bandwidth-down-wan2:
+ type: string
+ description: indicates the downstream bandwidth this service will use on the WAN2 port of the physical device.
+ vhn-portal-url:
+ type: string
+ description: URL customers will use to access the vHN Portal.
+ service-instance-location-id:
+ type: string
+ description: An identifier that customers assign to the location where this service is being used.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ selflink:
+ type: string
+ description: Path to the controller object.
+ orchestration-status:
+ type: string
+ description: Orchestration status of this service.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/vnfc"
- l3-networks:
+ $ref: "#/getDefinitions/relationship"
+ metadata:
type: array
items:
- $ref: "#/definitions/l3-network"
- network-policies:
+ $ref: "#/getDefinitions/metadatum"
+ allotted-resources:
type: array
items:
- $ref: "#/definitions/network-policy"
- generic-vnfs:
+ $ref: "#/getDefinitions/allotted-resource"
+ service-instances:
+ description: |
+ Collection of service instances
+ properties:
+ service-instance:
type: array
- items:
- $ref: "#/definitions/generic-vnf"
- lag-links:
+ items:
+ $ref: "#/getDefinitions/service-instance"
+ service-subscription:
+ description: |
+ Object that group service instances.
+ ###### Related Nodes
+ - TO customer( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)
+ - TO tenant( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)
+ - SERVICE-SUBSCRIPTION is DELETED when these are DELETED SERVICE-INSTANCE
+ required:
+ - service-type
+ properties:
+ service-type:
+ type: string
+ description: Value defined by orchestration to identify this service across ECOMP.
+ temp-ub-sub-account-id:
+ type: string
+ description: This property will be deleted from A&AI in the near future. Only stop gap solution.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ service-instances:
type: array
items:
- $ref: "#/definitions/lag-link"
- newvces:
+ $ref: "#/getDefinitions/service-instance"
+ relationship-list:
type: array
items:
- $ref: "#/definitions/newvce"
- pnfs:
+ $ref: "#/getDefinitions/relationship"
+ service-subscriptions:
+ description: |
+ Collection of objects that group service instances.
+ properties:
+ service-subscription:
type: array
- items:
- $ref: "#/definitions/pnf"
- physical-links:
+ items:
+ $ref: "#/getDefinitions/service-subscription"
+ services:
+ description: |
+ Collection of service model definitions. Likely to be deprecated in favor of models from ASDC.
+ properties:
+ service:
type: array
- items:
- $ref: "#/definitions/physical-link"
- ipsec-configurations:
+ items:
+ $ref: "#/getDefinitions/service"
+ site-pair:
+ description: |
+ ###### Related Nodes
+ - TO routing-instance( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)
+ - FROM class-of-service( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)
+ - SITE-PAIR is DELETED when these are DELETED CLASS-OF-SERVICE
+ required:
+ - site-pair-id
+ properties:
+ site-pair-id:
+ type: string
+ description: unique identifier of probe
+ source-ip:
+ type: string
+ description: Prefix address
+ destination-ip:
+ type: string
+ description: Prefix address
+ ip-version:
+ type: string
+ description: ip version, v4, v6
+ destination-hostname:
+ type: string
+ description: Hostname of the destination equipment to which SLAs are measured against.
+ destination-equip-type:
+ type: string
+ description: The type of destinatination equipment. Could be Router, UCPE, etc.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ classes-of-service:
type: array
items:
- $ref: "#/definitions/ipsec-configuration"
- route-table-references:
+ $ref: "#/getDefinitions/class-of-service"
+ relationship-list:
type: array
items:
- $ref: "#/definitions/route-table-reference"
- instance-groups:
+ $ref: "#/getDefinitions/relationship"
+ site-pair-set:
+ description: |
+ Set of instances for probes used to measure service level agreements
+ ###### Related Nodes
+ - TO generic-vnf( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM routing-instance( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)
+ - SITE-PAIR-SET is DELETED when these are DELETED ROUTING-INSTANCE
+ required:
+ - site-pair-set-id
+ properties:
+ site-pair-set-id:
+ type: string
+ description: Unique id of site pair set.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ routing-instances:
type: array
items:
- $ref: "#/definitions/instance-group"
- zones:
+ $ref: "#/getDefinitions/routing-instance"
+ relationship-list:
type: array
items:
- $ref: "#/definitions/zone"
- inventory:
+ $ref: "#/getDefinitions/relationship"
+ site-pair-sets:
+ description: |
+ Collection of sets of instances for probes related to generic-vnf
properties:
- search:
- type: object
- $ref: "#/definitions/search"
- actions:
- type: object
- $ref: "#/definitions/actions"
- cloud-infrastructure:
- type: object
- $ref: "#/definitions/cloud-infrastructure"
- external-system:
- type: object
- $ref: "#/definitions/external-system"
- business:
- type: object
- $ref: "#/definitions/business"
- service-design-and-creation:
- type: object
- $ref: "#/definitions/service-design-and-creation"
- network:
- type: object
- $ref: "#/definitions/network"
- aai-internal:
- type: object
- $ref: "#/definitions/aai-internal"
- nodes:
+ site-pair-set:
type: array
- items:
- $ref: "#/definitions/"
- edge-tag-query-result:
+ items:
+ $ref: "#/getDefinitions/site-pair-set"
+ site-pairs:
+ description: |
+ probe within a set
properties:
- tagged-inventory-item-list:
+ site-pair:
type: array
items:
- $ref: "#/definitions/tagged-inventory-item-list"
- tagged-inventory-item-list:
+ $ref: "#/getDefinitions/site-pair"
+ snapshot:
+ description: |
+ Openstack snapshot
+ ###### Related Nodes
+ - TO cloud-region( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)
+ required:
+ - snapshot-id
properties:
- inventory-item:
+ snapshot-id:
+ type: string
+ description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
+ snapshot-name:
+ type: string
+ description: Snapshot name
+ snapshot-architecture:
+ type: string
+ description: Operating system architecture
+ snapshot-os-distro:
+ type: string
+ description: The common name of the operating system distribution in lowercase
+ snapshot-os-version:
+ type: string
+ description: The operating system version as specified by the distributor.
+ application:
+ type: string
+ description: The application that the image instantiates.
+ application-vendor:
+ type: string
+ description: The vendor of the application.
+ application-version:
+ type: string
+ description: The version of the application.
+ snapshot-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ prev-snapshot-id:
+ type: string
+ description: This field contains the UUID of the previous snapshot (if any).
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ snapshots:
+ description: |
+ Collection of openstack snapshots
+ properties:
+ snapshot:
type: array
items:
- $ref: "#/definitions/inventory-item"
- inventory-item:
+ $ref: "#/getDefinitions/snapshot"
+ sriov-pf:
+ description: |
+ SR-IOV Physical Function
+ ###### Related Nodes
+ - TO p-interface( sriov-pf org.onap.relationships.inventory.BelongsTo p-interface, ONE2ONE)
+ - FROM sriov-vf( sriov-vf org.onap.relationships.inventory.Uses sriov-pf, MANY2ONE)
+ required:
+ - pf-pci-id
properties:
- inventory-item-type:
+ pf-pci-id:
type: string
- inventory-item-link:
+ description: Identifier for the sriov-pf
+ resource-version:
type: string
- inventory-item-data:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
- items:
- $ref: "#/definitions/inventory-item-data"
- tagged-inventory-item-list:
+ items:
+ $ref: "#/getDefinitions/relationship"
+ sriov-pfs:
+ description: |
+ Collection of SR-IOV Physical Functions.
+ properties:
+ sriov-pf:
type: array
items:
- $ref: "#/definitions/tagged-inventory-item-list"
- inventory-item-data:
+ $ref: "#/getDefinitions/sriov-pf"
+ sriov-vf:
+ description: |
+ SR-IOV Virtual Function (not to be confused with virtual network function)
+ ###### Related Nodes
+ - TO l-interface( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)
+ - TO sriov-pf( sriov-vf org.onap.relationships.inventory.Uses sriov-pf, MANY2ONE)
+ required:
+ - pci-id
properties:
- property-name:
+ pci-id:
type: string
- property-value:
+ description: PCI ID used to identify the sriov-vf
+ vf-vlan-filter:
type: string
- edge-tag-query-request:
- properties:
- edge-tag:
+ description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM.
+ vf-mac-filter:
type: string
- result-detail:
+ description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM.
+ vf-vlan-strip:
+ type: boolean
+ description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM.
+ vf-vlan-anti-spoof-check:
+ type: boolean
+ description: This option ensures anti VLAN spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
+ vf-mac-anti-spoof-check:
+ type: boolean
+ description: This option ensures anti MAC spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
+ vf-mirrors:
type: string
- start-node-type:
+ description: This option defines the set of Mirror objects which essentially mirrors the traffic from source to set of collector VNF Ports.
+ vf-broadcast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows all broadcast traffic to reach the VM
+ vf-unknown-multicast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows unknown multicast traffic to reach the VM
+ vf-unknown-unicast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows unknown unicast traffic to reach the VM
+ vf-insert-stag:
+ type: boolean
+ description: This option, if set to true, instructs to insert outer tag after traffic comes out of VM.
+ vf-link-status:
type: string
- start-node-filter:
- type: array
- items:
- $ref: "#/definitions/start-node-filter"
- include-node-filter:
+ description: This option is used to set the link status. Valid values as of 1607 are on, off, and auto.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
+ type: string
+ description: Neutron network id of the interface
+ relationship-list:
type: array
- items:
- $ref: "#/definitions/include-node-filter"
- secondary-filter:
+ items:
+ $ref: "#/getDefinitions/relationship"
+ sriov-vfs:
+ description: |
+ Collection of SR-IOV Virtual Functions.
+ properties:
+ sriov-vf:
type: array
items:
- $ref: "#/definitions/secondary-filter"
+ $ref: "#/getDefinitions/sriov-vf"
start-node-filter:
properties:
property-name:
type: string
property-value:
type: string
- include-node-filter:
+ subnet:
+ description: |
+ ###### Related Nodes
+ - TO l3-network( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - FROM host-route( host-route org.onap.relationships.inventory.BelongsTo subnet, MANY2ONE)
+ - FROM vip-ipv4-address-list( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)
+ - FROM vip-ipv6-address-list( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)
+ - SUBNET cannot be deleted if linked to L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST,VIP-IPV4-ADDRESS-LIST,VIP-IPV6-ADDRESS-LIST
+ - SUBNET is DELETED when these are DELETED HOST-ROUTE
+ required:
+ - subnet-id
+ - dhcp-enabled
properties:
- include-node-type:
+ subnet-id:
type: string
- secondary-filter:
- properties:
- property-name:
+ description: Subnet ID, should be UUID.
+ subnet-name:
type: string
- filter-type:
+ description: Name associated with the subnet.
+ neutron-subnet-id:
type: string
- property-value:
+ description: Neutron id of this subnet
+ gateway-address:
type: string
- search-results:
+ description: gateway ip address
+ network-start-address:
+ type: string
+ description: network start address
+ cidr-mask:
+ type: string
+ description: cidr mask
+ ip-version:
+ type: string
+ description: ip version
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ dhcp-enabled:
+ type: boolean
+ dhcp-start:
+ type: string
+ description: the start address reserved for use by dhcp
+ dhcp-end:
+ type: string
+ description: the last address reserved for use by dhcp
+ subnet-role:
+ type: string
+ description: role of the subnet, referenced when assigning IPs
+ ip-assignment-direction:
+ type: string
+ description: ip address assignment direction of the subnet
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ subnet-sequence:
+ type: integer
+ format: int32
+ description: sequence of the subnet
+ host-routes:
+ type: array
+ items:
+ $ref: "#/getDefinitions/host-route"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ subnets:
properties:
- result-data:
+ subnet:
type: array
items:
- $ref: "#/definitions/result-data"
- result-data:
+ $ref: "#/getDefinitions/subnet"
+ tagged-inventory-item-list:
properties:
- resource-type:
+ inventory-item:
+ type: array
+ items:
+ $ref: "#/getDefinitions/inventory-item"
+ tenant:
+ description: |
+ Openstack tenant
+ ###### Related Nodes
+ - TO cloud-region( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO group-assignment( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)
+ - TO l3-network( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO volume-group( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - FROM service-subscription( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)
+ - FROM vserver( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)
+ - TENANT cannot be deleted if linked to VSERVER
+ required:
+ - tenant-id
+ - tenant-name
+ properties:
+ tenant-id:
type: string
- description: The specific type of node in the A&AI graph
- resource-link:
+ description: Unique id relative to the cloud-region.
+ tenant-name:
type: string
- description: The URL to the specific resource
- sdn-zone-response:
+ description: Readable name of tenant
+ tenant-context:
+ type: string
+ description: This field will store the tenant context.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ vservers:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vserver"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ tenants:
+ description: |
+ Collection of openstack tenants.
properties:
- oam-networks:
- type: object
- $ref: "#/definitions/oam-networks"
- az-and-dvs-switches:
+ tenant:
type: array
items:
- $ref: "#/definitions/az-and-dvs-switches"
- az-and-dvs-switches:
+ $ref: "#/getDefinitions/tenant"
+ tunnel-xconnect:
+ description: |
+ Represents the specifics of a tunnel cross connect piece of a resource that gets separately allotted
+ ###### Related Nodes
+ - TO allotted-resource( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)
+ required:
+ - id
+ - bandwidth-up-wan1
+ - bandwidth-down-wan1
+ - bandwidth-up-wan2
+ - bandwidth-down-wan2
properties:
- dvs-switches:
- type: object
- $ref: "#/definitions/dvs-switches"
- availability-zone:
- type: object
- $ref: "#/definitions/availability-zone"
+ id:
+ type: string
+ description: Allotted Resource id UUID assigned to this instance.
+ bandwidth-up-wan1:
+ type: string
+ description: The WAN uplink bandwidth for WAN1
+ bandwidth-down-wan1:
+ type: string
+ description: The WAN downlink bandwidth for WAN1
+ bandwidth-up-wan2:
+ type: string
+ description: The WAN uplink bandwidth for WAN2
+ bandwidth-down-wan2:
+ type: string
+ description: The WAN downlink bandwidth for WAN2
+ resource-version:
+ type: string
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ tunnel-xconnects:
+ description: |
+ This object is used to store the specific tunnel cross connect aspects of an allotted resource
+ properties:
+ tunnel-xconnect:
+ type: array
+ items:
+ $ref: "#/getDefinitions/tunnel-xconnect"
update:
description: |
Serves a PATCH like function. Does not enforce concurrency control. Clear each usage with AAI team.
@@ -46406,341 +66736,823 @@ definitions:
update-node-key:
type: array
items:
- $ref: "#/definitions/update-node-key"
+ $ref: "#/getDefinitions/update-node-key"
update-node-uri:
type: string
action:
type: array
items:
- $ref: "#/definitions/action"
- action:
- properties:
- action-type:
- type: string
- action-data:
- type: array
- items:
- $ref: "#/definitions/action-data"
- action-data:
- properties:
- property-name:
- type: string
- property-value:
- type: string
+ $ref: "#/getDefinitions/action"
update-node-key:
properties:
key-name:
type: string
key-value:
type: string
- notify:
+ vce:
+ description: |
+ Virtual Customer Edge Router, used specifically for Gamma. This object is deprecated.
+ ###### Related Nodes
+ - TO availability-zone( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - TO complex( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)
+ - TO vserver( vce tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM entitlement( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM license( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM port-group( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)
+ - VCE is DELETED when these are DELETED ENTITLEMENT,LICENSE,PORT-GROUP
required:
- - event-id
+ - vnf-id
+ - vnf-name
+ - vnf-type
properties:
- event-id:
+ vnf-id:
type: string
- node-type:
+ description: Unique id of VNF. This is unique across the graph.
+ vnf-name:
type: string
- event-trigger:
+ description: Name of VNF.
+ vnf-name2:
type: string
- key-data:
- type: array
- items:
- $ref: "#/definitions/key-data"
- selflink:
+ description: Alternate name of VNF.
+ vnf-type:
type: string
- key-data:
- properties:
- key-name:
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ service-id:
type: string
- key-value:
+ description: Unique identifier of service, does not strictly map to ASDC services, SOON TO BE DEPRECATED.
+ regional-resource-zone:
type: string
- configurations:
+ description: Regional way of organizing pservers, source of truth should define values
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ operational-status:
+ type: string
+ description: Indicator for whether the resource is considered operational
+ license-key:
+ type: string
+ description: OBSOLETE - do not use
+ equipment-role:
+ type: string
+ description: Network role being played by this VNF
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ vpe-id:
+ type: string
+ description: Unique ID of VPE connected to this VCE.
+ v6-vce-wan-address:
+ type: string
+ description: Valid v6 IP address for the WAN Link on this router. Implied length of /64.
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure vce, also used for troubleshooting and is IP used for traps generated by VCE.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ ipv4-loopback0-address:
+ type: string
+ description: Loopback0 address
+ entitlement-resource-uuid:
+ type: string
+ description: OBSOLETE - see child relationships
+ port-groups:
+ type: array
+ items:
+ $ref: "#/getDefinitions/port-group"
+ licenses:
+ type: array
+ items:
+ $ref: "#/getDefinitions/license"
+ entitlements:
+ type: array
+ items:
+ $ref: "#/getDefinitions/entitlement"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ vces:
description: |
- Collection of configurations
+ Collection of Virtual Customer Edge Routers, used specifically for Gamma. This object is deprecated.
properties:
- configuration:
+ vce:
type: array
items:
- $ref: "#/definitions/configuration"
- configuration:
+ $ref: "#/getDefinitions/vce"
+ vf-module:
description: |
- Port Mirror Configuration.
+ a deployment unit of VNFCs
###### Related Nodes
- - TO logical-link (One2Many)
- - TO metadatum (comprises configuration, One2Many)
- - TO allotted-resource (One2One)
- - FROM service-instance
- - FROM generic-vnf
+ - TO generic-vnf( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO l3-network( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)
+ - TO vnfc( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)
+ - TO volume-group( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)
+ - TO vserver( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)
+ - VF-MODULE cannot be deleted if linked to VNFC
required:
- - configuration-id
- - configuration-type
- - configuration-sub-type
- - orchestration-status
- - operational-status
- - configuration-selflink
- - model-customization-id
+ - vf-module-id
+ - is-base-vf-module
properties:
- management-option:
+ vf-module-id:
type: string
- description: Indicates the entity that will manage this feature. Could be an organization or the name of the application as well.
- configuration-id:
+ description: Unique ID of vf-module.
+ vf-module-name:
type: string
- description: UUID assigned to configuration.
- configuration-name:
+ description: Name of vf-module
+ heat-stack-id:
type: string
- description: Name of the configuration.
- configuration-type:
+ description: Heat stack id corresponding to this instance.
+ orchestration-status:
type: string
- description: port-mirroring-configuration.
- configuration-sub-type:
+ description: orchestration status of this vf-module, mastered by MSO
+ is-base-vf-module:
+ type: boolean
+ resource-version:
type: string
- description: vprobe, pprobe.
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
model-invariant-id:
type: string
description: the ASDC model id for this resource or service model.
model-version-id:
type: string
description: the ASDC model version for this resource or service model.
- orchestration-status:
+ persona-model-version:
type: string
- description: Orchestration status of the configuration.
- operational-status:
+ description: the ASDC model version for this resource or service model.
+ model-customization-id:
type: string
- description: Indicator for whether the resource is considered operational.
- configuration-selflink:
+ description: captures the id of all the configuration used to customize the resource for the service.
+ widget-model-id:
type: string
- description: URL to endpoint where AAI can get more details from SDN-GC.
- model-customization-id:
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
type: string
- description: id of the configuration used to customize the resource
- resource-version:
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ contrail-service-instance-fqdn:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ description: the Contrail unique ID for a service-instance
+ module-index:
+ type: integer
+ format: int32
+ description: the index will track the number of modules of a given type that have been deployed in a VNF, starting with 0, and always choosing the lowest available digit
+ selflink:
+ type: string
+ description: Path to the controller object.
relationship-list:
- type: object
- $ref: "#/definitions/relationship-list"
- metadata:
- type: object
- $ref: "#/definitions/metadata"
- notification-event:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ vf-modules:
+ description: |
+ Collection of vf-modules, a deployment unit of VNFCs
properties:
- cambria.partition:
- type: string
- notification-event-header:
- type: object
- $ref: "#/definitions/notification-event-header"
- notification-event-header:
+ vf-module:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vf-module"
+ vig-server:
+ description: |
+ vig-server contains information about a vig server used for IPSec-configuration. Populated by SDN-C from 1607
+ ###### Related Nodes
+ - TO ipsec-configuration( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)
+ required:
+ - vig-address-type
properties:
- id:
- type: string
- timestamp:
+ vig-address-type:
type: string
- source-name:
+ description: indicates whether the VIG is for AVPN or INTERNET
+ ipaddress-v4-vig:
type: string
- domain:
+ description: v4 IP of the vig server
+ ipaddress-v6-vig:
type: string
- sequence-number:
+ description: v6 IP of the vig server
+ resource-version:
type: string
- severity:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ vig-servers:
+ properties:
+ vig-server:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vig-server"
+ vip-ipv4-address-list:
+ description: |
+ IPv4 Address Range
+ ###### Related Nodes
+ - TO cloud-region( vip-ipv4-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO instance-group( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO subnet( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv4-address-list, MANY2MANY)
+ required:
+ - vip-ipv4-address
+ properties:
+ vip-ipv4-address:
type: string
- event-type:
+ description: IP address
+ vip-ipv4-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 32 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ resource-version:
type: string
- version:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
type: string
- action:
+ description: Neutron network id of the interface that address belongs to
+ neutron-subnet-id:
type: string
- entity-type:
+ description: Neutron id of subnet that address belongs to
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ vip-ipv6-address-list:
+ description: |
+ IPv6 Address Range
+ ###### Related Nodes
+ - TO cloud-region( vip-ipv6-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO instance-group( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO subnet( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv6-address-list, MANY2MANY)
+ required:
+ - vip-ipv6-address
+ properties:
+ vip-ipv6-address:
type: string
- top-entity-type:
+ description: IP address
+ vip-ipv6-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 128 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ resource-version:
type: string
- entity-link:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
type: string
- status:
+ description: Neutron network id of the interface that address belongs to
+ neutron-subnet-id:
type: string
- reserved-prop-names:
+ description: Neutron id of subnet that address belongs to
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ virtual-data-center:
description: |
- Internal map to define some reserved properties of a vertex
+ Virtual organization of cloud infrastructure elements in a data center context
+ ###### Related Nodes
+ - FROM connector( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ required:
+ - vdc-id
+ - vdc-name
properties:
- last-mod-source-of-truth:
+ vdc-id:
type: string
- aai-node-type:
+ description: Unique ID of the vdc
+ vdc-name:
type: string
- aai-created-ts:
+ description: Name of the virtual data center
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ virtual-data-centers:
+ description: |
+ Virtual organization of cloud infrastructure elements in a data center context
+ properties:
+ virtual-data-center:
+ type: array
+ items:
+ $ref: "#/getDefinitions/virtual-data-center"
+ vlan:
+ description: |
+ Definition of vlan
+ ###### Related Nodes
+ - TO l-interface( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)
+ - TO logical-link( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - TO multicast-configuration( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ - VLAN is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST
+ - VLAN deletion means associated objects of these types are also DELETED:LOGICAL-LINK
+ required:
+ - vlan-interface
+ - in-maint
+ - is-ip-unnumbered
+ properties:
+ vlan-interface:
+ type: string
+ description: String that identifies the interface
+ vlan-id-inner:
type: integer
format: int64
- aai-unique-key:
- type: string
- aai-last-mod-ts:
+ description: Inner VLAN tag
+ vlan-id-outer:
type: integer
format: int64
- source-of-truth:
+ description: Outer VLAN tag
+ resource-version:
type: string
- aai-uri:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ speed-value:
type: string
- edge-prop-names:
- description: |
- Internal map to define the properties of an edge and interpret the map EdgeRules
- properties:
- edgeLabel:
+ description: Captures the numeric part of the speed
+ speed-units:
type: string
- direction:
+ description: Captures the units corresponding to the speed
+ vlan-description:
type: string
- multiplicityRule:
+ description: Used to describe (the service associated with) the vlan
+ backdoor-connection:
type: string
- contains-other-v:
+ description: Whether customer is going to use this VLAN for backdoor connection to another customer premise device.
+ vpn-key:
type: string
- delete-other-v:
+ description: This indicates the customers VPN ID associated with this vlan
+ orchestration-status:
type: string
- SVC-INFRA:
+ description: Status of a vnf's vlan interface, on which the customer circuit resides, mastered by SDN-C.
+ in-maint:
+ type: boolean
+ prov-status:
type: string
- prevent-delete:
+ description: Prov Status of the VLAN configuration related to a logical interface. Valid values [PREPROV/NVTPROV/PROV].
+ is-ip-unnumbered:
+ type: boolean
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ l3-interface-ipv4-address-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
+ l3-interface-ipv6-address-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
+ vlans:
+ properties:
+ vlan:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vlan"
+ vnf:
+ description: |
+ Abstract vnf class
+ required:
+ - vnf-id
+ properties:
+ vnf-id:
type: string
- model-and-named-query-search:
+ description: Unique id of VNF. This is unique across the graph.
+ vnf-image:
description: |
- ModelAndNamedQuerySearch holds query-parameters and instance-properties for performing a named-query or model query
+ Image object that pertain to a VNF that doesn't have associated vservers. This is a kludge.
+ ###### Related Nodes
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)
+ - VNF-IMAGE cannot be deleted if linked to GENERIC-VNF
+ required:
+ - vnf-image-uuid
+ - application
+ - application-vendor
properties:
- query-parameters:
- type: object
- $ref: "#/definitions/query-parameters"
- instance-filters:
- type: object
- $ref: "#/definitions/instance-filters"
- secondary-filts:
- type: object
- $ref: "#/definitions/secondary-filts"
- top-node-type:
+ vnf-image-uuid:
type: string
- secondary-filter-cut-point:
+ description: Unique ID of this asset
+ application:
type: string
- query-parameters:
+ description: The application that the image instantiates.
+ application-vendor:
+ type: string
+ description: The vendor of the application.
+ application-version:
+ type: string
+ description: The version of the application.
+ selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ vnf-images:
description: |
- QueryParameters for performing a named-query or model query
+ Collection of image objects that pertain to a VNF that doesn't have associated vservers. This is a kludge.
properties:
- named-query:
- type: object
- $ref: "#/definitions/named-query"
- overloaded-model:
- type: object
- $ref: "#/definitions/overloaded-model"
- overloaded-model:
+ vnf-image:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vnf-image"
+ vnfc:
description: |
- Allows for legacy POST of old-style and new-style models
+ ###### Related Nodes
+ - TO generic-vnf( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO instance-group( vnfc org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO vip-ipv4-address-list( vnfc org.onap.relationships.inventory.Uses vip-ipv4-address-list, MANY2MANY)
+ - TO vip-ipv6-address-list( vnfc org.onap.relationships.inventory.Uses vip-ipv6-address-list, MANY2MANY)
+ - TO vserver( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vnfc, MANY2ONE)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vnfc, MANY2ONE)
+ - VNFC is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST
required:
- - model-invariant-id
- - model-name-version-id
- - model-type
- - model-name
- - model-id
- - model-version
+ - vnfc-name
+ - nfc-naming-code
+ - nfc-function
+ - in-maint
+ - is-closed-loop-disabled
properties:
- model-invariant-id:
+ vnfc-name:
type: string
- description: Unique identifier corresponding to the main definition of a model in ASDC
- model-name-version-id:
+ description: Unique ID of vnfc.
+ nfc-naming-code:
type: string
- description: Unique identifier corresponding to one version of a model in ASDC
- model-type:
+ description: Short code that is used in naming instances of the item being modeled
+ nfc-function:
type: string
- description: Type of the model, e.g., service, resource, widget, etc.
- model-name:
+ description: English description of function that the specific resource deployment is providing. Assigned as part of the customization of a resource in a service
+ prov-status:
type: string
- description: Name of the model, which can change from version to version.
- model-id:
+ description: prov status of this vnfc
+ orchestration-status:
type: string
- description: Invariant unique ID which does not change from version to version
- model-version:
+ description: Orchestration status of this VNF, mastered by APP-C
+ ipaddress-v4-oam-vip:
type: string
- description: Version
- model-description:
+ description: Oam V4 vip address of this vnfc
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
+ group-notation:
type: string
- description: Description
+ description: Group notation of VNFC
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- model-vers:
- type: object
- $ref: "#/definitions/model-vers"
relationship-list:
- type: object
- $ref: "#/definitions/relationship-list"
- instance-filters:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ l3-interface-ipv4-address-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
+ l3-interface-ipv6-address-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
+ vnfcs:
description: |
- InstanceFilters for performing a named-query or model query
+ virtual network components associated with a vserver from application controller.
properties:
- instance-filter:
+ vnfc:
type: array
items:
- $ref: "#/definitions/instance-filter"
- instance-filter:
+ $ref: "#/getDefinitions/vnfc"
+ volume:
description: |
- InstanceFilter for performing a named-query or model query
- secondary-filts:
+ Ephemeral Block storage volume.
+ ###### Related Nodes
+ - FROM vserver (PARENT of volume, vserver tosca.relationships.AttachesTo volume)
+ required:
+ - volume-id
+ - volume-selflink
+ properties:
+ volume-id:
+ type: string
+ description: Unique ID of block storage volume relative to the vserver.
+ volume-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ volume-group:
description: |
- SecondaryFilts for performing a named-query or model query
+ Persistent block-level storage.
+ ###### Related Nodes
+ - TO cloud-region( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO complex( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ required:
+ - volume-group-id
+ - volume-group-name
+ - vnf-type
properties:
- secondary-filt:
+ volume-group-id:
+ type: string
+ description: Unique ID of volume-group.
+ volume-group-name:
+ type: string
+ description: Name of the volume group.
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this volume-group
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ orchestration-status:
+ type: string
+ description: Orchestration status of this volume-group
+ model-customization-id:
+ type: string
+ description: captures the id of all the configuration used to customize the resource for the service.
+ vf-module-model-customization-id:
+ type: string
+ description: helps relate the volume group to the vf-module whose components will require the volume group
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ volume-groups:
+ description: |
+ Collection of persistent block-level storage.
+ properties:
+ volume-group:
type: array
items:
- $ref: "#/definitions/secondary-filt"
- secondary-filt:
+ $ref: "#/getDefinitions/volume-group"
+ volumes:
description: |
- SecondaryFilt for performing a named-query or model query
- properties:
+ Collection of ephemeral Block storage volumes.
+ properties:
+ volume:
+ type: array
+ items:
+ $ref: "#/getDefinitions/volume"
+ vpls-pe:
description: |
- Property holder for query properties or instance properties
+ VPLS Provider Edge routers.
+ ###### Related Nodes
+ - TO complex( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO ctag-pool( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - VPLS-PE is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
+ required:
+ - equipment-name
properties:
- property-name:
+ equipment-name:
type: string
- property-value:
+ prov-status:
type: string
- response-list:
+ description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address).
+ equipment-role:
+ type: string
+ description: Client should send valid enumerated value, e.g., VPLS-PE.
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Temporary location for stag to get to VCE
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ p-interfaces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/p-interface"
+ lag-interfaces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/lag-interface"
+ vpls-pes:
description: |
- Response container for the results of a named-query or model query
+ Collection of VPLS Provider Edge routers
properties:
- inventory-response-items:
- type: object
- $ref: "#/definitions/inventory-response-items"
- inventory-response-items:
+ vpls-pe:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vpls-pe"
+ vpn-binding:
description: |
- Container for inventory items in response list
+ VPN binding
+ ###### Related Nodes
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2MANY)
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - FROM route-target( route-target org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2ONE)
+ - VPN-BINDING cannot be deleted if linked to ALLOTTED-RESOURCE,L3-NETWORK,LOGICAL-LINK
+ - VPN-BINDING is DELETED when these are DELETED ROUTE-TARGET
+ required:
+ - vpn-id
+ - vpn-name
properties:
- inventory-response-item:
+ vpn-id:
+ type: string
+ description: VPN ID, globally unique within A&AI
+ vpn-name:
+ type: string
+ description: VPN Name
+ vpn-platform:
+ type: string
+ description: the platform associated with the VPN example AVPN, Mobility
+ vpn-type:
+ type: string
+ description: Type of the vpn, should be taken from enumerated/valid values
+ vpn-region:
+ type: string
+ description: region of customer vpn
+ customer-vpn-id:
+ type: string
+ description: id for this customer vpn
+ route-distinguisher:
+ type: string
+ description: Used to distinguish the distinct VPN routes of separate customers who connect to the provider in an MPLS network.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ route-targets:
+ type: array
+ items:
+ $ref: "#/getDefinitions/route-target"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ description: l3-networks relate to vpn-bindings
+ vpn-bindings:
+ properties:
+ vpn-binding:
type: array
items:
- $ref: "#/definitions/inventory-response-item"
- inventory-response-item:
+ $ref: "#/getDefinitions/vpn-binding"
+ vserver:
description: |
- Inventory item for response list
+ Virtual Servers, aka virtual machine or VM.
+ ###### Related Nodes
+ - TO tenant( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)
+ - TO flavor( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)
+ - TO image( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)
+ - TO pserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)
+ - TO snapshot( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)
+ - TO volume (CHILD of vserver, vserver tosca.relationships.AttachesTo volume, ONE2MANY)
+ - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM vce( vce tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)
+ - FROM vnfc( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)
+ - VSERVER is DELETED when these are DELETED L-INTERFACE
+ - VSERVER deletion means associated objects of these types are also DELETED:VOLUME
+ required:
+ - vserver-id
+ - vserver-name
+ - vserver-selflink
+ - in-maint
+ - is-closed-loop-disabled
properties:
- model-name:
+ vserver-id:
type: string
- extra-properties:
- type: object
- $ref: "#/definitions/extra-properties"
- inventory-response-items:
- type: object
- $ref: "#/definitions/inventory-response-items"
- extra-properties:
+ description: Unique identifier for this vserver relative to its tenant
+ vserver-name:
+ type: string
+ description: Name of vserver
+ vserver-name2:
+ type: string
+ description: Alternative name of vserver
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ vserver-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ volumes:
+ type: array
+ items:
+ $ref: "#/getDefinitions/volume"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l-interface"
+ vservers:
description: |
- Extra properties for inventory item for response list
+ Collection of virtual Servers, aka virtual machines or VMs.
properties:
- extra-property:
+ vserver:
type: array
items:
- $ref: "#/definitions/extra-property"
- extra-property:
+ $ref: "#/getDefinitions/vserver"
+ zone:
+ description: |
+ A zone is a grouping of assets in a location homing to the same connections into the CBB
+ ###### Related Nodes
+ - TO complex( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM pnf( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ required:
+ - zone-id
+ - zone-name
+ - design-type
+ - zone-context
properties:
- property-name:
+ zone-id:
type: string
- property-value:
+ description: Code assigned by AIC to the zone
+ zone-name:
type: string
- vnf:
+ description: English name associated with the zone
+ design-type:
+ type: string
+ description: Design of zone [Medium/Large?]
+ zone-context:
+ type: string
+ description: Context of zone [production/test]
+ status:
+ type: string
+ description: Status of a zone.
+ resource-version:
+ type: string
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ zones:
description: |
- Abstract vnf class
- required:
- - vnf-id
+ Collection of zones
properties:
- vnf-id:
- type: string
- description: Unique id of VNF. This is unique across the graph.
+ zone:
+ type: array
+ items:
+ $ref: "#/getDefinitions/zone"
diff --git a/aai-schema/src/main/resources/aai_swagger_yaml/aai_swagger_v8.yaml b/aai-schema/src/main/resources/aai_swagger_yaml/aai_swagger_v8.yaml
index a61bf31a..38389232 100644
--- a/aai-schema/src/main/resources/aai_swagger_yaml/aai_swagger_v8.yaml
+++ b/aai-schema/src/main/resources/aai_swagger_yaml/aai_swagger_v8.yaml
@@ -1,28 +1,9 @@
-#
-# ============LICENSE_START=======================================================
-# org.onap.aai
-# ================================================================================
-# Copyright © 2017 AT&T Intellectual Property. All rights reserved.
-# ================================================================================
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-# http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-# ============LICENSE_END=========================================================
-#
-# ECOMP is a trademark and service mark of AT&T Intellectual Property.
-#
-
swagger: "2.0"
info:
description: |
+
+ [Differences versus the previous schema version](apidocs/aai_swagger_v8.diff)
+
Copyright &copy; 2017 AT&amp;T Intellectual Property. All rights reserved.
Licensed under the Creative Commons License, Attribution 4.0 Intl. (the &quot;License&quot;); you may not use this documentation except in compliance with the License.
@@ -71,19 +52,22 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: target-pe
in: path
description: The Target provider edge router
required: true
type: string
+ example: __TARGET-PE__
- name: availability-zone-name
in: path
description: Name of the availability zone
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureComplexesComplexCtagPoolsCtagPool.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -108,16 +92,19 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: target-pe
in: path
description: The Target provider edge router
required: true
type: string
+ example: __TARGET-PE__
- name: availability-zone-name
in: path
description: Name of the availability zone
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
/cloud-infrastructure/complexes/complex/{physical-location-id}/ctag-pools/ctag-pool/{target-pe}/{availability-zone-name}:
get:
tags:
@@ -132,7 +119,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/ctag-pool"
+ $ref: "#/getDefinitions/ctag-pool"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -141,16 +128,19 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: target-pe
in: path
description: The Target provider edge router
required: true
type: string
+ example: __TARGET-PE__
- name: availability-zone-name
in: path
description: Name of the availability zone
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: data-center-code
in: query
description: Data center code which can be an alternate way to identify a complex
@@ -170,7 +160,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing ctag-pool
- description: create or update an existing ctag-pool
+ description: |
+ Create or update an existing ctag-pool.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureComplexesComplexCtagPoolsCtagPool
consumes:
- application/json
@@ -187,22 +180,76 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: target-pe
in: path
description: The Target provider edge router
required: true
type: string
+ example: __TARGET-PE__
- name: availability-zone-name
in: path
description: Name of the availability zone
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: body
in: body
- description: ctag-pool object that needs to be created or updated
+ description: ctag-pool object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureComplexesComplexCtagPoolsCtagPool.json)
required: true
schema:
$ref: "#/definitions/ctag-pool"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing ctag-pool
+ description: |
+ Update an existing ctag-pool
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureComplexesComplexCtagPoolsCtagPool
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: physical-location-id
+ in: path
+ description: Unique identifier for physical location, e.g., CLLI
+ required: true
+ type: string
+ example: __PHYSICAL-LOCATION-ID__
+ - name: target-pe
+ in: path
+ description: The Target provider edge router
+ required: true
+ type: string
+ example: __TARGET-PE__
+ - name: availability-zone-name
+ in: path
+ description: Name of the availability zone
+ required: true
+ type: string
+ example: __AVAILABILITY-ZONE-NAME__
+ - name: body
+ in: body
+ description: ctag-pool object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/ctag-pool"
delete:
tags:
- CloudInfrastructure
@@ -224,16 +271,19 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: target-pe
in: path
description: The Target provider edge router
required: true
type: string
+ example: __TARGET-PE__
- name: availability-zone-name
in: path
description: Name of the availability zone
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -253,7 +303,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/ctag-pools"
+ $ref: "#/getDefinitions/ctag-pools"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -262,6 +312,7 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: data-center-code
in: query
description: Data center code which can be an alternate way to identify a complex
@@ -298,9 +349,10 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureComplexesComplex.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -325,6 +377,7 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
/cloud-infrastructure/complexes/complex/{physical-location-id}:
get:
tags:
@@ -339,7 +392,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/complex"
+ $ref: "#/getDefinitions/complex"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -348,6 +401,7 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: data-center-code
in: query
description: Data center code which can be an alternate way to identify a complex
@@ -367,7 +421,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing complex
- description: create or update an existing complex
+ description: |
+ Create or update an existing complex.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureComplexesComplex
consumes:
- application/json
@@ -384,12 +441,52 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: body
in: body
- description: complex object that needs to be created or updated
+ description: complex object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureComplexesComplex.json)
required: true
schema:
$ref: "#/definitions/complex"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing complex
+ description: |
+ Update an existing complex
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureComplexesComplex
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: physical-location-id
+ in: path
+ description: Unique identifier for physical location, e.g., CLLI
+ required: true
+ type: string
+ example: __PHYSICAL-LOCATION-ID__
+ - name: body
+ in: body
+ description: complex object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/complex"
delete:
tags:
- CloudInfrastructure
@@ -411,6 +508,7 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -430,7 +528,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/complexes"
+ $ref: "#/getDefinitions/complexes"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/volume-groups/volume-group/{volume-group-id}/relationship-list/relationship:
@@ -454,19 +552,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: volume-group-id
in: path
description: Unique ID of volume-group.
required: true
type: string
+ example: __VOLUME-GROUP-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -491,16 +592,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: volume-group-id
in: path
description: Unique ID of volume-group.
required: true
type: string
+ example: __VOLUME-GROUP-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/volume-groups/volume-group/{volume-group-id}:
get:
tags:
@@ -515,7 +619,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/volume-group"
+ $ref: "#/getDefinitions/volume-group"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -524,16 +628,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: volume-group-id
in: path
description: Unique ID of volume-group.
required: true
type: string
+ example: __VOLUME-GROUP-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -563,7 +670,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing volume-group
- description: create or update an existing volume-group
+ description: |
+ Create or update an existing volume-group.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup
consumes:
- application/json
@@ -580,22 +690,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: volume-group-id
in: path
description: Unique ID of volume-group.
required: true
type: string
+ example: __VOLUME-GROUP-ID__
- name: body
in: body
- description: volume-group object that needs to be created or updated
+ description: volume-group object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup.json)
required: true
schema:
$ref: "#/definitions/volume-group"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing volume-group
+ description: |
+ Update an existing volume-group
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: volume-group-id
+ in: path
+ description: Unique ID of volume-group.
+ required: true
+ type: string
+ example: __VOLUME-GROUP-ID__
+ - name: body
+ in: body
+ description: volume-group object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/volume-group"
delete:
tags:
- CloudInfrastructure
@@ -617,16 +781,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: volume-group-id
in: path
description: Unique ID of volume-group.
required: true
type: string
+ example: __VOLUME-GROUP-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -646,7 +813,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/volume-groups"
+ $ref: "#/getDefinitions/volume-groups"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -655,11 +822,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -691,29 +860,34 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: volume-id
in: path
description: Unique ID of block storage volume relative to the vserver.
required: true
type: string
+ example: __VOLUME-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -738,26 +912,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: volume-id
in: path
description: Unique ID of block storage volume relative to the vserver.
required: true
type: string
+ example: __VOLUME-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/volumes/volume/{volume-id}:
get:
tags:
@@ -772,7 +951,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/volume"
+ $ref: "#/getDefinitions/volume"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -781,26 +960,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: volume-id
in: path
description: Unique ID of block storage volume relative to the vserver.
required: true
type: string
+ example: __VOLUME-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -843,7 +1027,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing volume
- description: create or update an existing volume
+ description: |
+ Create or update an existing volume.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume
consumes:
- application/json
@@ -860,32 +1047,100 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: volume-id
in: path
description: Unique ID of block storage volume relative to the vserver.
required: true
type: string
+ example: __VOLUME-ID__
- name: body
in: body
- description: volume object that needs to be created or updated
+ description: volume object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume.json)
required: true
schema:
$ref: "#/definitions/volume"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing volume
+ description: |
+ Update an existing volume
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: volume-id
+ in: path
+ description: Unique ID of block storage volume relative to the vserver.
+ required: true
+ type: string
+ example: __VOLUME-ID__
+ - name: body
+ in: body
+ description: volume object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/volume"
delete:
tags:
- CloudInfrastructure
@@ -907,26 +1162,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: volume-id
in: path
description: Unique ID of block storage volume relative to the vserver.
required: true
type: string
+ example: __VOLUME-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -946,7 +1206,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/volumes"
+ $ref: "#/getDefinitions/volumes"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -955,21 +1215,25 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -1029,24 +1293,28 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -1071,21 +1339,25 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -1107,34 +1379,40 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -1159,31 +1437,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -1205,39 +1489,46 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -1262,36 +1553,43 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -1306,7 +1604,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -1315,36 +1613,43 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -1429,7 +1734,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -1446,42 +1754,124 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- CloudInfrastructure
@@ -1503,36 +1893,43 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -1559,39 +1956,46 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -1616,36 +2020,43 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -1660,7 +2071,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -1669,36 +2080,43 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -1783,7 +2201,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -1800,42 +2221,124 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- CloudInfrastructure
@@ -1857,36 +2360,43 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -1906,7 +2416,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -1915,31 +2425,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -2008,7 +2524,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -2025,37 +2544,112 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- CloudInfrastructure
@@ -2077,31 +2671,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -2121,7 +2721,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -2130,26 +2730,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -2224,34 +2829,40 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -2276,31 +2887,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -2315,7 +2932,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -2324,31 +2941,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -2426,7 +3049,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -2443,37 +3069,112 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- CloudInfrastructure
@@ -2495,31 +3196,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -2539,7 +3246,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -2548,26 +3255,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -2642,29 +3354,34 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -2689,26 +3406,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -2730,34 +3452,40 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -2782,31 +3510,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -2821,7 +3555,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -2830,31 +3564,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -2928,7 +3668,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -2945,37 +3688,112 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- CloudInfrastructure
@@ -2997,31 +3815,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -3048,34 +3872,40 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -3100,31 +3930,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -3139,7 +3975,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -3148,31 +3984,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -3246,7 +4088,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -3263,37 +4108,112 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- CloudInfrastructure
@@ -3315,31 +4235,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -3359,7 +4285,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -3368,26 +4294,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -3445,7 +4376,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface
consumes:
- application/json
@@ -3462,32 +4396,100 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- CloudInfrastructure
@@ -3509,26 +4511,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -3548,7 +4555,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -3557,21 +4564,25 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -3624,7 +4635,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vserver"
+ $ref: "#/getDefinitions/vserver"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -3633,21 +4644,25 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -3690,7 +4705,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing vserver
- description: create or update an existing vserver
+ description: |
+ Create or update an existing vserver.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver
consumes:
- application/json
@@ -3707,27 +4725,88 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: body
in: body
- description: vserver object that needs to be created or updated
+ description: vserver object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver.json)
required: true
schema:
$ref: "#/definitions/vserver"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing vserver
+ description: |
+ Update an existing vserver
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: body
+ in: body
+ description: vserver object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vserver"
delete:
tags:
- CloudInfrastructure
@@ -3749,21 +4828,25 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -3783,7 +4866,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vservers"
+ $ref: "#/getDefinitions/vservers"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -3792,16 +4875,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -3838,19 +4924,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenant.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -3875,16 +4964,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}:
get:
tags:
@@ -3899,7 +4991,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/tenant"
+ $ref: "#/getDefinitions/tenant"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -3908,16 +5000,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -3937,7 +5032,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing tenant
- description: create or update an existing tenant
+ description: |
+ Create or update an existing tenant.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenant
consumes:
- application/json
@@ -3954,22 +5052,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: body
in: body
- description: tenant object that needs to be created or updated
+ description: tenant object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionTenantsTenant.json)
required: true
schema:
$ref: "#/definitions/tenant"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing tenant
+ description: |
+ Update an existing tenant
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenant
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: body
+ in: body
+ description: tenant object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/tenant"
delete:
tags:
- CloudInfrastructure
@@ -3991,16 +5143,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -4020,7 +5175,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/tenants"
+ $ref: "#/getDefinitions/tenants"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4029,11 +5184,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4065,19 +5222,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: flavor-id
in: path
description: Flavor id, expected to be unique across cloud-region.
required: true
type: string
+ example: __FLAVOR-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -4102,16 +5262,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: flavor-id
in: path
description: Flavor id, expected to be unique across cloud-region.
required: true
type: string
+ example: __FLAVOR-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/flavors/flavor/{flavor-id}:
get:
tags:
@@ -4126,7 +5289,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/flavor"
+ $ref: "#/getDefinitions/flavor"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4135,16 +5298,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: flavor-id
in: path
description: Flavor id, expected to be unique across cloud-region.
required: true
type: string
+ example: __FLAVOR-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4164,7 +5330,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing flavor
- description: create or update an existing flavor
+ description: |
+ Create or update an existing flavor.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor
consumes:
- application/json
@@ -4181,22 +5350,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: flavor-id
in: path
description: Flavor id, expected to be unique across cloud-region.
required: true
type: string
+ example: __FLAVOR-ID__
- name: body
in: body
- description: flavor object that needs to be created or updated
+ description: flavor object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor.json)
required: true
schema:
$ref: "#/definitions/flavor"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing flavor
+ description: |
+ Update an existing flavor
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: flavor-id
+ in: path
+ description: Flavor id, expected to be unique across cloud-region.
+ required: true
+ type: string
+ example: __FLAVOR-ID__
+ - name: body
+ in: body
+ description: flavor object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/flavor"
delete:
tags:
- CloudInfrastructure
@@ -4218,16 +5441,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: flavor-id
in: path
description: Flavor id, expected to be unique across cloud-region.
required: true
type: string
+ example: __FLAVOR-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -4247,7 +5473,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/flavors"
+ $ref: "#/getDefinitions/flavors"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4256,11 +5482,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4292,19 +5520,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: group-id
in: path
description: Group id, expected to be unique across cloud-region.
required: true
type: string
+ example: __GROUP-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -4329,16 +5560,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: group-id
in: path
description: Group id, expected to be unique across cloud-region.
required: true
type: string
+ example: __GROUP-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/group-assignments/group-assignment/{group-id}:
get:
tags:
@@ -4353,7 +5587,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/group-assignment"
+ $ref: "#/getDefinitions/group-assignment"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4362,16 +5596,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: group-id
in: path
description: Group id, expected to be unique across cloud-region.
required: true
type: string
+ example: __GROUP-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4396,7 +5633,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing group-assignment
- description: create or update an existing group-assignment
+ description: |
+ Create or update an existing group-assignment.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment
consumes:
- application/json
@@ -4413,22 +5653,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: group-id
in: path
description: Group id, expected to be unique across cloud-region.
required: true
type: string
+ example: __GROUP-ID__
- name: body
in: body
- description: group-assignment object that needs to be created or updated
+ description: group-assignment object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment.json)
required: true
schema:
$ref: "#/definitions/group-assignment"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing group-assignment
+ description: |
+ Update an existing group-assignment
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: group-id
+ in: path
+ description: Group id, expected to be unique across cloud-region.
+ required: true
+ type: string
+ example: __GROUP-ID__
+ - name: body
+ in: body
+ description: group-assignment object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/group-assignment"
delete:
tags:
- CloudInfrastructure
@@ -4450,16 +5744,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: group-id
in: path
description: Group id, expected to be unique across cloud-region.
required: true
type: string
+ example: __GROUP-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -4479,7 +5776,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/group-assignments"
+ $ref: "#/getDefinitions/group-assignments"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4488,11 +5785,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4524,19 +5823,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: snapshot-id
in: path
description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
required: true
type: string
+ example: __SNAPSHOT-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -4561,16 +5863,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: snapshot-id
in: path
description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
required: true
type: string
+ example: __SNAPSHOT-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/snapshots/snapshot/{snapshot-id}:
get:
tags:
@@ -4585,7 +5890,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/snapshot"
+ $ref: "#/getDefinitions/snapshot"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4594,16 +5899,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: snapshot-id
in: path
description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
required: true
type: string
+ example: __SNAPSHOT-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4643,7 +5951,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing snapshot
- description: create or update an existing snapshot
+ description: |
+ Create or update an existing snapshot.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot
consumes:
- application/json
@@ -4660,22 +5971,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: snapshot-id
in: path
description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
required: true
type: string
+ example: __SNAPSHOT-ID__
- name: body
in: body
- description: snapshot object that needs to be created or updated
+ description: snapshot object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot.json)
required: true
schema:
$ref: "#/definitions/snapshot"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing snapshot
+ description: |
+ Update an existing snapshot
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: snapshot-id
+ in: path
+ description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
+ required: true
+ type: string
+ example: __SNAPSHOT-ID__
+ - name: body
+ in: body
+ description: snapshot object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/snapshot"
delete:
tags:
- CloudInfrastructure
@@ -4697,16 +6062,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: snapshot-id
in: path
description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
required: true
type: string
+ example: __SNAPSHOT-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -4726,7 +6094,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/snapshots"
+ $ref: "#/getDefinitions/snapshots"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4735,11 +6103,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4771,19 +6141,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionImagesImage.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -4808,16 +6181,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}/metadata/metadatum/{metaname}:
get:
tags:
@@ -4832,7 +6208,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadatum"
+ $ref: "#/getDefinitions/metadatum"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4841,20 +6217,24 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4889,7 +6269,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing metadatum
- description: create or update an existing metadatum
+ description: |
+ Create or update an existing metadatum.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionImagesImageMetadataMetadatum
consumes:
- application/json
@@ -4906,26 +6289,86 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: body
in: body
- description: metadatum object that needs to be created or updated
+ description: metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionImagesImageMetadataMetadatum.json)
required: true
schema:
$ref: "#/definitions/metadatum"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing metadatum
+ description: |
+ Update an existing metadatum
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionImagesImageMetadataMetadatum
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: image-id
+ in: path
+ description: Image id, expected to be unique across cloud region
+ required: true
+ type: string
+ example: __IMAGE-ID__
+ - name: metaname
+ in: path
+ required: true
+ type: string
+ example: __METANAME__
+ - name: body
+ in: body
+ description: metadatum object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/metadatum"
delete:
tags:
- CloudInfrastructure
@@ -4947,20 +6390,24 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -4980,7 +6427,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadata"
+ $ref: "#/getDefinitions/metadata"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4989,16 +6436,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5043,7 +6493,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/image"
+ $ref: "#/getDefinitions/image"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5052,16 +6502,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5096,7 +6549,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing image
- description: create or update an existing image
+ description: |
+ Create or update an existing image.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionImagesImage
consumes:
- application/json
@@ -5113,22 +6569,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: body
in: body
- description: image object that needs to be created or updated
+ description: image object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionImagesImage.json)
required: true
schema:
$ref: "#/definitions/image"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing image
+ description: |
+ Update an existing image
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionImagesImage
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: image-id
+ in: path
+ description: Image id, expected to be unique across cloud region
+ required: true
+ type: string
+ example: __IMAGE-ID__
+ - name: body
+ in: body
+ description: image object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/image"
delete:
tags:
- CloudInfrastructure
@@ -5150,16 +6660,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -5179,7 +6692,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/images"
+ $ref: "#/getDefinitions/images"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5188,11 +6701,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5224,19 +6739,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: switch-name
in: path
description: DVS switch name
required: true
type: string
+ example: __SWITCH-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -5261,16 +6779,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: switch-name
in: path
description: DVS switch name
required: true
type: string
+ example: __SWITCH-NAME__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/dvs-switches/dvs-switch/{switch-name}:
get:
tags:
@@ -5285,7 +6806,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/dvs-switch"
+ $ref: "#/getDefinitions/dvs-switch"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5294,16 +6815,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: switch-name
in: path
description: DVS switch name
required: true
type: string
+ example: __SWITCH-NAME__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5323,7 +6847,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing dvs-switch
- description: create or update an existing dvs-switch
+ description: |
+ Create or update an existing dvs-switch.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch
consumes:
- application/json
@@ -5340,22 +6867,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: switch-name
in: path
description: DVS switch name
required: true
type: string
+ example: __SWITCH-NAME__
- name: body
in: body
- description: dvs-switch object that needs to be created or updated
+ description: dvs-switch object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch.json)
required: true
schema:
$ref: "#/definitions/dvs-switch"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing dvs-switch
+ description: |
+ Update an existing dvs-switch
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: switch-name
+ in: path
+ description: DVS switch name
+ required: true
+ type: string
+ example: __SWITCH-NAME__
+ - name: body
+ in: body
+ description: dvs-switch object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/dvs-switch"
delete:
tags:
- CloudInfrastructure
@@ -5377,16 +6958,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: switch-name
in: path
description: DVS switch name
required: true
type: string
+ example: __SWITCH-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -5406,7 +6990,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/dvs-switches"
+ $ref: "#/getDefinitions/dvs-switches"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5415,11 +6999,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5451,19 +7037,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: network-uuid
in: path
description: UUID of the network. Unique across a cloud-region
required: true
type: string
+ example: __NETWORK-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -5488,16 +7077,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: network-uuid
in: path
description: UUID of the network. Unique across a cloud-region
required: true
type: string
+ example: __NETWORK-UUID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/oam-networks/oam-network/{network-uuid}:
get:
tags:
@@ -5512,7 +7104,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/oam-network"
+ $ref: "#/getDefinitions/oam-network"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5521,16 +7113,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: network-uuid
in: path
description: UUID of the network. Unique across a cloud-region
required: true
type: string
+ example: __NETWORK-UUID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5556,7 +7151,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing oam-network
- description: create or update an existing oam-network
+ description: |
+ Create or update an existing oam-network.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork
consumes:
- application/json
@@ -5573,22 +7171,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: network-uuid
in: path
description: UUID of the network. Unique across a cloud-region
required: true
type: string
+ example: __NETWORK-UUID__
- name: body
in: body
- description: oam-network object that needs to be created or updated
+ description: oam-network object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork.json)
required: true
schema:
$ref: "#/definitions/oam-network"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing oam-network
+ description: |
+ Update an existing oam-network
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: network-uuid
+ in: path
+ description: UUID of the network. Unique across a cloud-region
+ required: true
+ type: string
+ example: __NETWORK-UUID__
+ - name: body
+ in: body
+ description: oam-network object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/oam-network"
delete:
tags:
- CloudInfrastructure
@@ -5610,16 +7262,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: network-uuid
in: path
description: UUID of the network. Unique across a cloud-region
required: true
type: string
+ example: __NETWORK-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -5639,7 +7294,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/oam-networks"
+ $ref: "#/getDefinitions/oam-networks"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5648,11 +7303,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5684,19 +7341,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: availability-zone-name
in: path
description: Name of the availability zone. Unique across a cloud region
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -5721,16 +7381,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: availability-zone-name
in: path
description: Name of the availability zone. Unique across a cloud region
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/availability-zones/availability-zone/{availability-zone-name}:
get:
tags:
@@ -5745,7 +7408,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/availability-zone"
+ $ref: "#/getDefinitions/availability-zone"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5754,16 +7417,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: availability-zone-name
in: path
description: Name of the availability zone. Unique across a cloud region
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5778,7 +7444,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing availability-zone
- description: create or update an existing availability-zone
+ description: |
+ Create or update an existing availability-zone.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone
consumes:
- application/json
@@ -5795,22 +7464,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: availability-zone-name
in: path
description: Name of the availability zone. Unique across a cloud region
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: body
in: body
- description: availability-zone object that needs to be created or updated
+ description: availability-zone object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone.json)
required: true
schema:
$ref: "#/definitions/availability-zone"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing availability-zone
+ description: |
+ Update an existing availability-zone
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: availability-zone-name
+ in: path
+ description: Name of the availability zone. Unique across a cloud region
+ required: true
+ type: string
+ example: __AVAILABILITY-ZONE-NAME__
+ - name: body
+ in: body
+ description: availability-zone object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/availability-zone"
delete:
tags:
- CloudInfrastructure
@@ -5832,16 +7555,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: availability-zone-name
in: path
description: Name of the availability zone. Unique across a cloud region
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -5861,7 +7587,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/availability-zones"
+ $ref: "#/getDefinitions/availability-zones"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5870,11 +7596,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5906,14 +7634,16 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegion.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -5938,11 +7668,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}:
get:
tags:
@@ -5957,7 +7689,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/cloud-region"
+ $ref: "#/getDefinitions/cloud-region"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5966,11 +7698,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5985,7 +7719,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing cloud-region
- description: create or update an existing cloud-region
+ description: |
+ Create or update an existing cloud-region.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegion
consumes:
- application/json
@@ -6002,17 +7739,64 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: body
in: body
- description: cloud-region object that needs to be created or updated
+ description: cloud-region object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureCloudRegionsCloudRegion.json)
required: true
schema:
$ref: "#/definitions/cloud-region"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing cloud-region
+ description: |
+ Update an existing cloud-region
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegion
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: body
+ in: body
+ description: cloud-region object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/cloud-region"
delete:
tags:
- CloudInfrastructure
@@ -6034,11 +7818,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -6058,7 +7844,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/cloud-regions"
+ $ref: "#/getDefinitions/cloud-regions"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/cloud-infrastructure/network-profiles/network-profile/{nm-profile-name}/relationship-list/relationship:
@@ -6082,9 +7868,10 @@ paths:
description: Unique name of network profile.
required: true
type: string
+ example: __NM-PROFILE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureNetworkProfilesNetworkProfile.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -6109,6 +7896,7 @@ paths:
description: Unique name of network profile.
required: true
type: string
+ example: __NM-PROFILE-NAME__
/cloud-infrastructure/network-profiles/network-profile/{nm-profile-name}:
get:
tags:
@@ -6123,7 +7911,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/network-profile"
+ $ref: "#/getDefinitions/network-profile"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -6132,11 +7920,15 @@ paths:
description: Unique name of network profile.
required: true
type: string
+ example: __NM-PROFILE-NAME__
put:
tags:
- CloudInfrastructure
summary: create or update an existing network-profile
- description: create or update an existing network-profile
+ description: |
+ Create or update an existing network-profile.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureNetworkProfilesNetworkProfile
consumes:
- application/json
@@ -6153,12 +7945,52 @@ paths:
description: Unique name of network profile.
required: true
type: string
+ example: __NM-PROFILE-NAME__
- name: body
in: body
- description: network-profile object that needs to be created or updated
+ description: network-profile object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureNetworkProfilesNetworkProfile.json)
required: true
schema:
$ref: "#/definitions/network-profile"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing network-profile
+ description: |
+ Update an existing network-profile
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureNetworkProfilesNetworkProfile
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: nm-profile-name
+ in: path
+ description: Unique name of network profile.
+ required: true
+ type: string
+ example: __NM-PROFILE-NAME__
+ - name: body
+ in: body
+ description: network-profile object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/network-profile"
delete:
tags:
- CloudInfrastructure
@@ -6180,6 +8012,7 @@ paths:
description: Unique name of network profile.
required: true
type: string
+ example: __NM-PROFILE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -6199,7 +8032,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/network-profiles"
+ $ref: "#/getDefinitions/network-profiles"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/cloud-infrastructure/pservers/pserver/{hostname}/relationship-list/relationship:
@@ -6223,9 +8056,10 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserver.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -6250,6 +8084,7 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/relationship-list/relationship:
put:
tags:
@@ -6271,14 +8106,16 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -6303,11 +8140,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -6329,24 +8168,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -6371,21 +8214,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -6407,29 +8254,34 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -6454,26 +8306,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -6488,7 +8345,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -6497,26 +8354,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: pserver-id
in: query
description: ID of Pserver
@@ -6577,7 +8439,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -6594,32 +8459,100 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- CloudInfrastructure
@@ -6641,26 +8574,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -6687,29 +8625,34 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -6734,26 +8677,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -6768,7 +8716,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -6777,26 +8725,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: pserver-id
in: query
description: ID of Pserver
@@ -6857,7 +8810,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -6874,32 +8830,100 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- CloudInfrastructure
@@ -6921,26 +8945,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -6960,7 +8989,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -6969,21 +8998,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: pserver-id
in: query
description: ID of Pserver
@@ -7028,7 +9061,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -7045,27 +9081,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- CloudInfrastructure
@@ -7087,21 +9184,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -7121,7 +9222,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -7130,16 +9231,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pserver-id
in: query
description: ID of Pserver
@@ -7190,24 +9294,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -7232,21 +9340,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -7261,7 +9373,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -7270,21 +9382,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: pserver-id
in: query
description: ID of Pserver
@@ -7338,7 +9454,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -7355,27 +9474,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- CloudInfrastructure
@@ -7397,21 +9577,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -7431,7 +9615,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -7440,16 +9624,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pserver-id
in: query
description: ID of Pserver
@@ -7500,19 +9687,22 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -7537,16 +9727,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -7568,24 +9761,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -7610,21 +9807,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -7639,7 +9840,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -7648,21 +9849,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: pserver-id
in: query
description: ID of Pserver
@@ -7712,7 +9917,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -7729,27 +9937,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- CloudInfrastructure
@@ -7771,21 +10040,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -7812,24 +10085,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -7854,21 +10131,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -7883,7 +10164,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -7892,21 +10173,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: pserver-id
in: query
description: ID of Pserver
@@ -7956,7 +10241,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -7973,27 +10261,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- CloudInfrastructure
@@ -8015,21 +10364,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -8049,7 +10402,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -8058,16 +10411,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pserver-id
in: query
description: ID of Pserver
@@ -8101,7 +10457,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface
consumes:
- application/json
@@ -8118,22 +10477,76 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- CloudInfrastructure
@@ -8155,16 +10568,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -8184,7 +10600,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -8193,11 +10609,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pserver-id
in: query
description: ID of Pserver
@@ -8226,7 +10644,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/p-interface"
+ $ref: "#/getDefinitions/p-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -8235,11 +10653,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pserver-id
in: query
description: ID of Pserver
@@ -8258,7 +10678,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing p-interface
- description: create or update an existing p-interface
+ description: |
+ Create or update an existing p-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterface
consumes:
- application/json
@@ -8275,17 +10698,64 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: p-interface object that needs to be created or updated
+ description: p-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverPInterfacesPInterface.json)
required: true
schema:
$ref: "#/definitions/p-interface"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing p-interface
+ description: |
+ Update an existing p-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: p-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/p-interface"
delete:
tags:
- CloudInfrastructure
@@ -8307,11 +10777,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -8331,7 +10803,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/p-interfaces"
+ $ref: "#/getDefinitions/p-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -8340,6 +10812,7 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: pserver-id
in: query
description: ID of Pserver
@@ -8375,14 +10848,16 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -8407,11 +10882,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -8433,24 +10910,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -8475,21 +10956,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -8511,29 +10996,34 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -8558,26 +11048,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -8592,7 +11087,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -8601,26 +11096,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: pserver-id
in: query
description: ID of Pserver
@@ -8681,7 +11181,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -8698,32 +11201,100 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- CloudInfrastructure
@@ -8745,26 +11316,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -8791,29 +11367,34 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -8838,26 +11419,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -8872,7 +11458,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -8881,26 +11467,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: pserver-id
in: query
description: ID of Pserver
@@ -8961,7 +11552,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -8978,32 +11572,100 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- CloudInfrastructure
@@ -9025,26 +11687,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -9064,7 +11731,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -9073,21 +11740,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: pserver-id
in: query
description: ID of Pserver
@@ -9132,7 +11803,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -9149,27 +11823,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- CloudInfrastructure
@@ -9191,21 +11926,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -9225,7 +11964,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -9234,16 +11973,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pserver-id
in: query
description: ID of Pserver
@@ -9294,24 +12036,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -9336,21 +12082,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -9365,7 +12115,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -9374,21 +12124,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: pserver-id
in: query
description: ID of Pserver
@@ -9442,7 +12196,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -9459,27 +12216,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- CloudInfrastructure
@@ -9501,21 +12319,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -9535,7 +12357,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -9544,16 +12366,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pserver-id
in: query
description: ID of Pserver
@@ -9604,19 +12429,22 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -9641,16 +12469,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -9672,24 +12503,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -9714,21 +12549,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -9743,7 +12582,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -9752,21 +12591,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: pserver-id
in: query
description: ID of Pserver
@@ -9816,7 +12659,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -9833,27 +12679,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- CloudInfrastructure
@@ -9875,21 +12782,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -9916,24 +12827,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -9958,21 +12873,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -9987,7 +12906,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -9996,21 +12915,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: pserver-id
in: query
description: ID of Pserver
@@ -10060,7 +12983,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -10077,27 +13003,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- CloudInfrastructure
@@ -10119,21 +13106,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -10153,7 +13144,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -10162,16 +13153,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pserver-id
in: query
description: ID of Pserver
@@ -10205,7 +13199,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface
consumes:
- application/json
@@ -10222,22 +13219,76 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- CloudInfrastructure
@@ -10259,16 +13310,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -10288,7 +13342,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -10297,11 +13351,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pserver-id
in: query
description: ID of Pserver
@@ -10330,7 +13386,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interface"
+ $ref: "#/getDefinitions/lag-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -10339,11 +13395,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pserver-id
in: query
description: ID of Pserver
@@ -10362,7 +13420,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing lag-interface
- description: create or update an existing lag-interface
+ description: |
+ Create or update an existing lag-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterface
consumes:
- application/json
@@ -10379,17 +13440,64 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: lag-interface object that needs to be created or updated
+ description: lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserverLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/lag-interface"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing lag-interface
+ description: |
+ Update an existing lag-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: lag-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/lag-interface"
delete:
tags:
- CloudInfrastructure
@@ -10411,11 +13519,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -10435,7 +13545,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interfaces"
+ $ref: "#/getDefinitions/lag-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -10444,6 +13554,7 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: pserver-id
in: query
description: ID of Pserver
@@ -10472,7 +13583,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/pserver"
+ $ref: "#/getDefinitions/pserver"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -10481,6 +13592,7 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: pserver-id
in: query
description: ID of Pserver
@@ -10499,7 +13611,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing pserver
- description: create or update an existing pserver
+ description: |
+ Create or update an existing pserver.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserver
consumes:
- application/json
@@ -10516,12 +13631,52 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: body
in: body
- description: pserver object that needs to be created or updated
+ description: pserver object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructurePserversPserver.json)
required: true
schema:
$ref: "#/definitions/pserver"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing pserver
+ description: |
+ Update an existing pserver
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserver
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: body
+ in: body
+ description: pserver object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/pserver"
delete:
tags:
- CloudInfrastructure
@@ -10543,6 +13698,7 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -10562,7 +13718,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/pservers"
+ $ref: "#/getDefinitions/pservers"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}/relationship-list/relationship:
@@ -10586,9 +13742,10 @@ paths:
description: Unique ID of the vdc
required: true
type: string
+ example: __VDC-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureVirtualDataCentersVirtualDataCenter.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -10613,6 +13770,7 @@ paths:
description: Unique ID of the vdc
required: true
type: string
+ example: __VDC-ID__
/cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}:
get:
tags:
@@ -10627,7 +13785,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/virtual-data-center"
+ $ref: "#/getDefinitions/virtual-data-center"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -10636,6 +13794,7 @@ paths:
description: Unique ID of the vdc
required: true
type: string
+ example: __VDC-ID__
- name: vdc-name
in: query
description: Name of the virtual data center
@@ -10645,7 +13804,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing virtual-data-center
- description: create or update an existing virtual-data-center
+ description: |
+ Create or update an existing virtual-data-center.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureVirtualDataCentersVirtualDataCenter
consumes:
- application/json
@@ -10662,12 +13824,52 @@ paths:
description: Unique ID of the vdc
required: true
type: string
+ example: __VDC-ID__
- name: body
in: body
- description: virtual-data-center object that needs to be created or updated
+ description: virtual-data-center object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/CloudInfrastructureVirtualDataCentersVirtualDataCenter.json)
required: true
schema:
$ref: "#/definitions/virtual-data-center"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing virtual-data-center
+ description: |
+ Update an existing virtual-data-center
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureVirtualDataCentersVirtualDataCenter
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vdc-id
+ in: path
+ description: Unique ID of the vdc
+ required: true
+ type: string
+ example: __VDC-ID__
+ - name: body
+ in: body
+ description: virtual-data-center object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/virtual-data-center"
delete:
tags:
- CloudInfrastructure
@@ -10689,6 +13891,7 @@ paths:
description: Unique ID of the vdc
required: true
type: string
+ example: __VDC-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -10708,7 +13911,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/virtual-data-centers"
+ $ref: "#/getDefinitions/virtual-data-centers"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/business/connectors/connector/{resource-instance-id}/relationship-list/relationship:
@@ -10732,9 +13935,10 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/BusinessConnectorsConnector.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -10759,6 +13963,7 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
/business/connectors/connector/{resource-instance-id}/metadata/metadatum/{metaname}:
get:
tags:
@@ -10773,7 +13978,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadatum"
+ $ref: "#/getDefinitions/metadatum"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -10782,10 +13987,12 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: persona-model-id
in: query
description: the ASDC model id for this resource or service model.
@@ -10810,7 +14017,10 @@ paths:
tags:
- Business
summary: create or update an existing metadatum
- description: create or update an existing metadatum
+ description: |
+ Create or update an existing metadatum.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessConnectorsConnectorMetadataMetadatum
consumes:
- application/json
@@ -10827,16 +14037,62 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: body
in: body
- description: metadatum object that needs to be created or updated
+ description: metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/BusinessConnectorsConnectorMetadataMetadatum.json)
required: true
schema:
$ref: "#/definitions/metadatum"
+ patch:
+ tags:
+ - Business
+ summary: update an existing metadatum
+ description: |
+ Update an existing metadatum
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessConnectorsConnectorMetadataMetadatum
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: resource-instance-id
+ in: path
+ description: Unique id of resource instance.
+ required: true
+ type: string
+ example: __RESOURCE-INSTANCE-ID__
+ - name: metaname
+ in: path
+ required: true
+ type: string
+ example: __METANAME__
+ - name: body
+ in: body
+ description: metadatum object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/metadatum"
delete:
tags:
- Business
@@ -10858,10 +14114,12 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -10881,7 +14139,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadata"
+ $ref: "#/getDefinitions/metadata"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -10890,6 +14148,7 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: persona-model-id
in: query
description: the ASDC model id for this resource or service model.
@@ -10924,7 +14183,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/connector"
+ $ref: "#/getDefinitions/connector"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -10933,6 +14192,7 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: persona-model-id
in: query
description: the ASDC model id for this resource or service model.
@@ -10957,7 +14217,10 @@ paths:
tags:
- Business
summary: create or update an existing connector
- description: create or update an existing connector
+ description: |
+ Create or update an existing connector.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessConnectorsConnector
consumes:
- application/json
@@ -10974,12 +14237,52 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: body
in: body
- description: connector object that needs to be created or updated
+ description: connector object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/BusinessConnectorsConnector.json)
required: true
schema:
$ref: "#/definitions/connector"
+ patch:
+ tags:
+ - Business
+ summary: update an existing connector
+ description: |
+ Update an existing connector
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessConnectorsConnector
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: resource-instance-id
+ in: path
+ description: Unique id of resource instance.
+ required: true
+ type: string
+ example: __RESOURCE-INSTANCE-ID__
+ - name: body
+ in: body
+ description: connector object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/connector"
delete:
tags:
- Business
@@ -11001,6 +14304,7 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -11020,7 +14324,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/connectors"
+ $ref: "#/getDefinitions/connectors"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/relationship-list/relationship:
@@ -11044,19 +14348,22 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -11081,16 +14388,19 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/metadata/metadatum/{metaname}:
get:
tags:
@@ -11105,7 +14415,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadatum"
+ $ref: "#/getDefinitions/metadatum"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -11114,20 +14424,24 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -11172,7 +14486,10 @@ paths:
tags:
- Business
summary: create or update an existing metadatum
- description: create or update an existing metadatum
+ description: |
+ Create or update an existing metadatum.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceMetadataMetadatum
consumes:
- application/json
@@ -11189,26 +14506,86 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: body
in: body
- description: metadatum object that needs to be created or updated
+ description: metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceMetadataMetadatum.json)
required: true
schema:
$ref: "#/definitions/metadatum"
+ patch:
+ tags:
+ - Business
+ summary: update an existing metadatum
+ description: |
+ Update an existing metadatum
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceMetadataMetadatum
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: global-customer-id
+ in: path
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ required: true
+ type: string
+ example: __GLOBAL-CUSTOMER-ID__
+ - name: service-type
+ in: path
+ description: Value defined by orchestration to identify this service across ECOMP.
+ required: true
+ type: string
+ example: __SERVICE-TYPE__
+ - name: service-instance-id
+ in: path
+ description: Uniquely identifies this instance of a service
+ required: true
+ type: string
+ example: __SERVICE-INSTANCE-ID__
+ - name: metaname
+ in: path
+ required: true
+ type: string
+ example: __METANAME__
+ - name: body
+ in: body
+ description: metadatum object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/metadatum"
delete:
tags:
- Business
@@ -11230,20 +14607,24 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -11263,7 +14644,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadata"
+ $ref: "#/getDefinitions/metadata"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -11272,16 +14653,19 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -11336,7 +14720,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/service-instance"
+ $ref: "#/getDefinitions/service-instance"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -11345,16 +14729,19 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -11399,7 +14786,10 @@ paths:
tags:
- Business
summary: create or update an existing service-instance
- description: create or update an existing service-instance
+ description: |
+ Create or update an existing service-instance.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance
consumes:
- application/json
@@ -11416,22 +14806,76 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: body
in: body
- description: service-instance object that needs to be created or updated
+ description: service-instance object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance.json)
required: true
schema:
$ref: "#/definitions/service-instance"
+ patch:
+ tags:
+ - Business
+ summary: update an existing service-instance
+ description: |
+ Update an existing service-instance
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: global-customer-id
+ in: path
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ required: true
+ type: string
+ example: __GLOBAL-CUSTOMER-ID__
+ - name: service-type
+ in: path
+ description: Value defined by orchestration to identify this service across ECOMP.
+ required: true
+ type: string
+ example: __SERVICE-TYPE__
+ - name: service-instance-id
+ in: path
+ description: Uniquely identifies this instance of a service
+ required: true
+ type: string
+ example: __SERVICE-INSTANCE-ID__
+ - name: body
+ in: body
+ description: service-instance object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/service-instance"
delete:
tags:
- Business
@@ -11453,16 +14897,19 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -11482,7 +14929,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/service-instances"
+ $ref: "#/getDefinitions/service-instances"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -11491,11 +14938,13 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -11527,14 +14976,16 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/BusinessCustomersCustomerServiceSubscriptionsServiceSubscription.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -11559,11 +15010,13 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}:
get:
tags:
@@ -11578,7 +15031,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/service-subscription"
+ $ref: "#/getDefinitions/service-subscription"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -11587,11 +15040,13 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -11606,7 +15061,10 @@ paths:
tags:
- Business
summary: create or update an existing service-subscription
- description: create or update an existing service-subscription
+ description: |
+ Create or update an existing service-subscription.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscription
consumes:
- application/json
@@ -11623,17 +15081,64 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: body
in: body
- description: service-subscription object that needs to be created or updated
+ description: service-subscription object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/BusinessCustomersCustomerServiceSubscriptionsServiceSubscription.json)
required: true
schema:
$ref: "#/definitions/service-subscription"
+ patch:
+ tags:
+ - Business
+ summary: update an existing service-subscription
+ description: |
+ Update an existing service-subscription
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscription
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: global-customer-id
+ in: path
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ required: true
+ type: string
+ example: __GLOBAL-CUSTOMER-ID__
+ - name: service-type
+ in: path
+ description: Value defined by orchestration to identify this service across ECOMP.
+ required: true
+ type: string
+ example: __SERVICE-TYPE__
+ - name: body
+ in: body
+ description: service-subscription object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/service-subscription"
delete:
tags:
- Business
@@ -11655,11 +15160,13 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -11679,7 +15186,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/service-subscriptions"
+ $ref: "#/getDefinitions/service-subscriptions"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -11688,6 +15195,7 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -11719,9 +15227,10 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/BusinessCustomersCustomer.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -11746,6 +15255,7 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
/business/customers/customer/{global-customer-id}:
get:
tags:
@@ -11760,7 +15270,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/customer"
+ $ref: "#/getDefinitions/customer"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -11769,6 +15279,7 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -11783,7 +15294,10 @@ paths:
tags:
- Business
summary: create or update an existing customer
- description: create or update an existing customer
+ description: |
+ Create or update an existing customer.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessCustomersCustomer
consumes:
- application/json
@@ -11800,12 +15314,52 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: body
in: body
- description: customer object that needs to be created or updated
+ description: customer object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/BusinessCustomersCustomer.json)
required: true
schema:
$ref: "#/definitions/customer"
+ patch:
+ tags:
+ - Business
+ summary: update an existing customer
+ description: |
+ Update an existing customer
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessCustomersCustomer
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: global-customer-id
+ in: path
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ required: true
+ type: string
+ example: __GLOBAL-CUSTOMER-ID__
+ - name: body
+ in: body
+ description: customer object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/customer"
delete:
tags:
- Business
@@ -11827,6 +15381,7 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -11846,7 +15401,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/customers"
+ $ref: "#/getDefinitions/customers"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/service-design-and-creation/vnf-images/vnf-image/{vnf-image-uuid}/relationship-list/relationship:
@@ -11870,9 +15425,10 @@ paths:
description: Unique ID of this asset
required: true
type: string
+ example: __VNF-IMAGE-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationVnfImagesVnfImage.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -11897,6 +15453,7 @@ paths:
description: Unique ID of this asset
required: true
type: string
+ example: __VNF-IMAGE-UUID__
/service-design-and-creation/vnf-images/vnf-image/{vnf-image-uuid}:
get:
tags:
@@ -11911,7 +15468,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vnf-image"
+ $ref: "#/getDefinitions/vnf-image"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -11920,6 +15477,7 @@ paths:
description: Unique ID of this asset
required: true
type: string
+ example: __VNF-IMAGE-UUID__
- name: application
in: query
description: The application that the image instantiates.
@@ -11939,7 +15497,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing vnf-image
- description: create or update an existing vnf-image
+ description: |
+ Create or update an existing vnf-image.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationVnfImagesVnfImage
consumes:
- application/json
@@ -11956,12 +15517,52 @@ paths:
description: Unique ID of this asset
required: true
type: string
+ example: __VNF-IMAGE-UUID__
- name: body
in: body
- description: vnf-image object that needs to be created or updated
+ description: vnf-image object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationVnfImagesVnfImage.json)
required: true
schema:
$ref: "#/definitions/vnf-image"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing vnf-image
+ description: |
+ Update an existing vnf-image
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationVnfImagesVnfImage
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-image-uuid
+ in: path
+ description: Unique ID of this asset
+ required: true
+ type: string
+ example: __VNF-IMAGE-UUID__
+ - name: body
+ in: body
+ description: vnf-image object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vnf-image"
delete:
tags:
- ServiceDesignAndCreation
@@ -11983,6 +15584,7 @@ paths:
description: Unique ID of this asset
required: true
type: string
+ example: __VNF-IMAGE-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -12002,7 +15604,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vnf-images"
+ $ref: "#/getDefinitions/vnf-images"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/service-design-and-creation/services/service/{service-id}/relationship-list/relationship:
@@ -12026,9 +15628,10 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationServicesService.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -12053,6 +15656,7 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-ID__
/service-design-and-creation/services/service/{service-id}:
get:
tags:
@@ -12067,7 +15671,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/service"
+ $ref: "#/getDefinitions/service"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -12076,6 +15680,7 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-ID__
- name: service-description
in: query
description: Description of the service
@@ -12085,7 +15690,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing service
- description: create or update an existing service
+ description: |
+ Create or update an existing service.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationServicesService
consumes:
- application/json
@@ -12102,12 +15710,52 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-ID__
- name: body
in: body
- description: service object that needs to be created or updated
+ description: service object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationServicesService.json)
required: true
schema:
$ref: "#/definitions/service"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing service
+ description: |
+ Update an existing service
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationServicesService
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: service-id
+ in: path
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ required: true
+ type: string
+ example: __SERVICE-ID__
+ - name: body
+ in: body
+ description: service object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/service"
delete:
tags:
- ServiceDesignAndCreation
@@ -12129,6 +15777,7 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -12148,7 +15797,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/services"
+ $ref: "#/getDefinitions/services"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/service-design-and-creation/service-capabilities/service-capability/{service-type}/{vnf-type}/relationship-list/relationship:
@@ -12172,14 +15821,16 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: vnf-type
in: path
description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded and clients should expect changes to occur in the future to this field as ASDC matures.
required: true
type: string
+ example: __VNF-TYPE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationServiceCapabilitiesServiceCapability.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -12204,11 +15855,13 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: vnf-type
in: path
description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded and clients should expect changes to occur in the future to this field as ASDC matures.
required: true
type: string
+ example: __VNF-TYPE__
/service-design-and-creation/service-capabilities/service-capability/{service-type}/{vnf-type}:
get:
tags:
@@ -12223,7 +15876,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/service-capability"
+ $ref: "#/getDefinitions/service-capability"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -12232,16 +15885,21 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: vnf-type
in: path
description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded and clients should expect changes to occur in the future to this field as ASDC matures.
required: true
type: string
+ example: __VNF-TYPE__
put:
tags:
- ServiceDesignAndCreation
summary: create or update an existing service-capability
- description: create or update an existing service-capability
+ description: |
+ Create or update an existing service-capability.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationServiceCapabilitiesServiceCapability
consumes:
- application/json
@@ -12258,17 +15916,64 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: vnf-type
in: path
description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded and clients should expect changes to occur in the future to this field as ASDC matures.
required: true
type: string
+ example: __VNF-TYPE__
- name: body
in: body
- description: service-capability object that needs to be created or updated
+ description: service-capability object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationServiceCapabilitiesServiceCapability.json)
required: true
schema:
$ref: "#/definitions/service-capability"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing service-capability
+ description: |
+ Update an existing service-capability
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationServiceCapabilitiesServiceCapability
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: service-type
+ in: path
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ required: true
+ type: string
+ example: __SERVICE-TYPE__
+ - name: vnf-type
+ in: path
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded and clients should expect changes to occur in the future to this field as ASDC matures.
+ required: true
+ type: string
+ example: __VNF-TYPE__
+ - name: body
+ in: body
+ description: service-capability object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/service-capability"
delete:
tags:
- ServiceDesignAndCreation
@@ -12290,11 +15995,13 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: vnf-type
in: path
description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded and clients should expect changes to occur in the future to this field as ASDC matures.
required: true
type: string
+ example: __VNF-TYPE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -12314,7 +16021,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/service-capabilities"
+ $ref: "#/getDefinitions/service-capabilities"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/service-design-and-creation/models/model/{model-name-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}/element-choice-sets/element-choice-set/{element-choice-set-uuid}/relationship-list/relationship:
@@ -12338,25 +16045,30 @@ paths:
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-NAME-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: element-choice-set-uuid
in: path
required: true
type: string
+ example: __ELEMENT-CHOICE-SET-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationModelsModelModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -12381,22 +16093,27 @@ paths:
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-NAME-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: element-choice-set-uuid
in: path
required: true
type: string
+ example: __ELEMENT-CHOICE-SET-UUID__
/service-design-and-creation/models/model/{model-name-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}/element-choice-sets/element-choice-set/{element-choice-set-uuid}:
get:
tags:
@@ -12411,7 +16128,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/element-choice-set"
+ $ref: "#/getDefinitions/element-choice-set"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -12420,22 +16137,27 @@ paths:
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-NAME-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: element-choice-set-uuid
in: path
required: true
type: string
+ example: __ELEMENT-CHOICE-SET-UUID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -12460,7 +16182,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing element-choice-set
- description: create or update an existing element-choice-set
+ description: |
+ Create or update an existing element-choice-set.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationModelsModelModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet
consumes:
- application/json
@@ -12477,28 +16202,92 @@ paths:
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-NAME-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: element-choice-set-uuid
in: path
required: true
type: string
+ example: __ELEMENT-CHOICE-SET-UUID__
- name: body
in: body
- description: element-choice-set object that needs to be created or updated
+ description: element-choice-set object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationModelsModelModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet.json)
required: true
schema:
$ref: "#/definitions/element-choice-set"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing element-choice-set
+ description: |
+ Update an existing element-choice-set
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationModelsModelModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: model-name-version-id
+ in: path
+ description: Unique identifier corresponding to one version of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-NAME-VERSION-ID__
+ - name: model-element-uuid
+ in: path
+ required: true
+ type: string
+ example: __MODEL-ELEMENT-UUID__
+ - name: model-constraint-uuid
+ in: path
+ required: true
+ type: string
+ example: __MODEL-CONSTRAINT-UUID__
+ - name: constrained-element-set-uuid
+ in: path
+ required: true
+ type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
+ - name: element-choice-set-uuid
+ in: path
+ required: true
+ type: string
+ example: __ELEMENT-CHOICE-SET-UUID__
+ - name: body
+ in: body
+ description: element-choice-set object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/element-choice-set"
delete:
tags:
- ServiceDesignAndCreation
@@ -12520,22 +16309,27 @@ paths:
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-NAME-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: element-choice-set-uuid
in: path
required: true
type: string
+ example: __ELEMENT-CHOICE-SET-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -12555,7 +16349,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/element-choice-sets"
+ $ref: "#/getDefinitions/element-choice-sets"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -12564,18 +16358,22 @@ paths:
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-NAME-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -12617,21 +16415,25 @@ paths:
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-NAME-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationModelsModelModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -12656,18 +16458,22 @@ paths:
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-NAME-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
/service-design-and-creation/models/model/{model-name-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}:
get:
tags:
@@ -12682,7 +16488,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/constrained-element-set"
+ $ref: "#/getDefinitions/constrained-element-set"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -12691,18 +16497,22 @@ paths:
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-NAME-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -12727,7 +16537,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing constrained-element-set
- description: create or update an existing constrained-element-set
+ description: |
+ Create or update an existing constrained-element-set.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationModelsModelModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet
consumes:
- application/json
@@ -12744,24 +16557,82 @@ paths:
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-NAME-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: body
in: body
- description: constrained-element-set object that needs to be created or updated
+ description: constrained-element-set object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationModelsModelModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet.json)
required: true
schema:
$ref: "#/definitions/constrained-element-set"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing constrained-element-set
+ description: |
+ Update an existing constrained-element-set
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationModelsModelModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: model-name-version-id
+ in: path
+ description: Unique identifier corresponding to one version of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-NAME-VERSION-ID__
+ - name: model-element-uuid
+ in: path
+ required: true
+ type: string
+ example: __MODEL-ELEMENT-UUID__
+ - name: model-constraint-uuid
+ in: path
+ required: true
+ type: string
+ example: __MODEL-CONSTRAINT-UUID__
+ - name: constrained-element-set-uuid
+ in: path
+ required: true
+ type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
+ - name: body
+ in: body
+ description: constrained-element-set object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/constrained-element-set"
delete:
tags:
- ServiceDesignAndCreation
@@ -12783,18 +16654,22 @@ paths:
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-NAME-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -12814,7 +16689,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/constrained-element-sets"
+ $ref: "#/getDefinitions/constrained-element-sets"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -12823,14 +16698,17 @@ paths:
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-NAME-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -12865,7 +16743,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/model-constraint"
+ $ref: "#/getDefinitions/model-constraint"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -12874,14 +16752,17 @@ paths:
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-NAME-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -12906,7 +16787,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing model-constraint
- description: create or update an existing model-constraint
+ description: |
+ Create or update an existing model-constraint.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationModelsModelModelElementsModelElementModelConstraintsModelConstraint
consumes:
- application/json
@@ -12923,20 +16807,72 @@ paths:
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-NAME-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: body
in: body
- description: model-constraint object that needs to be created or updated
+ description: model-constraint object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationModelsModelModelElementsModelElementModelConstraintsModelConstraint.json)
required: true
schema:
$ref: "#/definitions/model-constraint"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing model-constraint
+ description: |
+ Update an existing model-constraint
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationModelsModelModelElementsModelElementModelConstraintsModelConstraint
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: model-name-version-id
+ in: path
+ description: Unique identifier corresponding to one version of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-NAME-VERSION-ID__
+ - name: model-element-uuid
+ in: path
+ required: true
+ type: string
+ example: __MODEL-ELEMENT-UUID__
+ - name: model-constraint-uuid
+ in: path
+ required: true
+ type: string
+ example: __MODEL-CONSTRAINT-UUID__
+ - name: body
+ in: body
+ description: model-constraint object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/model-constraint"
delete:
tags:
- ServiceDesignAndCreation
@@ -12958,14 +16894,17 @@ paths:
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-NAME-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -12985,7 +16924,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/model-constraints"
+ $ref: "#/getDefinitions/model-constraints"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -12994,10 +16933,12 @@ paths:
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-NAME-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -13039,13 +16980,15 @@ paths:
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-NAME-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationModelsModelModelElementsModelElement.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -13070,10 +17013,12 @@ paths:
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-NAME-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
/service-design-and-creation/models/model/{model-name-version-id}/model-elements/model-element/{model-element-uuid}:
get:
tags:
@@ -13088,7 +17033,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/model-element"
+ $ref: "#/getDefinitions/model-element"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -13097,10 +17042,12 @@ paths:
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-NAME-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -13125,7 +17072,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing model-element
- description: create or update an existing model-element
+ description: |
+ Create or update an existing model-element.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationModelsModelModelElementsModelElement
consumes:
- application/json
@@ -13142,16 +17092,62 @@ paths:
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-NAME-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: body
in: body
- description: model-element object that needs to be created or updated
+ description: model-element object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationModelsModelModelElementsModelElement.json)
required: true
schema:
$ref: "#/definitions/model-element"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing model-element
+ description: |
+ Update an existing model-element
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationModelsModelModelElementsModelElement
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: model-name-version-id
+ in: path
+ description: Unique identifier corresponding to one version of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-NAME-VERSION-ID__
+ - name: model-element-uuid
+ in: path
+ required: true
+ type: string
+ example: __MODEL-ELEMENT-UUID__
+ - name: body
+ in: body
+ description: model-element object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/model-element"
delete:
tags:
- ServiceDesignAndCreation
@@ -13173,10 +17169,12 @@ paths:
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-NAME-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -13196,7 +17194,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/model-elements"
+ $ref: "#/getDefinitions/model-elements"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -13205,6 +17203,7 @@ paths:
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-NAME-VERSION-ID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -13239,7 +17238,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadatum"
+ $ref: "#/getDefinitions/metadatum"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -13248,10 +17247,12 @@ paths:
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-NAME-VERSION-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -13276,7 +17277,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing metadatum
- description: create or update an existing metadatum
+ description: |
+ Create or update an existing metadatum.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationModelsModelMetadataMetadatum
consumes:
- application/json
@@ -13293,16 +17297,62 @@ paths:
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-NAME-VERSION-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: body
in: body
- description: metadatum object that needs to be created or updated
+ description: metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationModelsModelMetadataMetadatum.json)
required: true
schema:
$ref: "#/definitions/metadatum"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing metadatum
+ description: |
+ Update an existing metadatum
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationModelsModelMetadataMetadatum
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: model-name-version-id
+ in: path
+ description: Unique identifier corresponding to one version of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-NAME-VERSION-ID__
+ - name: metaname
+ in: path
+ required: true
+ type: string
+ example: __METANAME__
+ - name: body
+ in: body
+ description: metadatum object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/metadatum"
delete:
tags:
- ServiceDesignAndCreation
@@ -13324,10 +17374,12 @@ paths:
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-NAME-VERSION-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -13347,7 +17399,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadata"
+ $ref: "#/getDefinitions/metadata"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -13356,6 +17408,7 @@ paths:
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-NAME-VERSION-ID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -13397,9 +17450,10 @@ paths:
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-NAME-VERSION-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationModelsModel.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -13424,6 +17478,7 @@ paths:
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-NAME-VERSION-ID__
/service-design-and-creation/models/model/{model-name-version-id}:
get:
tags:
@@ -13438,7 +17493,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/model"
+ $ref: "#/getDefinitions/model"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -13447,6 +17502,7 @@ paths:
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-NAME-VERSION-ID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -13471,7 +17527,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing model
- description: create or update an existing model
+ description: |
+ Create or update an existing model.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationModelsModel
consumes:
- application/json
@@ -13488,12 +17547,52 @@ paths:
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-NAME-VERSION-ID__
- name: body
in: body
- description: model object that needs to be created or updated
+ description: model object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationModelsModel.json)
required: true
schema:
$ref: "#/definitions/model"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing model
+ description: |
+ Update an existing model
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationModelsModel
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: model-name-version-id
+ in: path
+ description: Unique identifier corresponding to one version of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-NAME-VERSION-ID__
+ - name: body
+ in: body
+ description: model object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/model"
delete:
tags:
- ServiceDesignAndCreation
@@ -13515,6 +17614,7 @@ paths:
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-NAME-VERSION-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -13534,7 +17634,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/models"
+ $ref: "#/getDefinitions/models"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/related-lookups/related-lookup/{related-lookup-uuid}/relationship-list/relationship:
@@ -13557,17 +17657,20 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: related-lookup-uuid
in: path
required: true
type: string
+ example: __RELATED-LOOKUP-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -13591,14 +17694,17 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: related-lookup-uuid
in: path
required: true
type: string
+ example: __RELATED-LOOKUP-UUID__
/service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/related-lookups/related-lookup/{related-lookup-uuid}:
get:
tags:
@@ -13613,7 +17719,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/related-lookup"
+ $ref: "#/getDefinitions/related-lookup"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -13621,14 +17727,17 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: related-lookup-uuid
in: path
required: true
type: string
+ example: __RELATED-LOOKUP-UUID__
- name: named-query-name
in: query
required: false
@@ -13637,7 +17746,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing related-lookup
- description: create or update an existing related-lookup
+ description: |
+ Create or update an existing related-lookup.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup
consumes:
- application/json
@@ -13653,20 +17765,71 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: related-lookup-uuid
in: path
required: true
type: string
+ example: __RELATED-LOOKUP-UUID__
- name: body
in: body
- description: related-lookup object that needs to be created or updated
+ description: related-lookup object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup.json)
required: true
schema:
$ref: "#/definitions/related-lookup"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing related-lookup
+ description: |
+ Update an existing related-lookup
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: named-query-uuid
+ in: path
+ required: true
+ type: string
+ example: __NAMED-QUERY-UUID__
+ - name: named-query-element-uuid
+ in: path
+ required: true
+ type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
+ - name: related-lookup-uuid
+ in: path
+ required: true
+ type: string
+ example: __RELATED-LOOKUP-UUID__
+ - name: body
+ in: body
+ description: related-lookup object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/related-lookup"
delete:
tags:
- ServiceDesignAndCreation
@@ -13687,14 +17850,17 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: related-lookup-uuid
in: path
required: true
type: string
+ example: __RELATED-LOOKUP-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -13714,7 +17880,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/related-lookups"
+ $ref: "#/getDefinitions/related-lookups"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -13722,10 +17888,12 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: named-query-name
in: query
required: false
@@ -13744,7 +17912,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/property-constraint"
+ $ref: "#/getDefinitions/property-constraint"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -13752,14 +17920,17 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: property-constraint-uuid
in: path
required: true
type: string
+ example: __PROPERTY-CONSTRAINT-UUID__
- name: named-query-name
in: query
required: false
@@ -13768,7 +17939,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing property-constraint
- description: create or update an existing property-constraint
+ description: |
+ Create or update an existing property-constraint.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementPropertyConstraintsPropertyConstraint
consumes:
- application/json
@@ -13784,20 +17958,71 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: property-constraint-uuid
in: path
required: true
type: string
+ example: __PROPERTY-CONSTRAINT-UUID__
- name: body
in: body
- description: property-constraint object that needs to be created or updated
+ description: property-constraint object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementPropertyConstraintsPropertyConstraint.json)
required: true
schema:
$ref: "#/definitions/property-constraint"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing property-constraint
+ description: |
+ Update an existing property-constraint
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementPropertyConstraintsPropertyConstraint
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: named-query-uuid
+ in: path
+ required: true
+ type: string
+ example: __NAMED-QUERY-UUID__
+ - name: named-query-element-uuid
+ in: path
+ required: true
+ type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
+ - name: property-constraint-uuid
+ in: path
+ required: true
+ type: string
+ example: __PROPERTY-CONSTRAINT-UUID__
+ - name: body
+ in: body
+ description: property-constraint object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/property-constraint"
delete:
tags:
- ServiceDesignAndCreation
@@ -13818,14 +18043,17 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: property-constraint-uuid
in: path
required: true
type: string
+ example: __PROPERTY-CONSTRAINT-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -13845,7 +18073,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/property-constraints"
+ $ref: "#/getDefinitions/property-constraints"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -13853,10 +18081,12 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: named-query-name
in: query
required: false
@@ -13881,13 +18111,15 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -13911,10 +18143,12 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
/service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}:
get:
tags:
@@ -13929,7 +18163,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/named-query-element"
+ $ref: "#/getDefinitions/named-query-element"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -13937,10 +18171,12 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: named-query-name
in: query
required: false
@@ -13949,7 +18185,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing named-query-element
- description: create or update an existing named-query-element
+ description: |
+ Create or update an existing named-query-element.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement
consumes:
- application/json
@@ -13965,16 +18204,61 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: body
in: body
- description: named-query-element object that needs to be created or updated
+ description: named-query-element object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement.json)
required: true
schema:
$ref: "#/definitions/named-query-element"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing named-query-element
+ description: |
+ Update an existing named-query-element
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: named-query-uuid
+ in: path
+ required: true
+ type: string
+ example: __NAMED-QUERY-UUID__
+ - name: named-query-element-uuid
+ in: path
+ required: true
+ type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
+ - name: body
+ in: body
+ description: named-query-element object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/named-query-element"
delete:
tags:
- ServiceDesignAndCreation
@@ -13995,10 +18279,12 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -14018,7 +18304,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/named-query-elements"
+ $ref: "#/getDefinitions/named-query-elements"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14026,6 +18312,7 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-name
in: query
required: false
@@ -14050,9 +18337,10 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationNamedQueriesNamedQuery.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -14076,6 +18364,7 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
/service-design-and-creation/named-queries/named-query/{named-query-uuid}:
get:
tags:
@@ -14090,7 +18379,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/named-query"
+ $ref: "#/getDefinitions/named-query"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14098,6 +18387,7 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-name
in: query
required: false
@@ -14106,7 +18396,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing named-query
- description: create or update an existing named-query
+ description: |
+ Create or update an existing named-query.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationNamedQueriesNamedQuery
consumes:
- application/json
@@ -14122,12 +18415,51 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: body
in: body
- description: named-query object that needs to be created or updated
+ description: named-query object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/ServiceDesignAndCreationNamedQueriesNamedQuery.json)
required: true
schema:
$ref: "#/definitions/named-query"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing named-query
+ description: |
+ Update an existing named-query
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationNamedQueriesNamedQuery
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: named-query-uuid
+ in: path
+ required: true
+ type: string
+ example: __NAMED-QUERY-UUID__
+ - name: body
+ in: body
+ description: named-query object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/named-query"
delete:
tags:
- ServiceDesignAndCreation
@@ -14148,6 +18480,7 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -14167,7 +18500,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/named-queries"
+ $ref: "#/getDefinitions/named-queries"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/logical-links/logical-link/{link-name}/relationship-list/relationship:
@@ -14191,9 +18524,10 @@ paths:
description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkLogicalLinksLogicalLink.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -14218,6 +18552,7 @@ paths:
description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
required: true
type: string
+ example: __LINK-NAME__
/network/logical-links/logical-link/{link-name}:
get:
tags:
@@ -14232,7 +18567,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/logical-link"
+ $ref: "#/getDefinitions/logical-link"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14241,6 +18576,7 @@ paths:
description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: persona-model-id
in: query
description: the ASDC model id for this resource or service model.
@@ -14270,7 +18606,10 @@ paths:
tags:
- Network
summary: create or update an existing logical-link
- description: create or update an existing logical-link
+ description: |
+ Create or update an existing logical-link.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkLogicalLinksLogicalLink
consumes:
- application/json
@@ -14287,12 +18626,52 @@ paths:
description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: body
in: body
- description: logical-link object that needs to be created or updated
+ description: logical-link object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkLogicalLinksLogicalLink.json)
required: true
schema:
$ref: "#/definitions/logical-link"
+ patch:
+ tags:
+ - Network
+ summary: update an existing logical-link
+ description: |
+ Update an existing logical-link
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkLogicalLinksLogicalLink
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: link-name
+ in: path
+ description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
+ required: true
+ type: string
+ example: __LINK-NAME__
+ - name: body
+ in: body
+ description: logical-link object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/logical-link"
delete:
tags:
- Network
@@ -14314,6 +18693,7 @@ paths:
description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -14333,7 +18713,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/logical-links"
+ $ref: "#/getDefinitions/logical-links"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}/classes-of-service/class-of-service/{cos}/relationship-list/relationship:
@@ -14357,24 +18737,28 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: cos
in: path
description: unique identifier of probe
required: true
type: string
+ example: __COS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -14399,21 +18783,25 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: cos
in: path
description: unique identifier of probe
required: true
type: string
+ example: __COS__
/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}/classes-of-service/class-of-service/{cos}:
get:
tags:
@@ -14428,7 +18816,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/class-of-service"
+ $ref: "#/getDefinitions/class-of-service"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14437,26 +18825,33 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: cos
in: path
description: unique identifier of probe
required: true
type: string
+ example: __COS__
put:
tags:
- Network
summary: create or update an existing class-of-service
- description: create or update an existing class-of-service
+ description: |
+ Create or update an existing class-of-service.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService
consumes:
- application/json
@@ -14473,27 +18868,88 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: cos
in: path
description: unique identifier of probe
required: true
type: string
+ example: __COS__
- name: body
in: body
- description: class-of-service object that needs to be created or updated
+ description: class-of-service object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService.json)
required: true
schema:
$ref: "#/definitions/class-of-service"
+ patch:
+ tags:
+ - Network
+ summary: update an existing class-of-service
+ description: |
+ Update an existing class-of-service
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: site-pair-set-id
+ in: path
+ description: Unique id of site pair set.
+ required: true
+ type: string
+ example: __SITE-PAIR-SET-ID__
+ - name: routing-instance-id
+ in: path
+ description: Unique id of routing instance
+ required: true
+ type: string
+ example: __ROUTING-INSTANCE-ID__
+ - name: site-pair-id
+ in: path
+ description: unique identifier of probe
+ required: true
+ type: string
+ example: __SITE-PAIR-ID__
+ - name: cos
+ in: path
+ description: unique identifier of probe
+ required: true
+ type: string
+ example: __COS__
+ - name: body
+ in: body
+ description: class-of-service object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/class-of-service"
delete:
tags:
- Network
@@ -14515,21 +18971,25 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: cos
in: path
description: unique identifier of probe
required: true
type: string
+ example: __COS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -14549,7 +19009,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/classes-of-service"
+ $ref: "#/getDefinitions/classes-of-service"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14558,16 +19018,19 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}/relationship-list/relationship:
put:
tags:
@@ -14589,19 +19052,22 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -14626,16 +19092,19 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}:
get:
tags:
@@ -14650,7 +19119,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/site-pair"
+ $ref: "#/getDefinitions/site-pair"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14659,21 +19128,27 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
put:
tags:
- Network
summary: create or update an existing site-pair
- description: create or update an existing site-pair
+ description: |
+ Create or update an existing site-pair.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair
consumes:
- application/json
@@ -14690,22 +19165,76 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: body
in: body
- description: site-pair object that needs to be created or updated
+ description: site-pair object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair.json)
required: true
schema:
$ref: "#/definitions/site-pair"
+ patch:
+ tags:
+ - Network
+ summary: update an existing site-pair
+ description: |
+ Update an existing site-pair
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: site-pair-set-id
+ in: path
+ description: Unique id of site pair set.
+ required: true
+ type: string
+ example: __SITE-PAIR-SET-ID__
+ - name: routing-instance-id
+ in: path
+ description: Unique id of routing instance
+ required: true
+ type: string
+ example: __ROUTING-INSTANCE-ID__
+ - name: site-pair-id
+ in: path
+ description: unique identifier of probe
+ required: true
+ type: string
+ example: __SITE-PAIR-ID__
+ - name: body
+ in: body
+ description: site-pair object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/site-pair"
delete:
tags:
- Network
@@ -14727,16 +19256,19 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -14756,7 +19288,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/site-pairs"
+ $ref: "#/getDefinitions/site-pairs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14765,11 +19297,13 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/relationship-list/relationship:
put:
tags:
@@ -14791,14 +19325,16 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -14823,11 +19359,13 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}:
get:
tags:
@@ -14842,7 +19380,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/routing-instance"
+ $ref: "#/getDefinitions/routing-instance"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14851,16 +19389,21 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
put:
tags:
- Network
summary: create or update an existing routing-instance
- description: create or update an existing routing-instance
+ description: |
+ Create or update an existing routing-instance.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance
consumes:
- application/json
@@ -14877,17 +19420,64 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: body
in: body
- description: routing-instance object that needs to be created or updated
+ description: routing-instance object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance.json)
required: true
schema:
$ref: "#/definitions/routing-instance"
+ patch:
+ tags:
+ - Network
+ summary: update an existing routing-instance
+ description: |
+ Update an existing routing-instance
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: site-pair-set-id
+ in: path
+ description: Unique id of site pair set.
+ required: true
+ type: string
+ example: __SITE-PAIR-SET-ID__
+ - name: routing-instance-id
+ in: path
+ description: Unique id of routing instance
+ required: true
+ type: string
+ example: __ROUTING-INSTANCE-ID__
+ - name: body
+ in: body
+ description: routing-instance object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/routing-instance"
delete:
tags:
- Network
@@ -14909,11 +19499,13 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -14933,7 +19525,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/routing-instances"
+ $ref: "#/getDefinitions/routing-instances"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14942,6 +19534,7 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
/network/site-pair-sets/site-pair-set/{site-pair-set-id}/relationship-list/relationship:
put:
tags:
@@ -14963,9 +19556,10 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkSitePairSetsSitePairSet.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -14990,6 +19584,7 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
/network/site-pair-sets/site-pair-set/{site-pair-set-id}:
get:
tags:
@@ -15004,7 +19599,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/site-pair-set"
+ $ref: "#/getDefinitions/site-pair-set"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -15013,11 +19608,15 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
put:
tags:
- Network
summary: create or update an existing site-pair-set
- description: create or update an existing site-pair-set
+ description: |
+ Create or update an existing site-pair-set.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkSitePairSetsSitePairSet
consumes:
- application/json
@@ -15034,12 +19633,52 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: body
in: body
- description: site-pair-set object that needs to be created or updated
+ description: site-pair-set object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkSitePairSetsSitePairSet.json)
required: true
schema:
$ref: "#/definitions/site-pair-set"
+ patch:
+ tags:
+ - Network
+ summary: update an existing site-pair-set
+ description: |
+ Update an existing site-pair-set
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkSitePairSetsSitePairSet
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: site-pair-set-id
+ in: path
+ description: Unique id of site pair set.
+ required: true
+ type: string
+ example: __SITE-PAIR-SET-ID__
+ - name: body
+ in: body
+ description: site-pair-set object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/site-pair-set"
delete:
tags:
- Network
@@ -15061,6 +19700,7 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -15080,7 +19720,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/site-pair-sets"
+ $ref: "#/getDefinitions/site-pair-sets"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/vpn-bindings/vpn-binding/{vpn-id}/relationship-list/relationship:
@@ -15104,9 +19744,10 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVpnBindingsVpnBinding.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -15131,6 +19772,7 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
/network/vpn-bindings/vpn-binding/{vpn-id}:
get:
tags:
@@ -15145,7 +19787,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vpn-binding"
+ $ref: "#/getDefinitions/vpn-binding"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -15154,6 +19796,7 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
- name: vpn-name
in: query
description: VPN Name
@@ -15168,7 +19811,10 @@ paths:
tags:
- Network
summary: create or update an existing vpn-binding
- description: create or update an existing vpn-binding
+ description: |
+ Create or update an existing vpn-binding.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVpnBindingsVpnBinding
consumes:
- application/json
@@ -15185,12 +19831,52 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
- name: body
in: body
- description: vpn-binding object that needs to be created or updated
+ description: vpn-binding object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVpnBindingsVpnBinding.json)
required: true
schema:
$ref: "#/definitions/vpn-binding"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vpn-binding
+ description: |
+ Update an existing vpn-binding
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVpnBindingsVpnBinding
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vpn-id
+ in: path
+ description: VPN ID, globally unique within A&AI
+ required: true
+ type: string
+ example: __VPN-ID__
+ - name: body
+ in: body
+ description: vpn-binding object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vpn-binding"
delete:
tags:
- Network
@@ -15212,6 +19898,7 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -15231,7 +19918,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vpn-bindings"
+ $ref: "#/getDefinitions/vpn-bindings"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/vpls-pes/vpls-pe/{equipment-name}/relationship-list/relationship:
@@ -15254,9 +19941,10 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPe.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -15280,6 +19968,7 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/relationship-list/relationship:
put:
tags:
@@ -15300,14 +19989,16 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -15331,11 +20022,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -15356,24 +20049,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -15397,21 +20094,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -15432,29 +20133,34 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -15478,26 +20184,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -15512,7 +20223,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -15520,26 +20231,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -15591,7 +20307,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -15607,32 +20326,99 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -15653,26 +20439,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -15698,29 +20489,34 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -15744,26 +20540,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -15778,7 +20579,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -15786,26 +20587,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -15857,7 +20663,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -15873,32 +20682,99 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -15919,26 +20795,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -15958,7 +20839,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -15966,21 +20847,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -16016,7 +20901,10 @@ paths:
tags:
- Network
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -16032,27 +20920,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- Network
@@ -16073,21 +21021,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -16107,7 +21059,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -16115,16 +21067,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -16165,24 +21120,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -16206,21 +21165,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -16235,7 +21198,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -16243,21 +21206,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -16302,7 +21269,10 @@ paths:
tags:
- Network
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -16318,27 +21288,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- Network
@@ -16359,21 +21389,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -16393,7 +21427,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -16401,16 +21435,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -16451,19 +21488,22 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -16487,16 +21527,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -16517,24 +21560,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -16558,21 +21605,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -16587,7 +21638,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -16595,21 +21646,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -16650,7 +21705,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -16666,27 +21724,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -16707,21 +21825,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -16747,24 +21869,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -16788,21 +21914,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -16817,7 +21947,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -16825,21 +21955,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -16880,7 +22014,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -16896,27 +22033,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -16937,21 +22134,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -16971,7 +22172,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -16979,16 +22180,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -17013,7 +22217,10 @@ paths:
tags:
- Network
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface
consumes:
- application/json
@@ -17029,22 +22236,75 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- Network
@@ -17065,16 +22325,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -17094,7 +22357,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -17102,11 +22365,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -17126,7 +22391,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/p-interface"
+ $ref: "#/getDefinitions/p-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -17134,11 +22399,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -17148,7 +22415,10 @@ paths:
tags:
- Network
summary: create or update an existing p-interface
- description: create or update an existing p-interface
+ description: |
+ Create or update an existing p-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterface
consumes:
- application/json
@@ -17164,17 +22434,63 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: p-interface object that needs to be created or updated
+ description: p-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPePInterfacesPInterface.json)
required: true
schema:
$ref: "#/definitions/p-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing p-interface
+ description: |
+ Update an existing p-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: p-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/p-interface"
delete:
tags:
- Network
@@ -17195,11 +22511,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -17219,7 +22537,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/p-interfaces"
+ $ref: "#/getDefinitions/p-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -17227,6 +22545,7 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -17252,14 +22571,16 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -17283,11 +22604,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -17308,24 +22631,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -17349,21 +22676,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -17384,29 +22715,34 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -17430,26 +22766,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -17464,7 +22805,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -17472,26 +22813,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -17543,7 +22889,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -17559,32 +22908,99 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -17605,26 +23021,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -17650,29 +23071,34 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -17696,26 +23122,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -17730,7 +23161,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -17738,26 +23169,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -17809,7 +23245,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -17825,32 +23264,99 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -17871,26 +23377,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -17910,7 +23421,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -17918,21 +23429,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -17968,7 +23483,10 @@ paths:
tags:
- Network
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -17984,27 +23502,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- Network
@@ -18025,21 +23603,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -18059,7 +23641,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -18067,16 +23649,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -18117,24 +23702,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -18158,21 +23747,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -18187,7 +23780,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -18195,21 +23788,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -18254,7 +23851,10 @@ paths:
tags:
- Network
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -18270,27 +23870,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- Network
@@ -18311,21 +23971,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -18345,7 +24009,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -18353,16 +24017,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -18403,19 +24070,22 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -18439,16 +24109,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -18469,24 +24142,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -18510,21 +24187,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -18539,7 +24220,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -18547,21 +24228,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -18602,7 +24287,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -18618,27 +24306,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -18659,21 +24407,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -18699,24 +24451,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -18740,21 +24496,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -18769,7 +24529,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -18777,21 +24537,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -18832,7 +24596,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -18848,27 +24615,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -18889,21 +24716,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -18923,7 +24754,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -18931,16 +24762,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -18965,7 +24799,10 @@ paths:
tags:
- Network
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface
consumes:
- application/json
@@ -18981,22 +24818,75 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- Network
@@ -19017,16 +24907,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -19046,7 +24939,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -19054,11 +24947,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -19078,7 +24973,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interface"
+ $ref: "#/getDefinitions/lag-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -19086,11 +24981,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -19100,7 +24997,10 @@ paths:
tags:
- Network
summary: create or update an existing lag-interface
- description: create or update an existing lag-interface
+ description: |
+ Create or update an existing lag-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterface
consumes:
- application/json
@@ -19116,17 +25016,63 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: lag-interface object that needs to be created or updated
+ description: lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPeLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/lag-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing lag-interface
+ description: |
+ Update an existing lag-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: lag-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/lag-interface"
delete:
tags:
- Network
@@ -19147,11 +25093,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -19171,7 +25119,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interfaces"
+ $ref: "#/getDefinitions/lag-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -19179,6 +25127,7 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -19198,7 +25147,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vpls-pe"
+ $ref: "#/getDefinitions/vpls-pe"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -19206,6 +25155,7 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -19215,7 +25165,10 @@ paths:
tags:
- Network
summary: create or update an existing vpls-pe
- description: create or update an existing vpls-pe
+ description: |
+ Create or update an existing vpls-pe.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPe
consumes:
- application/json
@@ -19231,12 +25184,51 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: body
in: body
- description: vpls-pe object that needs to be created or updated
+ description: vpls-pe object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVplsPesVplsPe.json)
required: true
schema:
$ref: "#/definitions/vpls-pe"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vpls-pe
+ description: |
+ Update an existing vpls-pe
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPe
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: body
+ in: body
+ description: vpls-pe object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vpls-pe"
delete:
tags:
- Network
@@ -19257,6 +25249,7 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -19276,7 +25269,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vpls-pes"
+ $ref: "#/getDefinitions/vpls-pes"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/multicast-configurations/multicast-configuration/{multicast-configuration-id}/relationship-list/relationship:
@@ -19300,9 +25293,10 @@ paths:
description: Unique id of multicast configuration.
required: true
type: string
+ example: __MULTICAST-CONFIGURATION-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkMulticastConfigurationsMulticastConfiguration.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -19327,6 +25321,7 @@ paths:
description: Unique id of multicast configuration.
required: true
type: string
+ example: __MULTICAST-CONFIGURATION-ID__
/network/multicast-configurations/multicast-configuration/{multicast-configuration-id}:
get:
tags:
@@ -19341,7 +25336,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/multicast-configuration"
+ $ref: "#/getDefinitions/multicast-configuration"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -19350,11 +25345,15 @@ paths:
description: Unique id of multicast configuration.
required: true
type: string
+ example: __MULTICAST-CONFIGURATION-ID__
put:
tags:
- Network
summary: create or update an existing multicast-configuration
- description: create or update an existing multicast-configuration
+ description: |
+ Create or update an existing multicast-configuration.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkMulticastConfigurationsMulticastConfiguration
consumes:
- application/json
@@ -19371,12 +25370,52 @@ paths:
description: Unique id of multicast configuration.
required: true
type: string
+ example: __MULTICAST-CONFIGURATION-ID__
- name: body
in: body
- description: multicast-configuration object that needs to be created or updated
+ description: multicast-configuration object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkMulticastConfigurationsMulticastConfiguration.json)
required: true
schema:
$ref: "#/definitions/multicast-configuration"
+ patch:
+ tags:
+ - Network
+ summary: update an existing multicast-configuration
+ description: |
+ Update an existing multicast-configuration
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkMulticastConfigurationsMulticastConfiguration
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: multicast-configuration-id
+ in: path
+ description: Unique id of multicast configuration.
+ required: true
+ type: string
+ example: __MULTICAST-CONFIGURATION-ID__
+ - name: body
+ in: body
+ description: multicast-configuration object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/multicast-configuration"
delete:
tags:
- Network
@@ -19398,6 +25437,7 @@ paths:
description: Unique id of multicast configuration.
required: true
type: string
+ example: __MULTICAST-CONFIGURATION-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -19417,7 +25457,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/multicast-configurations"
+ $ref: "#/getDefinitions/multicast-configurations"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}/cvlan-tags/cvlan-tag-entry/{cvlan-tag}/relationship-list/relationship:
@@ -19441,20 +25481,23 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: cvlan-tag
in: path
description: See mis-na-virtualization-platform.yang
required: true
type: integer
format: int64
+ example: __CVLAN-TAG__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -19479,17 +25522,20 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: cvlan-tag
in: path
description: See mis-na-virtualization-platform.yang
required: true
type: integer
format: int64
+ example: __CVLAN-TAG__
/network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}/cvlan-tags/cvlan-tag-entry/{cvlan-tag}:
get:
tags:
@@ -19504,7 +25550,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/cvlan-tag-entry"
+ $ref: "#/getDefinitions/cvlan-tag-entry"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -19513,17 +25559,20 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: cvlan-tag
in: path
description: See mis-na-virtualization-platform.yang
required: true
type: integer
format: int64
+ example: __CVLAN-TAG__
- name: vnf-name
in: query
description: Name of VNF.
@@ -19583,7 +25632,10 @@ paths:
tags:
- Network
summary: create or update an existing cvlan-tag-entry
- description: create or update an existing cvlan-tag-entry
+ description: |
+ Create or update an existing cvlan-tag-entry.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry
consumes:
- application/json
@@ -19600,23 +25652,78 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: cvlan-tag
in: path
description: See mis-na-virtualization-platform.yang
required: true
type: integer
format: int64
+ example: __CVLAN-TAG__
- name: body
in: body
- description: cvlan-tag-entry object that needs to be created or updated
+ description: cvlan-tag-entry object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry.json)
required: true
schema:
$ref: "#/definitions/cvlan-tag-entry"
+ patch:
+ tags:
+ - Network
+ summary: update an existing cvlan-tag-entry
+ description: |
+ Update an existing cvlan-tag-entry
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-id
+ in: path
+ description: Unique ID of the interface
+ required: true
+ type: string
+ example: __INTERFACE-ID__
+ - name: cvlan-tag
+ in: path
+ description: See mis-na-virtualization-platform.yang
+ required: true
+ type: integer
+ format: int64
+ example: __CVLAN-TAG__
+ - name: body
+ in: body
+ description: cvlan-tag-entry object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/cvlan-tag-entry"
delete:
tags:
- Network
@@ -19638,17 +25745,20 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: cvlan-tag
in: path
description: See mis-na-virtualization-platform.yang
required: true
type: integer
format: int64
+ example: __CVLAN-TAG__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -19668,7 +25778,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/cvlan-tags"
+ $ref: "#/getDefinitions/cvlan-tags"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -19677,11 +25787,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -19758,14 +25870,16 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVcesVcePortGroupsPortGroup.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -19790,11 +25904,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
/network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}:
get:
tags:
@@ -19809,7 +25925,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/port-group"
+ $ref: "#/getDefinitions/port-group"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -19818,11 +25934,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -19882,7 +26000,10 @@ paths:
tags:
- Network
summary: create or update an existing port-group
- description: create or update an existing port-group
+ description: |
+ Create or update an existing port-group.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVcesVcePortGroupsPortGroup
consumes:
- application/json
@@ -19899,17 +26020,64 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: body
in: body
- description: port-group object that needs to be created or updated
+ description: port-group object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVcesVcePortGroupsPortGroup.json)
required: true
schema:
$ref: "#/definitions/port-group"
+ patch:
+ tags:
+ - Network
+ summary: update an existing port-group
+ description: |
+ Update an existing port-group
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVcesVcePortGroupsPortGroup
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-id
+ in: path
+ description: Unique ID of the interface
+ required: true
+ type: string
+ example: __INTERFACE-ID__
+ - name: body
+ in: body
+ description: port-group object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/port-group"
delete:
tags:
- Network
@@ -19931,11 +26099,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -19955,7 +26125,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/port-groups"
+ $ref: "#/getDefinitions/port-groups"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -19964,6 +26134,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -20025,9 +26196,10 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVcesVce.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -20052,6 +26224,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
/network/vces/vce/{vnf-id}:
get:
tags:
@@ -20066,7 +26239,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vce"
+ $ref: "#/getDefinitions/vce"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -20075,6 +26248,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -20119,7 +26293,10 @@ paths:
tags:
- Network
summary: create or update an existing vce
- description: create or update an existing vce
+ description: |
+ Create or update an existing vce.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVcesVce
consumes:
- application/json
@@ -20136,12 +26313,52 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: body
in: body
- description: vce object that needs to be created or updated
+ description: vce object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVcesVce.json)
required: true
schema:
$ref: "#/definitions/vce"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vce
+ description: |
+ Update an existing vce
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVcesVce
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: body
+ in: body
+ description: vce object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vce"
delete:
tags:
- Network
@@ -20163,6 +26380,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -20182,7 +26400,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vces"
+ $ref: "#/getDefinitions/vces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/vnfcs/vnfc/{vnfc-name}/relationship-list/relationship:
@@ -20206,9 +26424,10 @@ paths:
description: Unique ID of vnfc.
required: true
type: string
+ example: __VNFC-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVnfcsVnfc.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -20233,6 +26452,7 @@ paths:
description: Unique ID of vnfc.
required: true
type: string
+ example: __VNFC-NAME__
/network/vnfcs/vnfc/{vnfc-name}:
get:
tags:
@@ -20247,7 +26467,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vnfc"
+ $ref: "#/getDefinitions/vnfc"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -20256,6 +26476,7 @@ paths:
description: Unique ID of vnfc.
required: true
type: string
+ example: __VNFC-NAME__
- name: vnfc-function-code
in: query
description: function code
@@ -20293,7 +26514,10 @@ paths:
tags:
- Network
summary: create or update an existing vnfc
- description: create or update an existing vnfc
+ description: |
+ Create or update an existing vnfc.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVnfcsVnfc
consumes:
- application/json
@@ -20310,12 +26534,52 @@ paths:
description: Unique ID of vnfc.
required: true
type: string
+ example: __VNFC-NAME__
- name: body
in: body
- description: vnfc object that needs to be created or updated
+ description: vnfc object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkVnfcsVnfc.json)
required: true
schema:
$ref: "#/definitions/vnfc"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vnfc
+ description: |
+ Update an existing vnfc
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVnfcsVnfc
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnfc-name
+ in: path
+ description: Unique ID of vnfc.
+ required: true
+ type: string
+ example: __VNFC-NAME__
+ - name: body
+ in: body
+ description: vnfc object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vnfc"
delete:
tags:
- Network
@@ -20337,6 +26601,7 @@ paths:
description: Unique ID of vnfc.
required: true
type: string
+ example: __VNFC-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -20356,7 +26621,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vnfcs"
+ $ref: "#/getDefinitions/vnfcs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/l3-networks/l3-network/{network-id}/subnets/subnet/{subnet-id}/relationship-list/relationship:
@@ -20380,14 +26645,16 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: subnet-id
in: path
description: Subnet ID, should be UUID.
required: true
type: string
+ example: __SUBNET-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkL3NetworksL3NetworkSubnetsSubnet.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -20412,11 +26679,13 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: subnet-id
in: path
description: Subnet ID, should be UUID.
required: true
type: string
+ example: __SUBNET-ID__
/network/l3-networks/l3-network/{network-id}/subnets/subnet/{subnet-id}:
get:
tags:
@@ -20431,7 +26700,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/subnet"
+ $ref: "#/getDefinitions/subnet"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -20440,11 +26709,13 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: subnet-id
in: path
description: Subnet ID, should be UUID.
required: true
type: string
+ example: __SUBNET-ID__
- name: network-name
in: query
description: Name of the network, governed by some naming convention..
@@ -20494,7 +26765,10 @@ paths:
tags:
- Network
summary: create or update an existing subnet
- description: create or update an existing subnet
+ description: |
+ Create or update an existing subnet.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkL3NetworksL3NetworkSubnetsSubnet
consumes:
- application/json
@@ -20511,17 +26785,64 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: subnet-id
in: path
description: Subnet ID, should be UUID.
required: true
type: string
+ example: __SUBNET-ID__
- name: body
in: body
- description: subnet object that needs to be created or updated
+ description: subnet object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkL3NetworksL3NetworkSubnetsSubnet.json)
required: true
schema:
$ref: "#/definitions/subnet"
+ patch:
+ tags:
+ - Network
+ summary: update an existing subnet
+ description: |
+ Update an existing subnet
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkL3NetworksL3NetworkSubnetsSubnet
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: network-id
+ in: path
+ description: Network ID, should be uuid. Unique across A&AI.
+ required: true
+ type: string
+ example: __NETWORK-ID__
+ - name: subnet-id
+ in: path
+ description: Subnet ID, should be UUID.
+ required: true
+ type: string
+ example: __SUBNET-ID__
+ - name: body
+ in: body
+ description: subnet object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/subnet"
delete:
tags:
- Network
@@ -20543,11 +26864,13 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: subnet-id
in: path
description: Subnet ID, should be UUID.
required: true
type: string
+ example: __SUBNET-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -20567,7 +26890,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/subnets"
+ $ref: "#/getDefinitions/subnets"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -20576,6 +26899,7 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: network-name
in: query
description: Name of the network, governed by some naming convention..
@@ -20637,15 +26961,17 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: vlan-id-inner
in: path
description: id.
required: true
type: integer
format: int64
+ example: __VLAN-ID-INNER__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -20670,12 +26996,14 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: vlan-id-inner
in: path
description: id.
required: true
type: integer
format: int64
+ example: __VLAN-ID-INNER__
/network/l3-networks/l3-network/{network-id}/ctag-assignments/ctag-assignment/{vlan-id-inner}:
get:
tags:
@@ -20690,7 +27018,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/ctag-assignment"
+ $ref: "#/getDefinitions/ctag-assignment"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -20699,12 +27027,14 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: vlan-id-inner
in: path
description: id.
required: true
type: integer
format: int64
+ example: __VLAN-ID-INNER__
- name: network-name
in: query
description: Name of the network, governed by some naming convention..
@@ -20749,7 +27079,10 @@ paths:
tags:
- Network
summary: create or update an existing ctag-assignment
- description: create or update an existing ctag-assignment
+ description: |
+ Create or update an existing ctag-assignment.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment
consumes:
- application/json
@@ -20766,18 +27099,66 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: vlan-id-inner
in: path
description: id.
required: true
type: integer
format: int64
+ example: __VLAN-ID-INNER__
- name: body
in: body
- description: ctag-assignment object that needs to be created or updated
+ description: ctag-assignment object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment.json)
required: true
schema:
$ref: "#/definitions/ctag-assignment"
+ patch:
+ tags:
+ - Network
+ summary: update an existing ctag-assignment
+ description: |
+ Update an existing ctag-assignment
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: network-id
+ in: path
+ description: Network ID, should be uuid. Unique across A&AI.
+ required: true
+ type: string
+ example: __NETWORK-ID__
+ - name: vlan-id-inner
+ in: path
+ description: id.
+ required: true
+ type: integer
+ format: int64
+ example: __VLAN-ID-INNER__
+ - name: body
+ in: body
+ description: ctag-assignment object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/ctag-assignment"
delete:
tags:
- Network
@@ -20799,12 +27180,14 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: vlan-id-inner
in: path
description: id.
required: true
type: integer
format: int64
+ example: __VLAN-ID-INNER__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -20824,7 +27207,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/ctag-assignments"
+ $ref: "#/getDefinitions/ctag-assignments"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -20833,6 +27216,7 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: network-name
in: query
description: Name of the network, governed by some naming convention..
@@ -20894,14 +27278,16 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: segmentation-id
in: path
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __SEGMENTATION-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -20926,11 +27312,13 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: segmentation-id
in: path
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __SEGMENTATION-ID__
/network/l3-networks/l3-network/{network-id}/segmentation-assignments/segmentation-assignment/{segmentation-id}:
get:
tags:
@@ -20945,7 +27333,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/segmentation-assignment"
+ $ref: "#/getDefinitions/segmentation-assignment"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -20954,11 +27342,13 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: segmentation-id
in: path
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __SEGMENTATION-ID__
- name: network-name
in: query
description: Name of the network, governed by some naming convention..
@@ -21003,7 +27393,10 @@ paths:
tags:
- Network
summary: create or update an existing segmentation-assignment
- description: create or update an existing segmentation-assignment
+ description: |
+ Create or update an existing segmentation-assignment.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment
consumes:
- application/json
@@ -21020,17 +27413,64 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: segmentation-id
in: path
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __SEGMENTATION-ID__
- name: body
in: body
- description: segmentation-assignment object that needs to be created or updated
+ description: segmentation-assignment object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment.json)
required: true
schema:
$ref: "#/definitions/segmentation-assignment"
+ patch:
+ tags:
+ - Network
+ summary: update an existing segmentation-assignment
+ description: |
+ Update an existing segmentation-assignment
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: network-id
+ in: path
+ description: Network ID, should be uuid. Unique across A&AI.
+ required: true
+ type: string
+ example: __NETWORK-ID__
+ - name: segmentation-id
+ in: path
+ description: Route Table Reference id, UUID assigned to this instance.
+ required: true
+ type: string
+ example: __SEGMENTATION-ID__
+ - name: body
+ in: body
+ description: segmentation-assignment object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/segmentation-assignment"
delete:
tags:
- Network
@@ -21052,11 +27492,13 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: segmentation-id
in: path
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __SEGMENTATION-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -21076,7 +27518,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/segmentation-assignments"
+ $ref: "#/getDefinitions/segmentation-assignments"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -21085,6 +27527,7 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: network-name
in: query
description: Name of the network, governed by some naming convention..
@@ -21146,9 +27589,10 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkL3NetworksL3Network.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -21173,6 +27617,7 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
/network/l3-networks/l3-network/{network-id}:
get:
tags:
@@ -21187,7 +27632,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-network"
+ $ref: "#/getDefinitions/l3-network"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -21196,6 +27641,7 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: network-name
in: query
description: Name of the network, governed by some naming convention..
@@ -21240,7 +27686,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-network
- description: create or update an existing l3-network
+ description: |
+ Create or update an existing l3-network.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkL3NetworksL3Network
consumes:
- application/json
@@ -21257,12 +27706,52 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: body
in: body
- description: l3-network object that needs to be created or updated
+ description: l3-network object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkL3NetworksL3Network.json)
required: true
schema:
$ref: "#/definitions/l3-network"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-network
+ description: |
+ Update an existing l3-network
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkL3NetworksL3Network
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: network-id
+ in: path
+ description: Network ID, should be uuid. Unique across A&AI.
+ required: true
+ type: string
+ example: __NETWORK-ID__
+ - name: body
+ in: body
+ description: l3-network object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-network"
delete:
tags:
- Network
@@ -21284,6 +27773,7 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -21303,7 +27793,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-networks"
+ $ref: "#/getDefinitions/l3-networks"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/network-policies/network-policy/{network-policy-id}/relationship-list/relationship:
@@ -21327,9 +27817,10 @@ paths:
description: UUID representing unique key to this instance
required: true
type: string
+ example: __NETWORK-POLICY-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNetworkPoliciesNetworkPolicy.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -21354,6 +27845,7 @@ paths:
description: UUID representing unique key to this instance
required: true
type: string
+ example: __NETWORK-POLICY-ID__
/network/network-policies/network-policy/{network-policy-id}:
get:
tags:
@@ -21368,7 +27860,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/network-policy"
+ $ref: "#/getDefinitions/network-policy"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -21377,6 +27869,7 @@ paths:
description: UUID representing unique key to this instance
required: true
type: string
+ example: __NETWORK-POLICY-ID__
- name: network-policy-fqdn
in: query
description: Contrail FQDN for the policy
@@ -21386,7 +27879,10 @@ paths:
tags:
- Network
summary: create or update an existing network-policy
- description: create or update an existing network-policy
+ description: |
+ Create or update an existing network-policy.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNetworkPoliciesNetworkPolicy
consumes:
- application/json
@@ -21403,12 +27899,52 @@ paths:
description: UUID representing unique key to this instance
required: true
type: string
+ example: __NETWORK-POLICY-ID__
- name: body
in: body
- description: network-policy object that needs to be created or updated
+ description: network-policy object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNetworkPoliciesNetworkPolicy.json)
required: true
schema:
$ref: "#/definitions/network-policy"
+ patch:
+ tags:
+ - Network
+ summary: update an existing network-policy
+ description: |
+ Update an existing network-policy
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNetworkPoliciesNetworkPolicy
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: network-policy-id
+ in: path
+ description: UUID representing unique key to this instance
+ required: true
+ type: string
+ example: __NETWORK-POLICY-ID__
+ - name: body
+ in: body
+ description: network-policy object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/network-policy"
delete:
tags:
- Network
@@ -21430,6 +27966,7 @@ paths:
description: UUID representing unique key to this instance
required: true
type: string
+ example: __NETWORK-POLICY-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -21449,7 +27986,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/network-policies"
+ $ref: "#/getDefinitions/network-policies"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/generic-vnfs/generic-vnf/{vnf-id}/relationship-list/relationship:
@@ -21473,9 +28010,10 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -21500,6 +28038,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -21521,19 +28060,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -21558,16 +28100,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -21589,24 +28134,28 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -21631,21 +28180,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -21660,7 +28213,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -21669,21 +28222,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -21793,7 +28350,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -21810,27 +28370,88 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -21852,21 +28473,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -21893,24 +28518,28 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -21935,21 +28564,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -21964,7 +28597,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -21973,21 +28606,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -22097,7 +28734,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -22114,27 +28754,88 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -22156,21 +28857,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -22190,7 +28895,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -22199,16 +28904,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: vnf-name
in: query
description: Name of VNF.
@@ -22302,7 +29010,10 @@ paths:
tags:
- Network
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -22319,22 +29030,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- Network
@@ -22356,16 +29121,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -22385,7 +29153,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -22394,11 +29162,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -22498,19 +29268,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -22535,16 +29308,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -22559,7 +29335,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -22568,16 +29344,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -22680,7 +29459,10 @@ paths:
tags:
- Network
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -22697,22 +29479,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- Network
@@ -22734,16 +29570,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -22763,7 +29602,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -22772,11 +29611,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -22876,14 +29717,16 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -22908,11 +29751,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -22934,19 +29779,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -22971,16 +29819,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -22995,7 +29846,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -23004,16 +29855,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -23112,7 +29966,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -23129,22 +29986,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -23166,16 +30077,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -23202,19 +30116,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -23239,16 +30156,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -23263,7 +30183,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -23272,16 +30192,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -23380,7 +30303,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -23397,22 +30323,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -23434,16 +30414,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -23463,7 +30446,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -23472,11 +30455,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -23559,7 +30544,10 @@ paths:
tags:
- Network
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterface
consumes:
- application/json
@@ -23576,17 +30564,64 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- Network
@@ -23608,11 +30643,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -23632,7 +30669,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -23641,6 +30678,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -23725,14 +30763,16 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -23757,11 +30797,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -23783,24 +30825,28 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -23825,21 +30871,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -23861,29 +30911,34 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -23908,26 +30963,31 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -23942,7 +31002,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -23951,26 +31011,31 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -24080,7 +31145,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -24097,32 +31165,100 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -24144,26 +31280,31 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -24190,29 +31331,34 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -24237,26 +31383,31 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -24271,7 +31422,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -24280,26 +31431,31 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -24409,7 +31565,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -24426,32 +31585,100 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -24473,26 +31700,31 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -24512,7 +31744,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -24521,21 +31753,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: vnf-name
in: query
description: Name of VNF.
@@ -24629,7 +31865,10 @@ paths:
tags:
- Network
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -24646,27 +31885,88 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- Network
@@ -24688,21 +31988,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -24722,7 +32026,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -24731,16 +32035,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -24840,24 +32147,28 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -24882,21 +32193,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -24911,7 +32226,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -24920,21 +32235,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -25037,7 +32356,10 @@ paths:
tags:
- Network
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -25054,27 +32376,88 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- Network
@@ -25096,21 +32479,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -25130,7 +32517,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -25139,16 +32526,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -25248,19 +32638,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -25285,16 +32678,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -25316,24 +32712,28 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -25358,21 +32758,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -25387,7 +32791,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -25396,21 +32800,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -25509,7 +32917,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -25526,27 +32937,88 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -25568,21 +33040,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -25609,24 +33085,28 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -25651,21 +33131,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -25680,7 +33164,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -25689,21 +33173,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -25802,7 +33290,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -25819,27 +33310,88 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -25861,21 +33413,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -25895,7 +33451,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -25904,16 +33460,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -25996,7 +33555,10 @@ paths:
tags:
- Network
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface
consumes:
- application/json
@@ -26013,22 +33575,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- Network
@@ -26050,16 +33666,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -26079,7 +33698,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -26088,11 +33707,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -26170,7 +33791,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interface"
+ $ref: "#/getDefinitions/lag-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -26179,11 +33800,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -26251,7 +33874,10 @@ paths:
tags:
- Network
summary: create or update an existing lag-interface
- description: create or update an existing lag-interface
+ description: |
+ Create or update an existing lag-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterface
consumes:
- application/json
@@ -26268,17 +33894,64 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: lag-interface object that needs to be created or updated
+ description: lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/lag-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing lag-interface
+ description: |
+ Update an existing lag-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: lag-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/lag-interface"
delete:
tags:
- Network
@@ -26300,11 +33973,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -26324,7 +33999,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interfaces"
+ $ref: "#/getDefinitions/lag-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -26333,6 +34008,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -26417,14 +34093,16 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vf-module-id
in: path
description: Unique ID of vf-module.
required: true
type: string
+ example: __VF-MODULE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfVfModulesVfModule.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -26449,11 +34127,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vf-module-id
in: path
description: Unique ID of vf-module.
required: true
type: string
+ example: __VF-MODULE-ID__
/network/generic-vnfs/generic-vnf/{vnf-id}/vf-modules/vf-module/{vf-module-id}:
get:
tags:
@@ -26468,7 +34148,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vf-module"
+ $ref: "#/getDefinitions/vf-module"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -26477,11 +34157,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vf-module-id
in: path
description: Unique ID of vf-module.
required: true
type: string
+ example: __VF-MODULE-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -26584,7 +34266,10 @@ paths:
tags:
- Network
summary: create or update an existing vf-module
- description: create or update an existing vf-module
+ description: |
+ Create or update an existing vf-module.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfVfModulesVfModule
consumes:
- application/json
@@ -26601,17 +34286,64 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vf-module-id
in: path
description: Unique ID of vf-module.
required: true
type: string
+ example: __VF-MODULE-ID__
- name: body
in: body
- description: vf-module object that needs to be created or updated
+ description: vf-module object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnfVfModulesVfModule.json)
required: true
schema:
$ref: "#/definitions/vf-module"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vf-module
+ description: |
+ Update an existing vf-module
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfVfModulesVfModule
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: vf-module-id
+ in: path
+ description: Unique ID of vf-module.
+ required: true
+ type: string
+ example: __VF-MODULE-ID__
+ - name: body
+ in: body
+ description: vf-module object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vf-module"
delete:
tags:
- Network
@@ -26633,11 +34365,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vf-module-id
in: path
description: Unique ID of vf-module.
required: true
type: string
+ example: __VF-MODULE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -26657,7 +34391,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vf-modules"
+ $ref: "#/getDefinitions/vf-modules"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -26666,6 +34400,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -26743,7 +34478,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/generic-vnf"
+ $ref: "#/getDefinitions/generic-vnf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -26752,6 +34487,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -26819,7 +34555,10 @@ paths:
tags:
- Network
summary: create or update an existing generic-vnf
- description: create or update an existing generic-vnf
+ description: |
+ Create or update an existing generic-vnf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnf
consumes:
- application/json
@@ -26836,12 +34575,52 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: body
in: body
- description: generic-vnf object that needs to be created or updated
+ description: generic-vnf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkGenericVnfsGenericVnf.json)
required: true
schema:
$ref: "#/definitions/generic-vnf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing generic-vnf
+ description: |
+ Update an existing generic-vnf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: body
+ in: body
+ description: generic-vnf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/generic-vnf"
delete:
tags:
- Network
@@ -26863,6 +34642,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -26882,7 +34662,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/generic-vnfs"
+ $ref: "#/getDefinitions/generic-vnfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/lag-links/lag-link/{link-name}/relationship-list/relationship:
@@ -26906,9 +34686,10 @@ paths:
description: Alphabetical concatenation of lag-interface names
required: true
type: string
+ example: __LINK-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkLagLinksLagLink.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -26933,6 +34714,7 @@ paths:
description: Alphabetical concatenation of lag-interface names
required: true
type: string
+ example: __LINK-NAME__
/network/lag-links/lag-link/{link-name}:
get:
tags:
@@ -26947,7 +34729,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-link"
+ $ref: "#/getDefinitions/lag-link"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -26956,11 +34738,15 @@ paths:
description: Alphabetical concatenation of lag-interface names
required: true
type: string
+ example: __LINK-NAME__
put:
tags:
- Network
summary: create or update an existing lag-link
- description: create or update an existing lag-link
+ description: |
+ Create or update an existing lag-link.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkLagLinksLagLink
consumes:
- application/json
@@ -26977,12 +34763,52 @@ paths:
description: Alphabetical concatenation of lag-interface names
required: true
type: string
+ example: __LINK-NAME__
- name: body
in: body
- description: lag-link object that needs to be created or updated
+ description: lag-link object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkLagLinksLagLink.json)
required: true
schema:
$ref: "#/definitions/lag-link"
+ patch:
+ tags:
+ - Network
+ summary: update an existing lag-link
+ description: |
+ Update an existing lag-link
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkLagLinksLagLink
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: link-name
+ in: path
+ description: Alphabetical concatenation of lag-interface names
+ required: true
+ type: string
+ example: __LINK-NAME__
+ - name: body
+ in: body
+ description: lag-link object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/lag-link"
delete:
tags:
- Network
@@ -27004,6 +34830,7 @@ paths:
description: Alphabetical concatenation of lag-interface names
required: true
type: string
+ example: __LINK-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -27023,7 +34850,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-links"
+ $ref: "#/getDefinitions/lag-links"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/newvces/newvce/{vnf-id2}/relationship-list/relationship:
@@ -27047,9 +34874,10 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvce.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -27074,6 +34902,7 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -27095,19 +34924,22 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -27132,16 +34964,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -27163,24 +34998,28 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -27205,21 +35044,25 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -27234,7 +35077,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -27243,21 +35086,25 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -27329,7 +35176,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -27346,27 +35196,88 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -27388,21 +35299,25 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -27429,24 +35344,28 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -27471,21 +35390,25 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -27500,7 +35423,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -27509,21 +35432,25 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -27595,7 +35522,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -27612,27 +35542,88 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -27654,21 +35645,25 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -27688,7 +35683,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -27697,16 +35692,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: vnf-name
in: query
description: Name of VNF.
@@ -27762,7 +35760,10 @@ paths:
tags:
- Network
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -27779,22 +35780,76 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- Network
@@ -27816,16 +35871,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -27845,7 +35903,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -27854,11 +35912,13 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -27920,19 +35980,22 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -27957,16 +36020,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -27981,7 +36047,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -27990,16 +36056,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -28064,7 +36133,10 @@ paths:
tags:
- Network
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -28081,22 +36153,76 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- Network
@@ -28118,16 +36244,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -28147,7 +36276,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -28156,11 +36285,13 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -28222,14 +36353,16 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -28254,11 +36387,13 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -28280,19 +36415,22 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -28317,16 +36455,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -28341,7 +36482,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -28350,16 +36491,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -28420,7 +36564,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -28437,22 +36584,76 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -28474,16 +36675,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -28510,19 +36714,22 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -28547,16 +36754,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -28571,7 +36781,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -28580,16 +36790,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -28650,7 +36863,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -28667,22 +36883,76 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -28704,16 +36974,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -28733,7 +37006,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -28742,11 +37015,13 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -28791,7 +37066,10 @@ paths:
tags:
- Network
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterface
consumes:
- application/json
@@ -28808,17 +37086,64 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- Network
@@ -28840,11 +37165,13 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -28864,7 +37191,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -28873,6 +37200,7 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: vnf-name
in: query
description: Name of VNF.
@@ -28912,7 +37240,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/newvce"
+ $ref: "#/getDefinitions/newvce"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -28921,6 +37249,7 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: vnf-name
in: query
description: Name of VNF.
@@ -28950,7 +37279,10 @@ paths:
tags:
- Network
summary: create or update an existing newvce
- description: create or update an existing newvce
+ description: |
+ Create or update an existing newvce.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvce
consumes:
- application/json
@@ -28967,12 +37299,52 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: body
in: body
- description: newvce object that needs to be created or updated
+ description: newvce object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkNewvcesNewvce.json)
required: true
schema:
$ref: "#/definitions/newvce"
+ patch:
+ tags:
+ - Network
+ summary: update an existing newvce
+ description: |
+ Update an existing newvce
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvce
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: body
+ in: body
+ description: newvce object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/newvce"
delete:
tags:
- Network
@@ -28994,6 +37366,7 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -29013,7 +37386,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/newvces"
+ $ref: "#/getDefinitions/newvces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/pnfs/pnf/{pnf-name}/relationship-list/relationship:
@@ -29037,9 +37410,10 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -29064,6 +37438,7 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/relationship-list/relationship:
put:
tags:
@@ -29085,14 +37460,16 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -29117,11 +37494,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -29143,24 +37522,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -29185,21 +37568,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -29221,29 +37608,34 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -29268,26 +37660,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -29302,7 +37699,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -29311,26 +37708,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: orchestration-status
in: query
description: orchestration-status is the status of orchestration on the PNF.
@@ -29382,7 +37784,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -29399,32 +37804,100 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -29446,26 +37919,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -29492,29 +37970,34 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -29539,26 +38022,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -29573,7 +38061,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -29582,26 +38070,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: orchestration-status
in: query
description: orchestration-status is the status of orchestration on the PNF.
@@ -29653,7 +38146,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -29670,32 +38166,100 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -29717,26 +38281,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -29756,7 +38325,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -29765,21 +38334,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: orchestration-status
in: query
description: orchestration-status is the status of orchestration on the PNF.
@@ -29815,7 +38388,10 @@ paths:
tags:
- Network
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -29832,27 +38408,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- Network
@@ -29874,21 +38511,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -29908,7 +38549,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -29917,16 +38558,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: orchestration-status
in: query
description: orchestration-status is the status of orchestration on the PNF.
@@ -29968,24 +38612,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -30010,21 +38658,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -30039,7 +38691,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -30048,21 +38700,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: orchestration-status
in: query
description: orchestration-status is the status of orchestration on the PNF.
@@ -30107,7 +38763,10 @@ paths:
tags:
- Network
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -30124,27 +38783,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- Network
@@ -30166,21 +38886,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -30200,7 +38924,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -30209,16 +38933,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: orchestration-status
in: query
description: orchestration-status is the status of orchestration on the PNF.
@@ -30260,19 +38987,22 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -30297,16 +39027,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -30328,24 +39061,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -30370,21 +39107,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -30399,7 +39140,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -30408,21 +39149,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: orchestration-status
in: query
description: orchestration-status is the status of orchestration on the PNF.
@@ -30463,7 +39208,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -30480,27 +39228,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -30522,21 +39331,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -30563,24 +39376,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -30605,21 +39422,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -30634,7 +39455,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -30643,21 +39464,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: orchestration-status
in: query
description: orchestration-status is the status of orchestration on the PNF.
@@ -30698,7 +39523,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -30715,27 +39543,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -30757,21 +39646,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -30791,7 +39684,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -30800,16 +39693,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: orchestration-status
in: query
description: orchestration-status is the status of orchestration on the PNF.
@@ -30834,7 +39730,10 @@ paths:
tags:
- Network
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface
consumes:
- application/json
@@ -30851,22 +39750,76 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- Network
@@ -30888,16 +39841,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -30917,7 +39873,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -30926,11 +39882,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: orchestration-status
in: query
description: orchestration-status is the status of orchestration on the PNF.
@@ -30950,7 +39908,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/p-interface"
+ $ref: "#/getDefinitions/p-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -30959,11 +39917,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: orchestration-status
in: query
description: orchestration-status is the status of orchestration on the PNF.
@@ -30973,7 +39933,10 @@ paths:
tags:
- Network
summary: create or update an existing p-interface
- description: create or update an existing p-interface
+ description: |
+ Create or update an existing p-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterface
consumes:
- application/json
@@ -30990,17 +39953,64 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: p-interface object that needs to be created or updated
+ description: p-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfPInterfacesPInterface.json)
required: true
schema:
$ref: "#/definitions/p-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing p-interface
+ description: |
+ Update an existing p-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: p-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/p-interface"
delete:
tags:
- Network
@@ -31022,11 +40032,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -31046,7 +40058,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/p-interfaces"
+ $ref: "#/getDefinitions/p-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -31055,6 +40067,7 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: orchestration-status
in: query
description: orchestration-status is the status of orchestration on the PNF.
@@ -31081,14 +40094,16 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -31113,11 +40128,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -31139,24 +40156,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -31181,21 +40202,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -31217,29 +40242,34 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -31264,26 +40294,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -31298,7 +40333,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -31307,26 +40342,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: orchestration-status
in: query
description: orchestration-status is the status of orchestration on the PNF.
@@ -31378,7 +40418,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -31395,32 +40438,100 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -31442,26 +40553,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -31488,29 +40604,34 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -31535,26 +40656,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -31569,7 +40695,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -31578,26 +40704,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: orchestration-status
in: query
description: orchestration-status is the status of orchestration on the PNF.
@@ -31649,7 +40780,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -31666,32 +40800,100 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -31713,26 +40915,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -31752,7 +40959,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -31761,21 +40968,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: orchestration-status
in: query
description: orchestration-status is the status of orchestration on the PNF.
@@ -31811,7 +41022,10 @@ paths:
tags:
- Network
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -31828,27 +41042,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- Network
@@ -31870,21 +41145,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -31904,7 +41183,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -31913,16 +41192,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: orchestration-status
in: query
description: orchestration-status is the status of orchestration on the PNF.
@@ -31964,24 +41246,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -32006,21 +41292,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -32035,7 +41325,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -32044,21 +41334,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: orchestration-status
in: query
description: orchestration-status is the status of orchestration on the PNF.
@@ -32103,7 +41397,10 @@ paths:
tags:
- Network
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -32120,27 +41417,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- Network
@@ -32162,21 +41520,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -32196,7 +41558,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -32205,16 +41567,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: orchestration-status
in: query
description: orchestration-status is the status of orchestration on the PNF.
@@ -32256,19 +41621,22 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -32293,16 +41661,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -32324,24 +41695,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -32366,21 +41741,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -32395,7 +41774,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -32404,21 +41783,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: orchestration-status
in: query
description: orchestration-status is the status of orchestration on the PNF.
@@ -32459,7 +41842,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -32476,27 +41862,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -32518,21 +41965,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -32559,24 +42010,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -32601,21 +42056,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -32630,7 +42089,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -32639,21 +42098,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: orchestration-status
in: query
description: orchestration-status is the status of orchestration on the PNF.
@@ -32694,7 +42157,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -32711,27 +42177,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -32753,21 +42280,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -32787,7 +42318,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -32796,16 +42327,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: orchestration-status
in: query
description: orchestration-status is the status of orchestration on the PNF.
@@ -32830,7 +42364,10 @@ paths:
tags:
- Network
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface
consumes:
- application/json
@@ -32847,22 +42384,76 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- Network
@@ -32884,16 +42475,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -32913,7 +42507,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -32922,11 +42516,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: orchestration-status
in: query
description: orchestration-status is the status of orchestration on the PNF.
@@ -32946,7 +42542,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interface"
+ $ref: "#/getDefinitions/lag-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -32955,11 +42551,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: orchestration-status
in: query
description: orchestration-status is the status of orchestration on the PNF.
@@ -32969,7 +42567,10 @@ paths:
tags:
- Network
summary: create or update an existing lag-interface
- description: create or update an existing lag-interface
+ description: |
+ Create or update an existing lag-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterface
consumes:
- application/json
@@ -32986,17 +42587,64 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: lag-interface object that needs to be created or updated
+ description: lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnfLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/lag-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing lag-interface
+ description: |
+ Update an existing lag-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: lag-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/lag-interface"
delete:
tags:
- Network
@@ -33018,11 +42666,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -33042,7 +42692,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interfaces"
+ $ref: "#/getDefinitions/lag-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -33051,6 +42701,7 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: orchestration-status
in: query
description: orchestration-status is the status of orchestration on the PNF.
@@ -33070,7 +42721,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/pnf"
+ $ref: "#/getDefinitions/pnf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -33079,6 +42730,7 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: orchestration-status
in: query
description: orchestration-status is the status of orchestration on the PNF.
@@ -33088,7 +42740,10 @@ paths:
tags:
- Network
summary: create or update an existing pnf
- description: create or update an existing pnf
+ description: |
+ Create or update an existing pnf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnf
consumes:
- application/json
@@ -33105,12 +42760,52 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: body
in: body
- description: pnf object that needs to be created or updated
+ description: pnf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPnfsPnf.json)
required: true
schema:
$ref: "#/definitions/pnf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing pnf
+ description: |
+ Update an existing pnf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: body
+ in: body
+ description: pnf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/pnf"
delete:
tags:
- Network
@@ -33132,6 +42827,7 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -33151,7 +42847,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/pnfs"
+ $ref: "#/getDefinitions/pnfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/physical-links/physical-link/{link-name}/relationship-list/relationship:
@@ -33175,9 +42871,10 @@ paths:
description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPhysicalLinksPhysicalLink.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -33202,6 +42899,7 @@ paths:
description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
required: true
type: string
+ example: __LINK-NAME__
/network/physical-links/physical-link/{link-name}:
get:
tags:
@@ -33216,7 +42914,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/physical-link"
+ $ref: "#/getDefinitions/physical-link"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -33225,6 +42923,7 @@ paths:
description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: circuit-id
in: query
description: Circuit it
@@ -33234,7 +42933,10 @@ paths:
tags:
- Network
summary: create or update an existing physical-link
- description: create or update an existing physical-link
+ description: |
+ Create or update an existing physical-link.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPhysicalLinksPhysicalLink
consumes:
- application/json
@@ -33251,12 +42953,52 @@ paths:
description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: body
in: body
- description: physical-link object that needs to be created or updated
+ description: physical-link object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkPhysicalLinksPhysicalLink.json)
required: true
schema:
$ref: "#/definitions/physical-link"
+ patch:
+ tags:
+ - Network
+ summary: update an existing physical-link
+ description: |
+ Update an existing physical-link
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPhysicalLinksPhysicalLink
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: link-name
+ in: path
+ description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
+ required: true
+ type: string
+ example: __LINK-NAME__
+ - name: body
+ in: body
+ description: physical-link object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/physical-link"
delete:
tags:
- Network
@@ -33278,6 +43020,7 @@ paths:
description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -33297,7 +43040,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/physical-links"
+ $ref: "#/getDefinitions/physical-links"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}/relationship-list/relationship:
@@ -33321,9 +43064,10 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkIpsecConfigurationsIpsecConfiguration.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -33348,6 +43092,7 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
/network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}/vig-servers/vig-server/{vig-address-type}/relationship-list/relationship:
put:
tags:
@@ -33369,14 +43114,16 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: vig-address-type
in: path
description: indicates whether the VIG is for AVPN or INTERNET
required: true
type: string
+ example: __VIG-ADDRESS-TYPE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -33401,11 +43148,13 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: vig-address-type
in: path
description: indicates whether the VIG is for AVPN or INTERNET
required: true
type: string
+ example: __VIG-ADDRESS-TYPE__
/network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}/vig-servers/vig-server/{vig-address-type}:
get:
tags:
@@ -33420,7 +43169,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vig-server"
+ $ref: "#/getDefinitions/vig-server"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -33429,16 +43178,21 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: vig-address-type
in: path
description: indicates whether the VIG is for AVPN or INTERNET
required: true
type: string
+ example: __VIG-ADDRESS-TYPE__
put:
tags:
- Network
summary: create or update an existing vig-server
- description: create or update an existing vig-server
+ description: |
+ Create or update an existing vig-server.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer
consumes:
- application/json
@@ -33455,17 +43209,64 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: vig-address-type
in: path
description: indicates whether the VIG is for AVPN or INTERNET
required: true
type: string
+ example: __VIG-ADDRESS-TYPE__
- name: body
in: body
- description: vig-server object that needs to be created or updated
+ description: vig-server object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer.json)
required: true
schema:
$ref: "#/definitions/vig-server"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vig-server
+ description: |
+ Update an existing vig-server
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: ipsec-configuration-id
+ in: path
+ description: UUID of this configuration
+ required: true
+ type: string
+ example: __IPSEC-CONFIGURATION-ID__
+ - name: vig-address-type
+ in: path
+ description: indicates whether the VIG is for AVPN or INTERNET
+ required: true
+ type: string
+ example: __VIG-ADDRESS-TYPE__
+ - name: body
+ in: body
+ description: vig-server object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vig-server"
delete:
tags:
- Network
@@ -33487,11 +43288,13 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: vig-address-type
in: path
description: indicates whether the VIG is for AVPN or INTERNET
required: true
type: string
+ example: __VIG-ADDRESS-TYPE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -33511,7 +43314,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vig-servers"
+ $ref: "#/getDefinitions/vig-servers"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -33520,6 +43323,7 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
/network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}:
get:
tags:
@@ -33534,7 +43338,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/ipsec-configuration"
+ $ref: "#/getDefinitions/ipsec-configuration"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -33543,11 +43347,15 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
put:
tags:
- Network
summary: create or update an existing ipsec-configuration
- description: create or update an existing ipsec-configuration
+ description: |
+ Create or update an existing ipsec-configuration.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkIpsecConfigurationsIpsecConfiguration
consumes:
- application/json
@@ -33564,12 +43372,52 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: body
in: body
- description: ipsec-configuration object that needs to be created or updated
+ description: ipsec-configuration object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkIpsecConfigurationsIpsecConfiguration.json)
required: true
schema:
$ref: "#/definitions/ipsec-configuration"
+ patch:
+ tags:
+ - Network
+ summary: update an existing ipsec-configuration
+ description: |
+ Update an existing ipsec-configuration
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkIpsecConfigurationsIpsecConfiguration
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: ipsec-configuration-id
+ in: path
+ description: UUID of this configuration
+ required: true
+ type: string
+ example: __IPSEC-CONFIGURATION-ID__
+ - name: body
+ in: body
+ description: ipsec-configuration object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/ipsec-configuration"
delete:
tags:
- Network
@@ -33591,6 +43439,7 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -33610,7 +43459,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/ipsec-configurations"
+ $ref: "#/getDefinitions/ipsec-configurations"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/route-table-references/route-table-reference/{route-table-reference-id}/relationship-list/relationship:
@@ -33634,9 +43483,10 @@ paths:
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __ROUTE-TABLE-REFERENCE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkRouteTableReferencesRouteTableReference.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -33661,6 +43511,7 @@ paths:
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __ROUTE-TABLE-REFERENCE-ID__
/network/route-table-references/route-table-reference/{route-table-reference-id}:
get:
tags:
@@ -33675,7 +43526,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/route-table-reference"
+ $ref: "#/getDefinitions/route-table-reference"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -33684,6 +43535,7 @@ paths:
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __ROUTE-TABLE-REFERENCE-ID__
- name: route-table-reference-fqdn
in: query
description: FQDN entry in the route table.
@@ -33693,7 +43545,10 @@ paths:
tags:
- Network
summary: create or update an existing route-table-reference
- description: create or update an existing route-table-reference
+ description: |
+ Create or update an existing route-table-reference.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkRouteTableReferencesRouteTableReference
consumes:
- application/json
@@ -33710,12 +43565,52 @@ paths:
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __ROUTE-TABLE-REFERENCE-ID__
- name: body
in: body
- description: route-table-reference object that needs to be created or updated
+ description: route-table-reference object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v8/NetworkRouteTableReferencesRouteTableReference.json)
required: true
schema:
$ref: "#/definitions/route-table-reference"
+ patch:
+ tags:
+ - Network
+ summary: update an existing route-table-reference
+ description: |
+ Update an existing route-table-reference
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkRouteTableReferencesRouteTableReference
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: route-table-reference-id
+ in: path
+ description: Route Table Reference id, UUID assigned to this instance.
+ required: true
+ type: string
+ example: __ROUTE-TABLE-REFERENCE-ID__
+ - name: body
+ in: body
+ description: route-table-reference object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/route-table-reference"
delete:
tags:
- Network
@@ -33737,6 +43632,7 @@ paths:
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __ROUTE-TABLE-REFERENCE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -33756,24 +43652,30 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/route-table-references"
+ $ref: "#/getDefinitions/route-table-references"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
definitions:
- search:
+ aai-internal:
properties:
- edge-tag-query-result:
- type: object
- $ref: "#/definitions/edge-tag-query-result"
- edge-tag-query-request:
- type: object
- $ref: "#/definitions/edge-tag-query-request"
- search-results:
- type: object
- $ref: "#/definitions/search-results"
- sdn-zone-response:
- type: object
- $ref: "#/definitions/sdn-zone-response"
+ property-name:
+ type: string
+ property-value:
+ type: string
+ action:
+ properties:
+ action-type:
+ type: string
+ action-data:
+ type: array
+ items:
+ $ref: "#/definitions/action-data"
+ action-data:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
actions:
description: |
APIs that are more action related than REST (e.g., notify, update).
@@ -33784,98 +43686,288 @@ definitions:
notify:
type: object
$ref: "#/definitions/notify"
- relationship-data:
+ allotted-resource:
+ description: |
+ Represents a slice or partial piece of a resource that gets separately allotted
+ ###### Related Nodes
+ - TO generic-vnf( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY)
+ - TO instance-group( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO l3-network( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY)
+ - TO vlan( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY)
+ - TO service-instance( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM tunnel-xconnect( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY)
+ - ALLOTTED-RESOURCE is DELETED when these are DELETED TUNNEL-XCONNECT
required:
- - relationship-key
- - relationship-value
+ - id
properties:
- relationship-key:
+ id:
type: string
- description: A keyword provided by A&AI to indicate an attribute.
- relationship-value:
+ description: Allotted Resource id UUID assigned to this instance.
+ description:
type: string
- description: Value of the attribute.
- related-to-property:
- properties:
- property-key:
+ description: The descriptive information assigned to this allotted resource instance
+ selflink:
type: string
- description: Key part of a key/value pair
- property-value:
+ description: Link back to more information in the controller
+ persona-model-id:
type: string
- description: Value part of a key/value pair
- relationship:
- properties:
- related-to:
+ description: the ASDC model id for this resource or service model.
+ persona-model-version:
type: string
- description: A keyword provided by A&AI to indicate type of node.
- related-link:
+ description: the ASDC model version for this resource or service model.
+ model-version-id:
type: string
- description: URL to the object in A&AI.
- relationship-data:
+ description: the ASDC model version for this resource or service model.
+ persona-model-customization-id:
+ type: string
+ description: captures the id of all the configuration used to customize the resource for the service.
+ resource-version:
+ type: string
+ description: Concurrency value
+ tunnel-xconnects:
type: array
- items:
- $ref: "#/definitions/relationship-data"
- related-to-property:
+ items:
+ $ref: "#/definitions/tunnel-xconnect"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ allotted-resources:
+ description: |
+ This object is used to store slices of services being offered
+ properties:
+ allotted-resource:
type: array
items:
- $ref: "#/definitions/related-to-property"
- relationship-list:
+ $ref: "#/definitions/allotted-resource"
+ availability-zone:
+ description: |
+ Availability zone, a collection of compute hosts/pservers
+ ###### Related Nodes
+ - TO complex( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO service-capability( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - TO cloud-region( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM ctag-pool( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM dvs-switch( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - FROM pserver( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)
+ - FROM vce( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - AVAILABILITY-ZONE cannot be deleted if linked to CTAG-POOL,DVS-SWITCH,GENERIC-VNF,PSERVER,VCE
+ required:
+ - availability-zone-name
+ - hypervisor-type
properties:
- relationship:
+ availability-zone-name:
+ type: string
+ description: Name of the availability zone. Unique across a cloud region
+ hypervisor-type:
+ type: string
+ description: Type of hypervisor. Source of truth should define valid values.
+ operational-state:
+ type: string
+ description: State that indicates whether the availability zone should be used, etc. Source of truth should define valid values.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ availability-zones:
+ description: |
+ Collection of availability zones
+ properties:
+ availability-zone:
type: array
items:
+ $ref: "#/definitions/availability-zone"
+ az-and-dvs-switches:
+ properties:
+ dvs-switches:
+ type: object
+ $ref: "#/definitions/dvs-switches"
+ availability-zone:
+ type: object
+ $ref: "#/definitions/availability-zone"
+ business:
+ description: |
+ Namespace for business related constructs
+ properties:
+ connectors:
+ type: array
+ items:
+ $ref: "#/definitions/connector"
+ customers:
+ type: array
+ items:
+ $ref: "#/definitions/customer"
+ class-of-service:
+ description: |
+ ###### Related Nodes
+ - TO site-pair( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)
+ required:
+ - cos
+ properties:
+ cos:
+ type: string
+ description: unique identifier of probe
+ probe-id:
+ type: string
+ description: identifier of probe
+ probe-type:
+ type: string
+ description: type of probe
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
$ref: "#/definitions/relationship"
- ctag-pool:
+ classes-of-service:
description: |
- A collection of C tags (vlan tags) grouped for a specific purpose.
+ class-of-service of probe
+ properties:
+ class-of-service:
+ type: array
+ items:
+ $ref: "#/definitions/class-of-service"
+ cloud-infrastructure:
+ description: |
+ Namespace for cloud infrastructure.
+ properties:
+ complexes:
+ type: array
+ items:
+ $ref: "#/definitions/complex"
+ cloud-regions:
+ type: array
+ items:
+ $ref: "#/definitions/cloud-region"
+ network-profiles:
+ type: array
+ items:
+ $ref: "#/definitions/network-profile"
+ pservers:
+ type: array
+ items:
+ $ref: "#/definitions/pserver"
+ virtual-data-centers:
+ type: array
+ items:
+ $ref: "#/definitions/virtual-data-center"
+ cloud-region:
+ description: |
+ cloud-region designates an installation of a cloud cluster or region or instantiation.
###### Related Nodes
- - TO availability-zone (Many2Many)
- - FROM complex (is composed of ctag-pool)
- - FROM vpls-pe
+ - TO complex( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO l3-network( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM dvs-switch( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM flavor( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM group-assignment( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM image( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM snapshot( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM volume-group( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)
+ - CLOUD-REGION cannot be deleted if linked to DVS-SWITCH,FLAVOR,GROUP-ASSIGNMENT,IMAGE,OAM-NETWORK,SNAPSHOT,TENANT,VOLUME-GROUP
+ - CLOUD-REGION is DELETED when these are DELETED AVAILABILITY-ZONE
required:
- - target-pe
- - availability-zone-name
- - ctag-pool-purpose
+ - cloud-owner
+ - cloud-region-id
properties:
- target-pe:
+ cloud-owner:
type: string
- description: The Target provider edge router
- availability-zone-name:
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ cloud-region-id:
type: string
- description: Name of the availability zone
- ctag-pool-purpose:
+ description: Identifier used by the vendor for the region. Second part of composite key
+ cloud-type:
type: string
- description: Describes what the intended purpose of this pool is.
- ctag-values:
+ description: Type of the cloud (e.g., openstack)
+ owner-defined-type:
type: string
- description: Comma separated list of ctags
+ description: Cloud-owner defined type indicator (e.g., DCP, LCP)
+ cloud-region-version:
+ type: string
+ description: Software version employed at the site
+ identity-url:
+ type: string
+ description: URL of the keystone identity service
+ cloud-zone:
+ type: string
+ description: Zone where the cloud is homed
+ complex-name:
+ type: string
+ description: complex name for cloud-region instance
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ volume-groups:
+ type: array
+ items:
+ $ref: "#/definitions/volume-group"
+ tenants:
+ type: array
+ items:
+ $ref: "#/definitions/tenant"
+ flavors:
+ type: array
+ items:
+ $ref: "#/definitions/flavor"
+ group-assignments:
+ type: array
+ items:
+ $ref: "#/definitions/group-assignment"
+ snapshots:
+ type: array
+ items:
+ $ref: "#/definitions/snapshot"
+ images:
+ type: array
+ items:
+ $ref: "#/definitions/image"
+ dvs-switches:
+ type: array
+ items:
+ $ref: "#/definitions/dvs-switch"
+ oam-networks:
+ type: array
+ items:
+ $ref: "#/definitions/oam-network"
+ availability-zones:
+ type: array
+ items:
+ $ref: "#/definitions/availability-zone"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- ctag-pools:
+ cloud-regions:
properties:
- ctag-pool:
+ cloud-region:
type: array
items:
- $ref: "#/definitions/ctag-pool"
+ $ref: "#/definitions/cloud-region"
complex:
description: |
Collection of physical locations that can house cloud-regions.
###### Related Nodes
- - TO ctag-pool (comprises complex, Many2Many)
- - TO l3-network (Many2Many)
- - FROM availability-zone
- - FROM cloud-region
- - FROM oam-network
- - FROM pserver
- - FROM pnf
- - FROM vce
- - FROM vpls-pe
- - FROM volume-group
+ - TO l3-network( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM ctag-pool( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)
+ - FROM pnf( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM vce( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)
+ - FROM volume-group( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM vpls-pe( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - COMPLEX cannot be deleted if linked to AVAILABILITY-ZONE,CLOUD-REGION,OAM-NETWORK,PNF,PSERVER,VCE,VOLUME-GROUP,VPLS-PE
+ - COMPLEX is DELETED when these are DELETED CTAG-POOL
required:
- physical-location-id
- physical-location-type
@@ -33941,37 +44033,59 @@ definitions:
type: array
items:
$ref: "#/definitions/complex"
- volume-group:
+ configuration:
description: |
- Persistent block-level storage.
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Port Mirror Configuration.
###### Related Nodes
- - TO complex (Many2Many)
- - TO tenant (Many2Many)
- - FROM cloud-region (is composed of volume-group)
- - FROM vf-module
- - FROM generic-vnf
+ - TO allotted-resource( configuration org.onap.relationships.inventory.Uses allotted-resource, ONE2ONE)
+ - TO logical-link( configuration org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo configuration, MANY2ONE)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses configuration, ONE2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses configuration, ONE2MANY)
+ - CONFIGURATION is DELETED when these are DELETED METADATUM
+ - CONFIGURATION deletion means associated objects of these types are also DELETED:ALLOTTED-RESOURCE,LOGICAL-LINK
required:
- - volume-group-id
- - volume-group-name
- - vnf-type
+ - configuration-id
+ - configuration-type
+ - configuration-sub-type
+ - orchestration-status
+ - operational-status
+ - configuration-selflink
+ - model-customization-id
properties:
- volume-group-id:
+ configuration-id:
type: string
- description: Unique ID of volume-group.
- volume-group-name:
+ description: UUID assigned to configuration.
+ management-option:
type: string
- description: Name of the volume group.
- heat-stack-id:
+ description: Indicates the entity that will manage this feature. Could be an organization or the name of the application as well.
+ configuration-name:
type: string
- description: Heat stack id corresponding to this volume-group
- vnf-type:
+ description: Name of the configuration.
+ configuration-type:
type: string
- description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded and clients should expect changes to occur in the future to this field as ASDC matures.
+ description: port-mirroring-configuration.
+ configuration-sub-type:
+ type: string
+ description: vprobe, pprobe.
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
orchestration-status:
type: string
- description: Orchestration status of this volume-group
+ description: Orchestration status of the configuration.
+ operational-status:
+ type: string
+ description: Indicator for whether the resource is considered operational.
+ configuration-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details from SDN-GC.
+ model-customization-id:
+ type: string
+ description: id of the configuration used to customize the resource
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
@@ -33979,447 +44093,633 @@ definitions:
type: array
items:
$ref: "#/definitions/relationship"
- volume-groups:
+ metadata:
+ type: array
+ items:
+ $ref: "#/definitions/metadatum"
+ configurations:
description: |
- Collection of persistent block-level storage.
+ Collection of configurations
properties:
- volume-group:
+ configuration:
type: array
items:
- $ref: "#/definitions/volume-group"
- volume:
+ $ref: "#/definitions/configuration"
+ connector:
description: |
- Ephemeral Block storage volume.
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Collection of resource instances used to connect a variety of disparate inventory widgets
###### Related Nodes
- - FROM vserver (is composed of volume)
+ - TO virtual-data-center( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)
+ - CONNECTOR is DELETED when these are DELETED METADATUM
required:
- - volume-id
- - volume-selflink
+ - resource-instance-id
properties:
- volume-id:
- type: string
- description: Unique ID of block storage volume relative to the vserver.
- volume-selflink:
+ resource-instance-id:
type: string
- description: URL to endpoint where AAI can get more details
+ description: Unique id of resource instance.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ persona-model-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- volumes:
+ metadata:
+ type: array
+ items:
+ $ref: "#/definitions/metadatum"
+ connectors:
description: |
- Collection of ephemeral Block storage volumes.
+ Collection of resource instances used to connect a variety of disparate inventory widgets
properties:
- volume:
+ connector:
type: array
items:
- $ref: "#/definitions/volume"
- l3-interface-ipv4-address-list:
+ $ref: "#/definitions/connector"
+ constrained-element-set:
description: |
- IPv4 Address Range
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ This is how we would capture constraints defining allowed sets of elements.
###### Related Nodes
- - TO l3-network (Many2Many)
- - TO subnet (Many2Many)
- - FROM l-interface (is composed of l3-interface-ipv4-address-list)
- - FROM vlan (is composed of l3-interface-ipv4-address-list)
+ - TO model-constraint( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)
+ - TO model-element( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM element-choice-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)
+ - CONSTRAINED-ELEMENT-SET is DELETED when these are DELETED ELEMENT-CHOICE-SET
required:
- - l3-interface-ipv4-address
+ - constrained-element-set-uuid
+ - constraint-type
+ - check-type
properties:
- l3-interface-ipv4-address:
+ constrained-element-set-uuid:
type: string
- description: IP address
- l3-interface-ipv4-prefix-length:
- type: integer
- format: int64
- description: Prefix length, 32 for single address
- vlan-id-inner:
- type: integer
- format: int64
- description: Inner VLAN tag
- vlan-id-outer:
- type: integer
- format: int64
- description: Outer VLAN tag
- is-floating:
- type: boolean
- description: Indicator of fixed or floating address
- resource-version:
+ constraint-type:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- neutron-network-id:
+ check-type:
type: string
- description: Neutron network id of the interface that address belongs to
- neutron-subnet-id:
+ resource-version:
type: string
- description: Neutron id of subnet that address belongs to
+ element-choice-sets:
+ type: array
+ items:
+ $ref: "#/definitions/element-choice-set"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- l3-interface-ipv6-address-list:
+ constrained-element-sets:
+ properties:
+ constrained-element-set:
+ type: array
+ items:
+ $ref: "#/definitions/constrained-element-set"
+ ctag-assignment:
description: |
- IPv6 Address Range
- ###### Default Delete Scope
- THIS_NODE_ONLY
###### Related Nodes
- - TO l3-network (Many2Many)
- - TO subnet (Many2Many)
- - FROM l-interface (is composed of l3-interface-ipv6-address-list)
- - FROM vlan (is composed of l3-interface-ipv6-address-list)
+ - TO l3-network( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
required:
- - l3-interface-ipv6-address
+ - vlan-id-inner
properties:
- l3-interface-ipv6-address:
- type: string
- description: IP address
- l3-interface-ipv6-prefix-length:
- type: integer
- format: int64
- description: Prefix length, 128 for single address
vlan-id-inner:
type: integer
format: int64
- description: Inner VLAN tag
- vlan-id-outer:
- type: integer
- format: int64
- description: Outer VLAN tag
- is-floating:
- type: boolean
- description: Indicator of fixed or floating address
+ description: id.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- neutron-network-id:
- type: string
- description: Neutron network id of the interface that address belongs to
- neutron-subnet-id:
- type: string
- description: Neutron id of subnet that address belongs to
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- vlan:
+ ctag-assignments:
+ properties:
+ ctag-assignment:
+ type: array
+ items:
+ $ref: "#/definitions/ctag-assignment"
+ ctag-pool:
description: |
- Definition of vlan
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
+ A collection of C tags (vlan tags) grouped for a specific purpose.
###### Related Nodes
- - TO l3-interface-ipv4-address-list (comprises vlan, Many2Many)
- - TO l3-interface-ipv6-address-list (comprises vlan, Many2Many)
- - TO multicast-configuration (Many2Many)
- - TO logical-link (One2One)
- - FROM l-interface (is composed of vlan)
- - FROM service-instance
+ - TO complex( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)
+ - TO availability-zone( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM vpls-pe( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)
required:
- - vlan-interface
+ - target-pe
+ - availability-zone-name
+ - ctag-pool-purpose
properties:
- vlan-interface:
+ target-pe:
type: string
- description: String that identifies the interface
- vlan-id-inner:
- type: integer
- format: int64
- description: Inner VLAN tag
- vlan-id-outer:
- type: integer
- format: int64
- description: Outer VLAN tag
+ description: The Target provider edge router
+ availability-zone-name:
+ type: string
+ description: Name of the availability zone
+ ctag-pool-purpose:
+ type: string
+ description: Describes what the intended purpose of this pool is.
+ ctag-values:
+ type: string
+ description: Comma separated list of ctags
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- speed-value:
- type: string
- description: Captures the numeric part of the speed
- speed-units:
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ ctag-pools:
+ properties:
+ ctag-pool:
+ type: array
+ items:
+ $ref: "#/definitions/ctag-pool"
+ customer:
+ description: |
+ customer identifiers to provide linkage back to BSS information.
+ ###### Related Nodes
+ - FROM service-subscription( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)
+ - CUSTOMER is DELETED when these are DELETED SERVICE-SUBSCRIPTION
+ required:
+ - global-customer-id
+ - subscriber-name
+ - subscriber-type
+ properties:
+ global-customer-id:
type: string
- description: Captures the units corresponding to the speed
- vlan-description:
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ subscriber-name:
type: string
- description: Used to describe (the service associated with) the vlan
- backdoor-connection:
+ description: Subscriber name, an alternate way to retrieve a customer.
+ subscriber-type:
type: string
- description: Whether customer is going to use this VLAN for backdoor connection to another customer premise device.
- vpn-id:
+ description: Subscriber type, a way to provide VID with only the INFRA customers.
+ resource-version:
type: string
- description: This indicates the customers VPN ID associated with this vlan
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ service-subscriptions:
+ type: array
+ items:
+ $ref: "#/definitions/service-subscription"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- l3-interface-ipv4-address-list:
+ customers:
+ description: |
+ Collection of customer identifiers to provide linkage back to BSS information.
+ properties:
+ customer:
type: array
items:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
- l3-interface-ipv6-address-list:
+ $ref: "#/definitions/customer"
+ cvlan-tag-entry:
+ required:
+ - cvlan-tag
+ properties:
+ cvlan-tag:
+ type: integer
+ format: int64
+ description: See mis-na-virtualization-platform.yang
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
- items:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
- vlans:
+ items:
+ $ref: "#/definitions/relationship"
+ cvlan-tags:
properties:
- vlan:
+ cvlan-tag-entry:
type: array
items:
- $ref: "#/definitions/vlan"
- sriov-vf:
+ $ref: "#/definitions/cvlan-tag-entry"
+ dvs-switch:
description: |
- SR-IOV Virtual Function (not to be confused with virtual network function)
+ Digital virtual switch metadata, used by SDN-C to configure VCEs. A&AI needs to receive this data from the PO deployment team and administer it using the provisioningTool.sh into A&AI.
###### Related Nodes
- - FROM l-interface (is composed of sriov-vf)
+ - TO cloud-region( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO availability-zone( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
required:
- - pci-id
+ - switch-name
+ - vcenter-url
properties:
- pci-id:
- type: string
- description: PCI ID used to identify the sriov-vf
- vf-vlan-filter:
- type: string
- description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM.
- vf-mac-filter:
- type: string
- description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM.
- vf-vlan-strip:
- type: boolean
- description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM.
- vf-vlan-anti-spoof-check:
- type: boolean
- description: This option ensures anti VLAN spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
- vf-mac-anti-spoof-check:
- type: boolean
- description: This option ensures anti MAC spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
- vf-mirrors:
+ switch-name:
type: string
- description: This option defines the set of Mirror objects which essentially mirrors the traffic from source to set of collector VNF Ports.
- vf-broadcast-allow:
- type: boolean
- description: This option, if set to true, sets the VF in promiscuous mode and allows all broadcast traffic to reach the VM
- vf-unknown-multicast-allow:
- type: boolean
- description: This option, if set to true, sets the VF in promiscuous mode and allows unknown multicast traffic to reach the VM
- vf-unknown-unicast-allow:
- type: boolean
- description: This option, if set to true, sets the VF in promiscuous mode and allows unknown unicast traffic to reach the VM
- vf-insert-stag:
- type: boolean
- description: This option, if set to true, instructs to insert outer tag after traffic comes out of VM.
- vf-link-status:
+ description: DVS switch name
+ vcenter-url:
type: string
- description: This option is used to set the link status. Valid values as of 1607 are on, off, and auto.
+ description: URL used to reach the vcenter
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- neutron-network-id:
- type: string
- description: Neutron network id of the interface
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- sriov-vfs:
+ dvs-switches:
description: |
- Collection of SR-IOV Virtual Functions.
+ Collection of digital virtual switch metadata used for vmWare VCEs and GenericVnfs.
properties:
- sriov-vf:
+ dvs-switch:
type: array
items:
- $ref: "#/definitions/sriov-vf"
- l-interface:
+ $ref: "#/definitions/dvs-switch"
+ edge-prop-names:
description: |
- Logical interfaces, e.g., a vnic.
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
- ###### Related Nodes
- - TO l3-interface-ipv4-address-list (comprises l-interface, Many2Many)
- - TO l3-interface-ipv6-address-list (comprises l-interface, Many2Many)
- - TO logical-link (Many2Many)
- - TO vlan (comprises l-interface, Many2Many)
- - TO sriov-vf (comprises l-interface, One2One)
- - FROM generic-vnf (is composed of l-interface)
- - FROM lag-interface (is composed of l-interface)
- - FROM newvce (is composed of l-interface)
- - FROM p-interface (is composed of l-interface)
- - FROM vserver (is composed of l-interface)
- required:
- - interface-name
+ Internal map to define the properties of an edge and interpret the map EdgeRules
properties:
- interface-name:
+ edgeLabel:
type: string
- description: Name given to the interface
- interface-role:
+ direction:
type: string
- description: E.g., CUSTOMER, UPLINK, etc.
- v6-wan-link-ip:
+ multiplicityRule:
type: string
- description: Questionably placed - v6 ip addr of this interface (is in vr-lan-interface from Mary B.
- selflink:
+ isParent:
+ type: boolean
+ usesResource:
+ type: boolean
+ hasDelTarget:
+ type: boolean
+ SVC-INFRA:
+ type: boolean
+ SVC-INFRA-REV:
+ type: boolean
+ edge-tag-query-request:
+ properties:
+ edge-tag:
type: string
- description: URL to endpoint where AAI can get more details
- interface-id:
+ result-detail:
type: string
- description: ID of interface
- macaddr:
+ start-node-type:
type: string
- description: MAC address for the interface
- network-name:
+ start-node-filter:
+ type: array
+ items:
+ $ref: "#/definitions/start-node-filter"
+ include-node-filter:
+ type: array
+ items:
+ $ref: "#/definitions/include-node-filter"
+ secondary-filter:
+ type: array
+ items:
+ $ref: "#/definitions/secondary-filter"
+ edge-tag-query-result:
+ properties:
+ tagged-inventory-item-list:
+ type: array
+ items:
+ $ref: "#/definitions/tagged-inventory-item-list"
+ element-choice-set:
+ description: |
+ This is how we would capture constraints defining allowed sets of elements.
+ ###### Related Nodes
+ - TO constrained-element-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)
+ - ELEMENT-CHOICE-SET is DELETED when these are DELETED MODEL-ELEMENT
+ required:
+ - element-choice-set-uuid
+ - element-choice-set-name
+ properties:
+ element-choice-set-uuid:
type: string
- description: Name of the network
- management-option:
+ element-choice-set-name:
+ type: string
+ cardinality:
type: string
- description: Whether A&AI should be managing this interface of not. Could have value like CUSTOMER
resource-version:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- vlans:
- type: array
- items:
- $ref: "#/definitions/vlan"
- sriov-vfs:
+ model-elements:
type: array
items:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/definitions/model-element"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- l3-interface-ipv4-address-list:
+ element-choice-sets:
+ properties:
+ element-choice-set:
type: array
items:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
- l3-interface-ipv6-address-list:
+ $ref: "#/definitions/element-choice-set"
+ entitlement:
+ description: |
+ Metadata for entitlement group.
+ ###### Related Nodes
+ - TO generic-vnf( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vce( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ required:
+ - group-uuid
+ - resource-uuid
+ properties:
+ group-uuid:
+ type: string
+ description: Unique ID for the entitlement group the resource comes from, should be uuid.
+ resource-uuid:
+ type: string
+ description: Unique ID of an entitlement resource.
+ resource-version:
+ type: string
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ entitlements:
+ description: |
+ Entitlements, keyed by group-uuid and resource-uuid, related to license management
+ properties:
+ entitlement:
type: array
items:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
- l-interfaces:
+ $ref: "#/definitions/entitlement"
+ esr-ems:
description: |
- Collection of logical interfaces.
+ Persist EMS address information used by EMS driver.
+ ###### Related Nodes
+ - TO esr-system-info (CHILD of esr-ems, esr-ems has esr-system-info, One2Many)
+ - ESR-EMS deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
+ required:
+ - ems-id
properties:
- l-interface:
+ ems-id:
+ type: string
+ description: Unique ID of EMS.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ esr-system-info-list:
+ type: object
+ $ref: "#/definitions/esr-system-info-list"
+ relationship-list:
+ type: object
+ $ref: "#/definitions/relationship-list"
+ esr-ems-list:
+ properties:
+ esr-ems:
type: array
items:
- $ref: "#/definitions/l-interface"
- vserver:
+ $ref: "#/definitions/esr-ems"
+ esr-system-info:
description: |
- Virtual Servers, aka virtual machine or VM.
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
- ###### Related Nodes
- - TO flavor (Many2One)
- - TO image (Many2One)
- - TO l-interface (comprises vserver, Many2Many)
- - TO pserver (Many2One)
- - TO volume (comprises vserver, Many2Many)
- - TO vnfc (Many2Many)
- - TO snapshot (One2One)
- - TO vf-module (Many2One)
- - FROM generic-vnf
- - FROM tenant (is composed of vserver)
- - FROM vce
+ Persist common address information of external systems.
+ ###### Related Nodes
+ - FROM esr-ems (PARENT of esr-system-info, esr-ems has esr-system-info)
+ - FROM esr-vnfm (PARENT of esr-system-info, esr-vnfm has esr-system-info)
+ - FROM esr-thirdparty-sdnc (PARENT of esr-system-info, esr-thirdparty-sdnc has esr-system-info)
+ - FROM cloud-region (PARENT of esr-system-info, cloud-region has esr-system-info)
required:
- - vserver-id
- - vserver-name
- - vserver-selflink
- - in-maint
- - is-closed-loop-disabled
+ - esr-system-info-id
+ - user-name
+ - password
+ - system-type
properties:
- vserver-id:
+ esr-system-info-id:
type: string
- description: Unique identifier for this vserver relative to its tenant
- vserver-name:
+ description: Unique ID of esr system info.
+ system-name:
type: string
- description: Name of vserver
- vserver-name2:
+ description: name of external system.
+ type:
type: string
- description: Alternative name of vserver
- prov-status:
+ description: type of external systems.
+ vendor:
type: string
- description: Trigger for operational monitoring of this resource by Service Assurance systems.
- vserver-selflink:
+ description: vendor of external systems.
+ version:
type: string
- description: URL to endpoint where AAI can get more details
- in-maint:
+ description: version of external systems.
+ service-url:
+ type: string
+ description: url used to access external systems.
+ user-name:
+ type: string
+ description: username used to access external systems.
+ password:
+ type: string
+ description: password used to access external systems.
+ system-type:
+ type: string
+ description: it could be vim/vnfm/thirdparty-sdnc/ems-resource/ems-performance/ems-alarm.
+ protocol:
+ type: string
+ description: protocol of third party SDNC, for example netconf/snmp.
+ ssl-cacert:
+ type: string
+ description: ca file content if enabled ssl on auth-url.
+ ssl-insecure:
type: boolean
- is-closed-loop-disabled:
+ description: Whether to verify VIM's certificate.
+ ip-address:
+ type: string
+ description: service IP of ftp server.
+ port:
+ type: string
+ description: service port of ftp server.
+ cloud-domain:
+ type: string
+ description: domain info for authentication.
+ default-tenant:
+ type: string
+ description: default tenant of VIM.
+ passive:
type: boolean
+ description: ftp passive mode or not.
+ remote-path:
+ type: string
+ description: resource or performance data file path.
+ system-status:
+ type: string
+ description: the status of external system.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- volumes:
- type: array
- items:
- $ref: "#/definitions/volume"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- l-interfaces:
+ esr-system-info-list:
+ description: |
+ Collection of persistent block-level external system auth info.
+ properties:
+ esr-system-info:
type: array
- items:
- $ref: "#/definitions/l-interface"
- vservers:
+ items:
+ $ref: "#/definitions/esr-system-info"
+ esr-thirdparty-sdnc:
description: |
- Collection of virtual Servers, aka virtual machines or VMs.
+ Persist SDNC address information used by ONAP SDNC.
+ ###### Related Nodes
+ - TO esr-system-info (CHILD of esr-thirdparty-sdnc, esr-thirdparty-sdnc has esr-system-info, One2One)
+ - TO pnf( esr-thirdparty-sdnc has pnf, One2Many)
+ - ESR-THIRDPARTY-SDNC deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
+ required:
+ - thirdparty-sdnc-id
properties:
- vserver:
+ thirdparty-sdnc-id:
+ type: string
+ description: Unique ID of SDNC.
+ location:
+ type: string
+ description: used for DC type to indicate the location of SDNC, such as Core or Edge.
+ product-name:
+ type: string
+ description: password used to access SDNC server.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ esr-system-info-list:
+ type: object
+ $ref: "#/definitions/esr-system-info-list"
+ relationship-list:
+ type: object
+ $ref: "#/definitions/relationship-list"
+ esr-thirdparty-sdnc-list:
+ properties:
+ esr-thirdparty-sdnc:
type: array
items:
- $ref: "#/definitions/vserver"
- tenant:
+ $ref: "#/definitions/esr-thirdparty-sdnc"
+ esr-vnfm:
description: |
- Openstack tenant
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Persist VNFM address information used by VF-C.
###### Related Nodes
- - TO l3-network (Many2Many)
- - TO service-subscription (Many2Many)
- - TO vserver (comprises tenant, One2Many)
- - FROM cloud-region (is composed of tenant)
- - FROM group-assignment
- - FROM volume-group
+ - TO esr-system-info (CHILD of esr-vnfm, esr-vnfm has esr-system-info, One2One)
+ - ESR-VNFM deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
required:
- - tenant-id
- - tenant-name
+ - vnfm-id
properties:
- tenant-id:
+ vnfm-id:
type: string
- description: Unique id relative to the cloud-region.
- tenant-name:
+ description: Unique ID of VNFM.
+ vim-id:
type: string
- description: Readable name of tenant
+ description: indecate the VIM to deploy VNF.
+ certificate-url:
+ type: string
+ description: certificate url of VNFM.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- vservers:
+ esr-system-info-list:
+ type: object
+ $ref: "#/definitions/esr-system-info-list"
+ relationship-list:
+ type: object
+ $ref: "#/definitions/relationship-list"
+ esr-vnfm-list:
+ properties:
+ esr-vnfm:
type: array
- items:
- $ref: "#/definitions/vserver"
+ items:
+ $ref: "#/definitions/esr-vnfm"
+ evc:
+ description: |
+ evc object is an optional child object of the Configuration object.
+ ###### Related Nodes
+ - TO configuration( evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)
+ required:
+ - evc-id
+ properties:
+ evc-id:
+ type: string
+ description: Unique/key field for the evc object
+ forwarding-path-topology:
+ type: string
+ description: Point-to-Point, Multi-Point
+ cir-value:
+ type: string
+ description: Commited Information Rate
+ cir-units:
+ type: string
+ description: CIR units
+ connection-diversity-group-id:
+ type: string
+ description: Diversity Group ID
+ service-hours:
+ type: string
+ description: formerly Performance Group
+ esp-evc-circuit-id:
+ type: string
+ description: EVC Circuit ID of ESP EVC
+ esp-evc-cir-value:
+ type: string
+ description: Committed Information Rate (For ESP)
+ esp-evc-cir-units:
+ type: string
+ description: CIR units (For ESP)
+ esp-itu-code:
+ type: string
+ description: Identifies ESP
+ collector-pop-clli:
+ type: string
+ description: Collector POP CLLI (from the hostname of the access pnf)
+ inter-connect-type-ingress:
+ type: string
+ description: Interconnect type on ingress side of EVC.
+ tagmode-access-ingress:
+ type: string
+ description: tagode for collector side of EVC
+ tagmode-access-egress:
+ type: string
+ description: tagMode for network side of EVC
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- tenants:
- description: |
- Collection of openstack tenants.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ evcs:
properties:
- tenant:
+ evc:
type: array
items:
- $ref: "#/definitions/tenant"
+ $ref: "#/definitions/evc"
+ external-system:
+ description: |
+ Namespace for external system.
+ properties:
+ esr-ems-list:
+ type: object
+ $ref: "#/definitions/esr-ems-list"
+ esr-vnfm-list:
+ type: object
+ $ref: "#/definitions/esr-vnfm-list"
+ esr-thirdparty-sdnc-list:
+ type: object
+ $ref: "#/definitions/esr-thirdparty-sdnc-list"
+ extra-properties:
+ description: |
+ Extra properties for inventory item for response list
+ extra-property:
+ properties:
+ property-name:
+ type: string
flavor:
description: |
Openstack flavor.
- ###### Default Delete Scope
- ERROR_IF_ANY_IN_EDGES
###### Related Nodes
- - FROM cloud-region (is composed of flavor)
- - FROM vserver
+ - TO cloud-region( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)
+ - FLAVOR cannot be deleted if linked to VSERVER
required:
- flavor-id
- flavor-name
@@ -34474,143 +44774,358 @@ definitions:
type: array
items:
$ref: "#/definitions/flavor"
- group-assignment:
+ forwarder:
description: |
- Openstack group-assignment used to store exclusivity groups (EG).
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Entity describing a sequenced segment of forwarding path
###### Related Nodes
- - TO tenant (Many2Many)
- - TO pserver (One2Many)
- - FROM cloud-region (is composed of group-assignment)
+ - TO forwarding-path( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)
+ - TO l-interface( forwarder org.onap.relationships.inventory.ForwardsTo l-interface, MANY2ONE)
+ - TO configuration( forwarder org.onap.relationships.inventory.Uses configuration, ONE2ONE)
+ - TO lag-interface( forwarder org.onap.relationships.inventory.ForwardsTo lag-interface, MANY2ONE)
+ - TO p-interface( forwarder org.onap.relationships.inventory.ForwardsTo p-interface, MANY2ONE)
+ - FORWARDER deletion means associated objects of these types are also DELETED:CONFIGURATION
required:
- - group-id
- - group-type
- - group-name
+ - sequence
properties:
- group-id:
+ sequence:
+ type: integer
+ format: int32
+ description: Unique ID of this segmentation
+ forwarder-role:
type: string
- description: Group id, expected to be unique across cloud-region.
- group-type:
+ description: ingress, intermediate, egress
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ resource-version:
type: string
- description: Group type - the type of group this instance refers to
- group-name:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ forwarder-evc:
+ description: |
+ forwarder object is an optional child object of the Configuration object.
+ ###### Related Nodes
+ - TO configuration( forwarder-evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)
+ required:
+ - forwarder-evc-id
+ properties:
+ forwarder-evc-id:
type: string
- description: Group name - name assigned to the group
- group-description:
+ description: Key for forwarder-evc object
+ circuit-id:
type: string
- description: Group description - description of the group
- resource-version:
+ description: Circuit ID from customer/ESP/ingress end of EVC, or reference to beater circuit on gateway/network/egress end of EVC
+ ivlan:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ description: Internal VLAN.
+ svlan:
+ type: string
+ description: SVLAN value for ingress of egress forwarder.
+ cvlan:
+ type: string
+ description: CVLAN value for ingress of egress forwarder.
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- group-assignments:
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ forwarder-evcs:
+ properties:
+ forwarder-evc:
+ type: array
+ items:
+ $ref: "#/definitions/forwarder-evc"
+ forwarders:
+ properties:
+ forwarder:
+ type: array
+ items:
+ $ref: "#/definitions/forwarder"
+ forwarding-path:
description: |
- Collection of openstack group assignments
+ Entity that describes the sequenced forwarding path between interfaces of services or resources
+ ###### Related Nodes
+ - TO service-instance( forwarding-path org.onap.relationships.inventory.AppliesTo service-instance, MANY2ONE)
+ - TO configuration( forwarding-path org.onap.relationships.inventory.Uses configuration, ONE2ONE)
+ - FROM forwarder( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)
+ - FORWARDING-PATH is DELETED when these are DELETED FORWARDER
+ - FORWARDING-PATH deletion means associated objects of these types are also DELETED:CONFIGURATION
+ required:
+ - forwarding-path-id
+ - forwarding-path-name
properties:
- group-assignment:
+ forwarding-path-id:
+ type: string
+ description: Unique ID of this FP
+ forwarding-path-name:
+ type: string
+ description: Name of the FP
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ selflink:
+ type: string
+ description: the self link for this FP
+ forwarders:
+ type: array
+ items:
+ $ref: "#/definitions/forwarder"
+ forwarding-paths:
+ properties:
+ forwarding-path:
type: array
items:
- $ref: "#/definitions/group-assignment"
- snapshot:
+ $ref: "#/definitions/forwarding-path"
+ generic-vnf:
description: |
- Openstack snapshot
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ General purpose VNF
###### Related Nodes
- - FROM cloud-region (is composed of snapshot)
- - FROM vserver
+ - TO availability-zone( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - TO ipsec-configuration( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)
+ - TO l3-network( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO license-key-resource( generic-vnf org.onap.relationships.inventory.Uses license-key-resource, MANY2MANY)
+ - TO pserver( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)
+ - TO vnf-image( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)
+ - TO volume-group( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - TO vserver( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)
+ - TO virtual-data-center( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM lag-interface( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM network-profile( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)
+ - FROM site-pair-set( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)
+ - GENERIC-VNF is DELETED when these are DELETED VNFC,LAG-INTERFACE,L-INTERFACE,VF-MODULE
required:
- - snapshot-id
+ - vnf-id
+ - vnf-name
+ - vnf-type
+ - in-maint
+ - is-closed-loop-disabled
properties:
- snapshot-id:
+ vnf-id:
type: string
- description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
- snapshot-name:
+ description: Unique id of VNF. This is unique across the graph.
+ vnf-name:
type: string
- description: Snapshot name
- snapshot-architecture:
+ description: Name of VNF.
+ vnf-name2:
type: string
- description: Operating system architecture
- snapshot-os-distro:
+ description: Alternate name of VNF.
+ vnf-type:
type: string
- description: The common name of the operating system distribution in lowercase
- snapshot-os-version:
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded and clients should expect changes to occur in the future to this field as ASDC matures.
+ service-id:
type: string
- description: The operating system version as specified by the distributor.
- application:
+ description: Unique identifier of service from ASDC
+ regional-resource-zone:
type: string
- description: The application that the image instantiates.
- application-vendor:
+ description: Regional way of organizing pservers, source of truth should define values
+ prov-status:
type: string
- description: The vendor of the application.
- application-version:
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ operational-state:
type: string
- description: The version of the application.
- snapshot-selflink:
+ description: Indicator for whether the resource is considered operational
+ license-key:
type: string
- description: URL to endpoint where AAI can get more details
- prev-snapshot-id:
+ description: License key
+ equipment-role:
type: string
- description: This field contains the UUID of the previous snapshot (if any).
+ description: Client should send valid enumerated value
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, used by MSO.
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ management-option:
+ type: string
+ description: identifier of managed by company or customer
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by generic-vnf.
+ ipv4-loopback0-address:
+ type: string
+ description: v4 Loopback0 address
+ nm-lan-v6-address:
+ type: string
+ description: v6 Loopback address
+ management-v6-address:
+ type: string
+ description: v6 management address
+ vcpu:
+ type: integer
+ format: int64
+ description: number of vcpus ordered for this instance of VNF, used for VNFs with no vservers/flavors
+ vcpu-units:
+ type: string
+ description: units associated with vcpu, used for VNFs with no vservers/flavors
+ vmemory:
+ type: integer
+ format: int64
+ description: number of GB of memory ordered for this instance of VNF, used for VNFs with no vservers/flavors
+ vmemory-units:
+ type: string
+ description: units associated with vmemory, used for VNFs with no vservers/flavors
+ vdisk:
+ type: integer
+ format: int64
+ description: number of vdisks ordered for this instance of VNF, used for VNFs with no vservers/flavors
+ vdisk-units:
+ type: string
+ description: units associated with vdisk, used for VNFs with no vservers/flavors
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ summary-status:
+ type: string
+ description: details regarding the generic-vnf operation
+ encrypted-access-flag:
+ type: boolean
+ description: indicates whether generic-vnf access uses SSH
+ persona-model-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ as-number:
+ type: string
+ description: as-number of the VNF
+ regional-resource-subzone:
+ type: string
+ description: represents sub zone of the rr plane
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- snapshots:
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/l-interface"
+ lag-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/lag-interface"
+ vf-modules:
+ type: array
+ items:
+ $ref: "#/definitions/vf-module"
+ generic-vnfs:
description: |
- Collection of openstack snapshots
+ Collection of VNFs
properties:
- snapshot:
+ generic-vnf:
type: array
items:
- $ref: "#/definitions/snapshot"
- metadatum:
+ $ref: "#/definitions/generic-vnf"
+ group-assignment:
description: |
- Key/value pairs
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Openstack group-assignment used to store exclusivity groups (EG).
###### Related Nodes
- - FROM image (is composed of metadatum)
- - FROM model (is composed of metadatum)
- - FROM service-instance (is composed of metadatum)
- - FROM connector (is composed of metadatum)
+ - TO cloud-region( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)
required:
- - metaname
- - metaval
+ - group-id
+ - group-type
+ - group-name
properties:
- metaname:
+ group-id:
type: string
- metaval:
+ description: Group id, expected to be unique across cloud-region.
+ group-type:
+ type: string
+ description: Group type - the type of group this instance refers to
+ group-name:
type: string
+ description: Group name - name assigned to the group
+ group-description:
+ type: string
+ description: Group description - description of the group
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- metadata:
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ group-assignments:
description: |
- Collection of metadatum (key/value pairs)
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Collection of openstack group assignments
properties:
- metadatum:
+ group-assignment:
type: array
items:
- $ref: "#/definitions/metadatum"
+ $ref: "#/definitions/group-assignment"
+ host-route:
+ description: |
+ ###### Related Nodes
+ - TO subnet( host-route org.onap.relationships.inventory.BelongsTo subnet, MANY2ONE)
+ required:
+ - host-route-id
+ - route-prefix
+ - next-hop
+ properties:
+ host-route-id:
+ type: string
+ description: host-route id
+ route-prefix:
+ type: string
+ description: subnet prefix
+ next-hop:
+ type: string
+ description: Could be ip-address, hostname, or service-instance
+ next-hop-type:
+ type: string
+ description: Should be ip-address, hostname, or service-instance to match next-hop
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ host-routes:
+ properties:
+ host-route:
+ type: array
+ items:
+ $ref: "#/definitions/host-route"
image:
description: |
Openstack image.
- ###### Default Delete Scope
- ERROR_4_IN_EDGES_OR_CASCADE
###### Related Nodes
- - TO metadatum (comprises image, Many2Many)
- - FROM cloud-region (is composed of image)
- - FROM vserver
+ - TO cloud-region( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)
+ - IMAGE cannot be deleted if linked to VSERVER
+ - IMAGE is DELETED when these are DELETED METADATUM
required:
- image-id
- image-name
@@ -34664,22 +45179,198 @@ definitions:
type: array
items:
$ref: "#/definitions/image"
- dvs-switch:
+ include-node-filter:
+ properties:
+ include-node-type:
+ type: string
+ instance-filter:
description: |
- Digital virtual switch metadata, used by SDN-C to configure VCEs. A&AI needs to receive this data from the PO deployment team and administer it using the provisioningTool.sh into A&AI.
+ InstanceFilter for performing a named-query or model query
+ instance-filters:
+ description: |
+ InstanceFilters for performing a named-query or model query
+ properties:
+ instance-filter:
+ type: array
+ items:
+ $ref: "#/definitions/instance-filter"
+ instance-group:
+ description: |
+ General mechanism for grouping instances
###### Related Nodes
- - TO availability-zone (Many2Many)
- - FROM cloud-region (is composed of dvs-switch)
+ - TO model( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM pnf( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
required:
- - switch-name
- - vcenter-url
+ - id
+ - description
+ - type
properties:
- switch-name:
+ id:
type: string
- description: DVS switch name
- vcenter-url:
+ description: Instance Group ID, UUID assigned to this instance.
+ description:
type: string
- description: URL used to reach the vcenter
+ description: Descriptive text to help identify the usage of this instance-group
+ type:
+ type: string
+ description: Only valid value today is lower case ha for high availability
+ sub-type:
+ type: string
+ description: Valid values for ha type are [geo-activeactive, geo-activestandby, local-activeactive, local-activestandby]
+ resource-version:
+ type: string
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ instance-groups:
+ description: |
+ Collection of openstack route table references
+ properties:
+ instance-group:
+ type: array
+ items:
+ $ref: "#/definitions/instance-group"
+ inventory:
+ properties:
+ search:
+ type: object
+ $ref: "#/definitions/search"
+ actions:
+ type: object
+ $ref: "#/definitions/actions"
+ cloud-infrastructure:
+ type: object
+ $ref: "#/definitions/cloud-infrastructure"
+ business:
+ type: object
+ $ref: "#/definitions/business"
+ service-design-and-creation:
+ type: object
+ $ref: "#/definitions/service-design-and-creation"
+ network:
+ type: object
+ $ref: "#/definitions/network"
+ aai-internal:
+ type: object
+ $ref: "#/definitions/aai-internal"
+ inventory-item:
+ properties:
+ inventory-item-type:
+ type: string
+ inventory-item-link:
+ type: string
+ inventory-item-data:
+ type: array
+ items:
+ $ref: "#/definitions/inventory-item-data"
+ tagged-inventory-item-list:
+ type: array
+ items:
+ $ref: "#/definitions/tagged-inventory-item-list"
+ inventory-item-data:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ inventory-response-item:
+ description: |
+ Inventory item for response list
+ properties:
+ model-name:
+ type: string
+ extra-properties:
+ type: object
+ $ref: "#/definitions/extra-properties"
+ inventory-response-items:
+ type: object
+ $ref: "#/definitions/inventory-response-items"
+ inventory-response-items:
+ description: |
+ Container for inventory items in response list
+ properties:
+ inventory-response-item:
+ type: array
+ items:
+ $ref: "#/definitions/inventory-response-item"
+ ipsec-configuration:
+ description: |
+ IPSec configuration node will contain various configuration data for the NMTE VNF. This node will have an edge to the generic-vnf (vnf type = TE). Starting 1607, this data will be populated by SDN-C
+ ###### Related Nodes
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)
+ - FROM vig-server( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)
+ - IPSEC-CONFIGURATION is DELETED when these are DELETED VIG-SERVER
+ required:
+ - ipsec-configuration-id
+ properties:
+ ipsec-configuration-id:
+ type: string
+ description: UUID of this configuration
+ requested-vig-address-type:
+ type: string
+ description: Indicate the type of VIG server like AVPN, INTERNET, BOTH
+ requested-encryption-strength:
+ type: string
+ description: Encryption values like 3des-cbc, des-cbc, aes-128-cbc, aes-192-cbc, aes-265-cbc
+ requested-dmz-type:
+ type: string
+ description: can offer a shared DMZ or a DMZ specific to a customer
+ shared-dmz-network-address:
+ type: string
+ description: Network address of shared DMZ
+ requested-customer-name:
+ type: string
+ description: If the DMZ is a custom DMZ, this field will indicate the customer information
+ ike-version:
+ type: string
+ description: can be 1 or 2
+ ikev1-authentication:
+ type: string
+ description: Contains values like md5, sha1, sha256, sha384
+ ikev1-encryption:
+ type: string
+ description: Encyption values like 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
+ ikev1-dh-group:
+ type: string
+ description: Diffie-Hellman group like DH-GROUP2, DH-GROUP5, DH-GROUP14
+ ikev1-am-group-id:
+ type: string
+ description: Group name defined in VIG for clients using aggressive mode
+ ikev1-am-password:
+ type: string
+ description: pre-shared key for the above group name
+ ikev1-sa-lifetime:
+ type: string
+ description: Lifetime for IKEv1 SA
+ ipsec-authentication:
+ type: string
+ description: md5, sha1, sha256, sha384
+ ipsec-encryption:
+ type: string
+ description: 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
+ ipsec-sa-lifetime:
+ type: string
+ description: Life time for IPSec SA
+ ipsec-pfs:
+ type: string
+ description: enable PFS or not
+ xauth-userid:
+ type: string
+ description: user ID for xAuth, sm-user, ,nmteHostName
+ xauth-user-password:
+ type: string
+ description: Encrypted using the Juniper $9$ algorithm
+ dpd-interval:
+ type: string
+ description: The time between DPD probe
+ dpd-frequency:
+ type: string
+ description: Maximum number of DPD before claiming the tunnel is down
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
@@ -34687,85 +45378,409 @@ definitions:
type: array
items:
$ref: "#/definitions/relationship"
- dvs-switches:
+ vig-servers:
+ type: array
+ items:
+ $ref: "#/definitions/vig-server"
+ ipsec-configurations:
+ properties:
+ ipsec-configuration:
+ type: array
+ items:
+ $ref: "#/definitions/ipsec-configuration"
+ key-data:
+ properties:
+ key-name:
+ type: string
+ key-value:
+ type: string
+ l-interface:
description: |
- Collection of digital virtual switch metadata used for vmWare VCEs and GenericVnfs.
+ Logical interfaces, e.g., a vnic.
+ ###### Related Nodes
+ - TO generic-vnf( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO lag-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)
+ - TO logical-link( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)
+ - TO newvce( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)
+ - TO p-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)
+ - TO vserver( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - FROM sriov-vf( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)
+ - FROM vlan( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)
+ - L-INTERFACE is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST,SRIOV-VF,VLAN
+ - L-INTERFACE deletion means associated objects of these types are also DELETED:LOGICAL-LINK
+ required:
+ - interface-name
properties:
- dvs-switch:
+ interface-name:
+ type: string
+ description: Name given to the interface
+ interface-role:
+ type: string
+ description: E.g., CUSTOMER, UPLINK, etc.
+ v6-wan-link-ip:
+ type: string
+ description: Questionably placed - v6 ip addr of this interface (is in vr-lan-interface from Mary B.
+ selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ interface-id:
+ type: string
+ description: ID of interface
+ macaddr:
+ type: string
+ description: MAC address for the interface
+ network-name:
+ type: string
+ description: Name of the network
+ management-option:
+ type: string
+ description: Whether A&AI should be managing this interface of not. Could have value like CUSTOMER
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ vlans:
+ type: array
+ items:
+ $ref: "#/definitions/vlan"
+ sriov-vfs:
+ type: array
+ items:
+ $ref: "#/definitions/sriov-vf"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ l3-interface-ipv4-address-list:
type: array
items:
- $ref: "#/definitions/dvs-switch"
- oam-network:
+ $ref: "#/definitions/l3-interface-ipv4-address-list"
+ l3-interface-ipv6-address-list:
+ type: array
+ items:
+ $ref: "#/definitions/l3-interface-ipv6-address-list"
+ l-interfaces:
description: |
- OAM network, to be deprecated shortly. Do not use for new purposes.
+ Collection of logical interfaces.
+ properties:
+ l-interface:
+ type: array
+ items:
+ $ref: "#/definitions/l-interface"
+ l3-interface-ipv4-address-list:
+ description: |
+ IPv4 Address Range
###### Related Nodes
- - TO complex (Many2Many)
- - TO service-capability (Many2Many)
- - FROM cloud-region (is composed of oam-network)
+ - TO l3-network( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - TO subnet( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - TO l-interface( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - TO vlan( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
required:
- - network-uuid
+ - l3-interface-ipv4-address
+ properties:
+ l3-interface-ipv4-address:
+ type: string
+ description: IP address
+ l3-interface-ipv4-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 32 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
+ type: string
+ description: Neutron network id of the interface that address belongs to
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of subnet that address belongs to
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ l3-interface-ipv6-address-list:
+ description: |
+ IPv6 Address Range
+ ###### Related Nodes
+ - TO l3-network( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - TO subnet( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - TO l-interface( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - TO vlan( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ required:
+ - l3-interface-ipv6-address
+ properties:
+ l3-interface-ipv6-address:
+ type: string
+ description: IP address
+ l3-interface-ipv6-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 128 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
+ type: string
+ description: Neutron network id of the interface that address belongs to
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of subnet that address belongs to
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ l3-network:
+ description: |
+ Generic network definition
+ ###### Related Nodes
+ - TO network-policy( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)
+ - TO route-table-reference( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)
+ - TO vpn-binding( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM complex( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - FROM ctag-assignment( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM segmentation-assignment( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)
+ - FROM subnet( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)
+ - L3-NETWORK is DELETED when these are DELETED CTAG-ASSIGNMENT,SEGMENTATION-ASSIGNMENT,SUBNET
+ required:
+ - network-id
- network-name
- - cvlan-tag
+ - is-bound-to-vpn
+ - is-provider-network
+ - is-shared-network
+ - is-external-network
properties:
- network-uuid:
+ network-id:
type: string
- description: UUID of the network. Unique across a cloud-region
+ description: Network ID, should be uuid. Unique across A&AI.
network-name:
type: string
- description: Name of the network.
- cvlan-tag:
+ description: Name of the network, governed by some naming convention..
+ network-type:
+ type: string
+ description: Type of the network - who defines these values?
+ network-role:
+ type: string
+ description: Role the network plans - who defines these values?
+ network-technology:
+ type: string
+ description: Network technology - who defines these values?
+ neutron-network-id:
+ type: string
+ description: Neutron network id of this Interface
+ is-bound-to-vpn:
+ type: boolean
+ service-id:
+ type: string
+ description: Unique identifier of service from ASDC
+ network-role-instance:
type: integer
format: int64
- description: cvlan-id
- ipv4-oam-gateway-address:
+ description: network role instance
+ resource-version:
type: string
- description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
- ipv4-oam-gateway-address-prefix-length:
- type: integer
- format: int32
- description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ contrail-network-fqdn:
+ type: string
+ description: Contrail FQDN for the network
+ persona-model-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ physical-network-name:
+ type: string
+ description: Name associated with the physical network.
+ is-provider-network:
+ type: boolean
+ is-shared-network:
+ type: boolean
+ is-external-network:
+ type: boolean
+ subnets:
+ type: array
+ items:
+ $ref: "#/definitions/subnet"
+ ctag-assignments:
+ type: array
+ items:
+ $ref: "#/definitions/ctag-assignment"
+ segmentation-assignments:
+ type: array
+ items:
+ $ref: "#/definitions/segmentation-assignment"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ description: Relates to tenant (or is it a child of tenant), complex, service, vpn-binding
+ l3-networks:
+ properties:
+ l3-network:
+ type: array
+ items:
+ $ref: "#/definitions/l3-network"
+ lag-interface:
+ description: |
+ Link aggregate interface
+ ###### Related Nodes
+ - TO generic-vnf( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO lag-link( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)
+ - TO p-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)
+ - TO pnf( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - TO pserver( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - TO vpls-pe( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)
+ - LAG-INTERFACE is DELETED when these are DELETED L-INTERFACE
+ - LAG-INTERFACE deletion means associated objects of these types are also DELETED:LAG-LINK
+ required:
+ - interface-name
+ properties:
+ interface-name:
+ type: string
+ description: Name that identifies the link aggregate interface
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- oam-networks:
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/l-interface"
+ lag-interfaces:
description: |
- Collection of OAM networks, to be deprecated shortly. Do not use for new purposes.
+ Collection of link aggregate interfaces.
properties:
- oam-network:
+ lag-interface:
type: array
items:
- $ref: "#/definitions/oam-network"
- availability-zone:
+ $ref: "#/definitions/lag-interface"
+ lag-link:
description: |
- Availability zone, a collection of compute hosts/pservers
- ###### Default Delete Scope
- ERROR_IF_ANY_IN_EDGES
- ###### Related Nodes
- - TO complex (Many2Many)
- - TO service-capability (Many2Many)
- - FROM cloud-region (is composed of availability-zone)
- - FROM ctag-pool
- - FROM dvs-switch
- - FROM generic-vnf
- - FROM pserver
- - FROM vce
+ LAG links can connect lag-interfaces
+ ###### Related Nodes
+ - FROM lag-interface( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)
required:
- - availability-zone-name
- - hypervisor-type
+ - link-name
properties:
- availability-zone-name:
+ link-name:
type: string
- description: Name of the availability zone. Unique across a cloud region
- hypervisor-type:
+ description: Alphabetical concatenation of lag-interface names
+ resource-version:
type: string
- description: Type of hypervisor. Source of truth should define valid values.
- operational-state:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ lag-links:
+ description: |
+ Collection of link aggregation connections
+ properties:
+ lag-link:
+ type: array
+ items:
+ $ref: "#/definitions/lag-link"
+ license:
+ description: |
+ Metadata for license group.
+ ###### Related Nodes
+ - TO generic-vnf( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vce( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ required:
+ - group-uuid
+ - resource-uuid
+ properties:
+ group-uuid:
type: string
- description: State that indicates whether the availability zone should be used, etc. Source of truth should define valid values.
+ description: Unique ID for the license group the resource belongs to, should be uuid.
+ resource-uuid:
+ type: string
+ description: Unique ID of a license resource.
+ resource-version:
+ type: string
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ licenses:
+ description: |
+ Licenses to be allocated across resources, keyed by group-uuid and resource-uuid, related to license management
+ properties:
+ license:
+ type: array
+ items:
+ $ref: "#/definitions/license"
+ line-of-business:
+ description: |
+ describes a line-of-business
+ ###### Related Nodes
+ - TO generic-vnf( line-of-business org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)
+ required:
+ - line-of-business-name
+ properties:
+ line-of-business-name:
+ type: string
+ description: Name of the line-of-business (product)
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
@@ -34773,114 +45788,536 @@ definitions:
type: array
items:
$ref: "#/definitions/relationship"
- availability-zones:
+ lines-of-business:
description: |
- Collection of availability zones
+ Collection of lines-of-business
properties:
- availability-zone:
+ line-of-business:
type: array
items:
- $ref: "#/definitions/availability-zone"
- cloud-region:
+ $ref: "#/definitions/line-of-business"
+ logical-link:
description: |
- cloud-region designates an installation of a cloud cluster or region or instantiation.
- ###### Default Delete Scope
- THIS_NODE_ONLY
- ###### Related Nodes
- - TO complex (Many2One)
- - TO l3-network (Many2Many)
- - TO tenant (comprises cloud-region, One2Many)
- - TO image (comprises cloud-region, One2Many)
- - TO flavor (comprises cloud-region, One2Many)
- - TO availability-zone (comprises cloud-region, One2Many)
- - TO oam-network (comprises cloud-region, One2Many)
- - TO dvs-switch (comprises cloud-region, One2Many)
- - TO volume-group (comprises cloud-region, One2Many)
- - TO group-assignment (comprises cloud-region, One2Many)
- - TO snapshot (comprises cloud-region, One2Many)
- - FROM pserver
+ Logical links generally connect l-interfaces but are used to express logical connectivity between two points
+ ###### Related Nodes
+ - TO generic-vnf( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)
+ - TO lag-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)
+ - TO logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - TO pnf( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)
+ - TO pserver( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)
+ - TO virtual-data-center( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)
+ - FROM p-interface( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - FROM vlan( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
required:
- - cloud-owner
- - cloud-region-id
+ - link-name
+ - link-type
properties:
- cloud-owner:
+ link-name:
type: string
- description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
- cloud-region-id:
+ description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
+ link-type:
type: string
- description: Identifier used by the vendor for the region. Second part of composite key
- cloud-type:
+ description: Type of logical link, e.g., evc
+ speed-value:
type: string
- description: Type of the cloud (e.g., openstack)
- owner-defined-type:
+ description: Captures the numeric part of the speed
+ speed-units:
type: string
- description: Cloud-owner defined type indicator (e.g., DCP, LCP)
- cloud-region-version:
+ description: Captures the units corresponding to the speed
+ ip-version:
type: string
- description: Software version employed at the site
- identity-url:
+ description: v4, v6, or ds for dual stack
+ routing-protocol:
type: string
- description: URL of the keystone identity service
- cloud-zone:
+ description: For example, static or BGP
+ resource-version:
type: string
- description: Zone where the cloud is homed
- complex-name:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ persona-model-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ operational-status:
+ type: string
+ description: Indication of operational status of the logical link.
+ link-role:
+ type: string
+ description: Indication of the network use of the logical link.
+ link-name2:
+ type: string
+ description: Alias or alternate name (CLCI or D1 name).
+ link-id:
+ type: string
+ description: UUID of the logical-link, SDNC generates this.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ logical-links:
+ description: |
+ Collection of logical connections
+ properties:
+ logical-link:
+ type: array
+ items:
+ $ref: "#/definitions/logical-link"
+ metadata:
+ description: |
+ Collection of metadatum (key/value pairs)
+ properties:
+ metadatum:
+ type: array
+ items:
+ $ref: "#/definitions/metadatum"
+ metadatum:
+ description: |
+ Key/value pairs
+ ###### Related Nodes
+ - TO connector( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)
+ - TO image( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)
+ - TO service-instance( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - TO model( metadatum org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ required:
+ - metaname
+ - metaval
+ properties:
+ metaname:
+ type: string
+ metaval:
type: string
- description: complex name for cloud-region instance
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- volume-groups:
+ model:
+ description: |
+ Subgraph definition provided by ASDC to describe an inventory asset and its connections related to ASDC models
+ ###### Related Nodes
+ - TO model( model-element isA model, MANY2ONE)
+ - TO model-element (CHILD of model, model startsWith model-element, ONE2MANY)
+ - FROM named-query( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)
+ - FROM model-element( model-element isA model, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - MODEL cannot be deleted if linked to NAMED-QUERY,NAMED-QUERY-ELEMENT
+ - MODEL is DELETED when these are DELETED METADATUM
+ - MODEL deletion means associated objects of these types are also DELETED:MODEL-ELEMENT
+ required:
+ - model-name-version-id
+ - model-type
+ - model-name
+ - model-id
+ - model-version
+ properties:
+ model-name-version-id:
+ type: string
+ description: Unique identifier corresponding to one version of a model in ASDC
+ model-type:
+ type: string
+ description: Type of the model, e.g., service, resource, widget, etc.
+ model-name:
+ type: string
+ description: Name of the model, which can change from version to version.
+ model-id:
+ type: string
+ description: Invariant unique ID which does not change from version to version
+ model-version:
+ type: string
+ description: Version
+ model-description:
+ type: string
+ description: Description
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-elements:
type: array
items:
- $ref: "#/definitions/volume-group"
- tenants:
+ $ref: "#/definitions/model-element"
+ metadata:
type: array
items:
- $ref: "#/definitions/tenant"
- flavors:
+ $ref: "#/definitions/metadatum"
+ relationship-list:
type: array
items:
- $ref: "#/definitions/flavor"
- group-assignments:
+ $ref: "#/definitions/relationship"
+ model-and-named-query-search:
+ description: |
+ ModelAndNamedQuerySearch holds query-parameters and instance-properties for performing a named-query or model query
+ properties:
+ query-parameters:
+ type: object
+ $ref: "#/definitions/query-parameters"
+ instance-filters:
+ type: object
+ $ref: "#/definitions/instance-filters"
+ top-node-type:
+ type: string
+ model-constraint:
+ description: |
+ This is how we would capture constraints defining allowed sets of elements.
+ ###### Related Nodes
+ - TO model-element( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)
+ - MODEL-CONSTRAINT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET
+ required:
+ - model-constraint-uuid
+ - constrained-element-set-uuid-to-replace
+ properties:
+ model-constraint-uuid:
+ type: string
+ constrained-element-set-uuid-to-replace:
+ type: string
+ constrained-element-sets:
type: array
items:
- $ref: "#/definitions/group-assignment"
- snapshots:
+ $ref: "#/definitions/constrained-element-set"
+ model-constraints:
+ properties:
+ model-constraint:
+ type: array
+ items:
+ $ref: "#/definitions/model-constraint"
+ model-element:
+ description: |
+ Defines how other models combine to make up a higher-level model.
+ ###### Related Nodes
+ - TO element-choice-set( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)
+ - TO model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - TO model( model-element isA model, MANY2ONE)
+ - FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM model-constraint( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM model (PARENT of model-element, model startsWith model-element)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - MODEL-ELEMENT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET,MODEL-CONSTRAINT
+ required:
+ - model-element-uuid
+ - new-data-del-flag
+ - cardinality
+ properties:
+ model-element-uuid:
+ type: string
+ new-data-del-flag:
+ type: string
+ description: Indicates whether this element was created as part of instantiation from this model
+ cardinality:
+ type: string
+ description: How many of this type of element are required/allowed
+ linkage-points:
+ type: string
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-elements:
type: array
items:
- $ref: "#/definitions/snapshot"
- images:
+ $ref: "#/definitions/model-element"
+ description: Defines how other models combine to make up a higher-level model
+ model-constraints:
type: array
items:
- $ref: "#/definitions/image"
- dvs-switches:
+ $ref: "#/definitions/model-constraint"
+ description: Describes new constraints on this model element that are not part of that model's definition
+ relationship-list:
type: array
items:
- $ref: "#/definitions/dvs-switch"
- oam-networks:
+ $ref: "#/definitions/relationship"
+ model-elements:
+ properties:
+ model-element:
+ type: array
+ items:
+ $ref: "#/definitions/model-element"
+ model-ver:
+ description: |
+ Subgraph definition provided by ASDC to describe a specific version of an inventory asset and its connections related to ASDC models
+ ###### Related Nodes
+ - TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - MODEL-VER cannot be deleted if linked to MODEL-ELEMENT
+ - MODEL-VER is DELETED when these are DELETED MODEL-ELEMENT,METADATUM
+ required:
+ - model-version-id
+ - model-name
+ - model-version
+ properties:
+ model-version-id:
+ type: string
+ description: Unique identifier corresponding to one version of a model in ASDC
+ model-name:
+ type: string
+ description: Name of the model, which can change from version to version.
+ model-version:
+ type: string
+ description: Version
+ model-description:
+ type: string
+ description: Description
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-elements:
type: array
items:
- $ref: "#/definitions/oam-network"
- availability-zones:
+ $ref: "#/definitions/model-element"
+ metadata:
type: array
items:
- $ref: "#/definitions/availability-zone"
+ $ref: "#/definitions/metadatum"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- cloud-regions:
+ model-vers:
properties:
- cloud-region:
+ model-ver:
type: array
items:
- $ref: "#/definitions/cloud-region"
+ $ref: "#/definitions/model-ver"
+ models:
+ description: |
+ Collection of subgraph definitions provided by ASDC to describe the inventory assets and their connections related to ASDC models
+ properties:
+ model:
+ type: array
+ items:
+ $ref: "#/definitions/model"
+ multicast-configuration:
+ description: |
+ ###### Related Nodes
+ - FROM vlan( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)
+ required:
+ - multicast-configuration-id
+ - multicast-protocol
+ - rp-type
+ properties:
+ multicast-configuration-id:
+ type: string
+ description: Unique id of multicast configuration.
+ multicast-protocol:
+ type: string
+ description: protocol of multicast configuration
+ rp-type:
+ type: string
+ description: rp type of multicast configuration
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ multicast-configurations:
+ description: |
+ multicast configuration of generic-vnf ip-address
+ properties:
+ multicast-configuration:
+ type: array
+ items:
+ $ref: "#/definitions/multicast-configuration"
+ named-queries:
+ properties:
+ named-query:
+ type: array
+ items:
+ $ref: "#/definitions/named-query"
+ named-query:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - TO model( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - NAMED-QUERY is DELETED when these are DELETED NAMED-QUERY-ELEMENT
+ required:
+ - named-query-uuid
+ - named-query-name
+ - named-query-version
+ properties:
+ named-query-uuid:
+ type: string
+ named-query-name:
+ type: string
+ named-query-version:
+ type: string
+ required-input-param:
+ type: string
+ description:
+ type: string
+ resource-version:
+ type: string
+ named-query-elements:
+ type: array
+ items:
+ $ref: "#/definitions/named-query-element"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ named-query-element:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - TO model( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)
+ - TO named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM property-constraint( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM related-lookup( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - NAMED-QUERY-ELEMENT is DELETED when these are DELETED PROPERTY-CONSTRAINT,RELATED-LOOKUP
+ required:
+ - named-query-element-uuid
+ properties:
+ named-query-element-uuid:
+ type: string
+ property-collect-list:
+ type: string
+ resource-version:
+ type: string
+ property-limit-desc:
+ type: string
+ do-not-output:
+ type: string
+ named-query-elements:
+ type: array
+ items:
+ $ref: "#/definitions/named-query-element"
+ related-lookups:
+ type: array
+ items:
+ $ref: "#/definitions/related-lookup"
+ property-constraints:
+ type: array
+ items:
+ $ref: "#/definitions/property-constraint"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ named-query-elements:
+ properties:
+ named-query-element:
+ type: array
+ items:
+ $ref: "#/definitions/named-query-element"
+ network:
+ description: |
+ Namespace for network inventory resources.
+ properties:
+ logical-links:
+ type: array
+ items:
+ $ref: "#/definitions/logical-link"
+ site-pair-sets:
+ type: array
+ items:
+ $ref: "#/definitions/site-pair-set"
+ vpn-bindings:
+ type: array
+ items:
+ $ref: "#/definitions/vpn-binding"
+ vpls-pes:
+ type: array
+ items:
+ $ref: "#/definitions/vpls-pe"
+ multicast-configurations:
+ type: array
+ items:
+ $ref: "#/definitions/multicast-configuration"
+ vces:
+ type: array
+ items:
+ $ref: "#/definitions/vce"
+ vnfcs:
+ type: array
+ items:
+ $ref: "#/definitions/vnfc"
+ l3-networks:
+ type: array
+ items:
+ $ref: "#/definitions/l3-network"
+ network-policies:
+ type: array
+ items:
+ $ref: "#/definitions/network-policy"
+ generic-vnfs:
+ type: array
+ items:
+ $ref: "#/definitions/generic-vnf"
+ lag-links:
+ type: array
+ items:
+ $ref: "#/definitions/lag-link"
+ newvces:
+ type: array
+ items:
+ $ref: "#/definitions/newvce"
+ pnfs:
+ type: array
+ items:
+ $ref: "#/definitions/pnf"
+ physical-links:
+ type: array
+ items:
+ $ref: "#/definitions/physical-link"
+ ipsec-configurations:
+ type: array
+ items:
+ $ref: "#/definitions/ipsec-configuration"
+ route-table-references:
+ type: array
+ items:
+ $ref: "#/definitions/route-table-reference"
+ network-policies:
+ properties:
+ network-policy:
+ type: array
+ items:
+ $ref: "#/definitions/network-policy"
+ network-policy:
+ description: |
+ ###### Related Nodes
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)
+ required:
+ - network-policy-id
+ properties:
+ network-policy-id:
+ type: string
+ description: UUID representing unique key to this instance
+ network-policy-fqdn:
+ type: string
+ description: Contrail FQDN for the policy
+ heat-stack-id:
+ type: string
+ description: ID for the openStack Heat instance
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
network-profile:
description: |
Network profile populated by SDN-GP for SNMP
###### Related Nodes
- - FROM generic-vnf
+ - TO generic-vnf( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
required:
- nm-profile-name
properties:
@@ -34905,19 +46342,301 @@ definitions:
type: array
items:
$ref: "#/definitions/network-profile"
+ newvce:
+ description: |
+ This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce.
+ ###### Related Nodes
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)
+ - NEWVCE is DELETED when these are DELETED L-INTERFACE
+ required:
+ - vnf-id2
+ - vnf-name
+ - vnf-type
+ properties:
+ vnf-id2:
+ type: string
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ vnf-name:
+ type: string
+ description: Name of VNF.
+ vnf-name2:
+ type: string
+ description: Alternate name of VNF.
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded and clients should expect changes to occur in the future to this field as ASDC matures.
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+ operational-state:
+ type: string
+ description: Indicator for whether the resource is considered operational
+ license-key:
+ type: string
+ description: License key
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address).
+ equipment-role:
+ type: string
+ description: Client should send valid enumerated value.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ ipv4-loopback0-address:
+ type: string
+ description: v4 Loopback0 address
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO.
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/l-interface"
+ newvces:
+ description: |
+ This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce.
+ properties:
+ newvce:
+ type: array
+ items:
+ $ref: "#/definitions/newvce"
+ notification-event:
+ properties:
+ cambria.partition:
+ type: string
+ notification-event-header:
+ type: object
+ $ref: "#/definitions/notification-event-header"
+ notification-event-header:
+ properties:
+ id:
+ type: string
+ timestamp:
+ type: string
+ source-name:
+ type: string
+ domain:
+ type: string
+ sequence-number:
+ type: string
+ severity:
+ type: string
+ event-type:
+ type: string
+ version:
+ type: string
+ action:
+ type: string
+ entity-type:
+ type: string
+ top-entity-type:
+ type: string
+ entity-link:
+ type: string
+ status:
+ type: string
+ notify:
+ required:
+ - event-id
+ properties:
+ event-id:
+ type: string
+ node-type:
+ type: string
+ event-trigger:
+ type: string
+ key-data:
+ type: array
+ items:
+ $ref: "#/definitions/key-data"
+ selflink:
+ type: string
+ oam-network:
+ description: |
+ OAM network, to be deprecated shortly. Do not use for new purposes.
+ ###### Related Nodes
+ - TO cloud-region( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO complex( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)
+ - TO service-capability( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ required:
+ - network-uuid
+ - network-name
+ - cvlan-tag
+ properties:
+ network-uuid:
+ type: string
+ description: UUID of the network. Unique across a cloud-region
+ network-name:
+ type: string
+ description: Name of the network.
+ cvlan-tag:
+ type: integer
+ format: int64
+ description: cvlan-id
+ ipv4-oam-gateway-address:
+ type: string
+ description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
+ ipv4-oam-gateway-address-prefix-length:
+ type: integer
+ format: int32
+ description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ oam-networks:
+ description: |
+ Collection of OAM networks, to be deprecated shortly. Do not use for new purposes.
+ properties:
+ oam-network:
+ type: array
+ items:
+ $ref: "#/definitions/oam-network"
+ operational-environment:
+ description: |
+ It is a logical partition of the cloud which allows to have multiple environments in the production AIC.
+ ###### Related Nodes
+ - TO operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)
+ - FROM operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)
+ required:
+ - operational-environment-id
+ - operational-environment-name
+ - operational-environment-type
+ - operational-environment-status
+ - tenant-context
+ - workload-context
+ properties:
+ operational-environment-id:
+ type: string
+ description: UUID of an operational environment
+ operational-environment-name:
+ type: string
+ description: Operational Environment name
+ operational-environment-type:
+ type: string
+ description: Operational Environment Type.
+ operational-environment-status:
+ type: string
+ description: Status
+ tenant-context:
+ type: string
+ description: Tenant Context.
+ workload-context:
+ type: string
+ description: Workload Context.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ operational-environments:
+ description: |
+ a logical partition of the cloud which allows to have multiple environments in the production AIC.
+ properties:
+ operational-environment:
+ type: array
+ items:
+ $ref: "#/definitions/operational-environment"
+ overloaded-model:
+ description: |
+ Allows for legacy POST of old-style and new-style models
+ required:
+ - model-invariant-id
+ - model-name-version-id
+ - model-type
+ - model-name
+ - model-id
+ - model-version
+ properties:
+ model-invariant-id:
+ type: string
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ model-name-version-id:
+ type: string
+ description: Unique identifier corresponding to one version of a model in ASDC
+ model-type:
+ type: string
+ description: Type of the model, e.g., service, resource, widget, etc.
+ model-name:
+ type: string
+ description: Name of the model, which can change from version to version.
+ model-id:
+ type: string
+ description: Invariant unique ID which does not change from version to version
+ model-version:
+ type: string
+ description: Version
+ model-description:
+ type: string
+ description: Description
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-vers:
+ type: object
+ $ref: "#/definitions/model-vers"
+ relationship-list:
+ type: object
+ $ref: "#/definitions/relationship-list"
+ owning-entities:
+ description: |
+ Collection of owning-entities
+ properties:
+ owning-entity:
+ type: array
+ items:
+ $ref: "#/definitions/owning-entity"
+ owning-entity:
+ description: |
+ describes an owning-entity
+ ###### Related Nodes
+ - FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo owning-entity, MANY2ONE)
+ required:
+ - owning-entity-id
+ - owning-entity-name
+ properties:
+ owning-entity-id:
+ type: string
+ description: UUID of an owning entity
+ owning-entity-name:
+ type: string
+ description: Owning entity name
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
p-interface:
description: |
Physical interface (e.g., nic)
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
###### Related Nodes
- - TO l-interface (comprises p-interface, Many2Many)
- - TO physical-link (Many2Many)
- - TO logical-link (Many2One)
- - FROM lag-interface
- - FROM pserver (is composed of p-interface)
- - FROM pnf (is composed of p-interface)
- - FROM vpls-pe (is composed of p-interface)
+ - TO logical-link( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)
+ - TO physical-link( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)
+ - TO pnf( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - TO pserver( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - TO vpls-pe( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM lag-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)
+ - P-INTERFACE is DELETED when these are DELETED L-INTERFACE
+ - P-INTERFACE deletion means associated objects of these types are also DELETED:PHYSICAL-LINK
required:
- interface-name
properties:
@@ -34961,65 +46680,285 @@ definitions:
type: array
items:
$ref: "#/definitions/p-interface"
- lag-interface:
+ physical-link:
description: |
- Link aggregate interface
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
+ Collection of physical connections, typically between p-interfaces
###### Related Nodes
- - TO lag-link (Many2Many)
- - TO p-interface (Many2Many)
- - TO l-interface (comprises lag-interface, Many2Many)
- - FROM generic-vnf (is composed of lag-interface)
- - FROM pserver (is composed of lag-interface)
- - FROM pnf (is composed of lag-interface)
- - FROM vpls-pe (is composed of lag-interface)
+ - FROM p-interface( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)
required:
- - interface-name
+ - link-name
properties:
- interface-name:
- type: string
- description: Name that identifies the link aggregate interface
- resource-version:
+ link-name:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
speed-value:
type: string
description: Captures the numeric part of the speed
speed-units:
type: string
description: Captures the units corresponding to the speed
+ circuit-id:
+ type: string
+ description: Circuit it
+ dual-mode:
+ type: string
+ description: Dual access mode (e.g., primary, secondary
+ management-option:
+ type: string
+ description: To provide information on who manages this circuit. A&AI or 3rd party transport provider
+ service-provider-name:
+ type: string
+ description: Name of the service Provider on this link.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- l-interfaces:
+ physical-links:
+ description: |
+ Collection of physical connections, typically between p-interfaces
+ properties:
+ physical-link:
+ type: array
+ items:
+ $ref: "#/definitions/physical-link"
+ platform:
+ description: |
+ describes a platform
+ ###### Related Nodes
+ - TO generic-vnf( platform org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)
+ required:
+ - platform-name
+ properties:
+ platform-name:
+ type: string
+ description: Name of the platform
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/l-interface"
- lag-interfaces:
+ $ref: "#/definitions/relationship"
+ platforms:
description: |
- Collection of link aggregate interfaces.
+ Collection of platforms
properties:
- lag-interface:
+ platform:
type: array
items:
+ $ref: "#/definitions/platform"
+ pnf:
+ description: |
+ PNF represents a physical network function. typically equipment used in the D1 world.
+ ###### Related Nodes
+ - TO complex( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - PNF is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
+ required:
+ - pnf-name
+ - in-maint
+ properties:
+ pnf-name:
+ type: string
+ description: unique name of Physical Network Function.
+ pnf-name2:
+ type: string
+ description: name of Physical Network Function.
+ pnf-name2-source:
+ type: string
+ description: source of name2
+ pnf-id:
+ type: string
+ description: id of pnf
+ equip-type:
+ type: string
+ description: Equipment type. Source of truth should define valid values.
+ equip-vendor:
+ type: string
+ description: Equipment vendor. Source of truth should define valid values.
+ equip-model:
+ type: string
+ description: Equipment model. Source of truth should define valid values.
+ management-option:
+ type: string
+ description: identifier of managed by company or customer
+ ipaddress-v4-oam:
+ type: string
+ description: ipv4-oam-address with new naming convention for IP addresses
+ sw-version:
+ type: string
+ description: sw-version is the version of SW for the hosted application on the PNF.
+ orchestration-status:
+ type: string
+ description: orchestration-status is the status of orchestration on the PNF.
+ in-maint:
+ type: boolean
+ frame-id:
+ type: string
+ description: ID of the physical frame (relay rack) where pnf is installed.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ p-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/p-interface"
+ lag-interfaces:
+ type: array
+ items:
$ref: "#/definitions/lag-interface"
+ pnfs:
+ description: |
+ Collection of Physical Network Functions.
+ properties:
+ pnf:
+ type: array
+ items:
+ $ref: "#/definitions/pnf"
+ port-group:
+ description: |
+ Used to capture the network interfaces of this VCE
+ ###### Related Nodes
+ - TO vce( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM cvlan-tag( cvlan-tag org.onap.relationships.inventory.BelongsTo port-group, MANY2ONE)
+ - PORT-GROUP is DELETED when these are DELETED CVLAN-TAG
+ required:
+ - interface-id
+ - orchestration-status
+ properties:
+ interface-id:
+ type: string
+ description: Unique ID of the interface
+ neutron-network-id:
+ type: string
+ description: Neutron network id of this Interface
+ neutron-network-name:
+ type: string
+ description: Neutron network name of this Interface
+ interface-role:
+ type: string
+ description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ port-group-id:
+ type: string
+ description: Unique ID for port group in vmware
+ port-group-name:
+ type: string
+ description: Likely to duplicate value of neutron network name
+ switch-name:
+ type: string
+ description: DVS or standard switch name (should be non-null for port groups associated with DVS)
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ cvlan-tags:
+ type: array
+ items:
+ $ref: "#/definitions/cvlan-tag-entry"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ port-groups:
+ properties:
+ port-group:
+ type: array
+ items:
+ $ref: "#/definitions/port-group"
+ project:
+ description: |
+ describes the project
+ ###### Related Nodes
+ - TO service-instance( project org.onap.relationships.inventory.Uses service-instance, ONE2MANY)
+ required:
+ - project-name
+ properties:
+ project-name:
+ type: string
+ description: Name of the project deploying a service
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ projects:
+ description: |
+ Collection of projects
+ properties:
+ project:
+ type: array
+ items:
+ $ref: "#/definitions/project"
+ properties:
+ description: |
+ Property holder for query properties or instance properties
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ property-constraint:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query-element( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ required:
+ - property-constraint-uuid
+ - constraint-type
+ - property-name
+ - property-value
+ properties:
+ property-constraint-uuid:
+ type: string
+ constraint-type:
+ type: string
+ property-name:
+ type: string
+ property-value:
+ type: string
+ resource-version:
+ type: string
+ property-constraints:
+ properties:
+ property-constraint:
+ type: array
+ items:
+ $ref: "#/definitions/property-constraint"
pserver:
description: |
Compute host whose hostname must be unique and must exactly match what is sent as a relationship to a vserver.
- ###### Default Delete Scope
- ERROR_4_IN_EDGES_OR_CASCADE
- ###### Related Nodes
- - TO complex (Many2One)
- - TO cloud-region (Many2One)
- - TO availability-zone (Many2One)
- - TO lag-interface (comprises pserver, Many2Many)
- - TO p-interface (comprises pserver, Many2Many)
- - FROM generic-vnf
- - FROM group-assignment
- - FROM vserver
- - FROM logical-link
+ ###### Related Nodes
+ - TO group-assignment( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)
+ - TO availability-zone( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)
+ - TO cloud-region( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)
+ - TO complex( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - FROM vserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)
+ - PSERVER cannot be deleted if linked to GENERIC-VNF,LOGICAL-LINK,VSERVER
+ - PSERVER is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
+ - PSERVER cannot be deleted if linked to GROUP-ASSIGNMENT
required:
- hostname
- in-maint
@@ -35100,126 +47039,389 @@ definitions:
type: array
items:
$ref: "#/definitions/pserver"
- virtual-data-center:
+ query-parameters:
description: |
- Virtual organization of cloud infrastructure elements in a data center context
+ QueryParameters for performing a named-query or model query
+ properties:
+ named-query:
+ type: object
+ $ref: "#/definitions/named-query"
+ model:
+ type: object
+ $ref: "#/definitions/model"
+ related-lookup:
+ description: |
+ TBD
###### Related Nodes
- - TO generic-vnf (Many2Many)
- - TO logical-link (Many2Many)
- - FROM connector
+ - TO named-query-element( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
required:
- - vdc-id
- - vdc-name
+ - related-lookup-uuid
+ - source-node-type
+ - source-node-property
+ - target-node-type
+ - target-node-property
properties:
- vdc-id:
+ related-lookup-uuid:
type: string
- description: Unique ID of the vdc
- vdc-name:
+ source-node-type:
+ type: string
+ source-node-property:
+ type: string
+ target-node-type:
+ type: string
+ target-node-property:
+ type: string
+ property-collect-list:
type: string
- description: Name of the virtual data center
resource-version:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- virtual-data-centers:
- description: |
- Virtual organization of cloud infrastructure elements in a data center context
+ related-lookups:
properties:
- virtual-data-center:
+ related-lookup:
type: array
items:
- $ref: "#/definitions/virtual-data-center"
- cloud-infrastructure:
+ $ref: "#/definitions/related-lookup"
+ related-to-property:
+ properties:
+ property-key:
+ type: string
+ description: Key part of a key/value pair
+ property-value:
+ type: string
+ description: Value part of a key/value pair
+ relationship:
+ properties:
+ related-to:
+ type: string
+ description: A keyword provided by A&AI to indicate type of node.
+ related-link:
+ type: string
+ description: URL to the object in A&AI.
+ relationship-data:
+ type: array
+ items:
+ $ref: "#/definitions/relationship-data"
+ relationship-data:
+ required:
+ - relationship-key
+ - relationship-value
+ properties:
+ relationship-key:
+ type: string
+ description: A keyword provided by A&AI to indicate an attribute.
+ relationship-value:
+ type: string
+ description: Value of the attribute.
+ relationship-list:
+ properties:
+ relationship:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ reserved-prop-names:
description: |
- Namespace for cloud infrastructure.
+ Internal map to define some reserved properties of a vertex
properties:
- complexes:
+ last-mod-source-of-truth:
+ type: string
+ aai-node-type:
+ type: string
+ aai-created-ts:
+ type: integer
+ format: int64
+ aai-unique-key:
+ type: string
+ aai-last-mod-ts:
+ type: integer
+ format: int64
+ source-of-truth:
+ type: string
+ response-list:
+ description: |
+ Response container for the results of a named-query or model query
+ properties:
+ inventory-response-items:
+ type: object
+ $ref: "#/definitions/inventory-response-items"
+ result-data:
+ properties:
+ resource-type:
+ type: string
+ description: The specific type of node in the A&AI graph
+ resource-link:
+ type: string
+ description: The URL to the specific resource
+ route-table-reference:
+ description: |
+ Openstack route table reference.
+ ###### Related Nodes
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)
+ required:
+ - route-table-reference-id
+ - route-table-reference-fqdn
+ properties:
+ route-table-reference-id:
+ type: string
+ description: Route Table Reference id, UUID assigned to this instance.
+ route-table-reference-fqdn:
+ type: string
+ description: FQDN entry in the route table.
+ resource-version:
+ type: string
+ description: Concurrency value
+ relationship-list:
type: array
items:
- $ref: "#/definitions/complex"
- cloud-regions:
+ $ref: "#/definitions/relationship"
+ route-table-references:
+ description: |
+ Collection of openstack route table references
+ properties:
+ route-table-reference:
type: array
- items:
- $ref: "#/definitions/cloud-region"
- network-profiles:
+ items:
+ $ref: "#/definitions/route-table-reference"
+ route-target:
+ description: |
+ Route target information
+ ###### Related Nodes
+ - TO vpn-binding( route-target org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2ONE)
+ required:
+ - global-route-target
+ - route-target-role
+ properties:
+ global-route-target:
+ type: string
+ description: Number used to identify an RT, globally unique in the network
+ route-target-role:
+ type: string
+ description: Role assigned to this route target
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/network-profile"
- pservers:
+ $ref: "#/definitions/relationship"
+ route-targets:
+ description: |
+ Collection of route target information
+ properties:
+ route-target:
+ type: array
+ items:
+ $ref: "#/definitions/route-target"
+ routing-instance:
+ description: |
+ ###### Related Nodes
+ - TO site-pair-set( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)
+ - FROM site-pair( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)
+ - ROUTING-INSTANCE is DELETED when these are DELETED SITE-PAIR
+ required:
+ - routing-instance-id
+ properties:
+ routing-instance-id:
+ type: string
+ description: Unique id of routing instance
+ rpm-owner:
+ type: string
+ description: rpm owner
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ site-pairs:
type: array
items:
- $ref: "#/definitions/pserver"
- virtual-data-centers:
+ $ref: "#/definitions/site-pair"
+ relationship-list:
type: array
items:
- $ref: "#/definitions/virtual-data-center"
- connector:
+ $ref: "#/definitions/relationship"
+ routing-instances:
description: |
- Collection of resource instances used to connect a variety of disparate inventory widgets
+ set of probes related to generic-vnf routing instance
+ properties:
+ routing-instance:
+ type: array
+ items:
+ $ref: "#/definitions/routing-instance"
+ sdn-zone-response:
+ properties:
+ oam-networks:
+ type: object
+ $ref: "#/definitions/oam-networks"
+ az-and-dvs-switches:
+ type: array
+ items:
+ $ref: "#/definitions/az-and-dvs-switches"
+ search:
+ properties:
+ edge-tag-query-result:
+ type: object
+ $ref: "#/definitions/edge-tag-query-result"
+ edge-tag-query-request:
+ type: object
+ $ref: "#/definitions/edge-tag-query-request"
+ search-results:
+ type: object
+ $ref: "#/definitions/search-results"
+ sdn-zone-response:
+ type: object
+ $ref: "#/definitions/sdn-zone-response"
+ search-results:
+ properties:
+ result-data:
+ type: array
+ items:
+ $ref: "#/definitions/result-data"
+ secondary-filt:
+ description: |
+ SecondaryFilt for performing a named-query or model query
+ secondary-filter:
+ properties:
+ property-name:
+ type: string
+ filter-type:
+ type: string
+ property-value:
+ type: string
+ secondary-filts:
+ description: |
+ SecondaryFilts for performing a named-query or model query
+ properties:
+ secondary-filt:
+ type: array
+ items:
+ $ref: "#/definitions/secondary-filt"
+ segmentation-assignment:
+ description: |
+ Openstack segmentation assignment.
###### Related Nodes
- - TO virtual-data-center (Many2Many)
- - TO metadatum (comprises connector, Many2Many)
- - FROM service-instance
+ - TO l3-network( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
required:
- - resource-instance-id
+ - segmentation-id
properties:
- resource-instance-id:
+ segmentation-id:
type: string
- description: Unique id of resource instance.
+ description: Route Table Reference id, UUID assigned to this instance.
resource-version:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- persona-model-id:
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ segmentation-assignments:
+ description: |
+ Collection of openstack segmentation assignments
+ properties:
+ segmentation-assignment:
+ type: array
+ items:
+ $ref: "#/definitions/segmentation-assignment"
+ service:
+ description: |
+ Stand-in for service model definitions. Likely to be deprecated in favor of models from ASDC.
+ required:
+ - service-id
+ - service-description
+ properties:
+ service-id:
type: string
- description: the ASDC model id for this resource or service model.
- persona-model-version:
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ service-description:
type: string
- description: the ASDC model version for this resource or service model.
- model-version-id:
+ description: Description of the service
+ service-selflink:
type: string
- description: the ASDC model version for this resource or service model.
- widget-model-id:
+ description: URL to endpoint where AAI can get more details
+ resource-version:
type: string
- description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
- widget-model-version:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ service-version:
type: string
- description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ description: service version
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- metadata:
+ service-capabilities:
+ description: |
+ Collection of service capabilities.
+ properties:
+ service-capability:
+ type: array
+ items:
+ $ref: "#/definitions/service-capability"
+ service-capability:
+ description: |
+ Early definition of server/resource pairings, likely to be replaced by models. No new use should be made of this.
+ ###### Related Nodes
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - SERVICE-CAPABILITY cannot be deleted if linked to AVAILABILITY-ZONE,OAM-NETWORK
+ required:
+ - service-type
+ - vnf-type
+ properties:
+ service-type:
+ type: string
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded and clients should expect changes to occur in the future to this field as ASDC matures.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/metadatum"
- connectors:
+ $ref: "#/definitions/relationship"
+ service-design-and-creation:
description: |
- Collection of resource instances used to connect a variety of disparate inventory widgets
+ Namespace for objects managed by ASDC
properties:
- connector:
+ vnf-images:
type: array
- items:
- $ref: "#/definitions/connector"
+ items:
+ $ref: "#/definitions/vnf-image"
+ services:
+ type: array
+ items:
+ $ref: "#/definitions/service"
+ service-capabilities:
+ type: array
+ items:
+ $ref: "#/definitions/service-capability"
+ models:
+ type: array
+ items:
+ $ref: "#/definitions/model"
+ named-queries:
+ type: array
+ items:
+ $ref: "#/definitions/named-query"
service-instance:
description: |
Instance of a service
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
- ###### Related Nodes
- - TO cvlan-tag (Many2Many)
- - TO connector (Many2Many)
- - TO metadatum (comprises service-instance, Many2Many)
- - TO logical-link (Many2Many)
- - TO vlan (One2Many)
- - TO service-instance (One2Many)
- - FROM generic-vnf
- - FROM l3-network
- - FROM service-subscription (is composed of service-instance)
- - FROM vce
- - FROM service-instance
+ ###### Related Nodes
+ - TO generic-vnf( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)
+ - TO l3-network( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)
+ - TO connector( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)
+ - TO cvlan-tag( service-instance org.onap.relationships.inventory.ComposedOf cvlan-tag, MANY2MANY)
+ - TO logical-link( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - TO service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)
+ - TO vlan( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)
+ - TO service-subscription( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)
+ - TO vce( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)
+ - SERVICE-INSTANCE is DELETED when these are DELETED METADATUM
+ - SERVICE-INSTANCE deletion means associated objects of these types are also DELETED:LOGICAL-LINK
required:
- service-instance-id
properties:
@@ -35287,12 +47489,11 @@ definitions:
service-subscription:
description: |
Object that group service instances.
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
###### Related Nodes
- - TO service-instance (comprises service-subscription, Many2Many)
- - FROM customer (is composed of service-subscription)
- - FROM tenant
+ - TO customer( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)
+ - TO tenant( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)
+ - SERVICE-SUBSCRIPTION is DELETED when these are DELETED SERVICE-INSTANCE
required:
- service-type
properties:
@@ -35321,63 +47522,781 @@ definitions:
type: array
items:
$ref: "#/definitions/service-subscription"
- customer:
+ services:
+ description: |
+ Collection of service model definitions. Likely to be deprecated in favor of models from ASDC.
+ properties:
+ service:
+ type: array
+ items:
+ $ref: "#/definitions/service"
+ site-pair:
description: |
- customer identifiers to provide linkage back to BSS information.
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
###### Related Nodes
- - TO service-subscription (comprises customer, Many2Many)
+ - TO routing-instance( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)
+ - FROM class-of-service( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)
+ - SITE-PAIR is DELETED when these are DELETED CLASS-OF-SERVICE
required:
- - global-customer-id
- - subscriber-name
- - subscriber-type
+ - site-pair-id
properties:
- global-customer-id:
+ site-pair-id:
type: string
- description: Global customer id used across ECOMP to uniquely identify customer.
- subscriber-name:
+ description: unique identifier of probe
+ source-ip:
type: string
- description: Subscriber name, an alternate way to retrieve a customer.
- subscriber-type:
+ description: Prefix address
+ destination-ip:
type: string
- description: Subscriber type, a way to provide VID with only the INFRA customers.
+ description: Prefix address
+ ip-version:
+ type: string
+ description: ip version, v4, v6
+ destination-hostname:
+ type: string
+ description: Hostname of the destination equipment to which SLAs are measured against.
+ destination-equip-type:
+ type: string
+ description: The type of destinatination equipment. Could be Router, etc.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- service-subscriptions:
+ classes-of-service:
type: array
items:
- $ref: "#/definitions/service-subscription"
+ $ref: "#/definitions/class-of-service"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- customers:
+ site-pair-set:
description: |
- Collection of customer identifiers to provide linkage back to BSS information.
+ Set of instances for probes used to measure service level agreements
+ ###### Related Nodes
+ - TO generic-vnf( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM routing-instance( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)
+ - SITE-PAIR-SET is DELETED when these are DELETED ROUTING-INSTANCE
+ required:
+ - site-pair-set-id
properties:
- customer:
+ site-pair-set-id:
+ type: string
+ description: Unique id of site pair set.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ routing-instances:
+ type: array
+ items:
+ $ref: "#/definitions/routing-instance"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ site-pair-sets:
+ description: |
+ Collection of sets of instances for probes related to generic-vnf
+ properties:
+ site-pair-set:
type: array
items:
- $ref: "#/definitions/customer"
- business:
+ $ref: "#/definitions/site-pair-set"
+ site-pairs:
description: |
- Namespace for business related constructs
+ probe within a set
properties:
- connectors:
+ site-pair:
+ type: array
+ items:
+ $ref: "#/definitions/site-pair"
+ snapshot:
+ description: |
+ Openstack snapshot
+ ###### Related Nodes
+ - TO cloud-region( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)
+ required:
+ - snapshot-id
+ properties:
+ snapshot-id:
+ type: string
+ description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
+ snapshot-name:
+ type: string
+ description: Snapshot name
+ snapshot-architecture:
+ type: string
+ description: Operating system architecture
+ snapshot-os-distro:
+ type: string
+ description: The common name of the operating system distribution in lowercase
+ snapshot-os-version:
+ type: string
+ description: The operating system version as specified by the distributor.
+ application:
+ type: string
+ description: The application that the image instantiates.
+ application-vendor:
+ type: string
+ description: The vendor of the application.
+ application-version:
+ type: string
+ description: The version of the application.
+ snapshot-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ prev-snapshot-id:
+ type: string
+ description: This field contains the UUID of the previous snapshot (if any).
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/connector"
- customers:
+ $ref: "#/definitions/relationship"
+ snapshots:
+ description: |
+ Collection of openstack snapshots
+ properties:
+ snapshot:
+ type: array
+ items:
+ $ref: "#/definitions/snapshot"
+ sriov-pf:
+ description: |
+ SR-IOV Physical Function
+ ###### Related Nodes
+ - TO p-interface( sriov-pf org.onap.relationships.inventory.BelongsTo p-interface, ONE2ONE)
+ - FROM sriov-vf( sriov-vf org.onap.relationships.inventory.Uses sriov-pf, MANY2ONE)
+ required:
+ - pf-pci-id
+ properties:
+ pf-pci-id:
+ type: string
+ description: Identifier for the sriov-pf
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/customer"
+ $ref: "#/definitions/relationship"
+ sriov-pfs:
+ description: |
+ Collection of SR-IOV Physical Functions.
+ properties:
+ sriov-pf:
+ type: array
+ items:
+ $ref: "#/definitions/sriov-pf"
+ sriov-vf:
+ description: |
+ SR-IOV Virtual Function (not to be confused with virtual network function)
+ ###### Related Nodes
+ - TO l-interface( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)
+ required:
+ - pci-id
+ properties:
+ pci-id:
+ type: string
+ description: PCI ID used to identify the sriov-vf
+ vf-vlan-filter:
+ type: string
+ description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM.
+ vf-mac-filter:
+ type: string
+ description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM.
+ vf-vlan-strip:
+ type: boolean
+ description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM.
+ vf-vlan-anti-spoof-check:
+ type: boolean
+ description: This option ensures anti VLAN spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
+ vf-mac-anti-spoof-check:
+ type: boolean
+ description: This option ensures anti MAC spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
+ vf-mirrors:
+ type: string
+ description: This option defines the set of Mirror objects which essentially mirrors the traffic from source to set of collector VNF Ports.
+ vf-broadcast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows all broadcast traffic to reach the VM
+ vf-unknown-multicast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows unknown multicast traffic to reach the VM
+ vf-unknown-unicast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows unknown unicast traffic to reach the VM
+ vf-insert-stag:
+ type: boolean
+ description: This option, if set to true, instructs to insert outer tag after traffic comes out of VM.
+ vf-link-status:
+ type: string
+ description: This option is used to set the link status. Valid values as of 1607 are on, off, and auto.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
+ type: string
+ description: Neutron network id of the interface
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ sriov-vfs:
+ description: |
+ Collection of SR-IOV Virtual Functions.
+ properties:
+ sriov-vf:
+ type: array
+ items:
+ $ref: "#/definitions/sriov-vf"
+ start-node-filter:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ subnet:
+ description: |
+ ###### Related Nodes
+ - TO l3-network( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - SUBNET cannot be deleted if linked to L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST
+ required:
+ - subnet-id
+ - dhcp-enabled
+ properties:
+ subnet-id:
+ type: string
+ description: Subnet ID, should be UUID.
+ subnet-name:
+ type: string
+ description: Name associated with the subnet.
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of this subnet
+ gateway-address:
+ type: string
+ description: gateway ip address
+ network-start-address:
+ type: string
+ description: network start address
+ cidr-mask:
+ type: string
+ description: cidr mask
+ ip-version:
+ type: string
+ description: ip version
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ dhcp-enabled:
+ type: boolean
+ dhcp-start:
+ type: string
+ description: the start address reserved for use by dhcp
+ dhcp-end:
+ type: string
+ description: the last address reserved for use by dhcp
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ subnets:
+ properties:
+ subnet:
+ type: array
+ items:
+ $ref: "#/definitions/subnet"
+ tagged-inventory-item-list:
+ properties:
+ inventory-item:
+ type: array
+ items:
+ $ref: "#/definitions/inventory-item"
+ tenant:
+ description: |
+ Openstack tenant
+ ###### Related Nodes
+ - TO cloud-region( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO group-assignment( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)
+ - TO l3-network( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO volume-group( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - FROM service-subscription( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)
+ - FROM vserver( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)
+ - TENANT cannot be deleted if linked to VSERVER
+ required:
+ - tenant-id
+ - tenant-name
+ properties:
+ tenant-id:
+ type: string
+ description: Unique id relative to the cloud-region.
+ tenant-name:
+ type: string
+ description: Readable name of tenant
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ vservers:
+ type: array
+ items:
+ $ref: "#/definitions/vserver"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ tenants:
+ description: |
+ Collection of openstack tenants.
+ properties:
+ tenant:
+ type: array
+ items:
+ $ref: "#/definitions/tenant"
+ tunnel-xconnect:
+ description: |
+ Represents the specifics of a tunnel cross connect piece of a resource that gets separately allotted
+ ###### Related Nodes
+ - TO allotted-resource( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)
+ required:
+ - id
+ - bandwidth-up-wan1
+ - bandwidth-down-wan1
+ - bandwidth-up-wan2
+ - bandwidth-down-wan2
+ properties:
+ id:
+ type: string
+ description: Allotted Resource id UUID assigned to this instance.
+ bandwidth-up-wan1:
+ type: string
+ description: The WAN uplink bandwidth for WAN1
+ bandwidth-down-wan1:
+ type: string
+ description: The WAN downlink bandwidth for WAN1
+ bandwidth-up-wan2:
+ type: string
+ description: The WAN uplink bandwidth for WAN2
+ bandwidth-down-wan2:
+ type: string
+ description: The WAN downlink bandwidth for WAN2
+ resource-version:
+ type: string
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ tunnel-xconnects:
+ description: |
+ This object is used to store the specific tunnel cross connect aspects of an allotted resource
+ properties:
+ tunnel-xconnect:
+ type: array
+ items:
+ $ref: "#/definitions/tunnel-xconnect"
+ update:
+ description: |
+ Serves a PATCH like function. Does not enforce concurrency control. Clear each usage with AAI team.
+ required:
+ - update-node-type
+ properties:
+ update-node-type:
+ type: string
+ update-node-key:
+ type: array
+ items:
+ $ref: "#/definitions/update-node-key"
+ update-node-uri:
+ type: string
+ action:
+ type: array
+ items:
+ $ref: "#/definitions/action"
+ update-node-key:
+ properties:
+ key-name:
+ type: string
+ key-value:
+ type: string
+ vce:
+ description: |
+ Virtual Customer Edge Router, used specifically for Gamma. This object is deprecated.
+ ###### Related Nodes
+ - TO availability-zone( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - TO complex( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)
+ - TO vserver( vce tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM port-group( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)
+ - VCE is DELETED when these are DELETED PORT-GROUP
+ required:
+ - vnf-id
+ - vnf-name
+ - vnf-type
+ properties:
+ vnf-id:
+ type: string
+ description: Unique id of VNF. This is unique across the graph.
+ vnf-name:
+ type: string
+ description: Name of VNF.
+ vnf-name2:
+ type: string
+ description: Alternate name of VNF.
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded and clients should expect changes to occur in the future to this field as ASDC matures.
+ service-id:
+ type: string
+ description: Unique identifier of service from ASDC. Expect this to change as ASDC matures.
+ regional-resource-zone:
+ type: string
+ description: Regional way of organizing pservers, source of truth should define values
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ operational-state:
+ type: string
+ description: Indicator for whether the resource is considered operational
+ license-key:
+ type: string
+ description: License key
+ equipment-role:
+ type: string
+ description: Network role being played by this VNF
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ vpe-id:
+ type: string
+ description: Unique ID of VPE connected to this VCE.
+ v6-vce-wan-address:
+ type: string
+ description: Valid v6 IP address for the WAN Link on this router. Implied length of /64.
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure vce, also used for troubleshooting and is IP used for traps generated by VCE.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ ipv4-loopback0-address:
+ type: string
+ description: Loopback0 address
+ entitlement-resource-uuid:
+ type: string
+ description: Entitlement resource uuid
+ port-groups:
+ type: array
+ items:
+ $ref: "#/definitions/port-group"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ vces:
+ description: |
+ Collection of Virtual Customer Edge Routers, used specifically for Gamma. This object is deprecated.
+ properties:
+ vce:
+ type: array
+ items:
+ $ref: "#/definitions/vce"
+ vf-module:
+ description: |
+ a deployment unit of VNFCs
+ ###### Related Nodes
+ - TO generic-vnf( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO l3-network( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)
+ - TO vnfc( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)
+ - TO volume-group( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)
+ - TO vserver( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)
+ - VF-MODULE cannot be deleted if linked to VNFC
+ required:
+ - vf-module-id
+ - is-base-vf-module
+ properties:
+ vf-module-id:
+ type: string
+ description: Unique ID of vf-module.
+ vf-module-name:
+ type: string
+ description: Name of vf-module
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance.
+ orchestration-status:
+ type: string
+ description: orchestration status of this vf-module, mastered by MSO
+ is-base-vf-module:
+ type: boolean
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ persona-model-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ contrail-service-instance-fqdn:
+ type: string
+ description: the Contrail unique ID for a service-instance
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ vf-modules:
+ description: |
+ Collection of vf-modules, a deployment unit of VNFCs
+ properties:
+ vf-module:
+ type: array
+ items:
+ $ref: "#/definitions/vf-module"
+ vig-server:
+ description: |
+ vig-server contains information about a vig server used for IPSec-configuration. Populated by SDN-C from 1607
+ ###### Related Nodes
+ - TO ipsec-configuration( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)
+ required:
+ - vig-address-type
+ properties:
+ vig-address-type:
+ type: string
+ description: indicates whether the VIG is for AVPN or INTERNET
+ ipaddress-v4-vig:
+ type: string
+ description: v4 IP of the vig server
+ ipaddress-v6-vig:
+ type: string
+ description: v6 IP of the vig server
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ vig-servers:
+ properties:
+ vig-server:
+ type: array
+ items:
+ $ref: "#/definitions/vig-server"
+ vip-ipv4-address-list:
+ description: |
+ IPv4 Address Range
+ ###### Related Nodes
+ - TO cloud-region( vip-ipv4-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO instance-group( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO subnet( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv4-address-list, MANY2MANY)
+ required:
+ - vip-ipv4-address
+ properties:
+ vip-ipv4-address:
+ type: string
+ description: IP address
+ vip-ipv4-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 32 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
+ type: string
+ description: Neutron network id of the interface that address belongs to
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of subnet that address belongs to
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ vip-ipv6-address-list:
+ description: |
+ IPv6 Address Range
+ ###### Related Nodes
+ - TO cloud-region( vip-ipv6-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO instance-group( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO subnet( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv6-address-list, MANY2MANY)
+ required:
+ - vip-ipv6-address
+ properties:
+ vip-ipv6-address:
+ type: string
+ description: IP address
+ vip-ipv6-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 128 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
+ type: string
+ description: Neutron network id of the interface that address belongs to
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of subnet that address belongs to
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ virtual-data-center:
+ description: |
+ Virtual organization of cloud infrastructure elements in a data center context
+ ###### Related Nodes
+ - FROM connector( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ required:
+ - vdc-id
+ - vdc-name
+ properties:
+ vdc-id:
+ type: string
+ description: Unique ID of the vdc
+ vdc-name:
+ type: string
+ description: Name of the virtual data center
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ virtual-data-centers:
+ description: |
+ Virtual organization of cloud infrastructure elements in a data center context
+ properties:
+ virtual-data-center:
+ type: array
+ items:
+ $ref: "#/definitions/virtual-data-center"
+ vlan:
+ description: |
+ Definition of vlan
+ ###### Related Nodes
+ - TO l-interface( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)
+ - TO logical-link( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - TO multicast-configuration( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ - VLAN is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST
+ - VLAN deletion means associated objects of these types are also DELETED:LOGICAL-LINK
+ required:
+ - vlan-interface
+ properties:
+ vlan-interface:
+ type: string
+ description: String that identifies the interface
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ vlan-description:
+ type: string
+ description: Used to describe (the service associated with) the vlan
+ backdoor-connection:
+ type: string
+ description: Whether customer is going to use this VLAN for backdoor connection to another customer premise device.
+ vpn-id:
+ type: string
+ description: This indicates the customers VPN ID associated with this vlan
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ l3-interface-ipv4-address-list:
+ type: array
+ items:
+ $ref: "#/definitions/l3-interface-ipv4-address-list"
+ l3-interface-ipv6-address-list:
+ type: array
+ items:
+ $ref: "#/definitions/l3-interface-ipv6-address-list"
+ vlans:
+ properties:
+ vlan:
+ type: array
+ items:
+ $ref: "#/definitions/vlan"
+ vnf:
+ description: |
+ Abstract vnf class
+ required:
+ - vnf-id
+ properties:
+ vnf-id:
+ type: string
+ description: Unique id of VNF. This is unique across the graph.
vnf-image:
description: |
Image object that pertain to a VNF that doesn't have associated vservers. This is a kludge.
###### Related Nodes
- - FROM generic-vnf
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)
+ - VNF-IMAGE cannot be deleted if linked to GENERIC-VNF
required:
- vnf-image-uuid
- application
@@ -35413,58 +48332,110 @@ definitions:
type: array
items:
$ref: "#/definitions/vnf-image"
- service:
+ vnfc:
description: |
- Stand-in for service model definitions. Likely to be deprecated in favor of models from ASDC.
- ###### Default Delete Scope
- ERROR_IF_ANY_IN_EDGES
+ ###### Related Nodes
+ - TO generic-vnf( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vserver( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)
required:
- - service-id
- - service-description
+ - vnfc-name
+ - vnfc-function-code
+ - vnfc-type
+ - in-maint
+ - is-closed-loop-disabled
properties:
- service-id:
+ vnfc-name:
type: string
- description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
- service-description:
+ description: Unique ID of vnfc.
+ vnfc-function-code:
type: string
- description: Description of the service
- service-selflink:
+ description: function code
+ vnfc-type:
type: string
- description: URL to endpoint where AAI can get more details
+ description: type
+ prov-status:
+ type: string
+ description: prov status of this vnfc
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by APP-C
+ ipaddress-v4-oam-vip:
+ type: string
+ description: Oam V4 vip address of this vnfc
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
+ group-notation:
+ type: string
+ description: Group notation of VNFC
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- service-version:
- type: string
- description: service version
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- services:
+ vnfcs:
description: |
- Collection of service model definitions. Likely to be deprecated in favor of models from ASDC.
+ virtual network components associated with a vserver from application controller.
properties:
- service:
+ vnfc:
type: array
items:
- $ref: "#/definitions/service"
- service-capability:
+ $ref: "#/definitions/vnfc"
+ volume:
description: |
- Early definition of server/resource pairings, likely to be replaced by models. No new use should be made of this.
+ Ephemeral Block storage volume.
###### Related Nodes
- - FROM availability-zone
- - FROM oam-network
+ - FROM vserver (PARENT of volume, vserver tosca.relationships.AttachesTo volume)
required:
- - service-type
+ - volume-id
+ - volume-selflink
+ properties:
+ volume-id:
+ type: string
+ description: Unique ID of block storage volume relative to the vserver.
+ volume-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ volume-group:
+ description: |
+ Persistent block-level storage.
+ ###### Related Nodes
+ - TO cloud-region( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO complex( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ required:
+ - volume-group-id
+ - volume-group-name
- vnf-type
properties:
- service-type:
+ volume-group-id:
type: string
- description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ description: Unique ID of volume-group.
+ volume-group-name:
+ type: string
+ description: Name of the volume group.
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this volume-group
vnf-type:
type: string
description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded and clients should expect changes to occur in the future to this field as ASDC matures.
+ orchestration-status:
+ type: string
+ description: Orchestration status of this volume-group
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
@@ -35472,53 +48443,584 @@ definitions:
type: array
items:
$ref: "#/definitions/relationship"
- service-capabilities:
+ volume-groups:
description: |
- Collection of service capabilities.
+ Collection of persistent block-level storage.
properties:
- service-capability:
+ volume-group:
type: array
items:
- $ref: "#/definitions/service-capability"
- element-choice-set:
+ $ref: "#/definitions/volume-group"
+ volumes:
description: |
- This is how we would capture constraints defining allowed sets of elements.
+ Collection of ephemeral Block storage volumes.
+ properties:
+ volume:
+ type: array
+ items:
+ $ref: "#/definitions/volume"
+ vpls-pe:
+ description: |
+ VPLS Provider Edge routers.
###### Related Nodes
- - TO model-element (comprises element-choice-set, One2Many)
- - FROM constrained-element-set (is composed of element-choice-set)
+ - TO complex( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO ctag-pool( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - VPLS-PE is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
required:
- - element-choice-set-uuid
- - element-choice-set-name
+ - equipment-name
properties:
- element-choice-set-uuid:
+ equipment-name:
type: string
- element-choice-set-name:
+ prov-status:
type: string
- cardinality:
+ description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address).
+ equipment-role:
type: string
+ description: Client should send valid enumerated value, e.g., VPLS-PE.
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Temporary location for stag to get to VCE
resource-version:
type: string
- model-elements:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/model-element"
+ $ref: "#/definitions/relationship"
+ p-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/p-interface"
+ lag-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/lag-interface"
+ vpls-pes:
+ description: |
+ Collection of VPLS Provider Edge routers
+ properties:
+ vpls-pe:
+ type: array
+ items:
+ $ref: "#/definitions/vpls-pe"
+ vpn-binding:
+ description: |
+ VPN binding
+ ###### Related Nodes
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - VPN-BINDING cannot be deleted if linked to L3-NETWORK
+ required:
+ - vpn-id
+ - vpn-name
+ - global-route-target
+ properties:
+ vpn-id:
+ type: string
+ description: VPN ID, globally unique within A&AI
+ vpn-name:
+ type: string
+ description: VPN Name
+ global-route-target:
+ type: string
+ description: Number used to identify a VPN, globally unique in the network
+ vpn-platform:
+ type: string
+ description: the platform associated with the VPN example AVPN, Mobility
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- element-choice-sets:
+ description: l3-networks relate to vpn-bindings
+ vpn-bindings:
properties:
- element-choice-set:
+ vpn-binding:
type: array
items:
- $ref: "#/definitions/element-choice-set"
+ $ref: "#/definitions/vpn-binding"
+ vserver:
+ description: |
+ Virtual Servers, aka virtual machine or VM.
+ ###### Related Nodes
+ - TO tenant( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)
+ - TO flavor( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)
+ - TO image( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)
+ - TO pserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)
+ - TO snapshot( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)
+ - TO volume (CHILD of vserver, vserver tosca.relationships.AttachesTo volume, ONE2MANY)
+ - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM vce( vce tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)
+ - FROM vnfc( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)
+ - VSERVER is DELETED when these are DELETED L-INTERFACE
+ - VSERVER deletion means associated objects of these types are also DELETED:VOLUME
+ required:
+ - vserver-id
+ - vserver-name
+ - vserver-selflink
+ - in-maint
+ - is-closed-loop-disabled
+ properties:
+ vserver-id:
+ type: string
+ description: Unique identifier for this vserver relative to its tenant
+ vserver-name:
+ type: string
+ description: Name of vserver
+ vserver-name2:
+ type: string
+ description: Alternative name of vserver
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ vserver-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ volumes:
+ type: array
+ items:
+ $ref: "#/definitions/volume"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/l-interface"
+ vservers:
+ description: |
+ Collection of virtual Servers, aka virtual machines or VMs.
+ properties:
+ vserver:
+ type: array
+ items:
+ $ref: "#/definitions/vserver"
+ zone:
+ description: |
+ A zone is a grouping of assets in a location homing to the same connections into the CBB
+ ###### Related Nodes
+ - TO complex( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM pnf( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ required:
+ - zone-id
+ - zone-name
+ - design-type
+ - zone-context
+ properties:
+ zone-id:
+ type: string
+ description: Code assigned by AIC to the zone
+ zone-name:
+ type: string
+ description: English name associated with the zone
+ design-type:
+ type: string
+ description: Design of zone [Medium/Large?]
+ zone-context:
+ type: string
+ description: Context of zone [production/test]
+ status:
+ type: string
+ description: Status of a zone.
+ resource-version:
+ type: string
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ zones:
+ description: |
+ Collection of zones
+ properties:
+ zone:
+ type: array
+ items:
+ $ref: "#/definitions/zone"
+patchDefinitions:
+ aai-internal:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ action:
+ properties:
+ action-type:
+ type: string
+ action-data:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/action-data"
+ action-data:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ actions:
+ description: |
+ APIs that are more action related than REST (e.g., notify, update).
+ properties:
+ update:
+ type: object
+ $ref: "#/patchDefinitions/update"
+ notify:
+ type: object
+ $ref: "#/patchDefinitions/notify"
+ allotted-resource:
+ description: |
+ Represents a slice or partial piece of a resource that gets separately allotted
+ ###### Related Nodes
+ - TO generic-vnf( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY)
+ - TO instance-group( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO l3-network( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY)
+ - TO vlan( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY)
+ - TO service-instance( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM tunnel-xconnect( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY)
+ - ALLOTTED-RESOURCE is DELETED when these are DELETED TUNNEL-XCONNECT
+ required:
+ - id
+ properties:
+ id:
+ type: string
+ description: Allotted Resource id UUID assigned to this instance.
+ description:
+ type: string
+ description: The descriptive information assigned to this allotted resource instance
+ selflink:
+ type: string
+ description: Link back to more information in the controller
+ persona-model-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ persona-model-customization-id:
+ type: string
+ description: captures the id of all the configuration used to customize the resource for the service.
+ allotted-resources:
+ description: |
+ This object is used to store slices of services being offered
+ properties:
+ allotted-resource:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/allotted-resource"
+ availability-zone:
+ description: |
+ Availability zone, a collection of compute hosts/pservers
+ ###### Related Nodes
+ - TO complex( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO service-capability( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - TO cloud-region( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM ctag-pool( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM dvs-switch( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - FROM pserver( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)
+ - FROM vce( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - AVAILABILITY-ZONE cannot be deleted if linked to CTAG-POOL,DVS-SWITCH,GENERIC-VNF,PSERVER,VCE
+ required:
+ - availability-zone-name
+ - hypervisor-type
+ properties:
+ availability-zone-name:
+ type: string
+ description: Name of the availability zone. Unique across a cloud region
+ hypervisor-type:
+ type: string
+ description: Type of hypervisor. Source of truth should define valid values.
+ operational-state:
+ type: string
+ description: State that indicates whether the availability zone should be used, etc. Source of truth should define valid values.
+ availability-zones:
+ description: |
+ Collection of availability zones
+ properties:
+ availability-zone:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/availability-zone"
+ az-and-dvs-switches:
+ properties:
+ dvs-switches:
+ type: object
+ $ref: "#/patchDefinitions/dvs-switches"
+ availability-zone:
+ type: object
+ $ref: "#/patchDefinitions/availability-zone"
+ business:
+ description: |
+ Namespace for business related constructs
+ properties:
+ connectors:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/connector"
+ customers:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/customer"
+ class-of-service:
+ description: |
+ ###### Related Nodes
+ - TO site-pair( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)
+ required:
+ - cos
+ properties:
+ cos:
+ type: string
+ description: unique identifier of probe
+ probe-id:
+ type: string
+ description: identifier of probe
+ probe-type:
+ type: string
+ description: type of probe
+ classes-of-service:
+ description: |
+ class-of-service of probe
+ properties:
+ class-of-service:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/class-of-service"
+ cloud-infrastructure:
+ description: |
+ Namespace for cloud infrastructure.
+ properties:
+ complexes:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/complex"
+ cloud-regions:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/cloud-region"
+ network-profiles:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/network-profile"
+ pservers:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/pserver"
+ virtual-data-centers:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/virtual-data-center"
+ cloud-region:
+ description: |
+ cloud-region designates an installation of a cloud cluster or region or instantiation.
+ ###### Related Nodes
+ - TO complex( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO l3-network( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM dvs-switch( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM flavor( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM group-assignment( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM image( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM snapshot( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM volume-group( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)
+ - CLOUD-REGION cannot be deleted if linked to DVS-SWITCH,FLAVOR,GROUP-ASSIGNMENT,IMAGE,OAM-NETWORK,SNAPSHOT,TENANT,VOLUME-GROUP
+ - CLOUD-REGION is DELETED when these are DELETED AVAILABILITY-ZONE
+ required:
+ - cloud-owner
+ - cloud-region-id
+ properties:
+ cloud-owner:
+ type: string
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ cloud-region-id:
+ type: string
+ description: Identifier used by the vendor for the region. Second part of composite key
+ cloud-type:
+ type: string
+ description: Type of the cloud (e.g., openstack)
+ owner-defined-type:
+ type: string
+ description: Cloud-owner defined type indicator (e.g., DCP, LCP)
+ cloud-region-version:
+ type: string
+ description: Software version employed at the site
+ identity-url:
+ type: string
+ description: URL of the keystone identity service
+ cloud-zone:
+ type: string
+ description: Zone where the cloud is homed
+ complex-name:
+ type: string
+ description: complex name for cloud-region instance
+ cloud-regions:
+ properties:
+ cloud-region:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/cloud-region"
+ complex:
+ description: |
+ Collection of physical locations that can house cloud-regions.
+ ###### Related Nodes
+ - TO l3-network( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM ctag-pool( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)
+ - FROM pnf( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM vce( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)
+ - FROM volume-group( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM vpls-pe( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - COMPLEX cannot be deleted if linked to AVAILABILITY-ZONE,CLOUD-REGION,OAM-NETWORK,PNF,PSERVER,VCE,VOLUME-GROUP,VPLS-PE
+ - COMPLEX is DELETED when these are DELETED CTAG-POOL
+ required:
+ - physical-location-id
+ - physical-location-type
+ - street1
+ - city
+ - postal-code
+ - country
+ - region
+ properties:
+ physical-location-id:
+ type: string
+ description: Unique identifier for physical location, e.g., CLLI
+ data-center-code:
+ type: string
+ description: Data center code which can be an alternate way to identify a complex
+ complex-name:
+ type: string
+ description: Gamma complex name for LCP instance.
+ identity-url:
+ type: string
+ description: URL of the keystone identity service
+ complexes:
+ description: |
+ Collection of physical locations that can house cloud-regions.
+ properties:
+ complex:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/complex"
+ configuration:
+ description: |
+ Port Mirror Configuration.
+ ###### Related Nodes
+ - TO allotted-resource( configuration org.onap.relationships.inventory.Uses allotted-resource, ONE2ONE)
+ - TO logical-link( configuration org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo configuration, MANY2ONE)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses configuration, ONE2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses configuration, ONE2MANY)
+ - CONFIGURATION is DELETED when these are DELETED METADATUM
+ - CONFIGURATION deletion means associated objects of these types are also DELETED:ALLOTTED-RESOURCE,LOGICAL-LINK
+ required:
+ - configuration-id
+ - configuration-type
+ - configuration-sub-type
+ - orchestration-status
+ - operational-status
+ - configuration-selflink
+ - model-customization-id
+ properties:
+ configuration-id:
+ type: string
+ description: UUID assigned to configuration.
+ management-option:
+ type: string
+ description: Indicates the entity that will manage this feature. Could be an organization or the name of the application as well.
+ configuration-name:
+ type: string
+ description: Name of the configuration.
+ configuration-type:
+ type: string
+ description: port-mirroring-configuration.
+ configuration-sub-type:
+ type: string
+ description: vprobe, pprobe.
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ orchestration-status:
+ type: string
+ description: Orchestration status of the configuration.
+ operational-status:
+ type: string
+ description: Indicator for whether the resource is considered operational.
+ configuration-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details from SDN-GC.
+ model-customization-id:
+ type: string
+ description: id of the configuration used to customize the resource
+ configurations:
+ description: |
+ Collection of configurations
+ properties:
+ configuration:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/configuration"
+ connector:
+ description: |
+ Collection of resource instances used to connect a variety of disparate inventory widgets
+ ###### Related Nodes
+ - TO virtual-data-center( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)
+ - CONNECTOR is DELETED when these are DELETED METADATUM
+ required:
+ - resource-instance-id
+ properties:
+ resource-instance-id:
+ type: string
+ description: Unique id of resource instance.
+ connectors:
+ description: |
+ Collection of resource instances used to connect a variety of disparate inventory widgets
+ properties:
+ connector:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/connector"
constrained-element-set:
description: |
This is how we would capture constraints defining allowed sets of elements.
###### Related Nodes
- - TO element-choice-set (comprises constrained-element-set, One2Many)
- - FROM model-element (is composed of constrained-element-set)
- - FROM model-constraint (is composed of constrained-element-set)
+ - TO model-constraint( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)
+ - TO model-element( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM element-choice-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)
+ - CONSTRAINED-ELEMENT-SET is DELETED when these are DELETED ELEMENT-CHOICE-SET
required:
- constrained-element-set-uuid
- constraint-type
@@ -35530,28 +49032,1382 @@ definitions:
type: string
check-type:
type: string
- resource-version:
+ constrained-element-sets:
+ properties:
+ constrained-element-set:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/constrained-element-set"
+ ctag-assignment:
+ description: |
+ ###### Related Nodes
+ - TO l3-network( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ required:
+ - vlan-id-inner
+ properties:
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: id.
+ ctag-assignments:
+ properties:
+ ctag-assignment:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/ctag-assignment"
+ ctag-pool:
+ description: |
+ A collection of C tags (vlan tags) grouped for a specific purpose.
+ ###### Related Nodes
+ - TO complex( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)
+ - TO availability-zone( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM vpls-pe( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)
+ required:
+ - target-pe
+ - availability-zone-name
+ - ctag-pool-purpose
+ properties:
+ target-pe:
type: string
- element-choice-sets:
+ description: The Target provider edge router
+ availability-zone-name:
+ type: string
+ description: Name of the availability zone
+ ctag-pool-purpose:
+ type: string
+ description: Describes what the intended purpose of this pool is.
+ ctag-values:
+ type: string
+ description: Comma separated list of ctags
+ ctag-pools:
+ properties:
+ ctag-pool:
type: array
- items:
- $ref: "#/definitions/element-choice-set"
- relationship-list:
+ items:
+ $ref: "#/patchDefinitions/ctag-pool"
+ customer:
+ description: |
+ customer identifiers to provide linkage back to BSS information.
+ ###### Related Nodes
+ - FROM service-subscription( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)
+ - CUSTOMER is DELETED when these are DELETED SERVICE-SUBSCRIPTION
+ required:
+ - global-customer-id
+ - subscriber-name
+ - subscriber-type
+ properties:
+ global-customer-id:
+ type: string
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ subscriber-name:
+ type: string
+ description: Subscriber name, an alternate way to retrieve a customer.
+ subscriber-type:
+ type: string
+ description: Subscriber type, a way to provide VID with only the INFRA customers.
+ customers:
+ description: |
+ Collection of customer identifiers to provide linkage back to BSS information.
+ properties:
+ customer:
type: array
- items:
- $ref: "#/definitions/relationship"
- constrained-element-sets:
+ items:
+ $ref: "#/patchDefinitions/customer"
+ cvlan-tag-entry:
+ required:
+ - cvlan-tag
properties:
- constrained-element-set:
+ cvlan-tag:
+ type: integer
+ format: int64
+ description: See mis-na-virtualization-platform.yang
+ cvlan-tags:
+ properties:
+ cvlan-tag-entry:
type: array
items:
- $ref: "#/definitions/constrained-element-set"
+ $ref: "#/patchDefinitions/cvlan-tag-entry"
+ dvs-switch:
+ description: |
+ Digital virtual switch metadata, used by SDN-C to configure VCEs. A&AI needs to receive this data from the PO deployment team and administer it using the provisioningTool.sh into A&AI.
+ ###### Related Nodes
+ - TO cloud-region( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO availability-zone( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ required:
+ - switch-name
+ - vcenter-url
+ properties:
+ switch-name:
+ type: string
+ description: DVS switch name
+ vcenter-url:
+ type: string
+ description: URL used to reach the vcenter
+ dvs-switches:
+ description: |
+ Collection of digital virtual switch metadata used for vmWare VCEs and GenericVnfs.
+ properties:
+ dvs-switch:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/dvs-switch"
+ edge-prop-names:
+ description: |
+ Internal map to define the properties of an edge and interpret the map EdgeRules
+ properties:
+ edgeLabel:
+ type: string
+ direction:
+ type: string
+ multiplicityRule:
+ type: string
+ isParent:
+ type: boolean
+ usesResource:
+ type: boolean
+ hasDelTarget:
+ type: boolean
+ SVC-INFRA:
+ type: boolean
+ SVC-INFRA-REV:
+ type: boolean
+ edge-tag-query-request:
+ properties:
+ edge-tag:
+ type: string
+ result-detail:
+ type: string
+ start-node-type:
+ type: string
+ start-node-filter:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/start-node-filter"
+ include-node-filter:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/include-node-filter"
+ secondary-filter:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/secondary-filter"
+ edge-tag-query-result:
+ properties:
+ tagged-inventory-item-list:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/tagged-inventory-item-list"
+ element-choice-set:
+ description: |
+ This is how we would capture constraints defining allowed sets of elements.
+ ###### Related Nodes
+ - TO constrained-element-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)
+ - ELEMENT-CHOICE-SET is DELETED when these are DELETED MODEL-ELEMENT
+ required:
+ - element-choice-set-uuid
+ - element-choice-set-name
+ properties:
+ element-choice-set-uuid:
+ type: string
+ element-choice-set-name:
+ type: string
+ cardinality:
+ type: string
+ element-choice-sets:
+ properties:
+ element-choice-set:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/element-choice-set"
+ entitlement:
+ description: |
+ Metadata for entitlement group.
+ ###### Related Nodes
+ - TO generic-vnf( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vce( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ required:
+ - group-uuid
+ - resource-uuid
+ properties:
+ group-uuid:
+ type: string
+ description: Unique ID for the entitlement group the resource comes from, should be uuid.
+ resource-uuid:
+ type: string
+ description: Unique ID of an entitlement resource.
+ entitlements:
+ description: |
+ Entitlements, keyed by group-uuid and resource-uuid, related to license management
+ properties:
+ entitlement:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/entitlement"
+ esr-ems:
+ description: |
+ Persist EMS address information used by EMS driver.
+ ###### Related Nodes
+ - TO esr-system-info (CHILD of esr-ems, esr-ems has esr-system-info, One2Many)
+ - ESR-EMS deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
+ required:
+ - ems-id
+ properties:
+ ems-id:
+ type: string
+ description: Unique ID of EMS.
+ esr-ems-list:
+ properties:
+ esr-ems:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/esr-ems"
+ esr-system-info:
+ description: |
+ Persist common address information of external systems.
+ ###### Related Nodes
+ - FROM esr-ems (PARENT of esr-system-info, esr-ems has esr-system-info)
+ - FROM esr-vnfm (PARENT of esr-system-info, esr-vnfm has esr-system-info)
+ - FROM esr-thirdparty-sdnc (PARENT of esr-system-info, esr-thirdparty-sdnc has esr-system-info)
+ - FROM cloud-region (PARENT of esr-system-info, cloud-region has esr-system-info)
+ required:
+ - esr-system-info-id
+ - user-name
+ - password
+ - system-type
+ properties:
+ esr-system-info-id:
+ type: string
+ description: Unique ID of esr system info.
+ system-name:
+ type: string
+ description: name of external system.
+ type:
+ type: string
+ description: type of external systems.
+ vendor:
+ type: string
+ description: vendor of external systems.
+ version:
+ type: string
+ description: version of external systems.
+ service-url:
+ type: string
+ description: url used to access external systems.
+ user-name:
+ type: string
+ description: username used to access external systems.
+ password:
+ type: string
+ description: password used to access external systems.
+ system-type:
+ type: string
+ description: it could be vim/vnfm/thirdparty-sdnc/ems-resource/ems-performance/ems-alarm.
+ protocol:
+ type: string
+ description: protocol of third party SDNC, for example netconf/snmp.
+ ssl-cacert:
+ type: string
+ description: ca file content if enabled ssl on auth-url.
+ ssl-insecure:
+ type: boolean
+ description: Whether to verify VIM's certificate.
+ ip-address:
+ type: string
+ description: service IP of ftp server.
+ port:
+ type: string
+ description: service port of ftp server.
+ cloud-domain:
+ type: string
+ description: domain info for authentication.
+ default-tenant:
+ type: string
+ description: default tenant of VIM.
+ passive:
+ type: boolean
+ description: ftp passive mode or not.
+ remote-path:
+ type: string
+ description: resource or performance data file path.
+ system-status:
+ type: string
+ description: the status of external system.
+ esr-system-info-list:
+ description: |
+ Collection of persistent block-level external system auth info.
+ properties:
+ esr-system-info:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/esr-system-info"
+ esr-thirdparty-sdnc:
+ description: |
+ Persist SDNC address information used by ONAP SDNC.
+ ###### Related Nodes
+ - TO esr-system-info (CHILD of esr-thirdparty-sdnc, esr-thirdparty-sdnc has esr-system-info, One2One)
+ - TO pnf( esr-thirdparty-sdnc has pnf, One2Many)
+ - ESR-THIRDPARTY-SDNC deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
+ required:
+ - thirdparty-sdnc-id
+ properties:
+ thirdparty-sdnc-id:
+ type: string
+ description: Unique ID of SDNC.
+ location:
+ type: string
+ description: used for DC type to indicate the location of SDNC, such as Core or Edge.
+ product-name:
+ type: string
+ description: password used to access SDNC server.
+ esr-thirdparty-sdnc-list:
+ properties:
+ esr-thirdparty-sdnc:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/esr-thirdparty-sdnc"
+ esr-vnfm:
+ description: |
+ Persist VNFM address information used by VF-C.
+ ###### Related Nodes
+ - TO esr-system-info (CHILD of esr-vnfm, esr-vnfm has esr-system-info, One2One)
+ - ESR-VNFM deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
+ required:
+ - vnfm-id
+ properties:
+ vnfm-id:
+ type: string
+ description: Unique ID of VNFM.
+ vim-id:
+ type: string
+ description: indecate the VIM to deploy VNF.
+ certificate-url:
+ type: string
+ description: certificate url of VNFM.
+ esr-vnfm-list:
+ properties:
+ esr-vnfm:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/esr-vnfm"
+ evc:
+ description: |
+ evc object is an optional child object of the Configuration object.
+ ###### Related Nodes
+ - TO configuration( evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)
+ required:
+ - evc-id
+ properties:
+ evc-id:
+ type: string
+ description: Unique/key field for the evc object
+ forwarding-path-topology:
+ type: string
+ description: Point-to-Point, Multi-Point
+ cir-value:
+ type: string
+ description: Commited Information Rate
+ cir-units:
+ type: string
+ description: CIR units
+ connection-diversity-group-id:
+ type: string
+ description: Diversity Group ID
+ service-hours:
+ type: string
+ description: formerly Performance Group
+ esp-evc-circuit-id:
+ type: string
+ description: EVC Circuit ID of ESP EVC
+ esp-evc-cir-value:
+ type: string
+ description: Committed Information Rate (For ESP)
+ esp-evc-cir-units:
+ type: string
+ description: CIR units (For ESP)
+ esp-itu-code:
+ type: string
+ description: Identifies ESP
+ collector-pop-clli:
+ type: string
+ description: Collector POP CLLI (from the hostname of the access pnf)
+ inter-connect-type-ingress:
+ type: string
+ description: Interconnect type on ingress side of EVC.
+ tagmode-access-ingress:
+ type: string
+ description: tagode for collector side of EVC
+ tagmode-access-egress:
+ type: string
+ description: tagMode for network side of EVC
+ evcs:
+ properties:
+ evc:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/evc"
+ external-system:
+ description: |
+ Namespace for external system.
+ properties:
+ esr-ems-list:
+ type: object
+ $ref: "#/patchDefinitions/esr-ems-list"
+ esr-vnfm-list:
+ type: object
+ $ref: "#/patchDefinitions/esr-vnfm-list"
+ esr-thirdparty-sdnc-list:
+ type: object
+ $ref: "#/patchDefinitions/esr-thirdparty-sdnc-list"
+ extra-properties:
+ description: |
+ Extra properties for inventory item for response list
+ extra-property:
+ properties:
+ property-name:
+ type: string
+ flavor:
+ description: |
+ Openstack flavor.
+ ###### Related Nodes
+ - TO cloud-region( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)
+ - FLAVOR cannot be deleted if linked to VSERVER
+ required:
+ - flavor-id
+ - flavor-name
+ - flavor-selflink
+ properties:
+ flavor-id:
+ type: string
+ description: Flavor id, expected to be unique across cloud-region.
+ flavor-name:
+ type: string
+ description: Flavor name
+ flavor-vcpus:
+ type: integer
+ format: int32
+ description: Number of CPUs
+ flavor-ram:
+ type: integer
+ format: int32
+ description: Amount of memory
+ flavor-disk:
+ type: integer
+ format: int32
+ description: Disk space
+ flavor-ephemeral:
+ type: integer
+ format: int32
+ description: Amount of ephemeral disk space
+ flavor-swap:
+ type: string
+ description: amount of swap space allocation
+ flavor-is-public:
+ type: boolean
+ description: whether flavor is available to all users or private to the tenant it was created in.
+ flavor-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ flavor-disabled:
+ type: boolean
+ description: Boolean as to whether this flavor is no longer enabled
+ flavors:
+ description: |
+ Collection of openstack flavors.
+ properties:
+ flavor:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/flavor"
+ forwarder:
+ description: |
+ Entity describing a sequenced segment of forwarding path
+ ###### Related Nodes
+ - TO forwarding-path( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)
+ - TO l-interface( forwarder org.onap.relationships.inventory.ForwardsTo l-interface, MANY2ONE)
+ - TO configuration( forwarder org.onap.relationships.inventory.Uses configuration, ONE2ONE)
+ - TO lag-interface( forwarder org.onap.relationships.inventory.ForwardsTo lag-interface, MANY2ONE)
+ - TO p-interface( forwarder org.onap.relationships.inventory.ForwardsTo p-interface, MANY2ONE)
+ - FORWARDER deletion means associated objects of these types are also DELETED:CONFIGURATION
+ required:
+ - sequence
+ properties:
+ sequence:
+ type: integer
+ format: int32
+ description: Unique ID of this segmentation
+ forwarder-role:
+ type: string
+ description: ingress, intermediate, egress
+ forwarder-evc:
+ description: |
+ forwarder object is an optional child object of the Configuration object.
+ ###### Related Nodes
+ - TO configuration( forwarder-evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)
+ required:
+ - forwarder-evc-id
+ properties:
+ forwarder-evc-id:
+ type: string
+ description: Key for forwarder-evc object
+ circuit-id:
+ type: string
+ description: Circuit ID from customer/ESP/ingress end of EVC, or reference to beater circuit on gateway/network/egress end of EVC
+ ivlan:
+ type: string
+ description: Internal VLAN.
+ svlan:
+ type: string
+ description: SVLAN value for ingress of egress forwarder.
+ cvlan:
+ type: string
+ description: CVLAN value for ingress of egress forwarder.
+ forwarder-evcs:
+ properties:
+ forwarder-evc:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/forwarder-evc"
+ forwarders:
+ properties:
+ forwarder:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/forwarder"
+ forwarding-path:
+ description: |
+ Entity that describes the sequenced forwarding path between interfaces of services or resources
+ ###### Related Nodes
+ - TO service-instance( forwarding-path org.onap.relationships.inventory.AppliesTo service-instance, MANY2ONE)
+ - TO configuration( forwarding-path org.onap.relationships.inventory.Uses configuration, ONE2ONE)
+ - FROM forwarder( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)
+ - FORWARDING-PATH is DELETED when these are DELETED FORWARDER
+ - FORWARDING-PATH deletion means associated objects of these types are also DELETED:CONFIGURATION
+ required:
+ - forwarding-path-id
+ - forwarding-path-name
+ properties:
+ forwarding-path-id:
+ type: string
+ description: Unique ID of this FP
+ forwarding-path-name:
+ type: string
+ description: Name of the FP
+ forwarding-paths:
+ properties:
+ forwarding-path:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/forwarding-path"
+ generic-vnf:
+ description: |
+ General purpose VNF
+ ###### Related Nodes
+ - TO availability-zone( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - TO ipsec-configuration( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)
+ - TO l3-network( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO license-key-resource( generic-vnf org.onap.relationships.inventory.Uses license-key-resource, MANY2MANY)
+ - TO pserver( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)
+ - TO vnf-image( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)
+ - TO volume-group( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - TO vserver( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)
+ - TO virtual-data-center( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM lag-interface( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM network-profile( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)
+ - FROM site-pair-set( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)
+ - GENERIC-VNF is DELETED when these are DELETED VNFC,LAG-INTERFACE,L-INTERFACE,VF-MODULE
+ required:
+ - vnf-id
+ - vnf-name
+ - vnf-type
+ - in-maint
+ - is-closed-loop-disabled
+ properties:
+ vnf-id:
+ type: string
+ description: Unique id of VNF. This is unique across the graph.
+ vnf-name:
+ type: string
+ description: Name of VNF.
+ vnf-name2:
+ type: string
+ description: Alternate name of VNF.
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded and clients should expect changes to occur in the future to this field as ASDC matures.
+ service-id:
+ type: string
+ description: Unique identifier of service from ASDC
+ regional-resource-zone:
+ type: string
+ description: Regional way of organizing pservers, source of truth should define values
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ operational-state:
+ type: string
+ description: Indicator for whether the resource is considered operational
+ license-key:
+ type: string
+ description: License key
+ equipment-role:
+ type: string
+ description: Client should send valid enumerated value
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, used by MSO.
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ management-option:
+ type: string
+ description: identifier of managed by company or customer
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by generic-vnf.
+ ipv4-loopback0-address:
+ type: string
+ description: v4 Loopback0 address
+ nm-lan-v6-address:
+ type: string
+ description: v6 Loopback address
+ management-v6-address:
+ type: string
+ description: v6 management address
+ vcpu:
+ type: integer
+ format: int64
+ description: number of vcpus ordered for this instance of VNF, used for VNFs with no vservers/flavors
+ vcpu-units:
+ type: string
+ description: units associated with vcpu, used for VNFs with no vservers/flavors
+ vmemory:
+ type: integer
+ format: int64
+ description: number of GB of memory ordered for this instance of VNF, used for VNFs with no vservers/flavors
+ vmemory-units:
+ type: string
+ description: units associated with vmemory, used for VNFs with no vservers/flavors
+ vdisk:
+ type: integer
+ format: int64
+ description: number of vdisks ordered for this instance of VNF, used for VNFs with no vservers/flavors
+ vdisk-units:
+ type: string
+ description: units associated with vdisk, used for VNFs with no vservers/flavors
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
+ generic-vnfs:
+ description: |
+ Collection of VNFs
+ properties:
+ generic-vnf:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/generic-vnf"
+ group-assignment:
+ description: |
+ Openstack group-assignment used to store exclusivity groups (EG).
+ ###### Related Nodes
+ - TO cloud-region( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)
+ required:
+ - group-id
+ - group-type
+ - group-name
+ properties:
+ group-id:
+ type: string
+ description: Group id, expected to be unique across cloud-region.
+ group-type:
+ type: string
+ description: Group type - the type of group this instance refers to
+ group-name:
+ type: string
+ description: Group name - name assigned to the group
+ group-description:
+ type: string
+ description: Group description - description of the group
+ group-assignments:
+ description: |
+ Collection of openstack group assignments
+ properties:
+ group-assignment:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/group-assignment"
+ host-route:
+ description: |
+ ###### Related Nodes
+ - TO subnet( host-route org.onap.relationships.inventory.BelongsTo subnet, MANY2ONE)
+ required:
+ - host-route-id
+ - route-prefix
+ - next-hop
+ properties:
+ host-route-id:
+ type: string
+ description: host-route id
+ route-prefix:
+ type: string
+ description: subnet prefix
+ next-hop:
+ type: string
+ description: Could be ip-address, hostname, or service-instance
+ next-hop-type:
+ type: string
+ description: Should be ip-address, hostname, or service-instance to match next-hop
+ host-routes:
+ properties:
+ host-route:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/host-route"
+ image:
+ description: |
+ Openstack image.
+ ###### Related Nodes
+ - TO cloud-region( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)
+ - IMAGE cannot be deleted if linked to VSERVER
+ - IMAGE is DELETED when these are DELETED METADATUM
+ required:
+ - image-id
+ - image-name
+ - image-os-distro
+ - image-os-version
+ - image-selflink
+ properties:
+ image-id:
+ type: string
+ description: Image id, expected to be unique across cloud region
+ image-name:
+ type: string
+ description: Image name
+ image-architecture:
+ type: string
+ description: Operating system architecture.
+ image-os-distro:
+ type: string
+ description: The common name of the operating system distribution in lowercase
+ image-os-version:
+ type: string
+ description: The operating system version as specified by the distributor.
+ application:
+ type: string
+ description: The application that the image instantiates.
+ application-vendor:
+ type: string
+ description: The vendor of the application.
+ application-version:
+ type: string
+ description: The version of the application.
+ image-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ images:
+ description: |
+ Collectio of Openstack images.
+ properties:
+ image:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/image"
+ include-node-filter:
+ properties:
+ include-node-type:
+ type: string
+ instance-filter:
+ description: |
+ InstanceFilter for performing a named-query or model query
+ instance-filters:
+ description: |
+ InstanceFilters for performing a named-query or model query
+ properties:
+ instance-filter:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/instance-filter"
+ instance-group:
+ description: |
+ General mechanism for grouping instances
+ ###### Related Nodes
+ - TO model( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM pnf( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ required:
+ - id
+ - description
+ - type
+ properties:
+ id:
+ type: string
+ description: Instance Group ID, UUID assigned to this instance.
+ description:
+ type: string
+ description: Descriptive text to help identify the usage of this instance-group
+ type:
+ type: string
+ description: Only valid value today is lower case ha for high availability
+ sub-type:
+ type: string
+ description: Valid values for ha type are [geo-activeactive, geo-activestandby, local-activeactive, local-activestandby]
+ instance-groups:
+ description: |
+ Collection of openstack route table references
+ properties:
+ instance-group:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/instance-group"
+ inventory:
+ properties:
+ search:
+ type: object
+ $ref: "#/patchDefinitions/search"
+ actions:
+ type: object
+ $ref: "#/patchDefinitions/actions"
+ cloud-infrastructure:
+ type: object
+ $ref: "#/patchDefinitions/cloud-infrastructure"
+ business:
+ type: object
+ $ref: "#/patchDefinitions/business"
+ service-design-and-creation:
+ type: object
+ $ref: "#/patchDefinitions/service-design-and-creation"
+ network:
+ type: object
+ $ref: "#/patchDefinitions/network"
+ aai-internal:
+ type: object
+ $ref: "#/patchDefinitions/aai-internal"
+ inventory-item:
+ properties:
+ inventory-item-type:
+ type: string
+ inventory-item-link:
+ type: string
+ inventory-item-data:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/inventory-item-data"
+ tagged-inventory-item-list:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/tagged-inventory-item-list"
+ inventory-item-data:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ inventory-response-item:
+ description: |
+ Inventory item for response list
+ properties:
+ model-name:
+ type: string
+ extra-properties:
+ type: object
+ $ref: "#/patchDefinitions/extra-properties"
+ inventory-response-items:
+ type: object
+ $ref: "#/patchDefinitions/inventory-response-items"
+ inventory-response-items:
+ description: |
+ Container for inventory items in response list
+ properties:
+ inventory-response-item:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/inventory-response-item"
+ ipsec-configuration:
+ description: |
+ IPSec configuration node will contain various configuration data for the NMTE VNF. This node will have an edge to the generic-vnf (vnf type = TE). Starting 1607, this data will be populated by SDN-C
+ ###### Related Nodes
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)
+ - FROM vig-server( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)
+ - IPSEC-CONFIGURATION is DELETED when these are DELETED VIG-SERVER
+ required:
+ - ipsec-configuration-id
+ properties:
+ ipsec-configuration-id:
+ type: string
+ description: UUID of this configuration
+ requested-vig-address-type:
+ type: string
+ description: Indicate the type of VIG server like AVPN, INTERNET, BOTH
+ requested-encryption-strength:
+ type: string
+ description: Encryption values like 3des-cbc, des-cbc, aes-128-cbc, aes-192-cbc, aes-265-cbc
+ requested-dmz-type:
+ type: string
+ description: can offer a shared DMZ or a DMZ specific to a customer
+ shared-dmz-network-address:
+ type: string
+ description: Network address of shared DMZ
+ requested-customer-name:
+ type: string
+ description: If the DMZ is a custom DMZ, this field will indicate the customer information
+ ike-version:
+ type: string
+ description: can be 1 or 2
+ ikev1-authentication:
+ type: string
+ description: Contains values like md5, sha1, sha256, sha384
+ ikev1-encryption:
+ type: string
+ description: Encyption values like 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
+ ikev1-dh-group:
+ type: string
+ description: Diffie-Hellman group like DH-GROUP2, DH-GROUP5, DH-GROUP14
+ ikev1-am-group-id:
+ type: string
+ description: Group name defined in VIG for clients using aggressive mode
+ ikev1-am-password:
+ type: string
+ description: pre-shared key for the above group name
+ ikev1-sa-lifetime:
+ type: string
+ description: Lifetime for IKEv1 SA
+ ipsec-authentication:
+ type: string
+ description: md5, sha1, sha256, sha384
+ ipsec-encryption:
+ type: string
+ description: 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
+ ipsec-sa-lifetime:
+ type: string
+ description: Life time for IPSec SA
+ ipsec-pfs:
+ type: string
+ description: enable PFS or not
+ xauth-userid:
+ type: string
+ description: user ID for xAuth, sm-user, ,nmteHostName
+ xauth-user-password:
+ type: string
+ description: Encrypted using the Juniper $9$ algorithm
+ dpd-interval:
+ type: string
+ description: The time between DPD probe
+ dpd-frequency:
+ type: string
+ description: Maximum number of DPD before claiming the tunnel is down
+ ipsec-configurations:
+ properties:
+ ipsec-configuration:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/ipsec-configuration"
+ key-data:
+ properties:
+ key-name:
+ type: string
+ key-value:
+ type: string
+ l-interface:
+ description: |
+ Logical interfaces, e.g., a vnic.
+ ###### Related Nodes
+ - TO generic-vnf( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO lag-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)
+ - TO logical-link( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)
+ - TO newvce( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)
+ - TO p-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)
+ - TO vserver( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - FROM sriov-vf( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)
+ - FROM vlan( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)
+ - L-INTERFACE is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST,SRIOV-VF,VLAN
+ - L-INTERFACE deletion means associated objects of these types are also DELETED:LOGICAL-LINK
+ required:
+ - interface-name
+ properties:
+ interface-name:
+ type: string
+ description: Name given to the interface
+ interface-role:
+ type: string
+ description: E.g., CUSTOMER, UPLINK, etc.
+ v6-wan-link-ip:
+ type: string
+ description: Questionably placed - v6 ip addr of this interface (is in vr-lan-interface from Mary B.
+ selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ interface-id:
+ type: string
+ description: ID of interface
+ macaddr:
+ type: string
+ description: MAC address for the interface
+ network-name:
+ type: string
+ description: Name of the network
+ management-option:
+ type: string
+ description: Whether A&AI should be managing this interface of not. Could have value like CUSTOMER
+ l-interfaces:
+ description: |
+ Collection of logical interfaces.
+ properties:
+ l-interface:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/l-interface"
+ l3-interface-ipv4-address-list:
+ description: |
+ IPv4 Address Range
+ ###### Related Nodes
+ - TO l3-network( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - TO subnet( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - TO l-interface( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - TO vlan( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ required:
+ - l3-interface-ipv4-address
+ properties:
+ l3-interface-ipv4-address:
+ type: string
+ description: IP address
+ l3-interface-ipv4-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 32 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ l3-interface-ipv6-address-list:
+ description: |
+ IPv6 Address Range
+ ###### Related Nodes
+ - TO l3-network( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - TO subnet( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - TO l-interface( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - TO vlan( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ required:
+ - l3-interface-ipv6-address
+ properties:
+ l3-interface-ipv6-address:
+ type: string
+ description: IP address
+ l3-interface-ipv6-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 128 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ l3-network:
+ description: |
+ Generic network definition
+ ###### Related Nodes
+ - TO network-policy( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)
+ - TO route-table-reference( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)
+ - TO vpn-binding( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM complex( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - FROM ctag-assignment( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM segmentation-assignment( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)
+ - FROM subnet( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)
+ - L3-NETWORK is DELETED when these are DELETED CTAG-ASSIGNMENT,SEGMENTATION-ASSIGNMENT,SUBNET
+ required:
+ - network-id
+ - network-name
+ - is-bound-to-vpn
+ - is-provider-network
+ - is-shared-network
+ - is-external-network
+ properties:
+ network-id:
+ type: string
+ description: Network ID, should be uuid. Unique across A&AI.
+ network-name:
+ type: string
+ description: Name of the network, governed by some naming convention..
+ network-type:
+ type: string
+ description: Type of the network - who defines these values?
+ network-role:
+ type: string
+ description: Role the network plans - who defines these values?
+ network-technology:
+ type: string
+ description: Network technology - who defines these values?
+ neutron-network-id:
+ type: string
+ description: Neutron network id of this Interface
+ is-bound-to-vpn:
+ type: boolean
+ service-id:
+ type: string
+ description: Unique identifier of service from ASDC
+ network-role-instance:
+ type: integer
+ format: int64
+ description: network role instance
+ l3-networks:
+ properties:
+ l3-network:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/l3-network"
+ lag-interface:
+ description: |
+ Link aggregate interface
+ ###### Related Nodes
+ - TO generic-vnf( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO lag-link( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)
+ - TO p-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)
+ - TO pnf( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - TO pserver( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - TO vpls-pe( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)
+ - LAG-INTERFACE is DELETED when these are DELETED L-INTERFACE
+ - LAG-INTERFACE deletion means associated objects of these types are also DELETED:LAG-LINK
+ required:
+ - interface-name
+ properties:
+ interface-name:
+ type: string
+ description: Name that identifies the link aggregate interface
+ lag-interfaces:
+ description: |
+ Collection of link aggregate interfaces.
+ properties:
+ lag-interface:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/lag-interface"
+ lag-link:
+ description: |
+ LAG links can connect lag-interfaces
+ ###### Related Nodes
+ - FROM lag-interface( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)
+ required:
+ - link-name
+ properties:
+ link-name:
+ type: string
+ description: Alphabetical concatenation of lag-interface names
+ lag-links:
+ description: |
+ Collection of link aggregation connections
+ properties:
+ lag-link:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/lag-link"
+ license:
+ description: |
+ Metadata for license group.
+ ###### Related Nodes
+ - TO generic-vnf( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vce( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ required:
+ - group-uuid
+ - resource-uuid
+ properties:
+ group-uuid:
+ type: string
+ description: Unique ID for the license group the resource belongs to, should be uuid.
+ resource-uuid:
+ type: string
+ description: Unique ID of a license resource.
+ licenses:
+ description: |
+ Licenses to be allocated across resources, keyed by group-uuid and resource-uuid, related to license management
+ properties:
+ license:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/license"
+ line-of-business:
+ description: |
+ describes a line-of-business
+ ###### Related Nodes
+ - TO generic-vnf( line-of-business org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)
+ required:
+ - line-of-business-name
+ properties:
+ line-of-business-name:
+ type: string
+ description: Name of the line-of-business (product)
+ lines-of-business:
+ description: |
+ Collection of lines-of-business
+ properties:
+ line-of-business:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/line-of-business"
+ logical-link:
+ description: |
+ Logical links generally connect l-interfaces but are used to express logical connectivity between two points
+ ###### Related Nodes
+ - TO generic-vnf( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)
+ - TO lag-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)
+ - TO logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - TO pnf( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)
+ - TO pserver( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)
+ - TO virtual-data-center( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)
+ - FROM p-interface( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - FROM vlan( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ required:
+ - link-name
+ - link-type
+ properties:
+ link-name:
+ type: string
+ description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
+ link-type:
+ type: string
+ description: Type of logical link, e.g., evc
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ ip-version:
+ type: string
+ description: v4, v6, or ds for dual stack
+ routing-protocol:
+ type: string
+ description: For example, static or BGP
+ logical-links:
+ description: |
+ Collection of logical connections
+ properties:
+ logical-link:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/logical-link"
+ metadata:
+ description: |
+ Collection of metadatum (key/value pairs)
+ properties:
+ metadatum:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/metadatum"
+ metadatum:
+ description: |
+ Key/value pairs
+ ###### Related Nodes
+ - TO connector( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)
+ - TO image( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)
+ - TO service-instance( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - TO model( metadatum org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ required:
+ - metaname
+ - metaval
+ properties:
+ metaname:
+ type: string
+ metaval:
+ type: string
+ model:
+ description: |
+ Subgraph definition provided by ASDC to describe an inventory asset and its connections related to ASDC models
+ ###### Related Nodes
+ - TO model( model-element isA model, MANY2ONE)
+ - TO model-element (CHILD of model, model startsWith model-element, ONE2MANY)
+ - FROM named-query( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)
+ - FROM model-element( model-element isA model, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - MODEL cannot be deleted if linked to NAMED-QUERY,NAMED-QUERY-ELEMENT
+ - MODEL is DELETED when these are DELETED METADATUM
+ - MODEL deletion means associated objects of these types are also DELETED:MODEL-ELEMENT
+ required:
+ - model-name-version-id
+ - model-type
+ - model-name
+ - model-id
+ - model-version
+ properties:
+ model-name-version-id:
+ type: string
+ description: Unique identifier corresponding to one version of a model in ASDC
+ model-type:
+ type: string
+ description: Type of the model, e.g., service, resource, widget, etc.
+ model-name:
+ type: string
+ description: Name of the model, which can change from version to version.
+ model-id:
+ type: string
+ description: Invariant unique ID which does not change from version to version
+ model-version:
+ type: string
+ description: Version
+ model-description:
+ type: string
+ description: Description
+ model-and-named-query-search:
+ description: |
+ ModelAndNamedQuerySearch holds query-parameters and instance-properties for performing a named-query or model query
+ properties:
+ query-parameters:
+ type: object
+ $ref: "#/patchDefinitions/query-parameters"
+ instance-filters:
+ type: object
+ $ref: "#/patchDefinitions/instance-filters"
+ top-node-type:
+ type: string
model-constraint:
description: |
This is how we would capture constraints defining allowed sets of elements.
###### Related Nodes
- - TO constrained-element-set (comprises model-constraint, One2Many)
- - FROM model-element (is composed of model-constraint)
+ - TO model-element( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)
+ - MODEL-CONSTRAINT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET
required:
- model-constraint-uuid
- constrained-element-set-uuid-to-replace
@@ -35563,26 +50419,25 @@ definitions:
constrained-element-sets:
type: array
items:
- $ref: "#/definitions/constrained-element-set"
+ $ref: "#/patchDefinitions/constrained-element-set"
model-constraints:
properties:
model-constraint:
type: array
items:
- $ref: "#/definitions/model-constraint"
+ $ref: "#/patchDefinitions/model-constraint"
model-element:
description: |
Defines how other models combine to make up a higher-level model.
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
###### Related Nodes
- - TO model (Many2One)
- - TO model-element (comprises model-element, One2Many)
- - TO model-constraint (comprises model-element, One2Many)
- - TO constrained-element-set (comprises model-element, One2Many)
- - FROM model (is composed of model-element)
- - FROM element-choice-set (is composed of model-element)
- - FROM model-element (is composed of model-element)
+ - TO element-choice-set( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)
+ - TO model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - TO model( model-element isA model, MANY2ONE)
+ - FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM model-constraint( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM model (PARENT of model-element, model startsWith model-element)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - MODEL-ELEMENT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET,MODEL-CONSTRAINT
required:
- model-element-uuid
- new-data-del-flag
@@ -35598,48 +50453,432 @@ definitions:
description: How many of this type of element are required/allowed
linkage-points:
type: string
- resource-version:
+ model-elements:
+ properties:
+ model-element:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/model-element"
+ model-ver:
+ description: |
+ Subgraph definition provided by ASDC to describe a specific version of an inventory asset and its connections related to ASDC models
+ ###### Related Nodes
+ - TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - MODEL-VER cannot be deleted if linked to MODEL-ELEMENT
+ - MODEL-VER is DELETED when these are DELETED MODEL-ELEMENT,METADATUM
+ required:
+ - model-version-id
+ - model-name
+ - model-version
+ properties:
+ model-version-id:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- model-elements:
+ description: Unique identifier corresponding to one version of a model in ASDC
+ model-name:
+ type: string
+ description: Name of the model, which can change from version to version.
+ model-version:
+ type: string
+ description: Version
+ model-description:
+ type: string
+ description: Description
+ model-vers:
+ properties:
+ model-ver:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/model-ver"
+ models:
+ description: |
+ Collection of subgraph definitions provided by ASDC to describe the inventory assets and their connections related to ASDC models
+ properties:
+ model:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/model"
+ multicast-configuration:
+ description: |
+ ###### Related Nodes
+ - FROM vlan( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)
+ required:
+ - multicast-configuration-id
+ - multicast-protocol
+ - rp-type
+ properties:
+ multicast-configuration-id:
+ type: string
+ description: Unique id of multicast configuration.
+ multicast-protocol:
+ type: string
+ description: protocol of multicast configuration
+ rp-type:
+ type: string
+ description: rp type of multicast configuration
+ multicast-configurations:
+ description: |
+ multicast configuration of generic-vnf ip-address
+ properties:
+ multicast-configuration:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/multicast-configuration"
+ named-queries:
+ properties:
+ named-query:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/named-query"
+ named-query:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - TO model( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - NAMED-QUERY is DELETED when these are DELETED NAMED-QUERY-ELEMENT
+ required:
+ - named-query-uuid
+ - named-query-name
+ - named-query-version
+ properties:
+ named-query-uuid:
+ type: string
+ named-query-name:
+ type: string
+ named-query-version:
+ type: string
+ required-input-param:
+ type: string
+ description:
+ type: string
+ named-query-element:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - TO model( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)
+ - TO named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM property-constraint( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM related-lookup( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - NAMED-QUERY-ELEMENT is DELETED when these are DELETED PROPERTY-CONSTRAINT,RELATED-LOOKUP
+ required:
+ - named-query-element-uuid
+ properties:
+ named-query-element-uuid:
+ type: string
+ property-collect-list:
+ type: string
+ named-query-elements:
+ properties:
+ named-query-element:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/named-query-element"
+ network:
+ description: |
+ Namespace for network inventory resources.
+ properties:
+ logical-links:
type: array
items:
- $ref: "#/definitions/model-element"
- description: Defines how other models combine to make up a higher-level model
- model-constraints:
+ $ref: "#/patchDefinitions/logical-link"
+ site-pair-sets:
type: array
items:
- $ref: "#/definitions/model-constraint"
- description: Describes new constraints on this model element that are not part of that model's definition
- relationship-list:
+ $ref: "#/patchDefinitions/site-pair-set"
+ vpn-bindings:
type: array
items:
- $ref: "#/definitions/relationship"
- model-elements:
+ $ref: "#/patchDefinitions/vpn-binding"
+ vpls-pes:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vpls-pe"
+ multicast-configurations:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/multicast-configuration"
+ vces:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vce"
+ vnfcs:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vnfc"
+ l3-networks:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/l3-network"
+ network-policies:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/network-policy"
+ generic-vnfs:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/generic-vnf"
+ lag-links:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/lag-link"
+ newvces:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/newvce"
+ pnfs:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/pnf"
+ physical-links:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/physical-link"
+ ipsec-configurations:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/ipsec-configuration"
+ route-table-references:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/route-table-reference"
+ network-policies:
properties:
- model-element:
+ network-policy:
type: array
items:
- $ref: "#/definitions/model-element"
- model:
+ $ref: "#/patchDefinitions/network-policy"
+ network-policy:
description: |
- Subgraph definition provided by ASDC to describe an inventory asset and its connections related to ASDC models
- ###### Default Delete Scope
- ERROR_4_IN_EDGES_OR_CASCADE
###### Related Nodes
- - TO model (Many2One)
- - TO model-element (comprises model, One2Many)
- - TO metadatum (comprises model, One2Many)
- - FROM model-element
- - FROM named-query
- - FROM named-query-element
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)
+ required:
+ - network-policy-id
+ properties:
+ network-policy-id:
+ type: string
+ description: UUID representing unique key to this instance
+ network-policy-fqdn:
+ type: string
+ description: Contrail FQDN for the policy
+ heat-stack-id:
+ type: string
+ description: ID for the openStack Heat instance
+ network-profile:
+ description: |
+ Network profile populated by SDN-GP for SNMP
+ ###### Related Nodes
+ - TO generic-vnf( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ required:
+ - nm-profile-name
+ properties:
+ nm-profile-name:
+ type: string
+ description: Unique name of network profile.
+ community-string:
+ type: string
+ description: Encrypted SNMP community string
+ network-profiles:
+ description: |
+ Collection of network profiles
+ properties:
+ network-profile:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/network-profile"
+ newvce:
+ description: |
+ This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce.
+ ###### Related Nodes
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)
+ - NEWVCE is DELETED when these are DELETED L-INTERFACE
required:
+ - vnf-id2
+ - vnf-name
+ - vnf-type
+ properties:
+ vnf-id2:
+ type: string
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ vnf-name:
+ type: string
+ description: Name of VNF.
+ vnf-name2:
+ type: string
+ description: Alternate name of VNF.
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded and clients should expect changes to occur in the future to this field as ASDC matures.
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+ operational-state:
+ type: string
+ description: Indicator for whether the resource is considered operational
+ license-key:
+ type: string
+ description: License key
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address).
+ equipment-role:
+ type: string
+ description: Client should send valid enumerated value.
+ newvces:
+ description: |
+ This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce.
+ properties:
+ newvce:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/newvce"
+ notification-event:
+ properties:
+ cambria.partition:
+ type: string
+ notification-event-header:
+ type: object
+ $ref: "#/patchDefinitions/notification-event-header"
+ notification-event-header:
+ properties:
+ id:
+ type: string
+ timestamp:
+ type: string
+ source-name:
+ type: string
+ domain:
+ type: string
+ sequence-number:
+ type: string
+ severity:
+ type: string
+ event-type:
+ type: string
+ version:
+ type: string
+ action:
+ type: string
+ entity-type:
+ type: string
+ top-entity-type:
+ type: string
+ entity-link:
+ type: string
+ status:
+ type: string
+ notify:
+ required:
+ - event-id
+ properties:
+ event-id:
+ type: string
+ node-type:
+ type: string
+ event-trigger:
+ type: string
+ key-data:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/key-data"
+ selflink:
+ type: string
+ oam-network:
+ description: |
+ OAM network, to be deprecated shortly. Do not use for new purposes.
+ ###### Related Nodes
+ - TO cloud-region( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO complex( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)
+ - TO service-capability( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ required:
+ - network-uuid
+ - network-name
+ - cvlan-tag
+ properties:
+ network-uuid:
+ type: string
+ description: UUID of the network. Unique across a cloud-region
+ network-name:
+ type: string
+ description: Name of the network.
+ cvlan-tag:
+ type: integer
+ format: int64
+ description: cvlan-id
+ ipv4-oam-gateway-address:
+ type: string
+ description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
+ ipv4-oam-gateway-address-prefix-length:
+ type: integer
+ format: int32
+ description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
+ oam-networks:
+ description: |
+ Collection of OAM networks, to be deprecated shortly. Do not use for new purposes.
+ properties:
+ oam-network:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/oam-network"
+ operational-environment:
+ description: |
+ It is a logical partition of the cloud which allows to have multiple environments in the production AIC.
+ ###### Related Nodes
+ - TO operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)
+ - FROM operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)
+ required:
+ - operational-environment-id
+ - operational-environment-name
+ - operational-environment-type
+ - operational-environment-status
+ - tenant-context
+ - workload-context
+ properties:
+ operational-environment-id:
+ type: string
+ description: UUID of an operational environment
+ operational-environment-name:
+ type: string
+ description: Operational Environment name
+ operational-environment-type:
+ type: string
+ description: Operational Environment Type.
+ operational-environment-status:
+ type: string
+ description: Status
+ tenant-context:
+ type: string
+ description: Tenant Context.
+ workload-context:
+ type: string
+ description: Workload Context.
+ operational-environments:
+ description: |
+ a logical partition of the cloud which allows to have multiple environments in the production AIC.
+ properties:
+ operational-environment:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/operational-environment"
+ overloaded-model:
+ description: |
+ Allows for legacy POST of old-style and new-style models
+ required:
+ - model-invariant-id
- model-name-version-id
- model-type
- model-name
- model-id
- model-version
properties:
+ model-invariant-id:
+ type: string
+ description: Unique identifier corresponding to the main definition of a model in ASDC
model-name-version-id:
type: string
description: Unique identifier corresponding to one version of a model in ASDC
@@ -35658,70 +50897,250 @@ definitions:
model-description:
type: string
description: Description
- resource-version:
- type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- model-elements:
+ owning-entities:
+ description: |
+ Collection of owning-entities
+ properties:
+ owning-entity:
type: array
- items:
- $ref: "#/definitions/model-element"
- metadata:
+ items:
+ $ref: "#/patchDefinitions/owning-entity"
+ owning-entity:
+ description: |
+ describes an owning-entity
+ ###### Related Nodes
+ - FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo owning-entity, MANY2ONE)
+ required:
+ - owning-entity-id
+ - owning-entity-name
+ properties:
+ owning-entity-id:
+ type: string
+ description: UUID of an owning entity
+ owning-entity-name:
+ type: string
+ description: Owning entity name
+ p-interface:
+ description: |
+ Physical interface (e.g., nic)
+ ###### Related Nodes
+ - TO logical-link( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)
+ - TO physical-link( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)
+ - TO pnf( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - TO pserver( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - TO vpls-pe( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM lag-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)
+ - P-INTERFACE is DELETED when these are DELETED L-INTERFACE
+ - P-INTERFACE deletion means associated objects of these types are also DELETED:PHYSICAL-LINK
+ required:
+ - interface-name
+ properties:
+ interface-name:
+ type: string
+ description: Name that identifies the physical interface
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ port-description:
+ type: string
+ description: Nature of the services and connectivity on this port.
+ equipment-identifier:
+ type: string
+ description: CLEI or other specification for p-interface hardware.
+ interface-role:
+ type: string
+ description: Role specification for p-interface hardware.
+ interface-type:
+ type: string
+ description: Indicates the physical properties of the interface.
+ p-interfaces:
+ description: |
+ Collection of physical interfaces.
+ properties:
+ p-interface:
type: array
- items:
- $ref: "#/definitions/metadatum"
- relationship-list:
+ items:
+ $ref: "#/patchDefinitions/p-interface"
+ physical-link:
+ description: |
+ Collection of physical connections, typically between p-interfaces
+ ###### Related Nodes
+ - FROM p-interface( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)
+ required:
+ - link-name
+ properties:
+ link-name:
+ type: string
+ description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ circuit-id:
+ type: string
+ description: Circuit it
+ dual-mode:
+ type: string
+ description: Dual access mode (e.g., primary, secondary
+ management-option:
+ type: string
+ description: To provide information on who manages this circuit. A&AI or 3rd party transport provider
+ service-provider-name:
+ type: string
+ description: Name of the service Provider on this link.
+ physical-links:
+ description: |
+ Collection of physical connections, typically between p-interfaces
+ properties:
+ physical-link:
type: array
- items:
- $ref: "#/definitions/relationship"
- models:
+ items:
+ $ref: "#/patchDefinitions/physical-link"
+ platform:
description: |
- Collection of subgraph definitions provided by ASDC to describe the inventory assets and their connections related to ASDC models
+ describes a platform
+ ###### Related Nodes
+ - TO generic-vnf( platform org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)
+ required:
+ - platform-name
properties:
- model:
+ platform-name:
+ type: string
+ description: Name of the platform
+ platforms:
+ description: |
+ Collection of platforms
+ properties:
+ platform:
type: array
items:
- $ref: "#/definitions/model"
- related-lookup:
+ $ref: "#/patchDefinitions/platform"
+ pnf:
description: |
- TBD
+ PNF represents a physical network function. typically equipment used in the D1 world.
###### Related Nodes
- - FROM named-query-element (is composed of related-lookup)
+ - TO complex( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - PNF is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
required:
- - related-lookup-uuid
- - source-node-type
- - source-node-property
- - target-node-type
- - target-node-property
+ - pnf-name
+ - in-maint
properties:
- related-lookup-uuid:
+ pnf-name:
type: string
- source-node-type:
+ description: unique name of Physical Network Function.
+ pnf-name2:
type: string
- source-node-property:
+ description: name of Physical Network Function.
+ pnf-name2-source:
type: string
- target-node-type:
+ description: source of name2
+ pnf-id:
type: string
- target-node-property:
+ description: id of pnf
+ equip-type:
type: string
- property-collect-list:
+ description: Equipment type. Source of truth should define valid values.
+ equip-vendor:
type: string
- resource-version:
+ description: Equipment vendor. Source of truth should define valid values.
+ equip-model:
type: string
- relationship-list:
+ description: Equipment model. Source of truth should define valid values.
+ management-option:
+ type: string
+ description: identifier of managed by company or customer
+ ipaddress-v4-oam:
+ type: string
+ description: ipv4-oam-address with new naming convention for IP addresses
+ sw-version:
+ type: string
+ description: sw-version is the version of SW for the hosted application on the PNF.
+ orchestration-status:
+ type: string
+ description: orchestration-status is the status of orchestration on the PNF.
+ in-maint:
+ type: boolean
+ frame-id:
+ type: string
+ description: ID of the physical frame (relay rack) where pnf is installed.
+ pnfs:
+ description: |
+ Collection of Physical Network Functions.
+ properties:
+ pnf:
type: array
- items:
- $ref: "#/definitions/relationship"
- related-lookups:
+ items:
+ $ref: "#/patchDefinitions/pnf"
+ port-group:
+ description: |
+ Used to capture the network interfaces of this VCE
+ ###### Related Nodes
+ - TO vce( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM cvlan-tag( cvlan-tag org.onap.relationships.inventory.BelongsTo port-group, MANY2ONE)
+ - PORT-GROUP is DELETED when these are DELETED CVLAN-TAG
+ required:
+ - interface-id
+ - orchestration-status
properties:
- related-lookup:
+ interface-id:
+ type: string
+ description: Unique ID of the interface
+ neutron-network-id:
+ type: string
+ description: Neutron network id of this Interface
+ neutron-network-name:
+ type: string
+ description: Neutron network name of this Interface
+ interface-role:
+ type: string
+ description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
+ port-groups:
+ properties:
+ port-group:
type: array
items:
- $ref: "#/definitions/related-lookup"
+ $ref: "#/patchDefinitions/port-group"
+ project:
+ description: |
+ describes the project
+ ###### Related Nodes
+ - TO service-instance( project org.onap.relationships.inventory.Uses service-instance, ONE2MANY)
+ required:
+ - project-name
+ properties:
+ project-name:
+ type: string
+ description: Name of the project deploying a service
+ projects:
+ description: |
+ Collection of projects
+ properties:
+ project:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/project"
+ properties:
+ description: |
+ Property holder for query properties or instance properties
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
property-constraint:
description: |
TBD
###### Related Nodes
- - FROM named-query-element (is composed of property-constraint)
+ - TO named-query-element( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
required:
- property-constraint-uuid
- constraint-type
@@ -35736,100 +51155,372 @@ definitions:
type: string
property-value:
type: string
- resource-version:
- type: string
property-constraints:
properties:
property-constraint:
type: array
items:
- $ref: "#/definitions/property-constraint"
- named-query-element:
+ $ref: "#/patchDefinitions/property-constraint"
+ pserver:
description: |
- TBD
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
+ Compute host whose hostname must be unique and must exactly match what is sent as a relationship to a vserver.
###### Related Nodes
- - TO named-query-element (comprises named-query-element, Many2Many)
- - TO model (Many2One)
- - TO property-constraint (comprises named-query-element, One2Many)
- - TO related-lookup (comprises named-query-element, One2Many)
- - FROM named-query (is composed of named-query-element)
- - FROM named-query-element (is composed of named-query-element)
+ - TO group-assignment( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)
+ - TO availability-zone( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)
+ - TO cloud-region( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)
+ - TO complex( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - FROM vserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)
+ - PSERVER cannot be deleted if linked to GENERIC-VNF,LOGICAL-LINK,VSERVER
+ - PSERVER is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
+ - PSERVER cannot be deleted if linked to GROUP-ASSIGNMENT
required:
- - named-query-element-uuid
+ - hostname
+ - in-maint
properties:
- named-query-element-uuid:
+ hostname:
type: string
- property-collect-list:
+ description: Value from executing hostname on the compute node.
+ ptnii-equip-name:
type: string
- resource-version:
+ description: PTNII name
+ number-of-cpus:
+ type: integer
+ format: int32
+ description: Number of cpus
+ disk-in-gigabytes:
+ type: integer
+ format: int32
+ description: Disk size, in GBs
+ ram-in-megabytes:
+ type: integer
+ format: int32
+ description: RAM size, in MBs
+ equip-type:
type: string
- property-limit-desc:
+ description: Equipment type. Source of truth should define valid values.
+ equip-vendor:
type: string
- do-not-output:
+ description: Equipment vendor. Source of truth should define valid values.
+ equip-model:
type: string
- named-query-elements:
+ description: Equipment model. Source of truth should define valid values.
+ fqdn:
+ type: string
+ description: Fully-qualified domain name
+ pserver-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ ipv4-oam-address:
+ type: string
+ description: Used to configure device, also used for troubleshooting and is IP used for traps generated by device.
+ serial-number:
+ type: string
+ description: Serial number, may be queried
+ pserver-id:
+ type: string
+ description: ID of Pserver
+ internet-topology:
+ type: string
+ description: internet topology of Pserver
+ in-maint:
+ type: boolean
+ pservers:
+ description: |
+ Collection of compute hosts.
+ properties:
+ pserver:
type: array
- items:
- $ref: "#/definitions/named-query-element"
- related-lookups:
+ items:
+ $ref: "#/patchDefinitions/pserver"
+ query-parameters:
+ description: |
+ QueryParameters for performing a named-query or model query
+ properties:
+ named-query:
+ type: object
+ $ref: "#/patchDefinitions/named-query"
+ model:
+ type: object
+ $ref: "#/patchDefinitions/model"
+ related-lookup:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query-element( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ required:
+ - related-lookup-uuid
+ - source-node-type
+ - source-node-property
+ - target-node-type
+ - target-node-property
+ properties:
+ related-lookup-uuid:
+ type: string
+ source-node-type:
+ type: string
+ source-node-property:
+ type: string
+ target-node-type:
+ type: string
+ target-node-property:
+ type: string
+ property-collect-list:
+ type: string
+ related-lookups:
+ properties:
+ related-lookup:
type: array
- items:
- $ref: "#/definitions/related-lookup"
- property-constraints:
+ items:
+ $ref: "#/patchDefinitions/related-lookup"
+ related-to-property:
+ properties:
+ property-key:
+ type: string
+ description: Key part of a key/value pair
+ property-value:
+ type: string
+ description: Value part of a key/value pair
+ relationship:
+ properties:
+ related-to:
+ type: string
+ description: A keyword provided by A&AI to indicate type of node.
+ related-link:
+ type: string
+ description: URL to the object in A&AI.
+ relationship-data:
type: array
- items:
- $ref: "#/definitions/property-constraint"
- relationship-list:
+ items:
+ $ref: "#/patchDefinitions/relationship-data"
+ related-to-property:
type: array
- items:
- $ref: "#/definitions/relationship"
- named-query-elements:
+ items:
+ $ref: "#/patchDefinitions/related-to-property"
+ relationship-data:
+ required:
+ - relationship-key
+ - relationship-value
properties:
- named-query-element:
+ relationship-key:
+ type: string
+ description: A keyword provided by A&AI to indicate an attribute.
+ relationship-value:
+ type: string
+ description: Value of the attribute.
+ reserved-prop-names:
+ description: |
+ Internal map to define some reserved properties of a vertex
+ properties:
+ last-mod-source-of-truth:
+ type: string
+ aai-node-type:
+ type: string
+ aai-created-ts:
+ type: integer
+ format: int64
+ aai-unique-key:
+ type: string
+ aai-last-mod-ts:
+ type: integer
+ format: int64
+ source-of-truth:
+ type: string
+ response-list:
+ description: |
+ Response container for the results of a named-query or model query
+ properties:
+ inventory-response-items:
+ type: object
+ $ref: "#/patchDefinitions/inventory-response-items"
+ result-data:
+ properties:
+ resource-type:
+ type: string
+ description: The specific type of node in the A&AI graph
+ resource-link:
+ type: string
+ description: The URL to the specific resource
+ route-table-reference:
+ description: |
+ Openstack route table reference.
+ ###### Related Nodes
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)
+ required:
+ - route-table-reference-id
+ - route-table-reference-fqdn
+ properties:
+ route-table-reference-id:
+ type: string
+ description: Route Table Reference id, UUID assigned to this instance.
+ route-table-reference-fqdn:
+ type: string
+ description: FQDN entry in the route table.
+ route-table-references:
+ description: |
+ Collection of openstack route table references
+ properties:
+ route-table-reference:
type: array
items:
- $ref: "#/definitions/named-query-element"
- named-query:
+ $ref: "#/patchDefinitions/route-table-reference"
+ route-target:
description: |
- TBD
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
+ Route target information
###### Related Nodes
- - TO model (One2Many)
- - TO named-query-element (comprises named-query, One2One)
+ - TO vpn-binding( route-target org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2ONE)
required:
- - named-query-uuid
- - named-query-name
- - named-query-version
+ - global-route-target
+ - route-target-role
properties:
- named-query-uuid:
+ global-route-target:
type: string
- named-query-name:
+ description: Number used to identify an RT, globally unique in the network
+ route-target-role:
type: string
- named-query-version:
+ description: Role assigned to this route target
+ route-targets:
+ description: |
+ Collection of route target information
+ properties:
+ route-target:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/route-target"
+ routing-instance:
+ description: |
+ ###### Related Nodes
+ - TO site-pair-set( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)
+ - FROM site-pair( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)
+ - ROUTING-INSTANCE is DELETED when these are DELETED SITE-PAIR
+ required:
+ - routing-instance-id
+ properties:
+ routing-instance-id:
type: string
- required-input-param:
+ description: Unique id of routing instance
+ rpm-owner:
type: string
- description:
+ description: rpm owner
+ routing-instances:
+ description: |
+ set of probes related to generic-vnf routing instance
+ properties:
+ routing-instance:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/routing-instance"
+ sdn-zone-response:
+ properties:
+ oam-networks:
+ type: object
+ $ref: "#/patchDefinitions/oam-networks"
+ az-and-dvs-switches:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/az-and-dvs-switches"
+ search:
+ properties:
+ edge-tag-query-result:
+ type: object
+ $ref: "#/patchDefinitions/edge-tag-query-result"
+ edge-tag-query-request:
+ type: object
+ $ref: "#/patchDefinitions/edge-tag-query-request"
+ search-results:
+ type: object
+ $ref: "#/patchDefinitions/search-results"
+ sdn-zone-response:
+ type: object
+ $ref: "#/patchDefinitions/sdn-zone-response"
+ search-results:
+ properties:
+ result-data:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/result-data"
+ secondary-filt:
+ description: |
+ SecondaryFilt for performing a named-query or model query
+ secondary-filter:
+ properties:
+ property-name:
type: string
- resource-version:
+ filter-type:
type: string
- named-query-elements:
+ property-value:
+ type: string
+ secondary-filts:
+ description: |
+ SecondaryFilts for performing a named-query or model query
+ properties:
+ secondary-filt:
type: array
- items:
- $ref: "#/definitions/named-query-element"
- relationship-list:
+ items:
+ $ref: "#/patchDefinitions/secondary-filt"
+ segmentation-assignment:
+ description: |
+ Openstack segmentation assignment.
+ ###### Related Nodes
+ - TO l3-network( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ required:
+ - segmentation-id
+ properties:
+ segmentation-id:
+ type: string
+ description: Route Table Reference id, UUID assigned to this instance.
+ segmentation-assignments:
+ description: |
+ Collection of openstack segmentation assignments
+ properties:
+ segmentation-assignment:
type: array
- items:
- $ref: "#/definitions/relationship"
- named-queries:
+ items:
+ $ref: "#/patchDefinitions/segmentation-assignment"
+ service:
+ description: |
+ Stand-in for service model definitions. Likely to be deprecated in favor of models from ASDC.
+ required:
+ - service-id
+ - service-description
properties:
- named-query:
+ service-id:
+ type: string
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ service-description:
+ type: string
+ description: Description of the service
+ service-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ service-capabilities:
+ description: |
+ Collection of service capabilities.
+ properties:
+ service-capability:
type: array
items:
- $ref: "#/definitions/named-query"
+ $ref: "#/patchDefinitions/service-capability"
+ service-capability:
+ description: |
+ Early definition of server/resource pairings, likely to be replaced by models. No new use should be made of this.
+ ###### Related Nodes
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - SERVICE-CAPABILITY cannot be deleted if linked to AVAILABILITY-ZONE,OAM-NETWORK
+ required:
+ - service-type
+ - vnf-type
+ properties:
+ service-type:
+ type: string
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded and clients should expect changes to occur in the future to this field as ASDC matures.
service-design-and-creation:
description: |
Namespace for objects managed by ASDC
@@ -35837,65 +51528,1051 @@ definitions:
vnf-images:
type: array
items:
- $ref: "#/definitions/vnf-image"
+ $ref: "#/patchDefinitions/vnf-image"
services:
type: array
items:
- $ref: "#/definitions/service"
+ $ref: "#/patchDefinitions/service"
service-capabilities:
type: array
items:
- $ref: "#/definitions/service-capability"
+ $ref: "#/patchDefinitions/service-capability"
models:
type: array
items:
- $ref: "#/definitions/model"
+ $ref: "#/patchDefinitions/model"
named-queries:
type: array
items:
- $ref: "#/definitions/named-query"
- logical-link:
+ $ref: "#/patchDefinitions/named-query"
+ service-instance:
description: |
- Logical links generally connect l-interfaces but are used to express logical connectivity between two points
- ###### Default Delete Scope
- THIS_NODE_ONLY
- ###### Related Nodes
- - TO lag-link (Many2Many)
- - TO pnf (Many2Many)
- - TO logical-link (One2Many)
- - TO generic-vnf (Many2Many)
- - TO pserver (Many2Many)
- - FROM l-interface
- - FROM p-interface
- - FROM service-instance
- - FROM virtual-data-center
- - FROM vlan
- - FROM logical-link
+ Instance of a service
+ ###### Related Nodes
+ - TO generic-vnf( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)
+ - TO l3-network( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)
+ - TO connector( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)
+ - TO cvlan-tag( service-instance org.onap.relationships.inventory.ComposedOf cvlan-tag, MANY2MANY)
+ - TO logical-link( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - TO service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)
+ - TO vlan( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)
+ - TO service-subscription( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)
+ - TO vce( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)
+ - SERVICE-INSTANCE is DELETED when these are DELETED METADATUM
+ - SERVICE-INSTANCE deletion means associated objects of these types are also DELETED:LOGICAL-LINK
required:
- - link-name
- - link-type
+ - service-instance-id
properties:
- link-name:
+ service-instance-id:
type: string
- description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
- link-type:
+ description: Uniquely identifies this instance of a service
+ service-instance-name:
type: string
- description: Type of logical link, e.g., evc
- speed-value:
+ description: This field will store a name assigned to the service-instance.
+ persona-model-id:
type: string
- description: Captures the numeric part of the speed
- speed-units:
+ description: the ASDC model id for this resource or service model.
+ persona-model-version:
type: string
- description: Captures the units corresponding to the speed
+ description: the ASDC model version for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ bandwidth-total:
+ type: string
+ description: Indicates the total bandwidth to be used for this service.
+ bandwidth-up-wan1:
+ type: string
+ description: indicates the upstream bandwidth this service will use on the WAN1 port of the physical device.
+ bandwidth-down-wan1:
+ type: string
+ description: indicates the downstream bandwidth this service will use on the WAN1 port of the physical device.
+ bandwidth-up-wan2:
+ type: string
+ description: indicates the upstream bandwidth this service will use on the WAN2 port of the physical device.
+ bandwidth-down-wan2:
+ type: string
+ description: indicates the downstream bandwidth this service will use on the WAN2 port of the physical device.
+ vhn-portal-url:
+ type: string
+ description: URL customers will use to access the vHN Portal.
+ service-instance-location-id:
+ type: string
+ description: An identifier that customers assign to the location where this service is being used.
+ service-instances:
+ description: |
+ Collection of service instances
+ properties:
+ service-instance:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/service-instance"
+ service-subscription:
+ description: |
+ Object that group service instances.
+ ###### Related Nodes
+ - TO customer( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)
+ - TO tenant( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)
+ - SERVICE-SUBSCRIPTION is DELETED when these are DELETED SERVICE-INSTANCE
+ required:
+ - service-type
+ properties:
+ service-type:
+ type: string
+ description: Value defined by orchestration to identify this service across ECOMP.
+ temp-ub-sub-account-id:
+ type: string
+ description: This property will be deleted from A&AI in the near future. Only stop gap solution.
+ service-subscriptions:
+ description: |
+ Collection of objects that group service instances.
+ properties:
+ service-subscription:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/service-subscription"
+ services:
+ description: |
+ Collection of service model definitions. Likely to be deprecated in favor of models from ASDC.
+ properties:
+ service:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/service"
+ site-pair:
+ description: |
+ ###### Related Nodes
+ - TO routing-instance( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)
+ - FROM class-of-service( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)
+ - SITE-PAIR is DELETED when these are DELETED CLASS-OF-SERVICE
+ required:
+ - site-pair-id
+ properties:
+ site-pair-id:
+ type: string
+ description: unique identifier of probe
+ source-ip:
+ type: string
+ description: Prefix address
+ destination-ip:
+ type: string
+ description: Prefix address
ip-version:
type: string
- description: v4, v6, or ds for dual stack
- routing-protocol:
+ description: ip version, v4, v6
+ destination-hostname:
type: string
- description: For example, static or BGP
- resource-version:
+ description: Hostname of the destination equipment to which SLAs are measured against.
+ destination-equip-type:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ description: The type of destinatination equipment. Could be Router, etc.
+ site-pair-set:
+ description: |
+ Set of instances for probes used to measure service level agreements
+ ###### Related Nodes
+ - TO generic-vnf( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM routing-instance( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)
+ - SITE-PAIR-SET is DELETED when these are DELETED ROUTING-INSTANCE
+ required:
+ - site-pair-set-id
+ properties:
+ site-pair-set-id:
+ type: string
+ description: Unique id of site pair set.
+ site-pair-sets:
+ description: |
+ Collection of sets of instances for probes related to generic-vnf
+ properties:
+ site-pair-set:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/site-pair-set"
+ site-pairs:
+ description: |
+ probe within a set
+ properties:
+ site-pair:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/site-pair"
+ snapshot:
+ description: |
+ Openstack snapshot
+ ###### Related Nodes
+ - TO cloud-region( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)
+ required:
+ - snapshot-id
+ properties:
+ snapshot-id:
+ type: string
+ description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
+ snapshot-name:
+ type: string
+ description: Snapshot name
+ snapshot-architecture:
+ type: string
+ description: Operating system architecture
+ snapshot-os-distro:
+ type: string
+ description: The common name of the operating system distribution in lowercase
+ snapshot-os-version:
+ type: string
+ description: The operating system version as specified by the distributor.
+ application:
+ type: string
+ description: The application that the image instantiates.
+ application-vendor:
+ type: string
+ description: The vendor of the application.
+ application-version:
+ type: string
+ description: The version of the application.
+ snapshot-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ prev-snapshot-id:
+ type: string
+ description: This field contains the UUID of the previous snapshot (if any).
+ snapshots:
+ description: |
+ Collection of openstack snapshots
+ properties:
+ snapshot:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/snapshot"
+ sriov-pf:
+ description: |
+ SR-IOV Physical Function
+ ###### Related Nodes
+ - TO p-interface( sriov-pf org.onap.relationships.inventory.BelongsTo p-interface, ONE2ONE)
+ - FROM sriov-vf( sriov-vf org.onap.relationships.inventory.Uses sriov-pf, MANY2ONE)
+ required:
+ - pf-pci-id
+ properties:
+ pf-pci-id:
+ type: string
+ description: Identifier for the sriov-pf
+ sriov-pfs:
+ description: |
+ Collection of SR-IOV Physical Functions.
+ properties:
+ sriov-pf:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/sriov-pf"
+ sriov-vf:
+ description: |
+ SR-IOV Virtual Function (not to be confused with virtual network function)
+ ###### Related Nodes
+ - TO l-interface( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)
+ required:
+ - pci-id
+ properties:
+ pci-id:
+ type: string
+ description: PCI ID used to identify the sriov-vf
+ vf-vlan-filter:
+ type: string
+ description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM.
+ vf-mac-filter:
+ type: string
+ description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM.
+ vf-vlan-strip:
+ type: boolean
+ description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM.
+ vf-vlan-anti-spoof-check:
+ type: boolean
+ description: This option ensures anti VLAN spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
+ vf-mac-anti-spoof-check:
+ type: boolean
+ description: This option ensures anti MAC spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
+ vf-mirrors:
+ type: string
+ description: This option defines the set of Mirror objects which essentially mirrors the traffic from source to set of collector VNF Ports.
+ vf-broadcast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows all broadcast traffic to reach the VM
+ vf-unknown-multicast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows unknown multicast traffic to reach the VM
+ vf-unknown-unicast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows unknown unicast traffic to reach the VM
+ vf-insert-stag:
+ type: boolean
+ description: This option, if set to true, instructs to insert outer tag after traffic comes out of VM.
+ vf-link-status:
+ type: string
+ description: This option is used to set the link status. Valid values as of 1607 are on, off, and auto.
+ sriov-vfs:
+ description: |
+ Collection of SR-IOV Virtual Functions.
+ properties:
+ sriov-vf:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/sriov-vf"
+ start-node-filter:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ subnet:
+ description: |
+ ###### Related Nodes
+ - TO l3-network( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - SUBNET cannot be deleted if linked to L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST
+ required:
+ - subnet-id
+ - dhcp-enabled
+ properties:
+ subnet-id:
+ type: string
+ description: Subnet ID, should be UUID.
+ subnet-name:
+ type: string
+ description: Name associated with the subnet.
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of this subnet
+ gateway-address:
+ type: string
+ description: gateway ip address
+ network-start-address:
+ type: string
+ description: network start address
+ cidr-mask:
+ type: string
+ description: cidr mask
+ ip-version:
+ type: string
+ description: ip version
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ dhcp-enabled:
+ type: boolean
+ dhcp-start:
+ type: string
+ description: the start address reserved for use by dhcp
+ dhcp-end:
+ type: string
+ description: the last address reserved for use by dhcp
+ subnets:
+ properties:
+ subnet:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/subnet"
+ tagged-inventory-item-list:
+ properties:
+ inventory-item:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/inventory-item"
+ tenant:
+ description: |
+ Openstack tenant
+ ###### Related Nodes
+ - TO cloud-region( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO group-assignment( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)
+ - TO l3-network( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO volume-group( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - FROM service-subscription( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)
+ - FROM vserver( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)
+ - TENANT cannot be deleted if linked to VSERVER
+ required:
+ - tenant-id
+ - tenant-name
+ properties:
+ tenant-id:
+ type: string
+ description: Unique id relative to the cloud-region.
+ tenant-name:
+ type: string
+ description: Readable name of tenant
+ tenants:
+ description: |
+ Collection of openstack tenants.
+ properties:
+ tenant:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/tenant"
+ tunnel-xconnect:
+ description: |
+ Represents the specifics of a tunnel cross connect piece of a resource that gets separately allotted
+ ###### Related Nodes
+ - TO allotted-resource( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)
+ required:
+ - id
+ - bandwidth-up-wan1
+ - bandwidth-down-wan1
+ - bandwidth-up-wan2
+ - bandwidth-down-wan2
+ properties:
+ id:
+ type: string
+ description: Allotted Resource id UUID assigned to this instance.
+ bandwidth-up-wan1:
+ type: string
+ description: The WAN uplink bandwidth for WAN1
+ bandwidth-down-wan1:
+ type: string
+ description: The WAN downlink bandwidth for WAN1
+ bandwidth-up-wan2:
+ type: string
+ description: The WAN uplink bandwidth for WAN2
+ bandwidth-down-wan2:
+ type: string
+ description: The WAN downlink bandwidth for WAN2
+ tunnel-xconnects:
+ description: |
+ This object is used to store the specific tunnel cross connect aspects of an allotted resource
+ properties:
+ tunnel-xconnect:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/tunnel-xconnect"
+ update:
+ description: |
+ Serves a PATCH like function. Does not enforce concurrency control. Clear each usage with AAI team.
+ required:
+ - update-node-type
+ properties:
+ update-node-type:
+ type: string
+ update-node-key:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/update-node-key"
+ update-node-uri:
+ type: string
+ action:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/action"
+ update-node-key:
+ properties:
+ key-name:
+ type: string
+ key-value:
+ type: string
+ vce:
+ description: |
+ Virtual Customer Edge Router, used specifically for Gamma. This object is deprecated.
+ ###### Related Nodes
+ - TO availability-zone( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - TO complex( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)
+ - TO vserver( vce tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM port-group( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)
+ - VCE is DELETED when these are DELETED PORT-GROUP
+ required:
+ - vnf-id
+ - vnf-name
+ - vnf-type
+ properties:
+ vnf-id:
+ type: string
+ description: Unique id of VNF. This is unique across the graph.
+ vnf-name:
+ type: string
+ description: Name of VNF.
+ vnf-name2:
+ type: string
+ description: Alternate name of VNF.
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded and clients should expect changes to occur in the future to this field as ASDC matures.
+ service-id:
+ type: string
+ description: Unique identifier of service from ASDC. Expect this to change as ASDC matures.
+ regional-resource-zone:
+ type: string
+ description: Regional way of organizing pservers, source of truth should define values
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ operational-state:
+ type: string
+ description: Indicator for whether the resource is considered operational
+ license-key:
+ type: string
+ description: License key
+ equipment-role:
+ type: string
+ description: Network role being played by this VNF
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ vpe-id:
+ type: string
+ description: Unique ID of VPE connected to this VCE.
+ v6-vce-wan-address:
+ type: string
+ description: Valid v6 IP address for the WAN Link on this router. Implied length of /64.
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure vce, also used for troubleshooting and is IP used for traps generated by VCE.
+ vces:
+ description: |
+ Collection of Virtual Customer Edge Routers, used specifically for Gamma. This object is deprecated.
+ properties:
+ vce:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vce"
+ vf-module:
+ description: |
+ a deployment unit of VNFCs
+ ###### Related Nodes
+ - TO generic-vnf( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO l3-network( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)
+ - TO vnfc( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)
+ - TO volume-group( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)
+ - TO vserver( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)
+ - VF-MODULE cannot be deleted if linked to VNFC
+ required:
+ - vf-module-id
+ - is-base-vf-module
+ properties:
+ vf-module-id:
+ type: string
+ description: Unique ID of vf-module.
+ vf-module-name:
+ type: string
+ description: Name of vf-module
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance.
+ orchestration-status:
+ type: string
+ description: orchestration status of this vf-module, mastered by MSO
+ is-base-vf-module:
+ type: boolean
+ vf-modules:
+ description: |
+ Collection of vf-modules, a deployment unit of VNFCs
+ properties:
+ vf-module:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vf-module"
+ vig-server:
+ description: |
+ vig-server contains information about a vig server used for IPSec-configuration. Populated by SDN-C from 1607
+ ###### Related Nodes
+ - TO ipsec-configuration( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)
+ required:
+ - vig-address-type
+ properties:
+ vig-address-type:
+ type: string
+ description: indicates whether the VIG is for AVPN or INTERNET
+ ipaddress-v4-vig:
+ type: string
+ description: v4 IP of the vig server
+ ipaddress-v6-vig:
+ type: string
+ description: v6 IP of the vig server
+ vig-servers:
+ properties:
+ vig-server:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vig-server"
+ vip-ipv4-address-list:
+ description: |
+ IPv4 Address Range
+ ###### Related Nodes
+ - TO cloud-region( vip-ipv4-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO instance-group( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO subnet( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv4-address-list, MANY2MANY)
+ required:
+ - vip-ipv4-address
+ properties:
+ vip-ipv4-address:
+ type: string
+ description: IP address
+ vip-ipv4-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 32 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ vip-ipv6-address-list:
+ description: |
+ IPv6 Address Range
+ ###### Related Nodes
+ - TO cloud-region( vip-ipv6-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO instance-group( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO subnet( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv6-address-list, MANY2MANY)
+ required:
+ - vip-ipv6-address
+ properties:
+ vip-ipv6-address:
+ type: string
+ description: IP address
+ vip-ipv6-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 128 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ virtual-data-center:
+ description: |
+ Virtual organization of cloud infrastructure elements in a data center context
+ ###### Related Nodes
+ - FROM connector( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ required:
+ - vdc-id
+ - vdc-name
+ properties:
+ vdc-id:
+ type: string
+ description: Unique ID of the vdc
+ vdc-name:
+ type: string
+ description: Name of the virtual data center
+ virtual-data-centers:
+ description: |
+ Virtual organization of cloud infrastructure elements in a data center context
+ properties:
+ virtual-data-center:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/virtual-data-center"
+ vlan:
+ description: |
+ Definition of vlan
+ ###### Related Nodes
+ - TO l-interface( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)
+ - TO logical-link( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - TO multicast-configuration( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ - VLAN is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST
+ - VLAN deletion means associated objects of these types are also DELETED:LOGICAL-LINK
+ required:
+ - vlan-interface
+ properties:
+ vlan-interface:
+ type: string
+ description: String that identifies the interface
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ vlans:
+ properties:
+ vlan:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vlan"
+ vnf:
+ description: |
+ Abstract vnf class
+ required:
+ - vnf-id
+ properties:
+ vnf-id:
+ type: string
+ description: Unique id of VNF. This is unique across the graph.
+ vnf-image:
+ description: |
+ Image object that pertain to a VNF that doesn't have associated vservers. This is a kludge.
+ ###### Related Nodes
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)
+ - VNF-IMAGE cannot be deleted if linked to GENERIC-VNF
+ required:
+ - vnf-image-uuid
+ - application
+ - application-vendor
+ properties:
+ vnf-image-uuid:
+ type: string
+ description: Unique ID of this asset
+ application:
+ type: string
+ description: The application that the image instantiates.
+ application-vendor:
+ type: string
+ description: The vendor of the application.
+ application-version:
+ type: string
+ description: The version of the application.
+ selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ vnf-images:
+ description: |
+ Collection of image objects that pertain to a VNF that doesn't have associated vservers. This is a kludge.
+ properties:
+ vnf-image:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vnf-image"
+ vnfc:
+ description: |
+ ###### Related Nodes
+ - TO generic-vnf( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vserver( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)
+ required:
+ - vnfc-name
+ - vnfc-function-code
+ - vnfc-type
+ - in-maint
+ - is-closed-loop-disabled
+ properties:
+ vnfc-name:
+ type: string
+ description: Unique ID of vnfc.
+ vnfc-function-code:
+ type: string
+ description: function code
+ vnfc-type:
+ type: string
+ description: type
+ prov-status:
+ type: string
+ description: prov status of this vnfc
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by APP-C
+ ipaddress-v4-oam-vip:
+ type: string
+ description: Oam V4 vip address of this vnfc
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
+ group-notation:
+ type: string
+ description: Group notation of VNFC
+ vnfcs:
+ description: |
+ virtual network components associated with a vserver from application controller.
+ properties:
+ vnfc:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vnfc"
+ volume:
+ description: |
+ Ephemeral Block storage volume.
+ ###### Related Nodes
+ - FROM vserver (PARENT of volume, vserver tosca.relationships.AttachesTo volume)
+ required:
+ - volume-id
+ - volume-selflink
+ properties:
+ volume-id:
+ type: string
+ description: Unique ID of block storage volume relative to the vserver.
+ volume-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ volume-group:
+ description: |
+ Persistent block-level storage.
+ ###### Related Nodes
+ - TO cloud-region( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO complex( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ required:
+ - volume-group-id
+ - volume-group-name
+ - vnf-type
+ properties:
+ volume-group-id:
+ type: string
+ description: Unique ID of volume-group.
+ volume-group-name:
+ type: string
+ description: Name of the volume group.
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this volume-group
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded and clients should expect changes to occur in the future to this field as ASDC matures.
+ orchestration-status:
+ type: string
+ description: Orchestration status of this volume-group
+ volume-groups:
+ description: |
+ Collection of persistent block-level storage.
+ properties:
+ volume-group:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/volume-group"
+ volumes:
+ description: |
+ Collection of ephemeral Block storage volumes.
+ properties:
+ volume:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/volume"
+ vpls-pe:
+ description: |
+ VPLS Provider Edge routers.
+ ###### Related Nodes
+ - TO complex( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO ctag-pool( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - VPLS-PE is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
+ required:
+ - equipment-name
+ properties:
+ equipment-name:
+ type: string
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address).
+ equipment-role:
+ type: string
+ description: Client should send valid enumerated value, e.g., VPLS-PE.
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Temporary location for stag to get to VCE
+ vpls-pes:
+ description: |
+ Collection of VPLS Provider Edge routers
+ properties:
+ vpls-pe:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vpls-pe"
+ vpn-binding:
+ description: |
+ VPN binding
+ ###### Related Nodes
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - VPN-BINDING cannot be deleted if linked to L3-NETWORK
+ required:
+ - vpn-id
+ - vpn-name
+ - global-route-target
+ properties:
+ vpn-id:
+ type: string
+ description: VPN ID, globally unique within A&AI
+ vpn-name:
+ type: string
+ description: VPN Name
+ global-route-target:
+ type: string
+ description: Number used to identify a VPN, globally unique in the network
+ vpn-platform:
+ type: string
+ description: the platform associated with the VPN example AVPN, Mobility
+ vpn-bindings:
+ properties:
+ vpn-binding:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vpn-binding"
+ vserver:
+ description: |
+ Virtual Servers, aka virtual machine or VM.
+ ###### Related Nodes
+ - TO tenant( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)
+ - TO flavor( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)
+ - TO image( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)
+ - TO pserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)
+ - TO snapshot( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)
+ - TO volume (CHILD of vserver, vserver tosca.relationships.AttachesTo volume, ONE2MANY)
+ - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM vce( vce tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)
+ - FROM vnfc( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)
+ - VSERVER is DELETED when these are DELETED L-INTERFACE
+ - VSERVER deletion means associated objects of these types are also DELETED:VOLUME
+ required:
+ - vserver-id
+ - vserver-name
+ - vserver-selflink
+ - in-maint
+ - is-closed-loop-disabled
+ properties:
+ vserver-id:
+ type: string
+ description: Unique identifier for this vserver relative to its tenant
+ vserver-name:
+ type: string
+ description: Name of vserver
+ vserver-name2:
+ type: string
+ description: Alternative name of vserver
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ vserver-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
+ vservers:
+ description: |
+ Collection of virtual Servers, aka virtual machines or VMs.
+ properties:
+ vserver:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vserver"
+ zone:
+ description: |
+ A zone is a grouping of assets in a location homing to the same connections into the CBB
+ ###### Related Nodes
+ - TO complex( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM pnf( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ required:
+ - zone-id
+ - zone-name
+ - design-type
+ - zone-context
+ properties:
+ zone-id:
+ type: string
+ description: Code assigned by AIC to the zone
+ zone-name:
+ type: string
+ description: English name associated with the zone
+ design-type:
+ type: string
+ description: Design of zone [Medium/Large?]
+ zone-context:
+ type: string
+ description: Context of zone [production/test]
+ status:
+ type: string
+ description: Status of a zone.
+ zones:
+ description: |
+ Collection of zones
+ properties:
+ zone:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/zone"
+getDefinitions:
+ aai-internal:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ action:
+ properties:
+ action-type:
+ type: string
+ action-data:
+ type: array
+ items:
+ $ref: "#/getDefinitions/action-data"
+ action-data:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ actions:
+ description: |
+ APIs that are more action related than REST (e.g., notify, update).
+ properties:
+ update:
+ type: object
+ $ref: "#/getDefinitions/update"
+ notify:
+ type: object
+ $ref: "#/getDefinitions/notify"
+ allotted-resource:
+ description: |
+ Represents a slice or partial piece of a resource that gets separately allotted
+ ###### Related Nodes
+ - TO generic-vnf( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY)
+ - TO instance-group( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO l3-network( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY)
+ - TO vlan( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY)
+ - TO service-instance( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM tunnel-xconnect( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY)
+ - ALLOTTED-RESOURCE is DELETED when these are DELETED TUNNEL-XCONNECT
+ required:
+ - id
+ properties:
+ id:
+ type: string
+ description: Allotted Resource id UUID assigned to this instance.
+ description:
+ type: string
+ description: The descriptive information assigned to this allotted resource instance
+ selflink:
+ type: string
+ description: Link back to more information in the controller
persona-model-id:
type: string
description: the ASDC model id for this resource or service model.
@@ -35905,40 +52582,93 @@ definitions:
model-version-id:
type: string
description: the ASDC model version for this resource or service model.
- widget-model-id:
+ persona-model-customization-id:
type: string
- description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
- widget-model-version:
+ description: captures the id of all the configuration used to customize the resource for the service.
+ resource-version:
type: string
- description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
- operational-status:
+ description: Concurrency value
+ tunnel-xconnects:
+ type: array
+ items:
+ $ref: "#/getDefinitions/tunnel-xconnect"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ allotted-resources:
+ description: |
+ This object is used to store slices of services being offered
+ properties:
+ allotted-resource:
+ type: array
+ items:
+ $ref: "#/getDefinitions/allotted-resource"
+ availability-zone:
+ description: |
+ Availability zone, a collection of compute hosts/pservers
+ ###### Related Nodes
+ - TO complex( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO service-capability( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - TO cloud-region( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM ctag-pool( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM dvs-switch( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - FROM pserver( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)
+ - FROM vce( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - AVAILABILITY-ZONE cannot be deleted if linked to CTAG-POOL,DVS-SWITCH,GENERIC-VNF,PSERVER,VCE
+ required:
+ - availability-zone-name
+ - hypervisor-type
+ properties:
+ availability-zone-name:
type: string
- description: Indication of operational status of the logical link.
- link-role:
+ description: Name of the availability zone. Unique across a cloud region
+ hypervisor-type:
type: string
- description: Indication of the network use of the logical link.
- link-name2:
+ description: Type of hypervisor. Source of truth should define valid values.
+ operational-state:
type: string
- description: Alias or alternate name (CLCI or D1 name).
- link-id:
+ description: State that indicates whether the availability zone should be used, etc. Source of truth should define valid values.
+ resource-version:
type: string
- description: UUID of the logical-link, SDNC generates this.
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- logical-links:
+ $ref: "#/getDefinitions/relationship"
+ availability-zones:
description: |
- Collection of logical connections
+ Collection of availability zones
properties:
- logical-link:
+ availability-zone:
type: array
items:
- $ref: "#/definitions/logical-link"
+ $ref: "#/getDefinitions/availability-zone"
+ az-and-dvs-switches:
+ properties:
+ dvs-switches:
+ type: object
+ $ref: "#/getDefinitions/dvs-switches"
+ availability-zone:
+ type: object
+ $ref: "#/getDefinitions/availability-zone"
+ business:
+ description: |
+ Namespace for business related constructs
+ properties:
+ connectors:
+ type: array
+ items:
+ $ref: "#/getDefinitions/connector"
+ customers:
+ type: array
+ items:
+ $ref: "#/getDefinitions/customer"
class-of-service:
description: |
###### Related Nodes
- - FROM site-pair (is composed of class-of-service)
+ - TO site-pair( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)
required:
- cos
properties:
@@ -35957,7 +52687,7 @@ definitions:
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
+ $ref: "#/getDefinitions/relationship"
classes-of-service:
description: |
class-of-service of probe
@@ -35965,234 +52695,462 @@ definitions:
class-of-service:
type: array
items:
- $ref: "#/definitions/class-of-service"
- site-pair:
+ $ref: "#/getDefinitions/class-of-service"
+ cloud-infrastructure:
description: |
+ Namespace for cloud infrastructure.
+ properties:
+ complexes:
+ type: array
+ items:
+ $ref: "#/getDefinitions/complex"
+ cloud-regions:
+ type: array
+ items:
+ $ref: "#/getDefinitions/cloud-region"
+ network-profiles:
+ type: array
+ items:
+ $ref: "#/getDefinitions/network-profile"
+ pservers:
+ type: array
+ items:
+ $ref: "#/getDefinitions/pserver"
+ virtual-data-centers:
+ type: array
+ items:
+ $ref: "#/getDefinitions/virtual-data-center"
+ cloud-region:
+ description: |
+ cloud-region designates an installation of a cloud cluster or region or instantiation.
###### Related Nodes
- - TO class-of-service (comprises site-pair, Many2Many)
- - FROM routing-instance (is composed of site-pair)
+ - TO complex( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO l3-network( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM dvs-switch( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM flavor( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM group-assignment( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM image( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM snapshot( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM volume-group( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)
+ - CLOUD-REGION cannot be deleted if linked to DVS-SWITCH,FLAVOR,GROUP-ASSIGNMENT,IMAGE,OAM-NETWORK,SNAPSHOT,TENANT,VOLUME-GROUP
+ - CLOUD-REGION is DELETED when these are DELETED AVAILABILITY-ZONE
required:
- - site-pair-id
+ - cloud-owner
+ - cloud-region-id
properties:
- site-pair-id:
+ cloud-owner:
type: string
- description: unique identifier of probe
- source-ip:
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ cloud-region-id:
type: string
- description: Prefix address
- destination-ip:
+ description: Identifier used by the vendor for the region. Second part of composite key
+ cloud-type:
type: string
- description: Prefix address
- ip-version:
+ description: Type of the cloud (e.g., openstack)
+ owner-defined-type:
type: string
- description: ip version, v4, v6
- destination-hostname:
+ description: Cloud-owner defined type indicator (e.g., DCP, LCP)
+ cloud-region-version:
type: string
- description: Hostname of the destination equipment to which SLAs are measured against.
- destination-equip-type:
+ description: Software version employed at the site
+ identity-url:
type: string
- description: The type of destinatination equipment. Could be Router, etc.
+ description: URL of the keystone identity service
+ cloud-zone:
+ type: string
+ description: Zone where the cloud is homed
+ complex-name:
+ type: string
+ description: complex name for cloud-region instance
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- classes-of-service:
+ volume-groups:
type: array
items:
- $ref: "#/definitions/class-of-service"
+ $ref: "#/getDefinitions/volume-group"
+ tenants:
+ type: array
+ items:
+ $ref: "#/getDefinitions/tenant"
+ flavors:
+ type: array
+ items:
+ $ref: "#/getDefinitions/flavor"
+ group-assignments:
+ type: array
+ items:
+ $ref: "#/getDefinitions/group-assignment"
+ snapshots:
+ type: array
+ items:
+ $ref: "#/getDefinitions/snapshot"
+ images:
+ type: array
+ items:
+ $ref: "#/getDefinitions/image"
+ dvs-switches:
+ type: array
+ items:
+ $ref: "#/getDefinitions/dvs-switch"
+ oam-networks:
+ type: array
+ items:
+ $ref: "#/getDefinitions/oam-network"
+ availability-zones:
+ type: array
+ items:
+ $ref: "#/getDefinitions/availability-zone"
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- site-pairs:
- description: |
- probe within a set
+ $ref: "#/getDefinitions/relationship"
+ cloud-regions:
properties:
- site-pair:
+ cloud-region:
type: array
items:
- $ref: "#/definitions/site-pair"
- routing-instance:
+ $ref: "#/getDefinitions/cloud-region"
+ complex:
description: |
+ Collection of physical locations that can house cloud-regions.
###### Related Nodes
- - TO site-pair (comprises routing-instance, Many2Many)
- - FROM site-pair-set (is composed of routing-instance)
+ - TO l3-network( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM ctag-pool( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)
+ - FROM pnf( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM vce( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)
+ - FROM volume-group( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM vpls-pe( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - COMPLEX cannot be deleted if linked to AVAILABILITY-ZONE,CLOUD-REGION,OAM-NETWORK,PNF,PSERVER,VCE,VOLUME-GROUP,VPLS-PE
+ - COMPLEX is DELETED when these are DELETED CTAG-POOL
required:
- - routing-instance-id
+ - physical-location-id
+ - physical-location-type
+ - street1
+ - city
+ - postal-code
+ - country
+ - region
properties:
- routing-instance-id:
+ physical-location-id:
type: string
- description: Unique id of routing instance
- rpm-owner:
+ description: Unique identifier for physical location, e.g., CLLI
+ data-center-code:
type: string
- description: rpm owner
+ description: Data center code which can be an alternate way to identify a complex
+ complex-name:
+ type: string
+ description: Gamma complex name for LCP instance.
+ identity-url:
+ type: string
+ description: URL of the keystone identity service
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- site-pairs:
+ physical-location-type:
+ type: string
+ description: Type, e.g., central office, data center.
+ street1:
+ type: string
+ street2:
+ type: string
+ city:
+ type: string
+ state:
+ type: string
+ postal-code:
+ type: string
+ country:
+ type: string
+ region:
+ type: string
+ latitude:
+ type: string
+ longitude:
+ type: string
+ elevation:
+ type: string
+ lata:
+ type: string
+ ctag-pools:
type: array
items:
- $ref: "#/definitions/site-pair"
+ $ref: "#/getDefinitions/ctag-pool"
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- routing-instances:
+ $ref: "#/getDefinitions/relationship"
+ complexes:
description: |
- set of probes related to generic-vnf routing instance
+ Collection of physical locations that can house cloud-regions.
properties:
- routing-instance:
+ complex:
type: array
items:
- $ref: "#/definitions/routing-instance"
- site-pair-set:
+ $ref: "#/getDefinitions/complex"
+ configuration:
description: |
- Set of instances for probes used to measure service level agreements
+ Port Mirror Configuration.
###### Related Nodes
- - TO routing-instance (comprises site-pair-set, Many2Many)
- - FROM generic-vnf
+ - TO allotted-resource( configuration org.onap.relationships.inventory.Uses allotted-resource, ONE2ONE)
+ - TO logical-link( configuration org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo configuration, MANY2ONE)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses configuration, ONE2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses configuration, ONE2MANY)
+ - CONFIGURATION is DELETED when these are DELETED METADATUM
+ - CONFIGURATION deletion means associated objects of these types are also DELETED:ALLOTTED-RESOURCE,LOGICAL-LINK
required:
- - site-pair-set-id
+ - configuration-id
+ - configuration-type
+ - configuration-sub-type
+ - orchestration-status
+ - operational-status
+ - configuration-selflink
+ - model-customization-id
properties:
- site-pair-set-id:
+ configuration-id:
type: string
- description: Unique id of site pair set.
+ description: UUID assigned to configuration.
+ management-option:
+ type: string
+ description: Indicates the entity that will manage this feature. Could be an organization or the name of the application as well.
+ configuration-name:
+ type: string
+ description: Name of the configuration.
+ configuration-type:
+ type: string
+ description: port-mirroring-configuration.
+ configuration-sub-type:
+ type: string
+ description: vprobe, pprobe.
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ orchestration-status:
+ type: string
+ description: Orchestration status of the configuration.
+ operational-status:
+ type: string
+ description: Indicator for whether the resource is considered operational.
+ configuration-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details from SDN-GC.
+ model-customization-id:
+ type: string
+ description: id of the configuration used to customize the resource
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- routing-instances:
+ relationship-list:
type: array
items:
- $ref: "#/definitions/routing-instance"
- relationship-list:
+ $ref: "#/getDefinitions/relationship"
+ metadata:
type: array
items:
- $ref: "#/definitions/relationship"
- site-pair-sets:
+ $ref: "#/getDefinitions/metadatum"
+ configurations:
description: |
- Collection of sets of instances for probes related to generic-vnf
+ Collection of configurations
properties:
- site-pair-set:
+ configuration:
type: array
items:
- $ref: "#/definitions/site-pair-set"
- vpn-binding:
+ $ref: "#/getDefinitions/configuration"
+ connector:
description: |
- VPN binding
+ Collection of resource instances used to connect a variety of disparate inventory widgets
###### Related Nodes
- - FROM l3-network
+ - TO virtual-data-center( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)
+ - CONNECTOR is DELETED when these are DELETED METADATUM
required:
- - vpn-id
- - vpn-name
- - global-route-target
+ - resource-instance-id
properties:
- vpn-id:
+ resource-instance-id:
type: string
- description: VPN ID, globally unique within A&AI
- vpn-name:
+ description: Unique id of resource instance.
+ resource-version:
type: string
- description: VPN Name
- global-route-target:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ persona-model-id:
type: string
- description: Number used to identify a VPN, globally unique in the network
- vpn-platform:
+ description: the ASDC model id for this resource or service model.
+ persona-model-version:
type: string
- description: the platform associated with the VPN example AVPN, Mobility
- resource-version:
+ description: the ASDC model version for this resource or service model.
+ model-version-id:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ description: the ASDC model version for this resource or service model.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- description: l3-networks relate to vpn-bindings
- vpn-bindings:
+ $ref: "#/getDefinitions/relationship"
+ metadata:
+ type: array
+ items:
+ $ref: "#/getDefinitions/metadatum"
+ connectors:
+ description: |
+ Collection of resource instances used to connect a variety of disparate inventory widgets
properties:
- vpn-binding:
+ connector:
type: array
items:
- $ref: "#/definitions/vpn-binding"
- vpls-pe:
+ $ref: "#/getDefinitions/connector"
+ constrained-element-set:
description: |
- VPLS Provider Edge routers.
+ This is how we would capture constraints defining allowed sets of elements.
###### Related Nodes
- - TO complex (Many2Many)
- - TO ctag-pool (Many2Many)
- - TO p-interface (comprises vpls-pe, Many2Many)
- - TO lag-interface (comprises vpls-pe, Many2Many)
+ - TO model-constraint( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)
+ - TO model-element( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM element-choice-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)
+ - CONSTRAINED-ELEMENT-SET is DELETED when these are DELETED ELEMENT-CHOICE-SET
required:
- - equipment-name
+ - constrained-element-set-uuid
+ - constraint-type
+ - check-type
properties:
- equipment-name:
+ constrained-element-set-uuid:
type: string
- prov-status:
+ constraint-type:
type: string
- description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
- ipv4-oam-address:
+ check-type:
type: string
- description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address).
- equipment-role:
+ resource-version:
type: string
- description: Client should send valid enumerated value, e.g., VPLS-PE.
- vlan-id-outer:
+ element-choice-sets:
+ type: array
+ items:
+ $ref: "#/getDefinitions/element-choice-set"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ constrained-element-sets:
+ properties:
+ constrained-element-set:
+ type: array
+ items:
+ $ref: "#/getDefinitions/constrained-element-set"
+ ctag-assignment:
+ description: |
+ ###### Related Nodes
+ - TO l3-network( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ required:
+ - vlan-id-inner
+ properties:
+ vlan-id-inner:
type: integer
format: int64
- description: Temporary location for stag to get to VCE
+ description: id.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- p-interfaces:
+ $ref: "#/getDefinitions/relationship"
+ ctag-assignments:
+ properties:
+ ctag-assignment:
type: array
- items:
- $ref: "#/definitions/p-interface"
- lag-interfaces:
+ items:
+ $ref: "#/getDefinitions/ctag-assignment"
+ ctag-pool:
+ description: |
+ A collection of C tags (vlan tags) grouped for a specific purpose.
+ ###### Related Nodes
+ - TO complex( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)
+ - TO availability-zone( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM vpls-pe( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)
+ required:
+ - target-pe
+ - availability-zone-name
+ - ctag-pool-purpose
+ properties:
+ target-pe:
+ type: string
+ description: The Target provider edge router
+ availability-zone-name:
+ type: string
+ description: Name of the availability zone
+ ctag-pool-purpose:
+ type: string
+ description: Describes what the intended purpose of this pool is.
+ ctag-values:
+ type: string
+ description: Comma separated list of ctags
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/lag-interface"
- vpls-pes:
- description: |
- Collection of VPLS Provider Edge routers
+ $ref: "#/getDefinitions/relationship"
+ ctag-pools:
properties:
- vpls-pe:
+ ctag-pool:
type: array
items:
- $ref: "#/definitions/vpls-pe"
- multicast-configuration:
+ $ref: "#/getDefinitions/ctag-pool"
+ customer:
description: |
+ customer identifiers to provide linkage back to BSS information.
###### Related Nodes
- - FROM vlan
+ - FROM service-subscription( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)
+ - CUSTOMER is DELETED when these are DELETED SERVICE-SUBSCRIPTION
required:
- - multicast-configuration-id
- - multicast-protocol
- - rp-type
+ - global-customer-id
+ - subscriber-name
+ - subscriber-type
properties:
- multicast-configuration-id:
+ global-customer-id:
type: string
- description: Unique id of multicast configuration.
- multicast-protocol:
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ subscriber-name:
type: string
- description: protocol of multicast configuration
- rp-type:
+ description: Subscriber name, an alternate way to retrieve a customer.
+ subscriber-type:
type: string
- description: rp type of multicast configuration
+ description: Subscriber type, a way to provide VID with only the INFRA customers.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ service-subscriptions:
+ type: array
+ items:
+ $ref: "#/getDefinitions/service-subscription"
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- multicast-configurations:
+ $ref: "#/getDefinitions/relationship"
+ customers:
description: |
- multicast configuration of generic-vnf ip-address
+ Collection of customer identifiers to provide linkage back to BSS information.
properties:
- multicast-configuration:
+ customer:
type: array
items:
- $ref: "#/definitions/multicast-configuration"
+ $ref: "#/getDefinitions/customer"
cvlan-tag-entry:
required:
- cvlan-tag
@@ -36207,83 +53165,614 @@ definitions:
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
+ $ref: "#/getDefinitions/relationship"
cvlan-tags:
properties:
cvlan-tag-entry:
type: array
items:
- $ref: "#/definitions/cvlan-tag-entry"
- port-group:
+ $ref: "#/getDefinitions/cvlan-tag-entry"
+ dvs-switch:
description: |
- Used to capture the network interfaces of this VCE
+ Digital virtual switch metadata, used by SDN-C to configure VCEs. A&AI needs to receive this data from the PO deployment team and administer it using the provisioningTool.sh into A&AI.
###### Related Nodes
- - TO cvlan-tag (comprises port-group, Many2Many)
- - FROM vce (is composed of port-group)
+ - TO cloud-region( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO availability-zone( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
required:
- - interface-id
- - orchestration-status
+ - switch-name
+ - vcenter-url
properties:
- interface-id:
+ switch-name:
type: string
- description: Unique ID of the interface
- neutron-network-id:
+ description: DVS switch name
+ vcenter-url:
type: string
- description: Neutron network id of this Interface
- neutron-network-name:
+ description: URL used to reach the vcenter
+ resource-version:
type: string
- description: Neutron network name of this Interface
- interface-role:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ dvs-switches:
+ description: |
+ Collection of digital virtual switch metadata used for vmWare VCEs and GenericVnfs.
+ properties:
+ dvs-switch:
+ type: array
+ items:
+ $ref: "#/getDefinitions/dvs-switch"
+ edge-prop-names:
+ description: |
+ Internal map to define the properties of an edge and interpret the map EdgeRules
+ properties:
+ edgeLabel:
+ type: string
+ direction:
+ type: string
+ multiplicityRule:
+ type: string
+ isParent:
+ type: boolean
+ usesResource:
+ type: boolean
+ hasDelTarget:
+ type: boolean
+ SVC-INFRA:
+ type: boolean
+ SVC-INFRA-REV:
+ type: boolean
+ edge-tag-query-request:
+ properties:
+ edge-tag:
+ type: string
+ result-detail:
+ type: string
+ start-node-type:
+ type: string
+ start-node-filter:
+ type: array
+ items:
+ $ref: "#/getDefinitions/start-node-filter"
+ include-node-filter:
+ type: array
+ items:
+ $ref: "#/getDefinitions/include-node-filter"
+ secondary-filter:
+ type: array
+ items:
+ $ref: "#/getDefinitions/secondary-filter"
+ edge-tag-query-result:
+ properties:
+ tagged-inventory-item-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/tagged-inventory-item-list"
+ element-choice-set:
+ description: |
+ This is how we would capture constraints defining allowed sets of elements.
+ ###### Related Nodes
+ - TO constrained-element-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)
+ - ELEMENT-CHOICE-SET is DELETED when these are DELETED MODEL-ELEMENT
+ required:
+ - element-choice-set-uuid
+ - element-choice-set-name
+ properties:
+ element-choice-set-uuid:
+ type: string
+ element-choice-set-name:
+ type: string
+ cardinality:
type: string
- description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
+ resource-version:
+ type: string
+ model-elements:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model-element"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ element-choice-sets:
+ properties:
+ element-choice-set:
+ type: array
+ items:
+ $ref: "#/getDefinitions/element-choice-set"
+ entitlement:
+ description: |
+ Metadata for entitlement group.
+ ###### Related Nodes
+ - TO generic-vnf( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vce( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ required:
+ - group-uuid
+ - resource-uuid
+ properties:
+ group-uuid:
+ type: string
+ description: Unique ID for the entitlement group the resource comes from, should be uuid.
+ resource-uuid:
+ type: string
+ description: Unique ID of an entitlement resource.
+ resource-version:
+ type: string
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ entitlements:
+ description: |
+ Entitlements, keyed by group-uuid and resource-uuid, related to license management
+ properties:
+ entitlement:
+ type: array
+ items:
+ $ref: "#/getDefinitions/entitlement"
+ esr-ems:
+ description: |
+ Persist EMS address information used by EMS driver.
+ ###### Related Nodes
+ - TO esr-system-info (CHILD of esr-ems, esr-ems has esr-system-info, One2Many)
+ - ESR-EMS deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
+ required:
+ - ems-id
+ properties:
+ ems-id:
+ type: string
+ description: Unique ID of EMS.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- port-group-id:
+ esr-system-info-list:
+ type: object
+ $ref: "#/getDefinitions/esr-system-info-list"
+ relationship-list:
+ type: object
+ $ref: "#/getDefinitions/relationship-list"
+ esr-ems-list:
+ properties:
+ esr-ems:
+ type: array
+ items:
+ $ref: "#/getDefinitions/esr-ems"
+ esr-system-info:
+ description: |
+ Persist common address information of external systems.
+ ###### Related Nodes
+ - FROM esr-ems (PARENT of esr-system-info, esr-ems has esr-system-info)
+ - FROM esr-vnfm (PARENT of esr-system-info, esr-vnfm has esr-system-info)
+ - FROM esr-thirdparty-sdnc (PARENT of esr-system-info, esr-thirdparty-sdnc has esr-system-info)
+ - FROM cloud-region (PARENT of esr-system-info, cloud-region has esr-system-info)
+ required:
+ - esr-system-info-id
+ - user-name
+ - password
+ - system-type
+ properties:
+ esr-system-info-id:
type: string
- description: Unique ID for port group in vmware
- port-group-name:
+ description: Unique ID of esr system info.
+ system-name:
type: string
- description: Likely to duplicate value of neutron network name
- switch-name:
+ description: name of external system.
+ type:
type: string
- description: DVS or standard switch name (should be non-null for port groups associated with DVS)
- orchestration-status:
+ description: type of external systems.
+ vendor:
type: string
- description: Orchestration status of this VNF, mastered by MSO
- heat-stack-id:
+ description: vendor of external systems.
+ version:
type: string
- description: Heat stack id corresponding to this instance, managed by MSO
- mso-catalog-key:
+ description: version of external systems.
+ service-url:
type: string
- description: Corresponds to the SDN-C catalog id used to configure this VCE
- cvlan-tags:
+ description: url used to access external systems.
+ user-name:
+ type: string
+ description: username used to access external systems.
+ password:
+ type: string
+ description: password used to access external systems.
+ system-type:
+ type: string
+ description: it could be vim/vnfm/thirdparty-sdnc/ems-resource/ems-performance/ems-alarm.
+ protocol:
+ type: string
+ description: protocol of third party SDNC, for example netconf/snmp.
+ ssl-cacert:
+ type: string
+ description: ca file content if enabled ssl on auth-url.
+ ssl-insecure:
+ type: boolean
+ description: Whether to verify VIM's certificate.
+ ip-address:
+ type: string
+ description: service IP of ftp server.
+ port:
+ type: string
+ description: service port of ftp server.
+ cloud-domain:
+ type: string
+ description: domain info for authentication.
+ default-tenant:
+ type: string
+ description: default tenant of VIM.
+ passive:
+ type: boolean
+ description: ftp passive mode or not.
+ remote-path:
+ type: string
+ description: resource or performance data file path.
+ system-status:
+ type: string
+ description: the status of external system.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/cvlan-tag-entry"
+ $ref: "#/getDefinitions/relationship"
+ esr-system-info-list:
+ description: |
+ Collection of persistent block-level external system auth info.
+ properties:
+ esr-system-info:
+ type: array
+ items:
+ $ref: "#/getDefinitions/esr-system-info"
+ esr-thirdparty-sdnc:
+ description: |
+ Persist SDNC address information used by ONAP SDNC.
+ ###### Related Nodes
+ - TO esr-system-info (CHILD of esr-thirdparty-sdnc, esr-thirdparty-sdnc has esr-system-info, One2One)
+ - TO pnf( esr-thirdparty-sdnc has pnf, One2Many)
+ - ESR-THIRDPARTY-SDNC deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
+ required:
+ - thirdparty-sdnc-id
+ properties:
+ thirdparty-sdnc-id:
+ type: string
+ description: Unique ID of SDNC.
+ location:
+ type: string
+ description: used for DC type to indicate the location of SDNC, such as Core or Edge.
+ product-name:
+ type: string
+ description: password used to access SDNC server.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ esr-system-info-list:
+ type: object
+ $ref: "#/getDefinitions/esr-system-info-list"
+ relationship-list:
+ type: object
+ $ref: "#/getDefinitions/relationship-list"
+ esr-thirdparty-sdnc-list:
+ properties:
+ esr-thirdparty-sdnc:
+ type: array
+ items:
+ $ref: "#/getDefinitions/esr-thirdparty-sdnc"
+ esr-vnfm:
+ description: |
+ Persist VNFM address information used by VF-C.
+ ###### Related Nodes
+ - TO esr-system-info (CHILD of esr-vnfm, esr-vnfm has esr-system-info, One2One)
+ - ESR-VNFM deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
+ required:
+ - vnfm-id
+ properties:
+ vnfm-id:
+ type: string
+ description: Unique ID of VNFM.
+ vim-id:
+ type: string
+ description: indecate the VIM to deploy VNF.
+ certificate-url:
+ type: string
+ description: certificate url of VNFM.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ esr-system-info-list:
+ type: object
+ $ref: "#/getDefinitions/esr-system-info-list"
+ relationship-list:
+ type: object
+ $ref: "#/getDefinitions/relationship-list"
+ esr-vnfm-list:
+ properties:
+ esr-vnfm:
+ type: array
+ items:
+ $ref: "#/getDefinitions/esr-vnfm"
+ evc:
+ description: |
+ evc object is an optional child object of the Configuration object.
+ ###### Related Nodes
+ - TO configuration( evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)
+ required:
+ - evc-id
+ properties:
+ evc-id:
+ type: string
+ description: Unique/key field for the evc object
+ forwarding-path-topology:
+ type: string
+ description: Point-to-Point, Multi-Point
+ cir-value:
+ type: string
+ description: Commited Information Rate
+ cir-units:
+ type: string
+ description: CIR units
+ connection-diversity-group-id:
+ type: string
+ description: Diversity Group ID
+ service-hours:
+ type: string
+ description: formerly Performance Group
+ esp-evc-circuit-id:
+ type: string
+ description: EVC Circuit ID of ESP EVC
+ esp-evc-cir-value:
+ type: string
+ description: Committed Information Rate (For ESP)
+ esp-evc-cir-units:
+ type: string
+ description: CIR units (For ESP)
+ esp-itu-code:
+ type: string
+ description: Identifies ESP
+ collector-pop-clli:
+ type: string
+ description: Collector POP CLLI (from the hostname of the access pnf)
+ inter-connect-type-ingress:
+ type: string
+ description: Interconnect type on ingress side of EVC.
+ tagmode-access-ingress:
+ type: string
+ description: tagode for collector side of EVC
+ tagmode-access-egress:
+ type: string
+ description: tagMode for network side of EVC
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- port-groups:
+ $ref: "#/getDefinitions/relationship"
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ evcs:
properties:
- port-group:
+ evc:
type: array
items:
- $ref: "#/definitions/port-group"
- vce:
+ $ref: "#/getDefinitions/evc"
+ external-system:
description: |
- Virtual Customer Edge Router, used specifically for Gamma. This object is deprecated.
+ Namespace for external system.
+ properties:
+ esr-ems-list:
+ type: object
+ $ref: "#/getDefinitions/esr-ems-list"
+ esr-vnfm-list:
+ type: object
+ $ref: "#/getDefinitions/esr-vnfm-list"
+ esr-thirdparty-sdnc-list:
+ type: object
+ $ref: "#/getDefinitions/esr-thirdparty-sdnc-list"
+ extra-properties:
+ description: |
+ Extra properties for inventory item for response list
+ extra-property:
+ properties:
+ property-name:
+ type: string
+ flavor:
+ description: |
+ Openstack flavor.
+ ###### Related Nodes
+ - TO cloud-region( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)
+ - FLAVOR cannot be deleted if linked to VSERVER
+ required:
+ - flavor-id
+ - flavor-name
+ - flavor-selflink
+ properties:
+ flavor-id:
+ type: string
+ description: Flavor id, expected to be unique across cloud-region.
+ flavor-name:
+ type: string
+ description: Flavor name
+ flavor-vcpus:
+ type: integer
+ format: int32
+ description: Number of CPUs
+ flavor-ram:
+ type: integer
+ format: int32
+ description: Amount of memory
+ flavor-disk:
+ type: integer
+ format: int32
+ description: Disk space
+ flavor-ephemeral:
+ type: integer
+ format: int32
+ description: Amount of ephemeral disk space
+ flavor-swap:
+ type: string
+ description: amount of swap space allocation
+ flavor-is-public:
+ type: boolean
+ description: whether flavor is available to all users or private to the tenant it was created in.
+ flavor-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ flavor-disabled:
+ type: boolean
+ description: Boolean as to whether this flavor is no longer enabled
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ flavors:
+ description: |
+ Collection of openstack flavors.
+ properties:
+ flavor:
+ type: array
+ items:
+ $ref: "#/getDefinitions/flavor"
+ forwarder:
+ description: |
+ Entity describing a sequenced segment of forwarding path
+ ###### Related Nodes
+ - TO forwarding-path( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)
+ - TO l-interface( forwarder org.onap.relationships.inventory.ForwardsTo l-interface, MANY2ONE)
+ - TO configuration( forwarder org.onap.relationships.inventory.Uses configuration, ONE2ONE)
+ - TO lag-interface( forwarder org.onap.relationships.inventory.ForwardsTo lag-interface, MANY2ONE)
+ - TO p-interface( forwarder org.onap.relationships.inventory.ForwardsTo p-interface, MANY2ONE)
+ - FORWARDER deletion means associated objects of these types are also DELETED:CONFIGURATION
+ required:
+ - sequence
+ properties:
+ sequence:
+ type: integer
+ format: int32
+ description: Unique ID of this segmentation
+ forwarder-role:
+ type: string
+ description: ingress, intermediate, egress
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ forwarder-evc:
+ description: |
+ forwarder object is an optional child object of the Configuration object.
+ ###### Related Nodes
+ - TO configuration( forwarder-evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)
+ required:
+ - forwarder-evc-id
+ properties:
+ forwarder-evc-id:
+ type: string
+ description: Key for forwarder-evc object
+ circuit-id:
+ type: string
+ description: Circuit ID from customer/ESP/ingress end of EVC, or reference to beater circuit on gateway/network/egress end of EVC
+ ivlan:
+ type: string
+ description: Internal VLAN.
+ svlan:
+ type: string
+ description: SVLAN value for ingress of egress forwarder.
+ cvlan:
+ type: string
+ description: CVLAN value for ingress of egress forwarder.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ forwarder-evcs:
+ properties:
+ forwarder-evc:
+ type: array
+ items:
+ $ref: "#/getDefinitions/forwarder-evc"
+ forwarders:
+ properties:
+ forwarder:
+ type: array
+ items:
+ $ref: "#/getDefinitions/forwarder"
+ forwarding-path:
+ description: |
+ Entity that describes the sequenced forwarding path between interfaces of services or resources
###### Related Nodes
- - TO availability-zone (Many2Many)
- - TO complex (Many2Many)
- - TO port-group (comprises vce, Many2Many)
- - TO vserver (Many2Many)
- - TO service-instance (Many2Many)
+ - TO service-instance( forwarding-path org.onap.relationships.inventory.AppliesTo service-instance, MANY2ONE)
+ - TO configuration( forwarding-path org.onap.relationships.inventory.Uses configuration, ONE2ONE)
+ - FROM forwarder( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)
+ - FORWARDING-PATH is DELETED when these are DELETED FORWARDER
+ - FORWARDING-PATH deletion means associated objects of these types are also DELETED:CONFIGURATION
+ required:
+ - forwarding-path-id
+ - forwarding-path-name
+ properties:
+ forwarding-path-id:
+ type: string
+ description: Unique ID of this FP
+ forwarding-path-name:
+ type: string
+ description: Name of the FP
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ selflink:
+ type: string
+ description: the self link for this FP
+ forwarders:
+ type: array
+ items:
+ $ref: "#/getDefinitions/forwarder"
+ forwarding-paths:
+ properties:
+ forwarding-path:
+ type: array
+ items:
+ $ref: "#/getDefinitions/forwarding-path"
+ generic-vnf:
+ description: |
+ General purpose VNF
+ ###### Related Nodes
+ - TO availability-zone( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - TO ipsec-configuration( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)
+ - TO l3-network( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO license-key-resource( generic-vnf org.onap.relationships.inventory.Uses license-key-resource, MANY2MANY)
+ - TO pserver( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)
+ - TO vnf-image( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)
+ - TO volume-group( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - TO vserver( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)
+ - TO virtual-data-center( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM lag-interface( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM network-profile( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)
+ - FROM site-pair-set( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)
+ - GENERIC-VNF is DELETED when these are DELETED VNFC,LAG-INTERFACE,L-INTERFACE,VF-MODULE
required:
- vnf-id
- vnf-name
- vnf-type
+ - in-maint
+ - is-closed-loop-disabled
properties:
vnf-id:
type: string
@@ -36299,7 +53788,7 @@ definitions:
description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded and clients should expect changes to occur in the future to this field as ASDC matures.
service-id:
type: string
- description: Unique identifier of service from ASDC. Expect this to change as ASDC matures.
+ description: Unique identifier of service from ASDC
regional-resource-zone:
type: string
description: Regional way of organizing pservers, source of truth should define values
@@ -36314,236 +53803,637 @@ definitions:
description: License key
equipment-role:
type: string
- description: Network role being played by this VNF
+ description: Client should send valid enumerated value
orchestration-status:
type: string
- description: Orchestration status of this VNF, mastered by MSO
+ description: Orchestration status of this VNF, used by MSO.
heat-stack-id:
type: string
description: Heat stack id corresponding to this instance, managed by MSO
mso-catalog-key:
type: string
description: Corresponds to the SDN-C catalog id used to configure this VCE
- vpe-id:
- type: string
- description: Unique ID of VPE connected to this VCE.
- v6-vce-wan-address:
+ management-option:
type: string
- description: Valid v6 IP address for the WAN Link on this router. Implied length of /64.
+ description: identifier of managed by company or customer
ipv4-oam-address:
type: string
- description: Address tail-f uses to configure vce, also used for troubleshooting and is IP used for traps generated by VCE.
+ description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by generic-vnf.
+ ipv4-loopback0-address:
+ type: string
+ description: v4 Loopback0 address
+ nm-lan-v6-address:
+ type: string
+ description: v6 Loopback address
+ management-v6-address:
+ type: string
+ description: v6 management address
+ vcpu:
+ type: integer
+ format: int64
+ description: number of vcpus ordered for this instance of VNF, used for VNFs with no vservers/flavors
+ vcpu-units:
+ type: string
+ description: units associated with vcpu, used for VNFs with no vservers/flavors
+ vmemory:
+ type: integer
+ format: int64
+ description: number of GB of memory ordered for this instance of VNF, used for VNFs with no vservers/flavors
+ vmemory-units:
+ type: string
+ description: units associated with vmemory, used for VNFs with no vservers/flavors
+ vdisk:
+ type: integer
+ format: int64
+ description: number of vdisks ordered for this instance of VNF, used for VNFs with no vservers/flavors
+ vdisk-units:
+ type: string
+ description: units associated with vdisk, used for VNFs with no vservers/flavors
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- ipv4-loopback0-address:
+ summary-status:
type: string
- description: Loopback0 address
- entitlement-resource-uuid:
+ description: details regarding the generic-vnf operation
+ encrypted-access-flag:
+ type: boolean
+ description: indicates whether generic-vnf access uses SSH
+ persona-model-id:
type: string
- description: Entitlement resource uuid
- port-groups:
+ description: the ASDC model id for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ as-number:
+ type: string
+ description: as-number of the VNF
+ regional-resource-subzone:
+ type: string
+ description: represents sub zone of the rr plane
+ relationship-list:
type: array
items:
- $ref: "#/definitions/port-group"
+ $ref: "#/getDefinitions/relationship"
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l-interface"
+ lag-interfaces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/lag-interface"
+ vf-modules:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vf-module"
+ generic-vnfs:
+ description: |
+ Collection of VNFs
+ properties:
+ generic-vnf:
+ type: array
+ items:
+ $ref: "#/getDefinitions/generic-vnf"
+ group-assignment:
+ description: |
+ Openstack group-assignment used to store exclusivity groups (EG).
+ ###### Related Nodes
+ - TO cloud-region( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)
+ required:
+ - group-id
+ - group-type
+ - group-name
+ properties:
+ group-id:
+ type: string
+ description: Group id, expected to be unique across cloud-region.
+ group-type:
+ type: string
+ description: Group type - the type of group this instance refers to
+ group-name:
+ type: string
+ description: Group name - name assigned to the group
+ group-description:
+ type: string
+ description: Group description - description of the group
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- vces:
+ $ref: "#/getDefinitions/relationship"
+ group-assignments:
description: |
- Collection of Virtual Customer Edge Routers, used specifically for Gamma. This object is deprecated.
+ Collection of openstack group assignments
properties:
- vce:
+ group-assignment:
type: array
items:
- $ref: "#/definitions/vce"
- vnfc:
+ $ref: "#/getDefinitions/group-assignment"
+ host-route:
description: |
- ###### Default Delete Scope
- THIS_NODE_ONLY
###### Related Nodes
- - FROM vserver
- - FROM vf-module
- - FROM generic-vnf
+ - TO subnet( host-route org.onap.relationships.inventory.BelongsTo subnet, MANY2ONE)
required:
- - vnfc-name
- - vnfc-function-code
- - vnfc-type
- - in-maint
- - is-closed-loop-disabled
+ - host-route-id
+ - route-prefix
+ - next-hop
properties:
- vnfc-name:
+ host-route-id:
type: string
- description: Unique ID of vnfc.
- vnfc-function-code:
+ description: host-route id
+ route-prefix:
type: string
- description: function code
- vnfc-type:
+ description: subnet prefix
+ next-hop:
type: string
- description: type
- prov-status:
+ description: Could be ip-address, hostname, or service-instance
+ next-hop-type:
type: string
- description: prov status of this vnfc
- orchestration-status:
+ description: Should be ip-address, hostname, or service-instance to match next-hop
+ resource-version:
type: string
- description: Orchestration status of this VNF, mastered by APP-C
- ipaddress-v4-oam-vip:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ host-routes:
+ properties:
+ host-route:
+ type: array
+ items:
+ $ref: "#/getDefinitions/host-route"
+ image:
+ description: |
+ Openstack image.
+ ###### Related Nodes
+ - TO cloud-region( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)
+ - IMAGE cannot be deleted if linked to VSERVER
+ - IMAGE is DELETED when these are DELETED METADATUM
+ required:
+ - image-id
+ - image-name
+ - image-os-distro
+ - image-os-version
+ - image-selflink
+ properties:
+ image-id:
type: string
- description: Oam V4 vip address of this vnfc
- in-maint:
- type: boolean
- is-closed-loop-disabled:
- type: boolean
- group-notation:
+ description: Image id, expected to be unique across cloud region
+ image-name:
type: string
- description: Group notation of VNFC
+ description: Image name
+ image-architecture:
+ type: string
+ description: Operating system architecture.
+ image-os-distro:
+ type: string
+ description: The common name of the operating system distribution in lowercase
+ image-os-version:
+ type: string
+ description: The operating system version as specified by the distributor.
+ application:
+ type: string
+ description: The application that the image instantiates.
+ application-vendor:
+ type: string
+ description: The vendor of the application.
+ application-version:
+ type: string
+ description: The version of the application.
+ image-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- vnfcs:
+ $ref: "#/getDefinitions/relationship"
+ metadata:
+ type: array
+ items:
+ $ref: "#/getDefinitions/metadatum"
+ images:
description: |
- virtual network components associated with a vserver from application controller.
+ Collectio of Openstack images.
properties:
- vnfc:
+ image:
type: array
items:
- $ref: "#/definitions/vnfc"
- subnet:
+ $ref: "#/getDefinitions/image"
+ include-node-filter:
+ properties:
+ include-node-type:
+ type: string
+ instance-filter:
+ description: |
+ InstanceFilter for performing a named-query or model query
+ instance-filters:
+ description: |
+ InstanceFilters for performing a named-query or model query
+ properties:
+ instance-filter:
+ type: array
+ items:
+ $ref: "#/getDefinitions/instance-filter"
+ instance-group:
description: |
- ###### Default Delete Scope
- ERROR_IF_ANY_IN_EDGES
+ General mechanism for grouping instances
###### Related Nodes
- - FROM l3-interface-ipv4-address-list
- - FROM l3-interface-ipv6-address-list
- - FROM l3-network (is composed of subnet)
+ - TO model( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM pnf( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
required:
- - subnet-id
- - dhcp-enabled
+ - id
+ - description
+ - type
properties:
- subnet-id:
+ id:
type: string
- description: Subnet ID, should be UUID.
- subnet-name:
+ description: Instance Group ID, UUID assigned to this instance.
+ description:
type: string
- description: Name associated with the subnet.
- neutron-subnet-id:
+ description: Descriptive text to help identify the usage of this instance-group
+ type:
type: string
- description: Neutron id of this subnet
- gateway-address:
+ description: Only valid value today is lower case ha for high availability
+ sub-type:
type: string
- description: gateway ip address
- network-start-address:
+ description: Valid values for ha type are [geo-activeactive, geo-activestandby, local-activeactive, local-activestandby]
+ resource-version:
type: string
- description: network start address
- cidr-mask:
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ instance-groups:
+ description: |
+ Collection of openstack route table references
+ properties:
+ instance-group:
+ type: array
+ items:
+ $ref: "#/getDefinitions/instance-group"
+ inventory:
+ properties:
+ search:
+ type: object
+ $ref: "#/getDefinitions/search"
+ actions:
+ type: object
+ $ref: "#/getDefinitions/actions"
+ cloud-infrastructure:
+ type: object
+ $ref: "#/getDefinitions/cloud-infrastructure"
+ business:
+ type: object
+ $ref: "#/getDefinitions/business"
+ service-design-and-creation:
+ type: object
+ $ref: "#/getDefinitions/service-design-and-creation"
+ network:
+ type: object
+ $ref: "#/getDefinitions/network"
+ aai-internal:
+ type: object
+ $ref: "#/getDefinitions/aai-internal"
+ inventory-item:
+ properties:
+ inventory-item-type:
type: string
- description: cidr mask
- ip-version:
+ inventory-item-link:
type: string
- description: ip version
- orchestration-status:
+ inventory-item-data:
+ type: array
+ items:
+ $ref: "#/getDefinitions/inventory-item-data"
+ tagged-inventory-item-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/tagged-inventory-item-list"
+ inventory-item-data:
+ properties:
+ property-name:
type: string
- description: Orchestration status of this VNF, mastered by MSO
- dhcp-enabled:
- type: boolean
- dhcp-start:
+ property-value:
type: string
- description: the start address reserved for use by dhcp
- dhcp-end:
+ inventory-response-item:
+ description: |
+ Inventory item for response list
+ properties:
+ model-name:
type: string
- description: the last address reserved for use by dhcp
+ extra-properties:
+ type: object
+ $ref: "#/getDefinitions/extra-properties"
+ inventory-response-items:
+ type: object
+ $ref: "#/getDefinitions/inventory-response-items"
+ inventory-response-items:
+ description: |
+ Container for inventory items in response list
+ properties:
+ inventory-response-item:
+ type: array
+ items:
+ $ref: "#/getDefinitions/inventory-response-item"
+ ipsec-configuration:
+ description: |
+ IPSec configuration node will contain various configuration data for the NMTE VNF. This node will have an edge to the generic-vnf (vnf type = TE). Starting 1607, this data will be populated by SDN-C
+ ###### Related Nodes
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)
+ - FROM vig-server( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)
+ - IPSEC-CONFIGURATION is DELETED when these are DELETED VIG-SERVER
+ required:
+ - ipsec-configuration-id
+ properties:
+ ipsec-configuration-id:
+ type: string
+ description: UUID of this configuration
+ requested-vig-address-type:
+ type: string
+ description: Indicate the type of VIG server like AVPN, INTERNET, BOTH
+ requested-encryption-strength:
+ type: string
+ description: Encryption values like 3des-cbc, des-cbc, aes-128-cbc, aes-192-cbc, aes-265-cbc
+ requested-dmz-type:
+ type: string
+ description: can offer a shared DMZ or a DMZ specific to a customer
+ shared-dmz-network-address:
+ type: string
+ description: Network address of shared DMZ
+ requested-customer-name:
+ type: string
+ description: If the DMZ is a custom DMZ, this field will indicate the customer information
+ ike-version:
+ type: string
+ description: can be 1 or 2
+ ikev1-authentication:
+ type: string
+ description: Contains values like md5, sha1, sha256, sha384
+ ikev1-encryption:
+ type: string
+ description: Encyption values like 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
+ ikev1-dh-group:
+ type: string
+ description: Diffie-Hellman group like DH-GROUP2, DH-GROUP5, DH-GROUP14
+ ikev1-am-group-id:
+ type: string
+ description: Group name defined in VIG for clients using aggressive mode
+ ikev1-am-password:
+ type: string
+ description: pre-shared key for the above group name
+ ikev1-sa-lifetime:
+ type: string
+ description: Lifetime for IKEv1 SA
+ ipsec-authentication:
+ type: string
+ description: md5, sha1, sha256, sha384
+ ipsec-encryption:
+ type: string
+ description: 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
+ ipsec-sa-lifetime:
+ type: string
+ description: Life time for IPSec SA
+ ipsec-pfs:
+ type: string
+ description: enable PFS or not
+ xauth-userid:
+ type: string
+ description: user ID for xAuth, sm-user, ,nmteHostName
+ xauth-user-password:
+ type: string
+ description: Encrypted using the Juniper $9$ algorithm
+ dpd-interval:
+ type: string
+ description: The time between DPD probe
+ dpd-frequency:
+ type: string
+ description: Maximum number of DPD before claiming the tunnel is down
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- subnets:
+ $ref: "#/getDefinitions/relationship"
+ vig-servers:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vig-server"
+ ipsec-configurations:
properties:
- subnet:
+ ipsec-configuration:
type: array
items:
- $ref: "#/definitions/subnet"
- ctag-assignment:
+ $ref: "#/getDefinitions/ipsec-configuration"
+ key-data:
+ properties:
+ key-name:
+ type: string
+ key-value:
+ type: string
+ l-interface:
description: |
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Logical interfaces, e.g., a vnic.
###### Related Nodes
- - FROM l3-network (is composed of ctag-assignment)
+ - TO generic-vnf( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO lag-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)
+ - TO logical-link( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)
+ - TO newvce( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)
+ - TO p-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)
+ - TO vserver( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - FROM sriov-vf( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)
+ - FROM vlan( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)
+ - L-INTERFACE is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST,SRIOV-VF,VLAN
+ - L-INTERFACE deletion means associated objects of these types are also DELETED:LOGICAL-LINK
required:
- - vlan-id-inner
+ - interface-name
properties:
- vlan-id-inner:
- type: integer
- format: int64
- description: id.
+ interface-name:
+ type: string
+ description: Name given to the interface
+ interface-role:
+ type: string
+ description: E.g., CUSTOMER, UPLINK, etc.
+ v6-wan-link-ip:
+ type: string
+ description: Questionably placed - v6 ip addr of this interface (is in vr-lan-interface from Mary B.
+ selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ interface-id:
+ type: string
+ description: ID of interface
+ macaddr:
+ type: string
+ description: MAC address for the interface
+ network-name:
+ type: string
+ description: Name of the network
+ management-option:
+ type: string
+ description: Whether A&AI should be managing this interface of not. Could have value like CUSTOMER
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ vlans:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vlan"
+ sriov-vfs:
+ type: array
+ items:
+ $ref: "#/getDefinitions/sriov-vf"
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- ctag-assignments:
+ $ref: "#/getDefinitions/relationship"
+ l3-interface-ipv4-address-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
+ l3-interface-ipv6-address-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
+ l-interfaces:
+ description: |
+ Collection of logical interfaces.
properties:
- ctag-assignment:
+ l-interface:
type: array
items:
- $ref: "#/definitions/ctag-assignment"
- segmentation-assignment:
+ $ref: "#/getDefinitions/l-interface"
+ l3-interface-ipv4-address-list:
description: |
- Openstack segmentation assignment.
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ IPv4 Address Range
###### Related Nodes
- - FROM l3-network (is composed of segmentation-assignment)
+ - TO l3-network( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - TO subnet( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - TO l-interface( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - TO vlan( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
required:
- - segmentation-id
+ - l3-interface-ipv4-address
properties:
- segmentation-id:
+ l3-interface-ipv4-address:
type: string
- description: Route Table Reference id, UUID assigned to this instance.
+ description: IP address
+ l3-interface-ipv4-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 32 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
resource-version:
type: string
- description: Concurrency value
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
+ type: string
+ description: Neutron network id of the interface that address belongs to
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of subnet that address belongs to
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- segmentation-assignments:
+ $ref: "#/getDefinitions/relationship"
+ l3-interface-ipv6-address-list:
description: |
- Collection of openstack segmentation assignments
+ IPv6 Address Range
+ ###### Related Nodes
+ - TO l3-network( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - TO subnet( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - TO l-interface( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - TO vlan( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ required:
+ - l3-interface-ipv6-address
properties:
- segmentation-assignment:
+ l3-interface-ipv6-address:
+ type: string
+ description: IP address
+ l3-interface-ipv6-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 128 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
+ type: string
+ description: Neutron network id of the interface that address belongs to
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of subnet that address belongs to
+ relationship-list:
type: array
- items:
- $ref: "#/definitions/segmentation-assignment"
+ items:
+ $ref: "#/getDefinitions/relationship"
l3-network:
description: |
Generic network definition
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
- ###### Related Nodes
- - TO vpn-binding (Many2Many)
- - TO subnet (comprises l3-network, Many2Many)
- - TO service-instance (Many2Many)
- - TO ctag-assignment (comprises l3-network, Many2Many)
- - TO network-policy (Many2Many)
- - TO segmentation-assignment (comprises l3-network, One2Many)
- - TO route-table-reference (Many2Many)
- - FROM cloud-region
- - FROM complex
- - FROM generic-vnf
- - FROM l3-interface-ipv4-address-list
- - FROM l3-interface-ipv6-address-list
- - FROM tenant
- - FROM vf-module
+ ###### Related Nodes
+ - TO network-policy( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)
+ - TO route-table-reference( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)
+ - TO vpn-binding( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM complex( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - FROM ctag-assignment( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM segmentation-assignment( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)
+ - FROM subnet( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)
+ - L3-NETWORK is DELETED when these are DELETED CTAG-ASSIGNMENT,SEGMENTATION-ASSIGNMENT,SUBNET
required:
- network-id
- network-name
@@ -36621,84 +54511,191 @@ definitions:
subnets:
type: array
items:
- $ref: "#/definitions/subnet"
+ $ref: "#/getDefinitions/subnet"
ctag-assignments:
type: array
items:
- $ref: "#/definitions/ctag-assignment"
+ $ref: "#/getDefinitions/ctag-assignment"
segmentation-assignments:
type: array
items:
- $ref: "#/definitions/segmentation-assignment"
+ $ref: "#/getDefinitions/segmentation-assignment"
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
+ $ref: "#/getDefinitions/relationship"
description: Relates to tenant (or is it a child of tenant), complex, service, vpn-binding
l3-networks:
properties:
l3-network:
type: array
items:
- $ref: "#/definitions/l3-network"
- network-policy:
+ $ref: "#/getDefinitions/l3-network"
+ lag-interface:
description: |
+ Link aggregate interface
###### Related Nodes
- - FROM l3-network
+ - TO generic-vnf( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO lag-link( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)
+ - TO p-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)
+ - TO pnf( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - TO pserver( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - TO vpls-pe( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)
+ - LAG-INTERFACE is DELETED when these are DELETED L-INTERFACE
+ - LAG-INTERFACE deletion means associated objects of these types are also DELETED:LAG-LINK
required:
- - network-policy-id
+ - interface-name
properties:
- network-policy-id:
+ interface-name:
type: string
- description: UUID representing unique key to this instance
- network-policy-fqdn:
+ description: Name that identifies the link aggregate interface
+ resource-version:
type: string
- description: Contrail FQDN for the policy
- heat-stack-id:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ speed-value:
type: string
- description: ID for the openStack Heat instance
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l-interface"
+ lag-interfaces:
+ description: |
+ Collection of link aggregate interfaces.
+ properties:
+ lag-interface:
+ type: array
+ items:
+ $ref: "#/getDefinitions/lag-interface"
+ lag-link:
+ description: |
+ LAG links can connect lag-interfaces
+ ###### Related Nodes
+ - FROM lag-interface( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)
+ required:
+ - link-name
+ properties:
+ link-name:
+ type: string
+ description: Alphabetical concatenation of lag-interface names
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- network-policies:
+ $ref: "#/getDefinitions/relationship"
+ lag-links:
+ description: |
+ Collection of link aggregation connections
properties:
- network-policy:
+ lag-link:
type: array
items:
- $ref: "#/definitions/network-policy"
- vf-module:
+ $ref: "#/getDefinitions/lag-link"
+ license:
description: |
- a deployment unit of VNFCs
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Metadata for license group.
###### Related Nodes
- - TO volume-group (One2One)
- - TO l3-network (Many2Many)
- - TO vnfc (One2Many)
- - FROM vserver
- - FROM generic-vnf (is composed of vf-module)
+ - TO generic-vnf( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vce( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
required:
- - vf-module-id
- - is-base-vf-module
+ - group-uuid
+ - resource-uuid
properties:
- vf-module-id:
+ group-uuid:
type: string
- description: Unique ID of vf-module.
- vf-module-name:
+ description: Unique ID for the license group the resource belongs to, should be uuid.
+ resource-uuid:
type: string
- description: Name of vf-module
- heat-stack-id:
+ description: Unique ID of a license resource.
+ resource-version:
type: string
- description: Heat stack id corresponding to this instance.
- orchestration-status:
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ licenses:
+ description: |
+ Licenses to be allocated across resources, keyed by group-uuid and resource-uuid, related to license management
+ properties:
+ license:
+ type: array
+ items:
+ $ref: "#/getDefinitions/license"
+ line-of-business:
+ description: |
+ describes a line-of-business
+ ###### Related Nodes
+ - TO generic-vnf( line-of-business org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)
+ required:
+ - line-of-business-name
+ properties:
+ line-of-business-name:
type: string
- description: orchestration status of this vf-module, mastered by MSO
- is-base-vf-module:
- type: boolean
+ description: Name of the line-of-business (product)
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ lines-of-business:
+ description: |
+ Collection of lines-of-business
+ properties:
+ line-of-business:
+ type: array
+ items:
+ $ref: "#/getDefinitions/line-of-business"
+ logical-link:
+ description: |
+ Logical links generally connect l-interfaces but are used to express logical connectivity between two points
+ ###### Related Nodes
+ - TO generic-vnf( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)
+ - TO lag-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)
+ - TO logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - TO pnf( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)
+ - TO pserver( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)
+ - TO virtual-data-center( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)
+ - FROM p-interface( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - FROM vlan( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ required:
+ - link-name
+ - link-type
+ properties:
+ link-name:
+ type: string
+ description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
+ link-type:
+ type: string
+ description: Type of logical link, e.g., evc
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ ip-version:
+ type: string
+ description: v4, v6, or ds for dual stack
+ routing-protocol:
+ type: string
+ description: For example, static or BGP
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
@@ -36717,216 +54714,503 @@ definitions:
widget-model-version:
type: string
description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
- contrail-service-instance-fqdn:
+ operational-status:
type: string
- description: the Contrail unique ID for a service-instance
+ description: Indication of operational status of the logical link.
+ link-role:
+ type: string
+ description: Indication of the network use of the logical link.
+ link-name2:
+ type: string
+ description: Alias or alternate name (CLCI or D1 name).
+ link-id:
+ type: string
+ description: UUID of the logical-link, SDNC generates this.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- vf-modules:
+ $ref: "#/getDefinitions/relationship"
+ logical-links:
description: |
- Collection of vf-modules, a deployment unit of VNFCs
+ Collection of logical connections
properties:
- vf-module:
+ logical-link:
type: array
items:
- $ref: "#/definitions/vf-module"
- generic-vnf:
+ $ref: "#/getDefinitions/logical-link"
+ metadata:
description: |
- General purpose VNF
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
- ###### Related Nodes
- - TO license-key-resource (Many2Many)
- - TO l-interface (comprises generic-vnf, Many2Many)
- - TO availability-zone (Many2Many)
- - TO lag-interface (comprises generic-vnf, Many2Many)
- - TO l3-network (Many2Many)
- - TO pserver (Many2Many)
- - TO vnf-image (Many2One)
- - TO vserver (One2Many)
- - TO service-instance (Many2Many)
- - TO site-pair-set (Many2Many)
- - TO network-profile (Many2Many)
- - TO ipsec-configuration (Many2One)
- - TO vf-module (comprises generic-vnf, One2Many)
- - TO volume-group (One2Many)
- - TO vnfc (One2Many)
- - FROM virtual-data-center
- - FROM logical-link
+ Collection of metadatum (key/value pairs)
+ properties:
+ metadatum:
+ type: array
+ items:
+ $ref: "#/getDefinitions/metadatum"
+ metadatum:
+ description: |
+ Key/value pairs
+ ###### Related Nodes
+ - TO connector( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)
+ - TO image( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)
+ - TO service-instance( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - TO model( metadatum org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
required:
- - vnf-id
- - vnf-name
- - vnf-type
- - in-maint
- - is-closed-loop-disabled
+ - metaname
+ - metaval
properties:
- vnf-id:
+ metaname:
type: string
- description: Unique id of VNF. This is unique across the graph.
- vnf-name:
+ metaval:
type: string
- description: Name of VNF.
- vnf-name2:
+ resource-version:
type: string
- description: Alternate name of VNF.
- vnf-type:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model:
+ description: |
+ Subgraph definition provided by ASDC to describe an inventory asset and its connections related to ASDC models
+ ###### Related Nodes
+ - TO model( model-element isA model, MANY2ONE)
+ - TO model-element (CHILD of model, model startsWith model-element, ONE2MANY)
+ - FROM named-query( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)
+ - FROM model-element( model-element isA model, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - MODEL cannot be deleted if linked to NAMED-QUERY,NAMED-QUERY-ELEMENT
+ - MODEL is DELETED when these are DELETED METADATUM
+ - MODEL deletion means associated objects of these types are also DELETED:MODEL-ELEMENT
+ required:
+ - model-name-version-id
+ - model-type
+ - model-name
+ - model-id
+ - model-version
+ properties:
+ model-name-version-id:
type: string
- description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded and clients should expect changes to occur in the future to this field as ASDC matures.
- service-id:
+ description: Unique identifier corresponding to one version of a model in ASDC
+ model-type:
type: string
- description: Unique identifier of service from ASDC
- regional-resource-zone:
+ description: Type of the model, e.g., service, resource, widget, etc.
+ model-name:
type: string
- description: Regional way of organizing pservers, source of truth should define values
- prov-status:
+ description: Name of the model, which can change from version to version.
+ model-id:
type: string
- description: Trigger for operational monitoring of this resource by Service Assurance systems.
- operational-state:
+ description: Invariant unique ID which does not change from version to version
+ model-version:
type: string
- description: Indicator for whether the resource is considered operational
- license-key:
+ description: Version
+ model-description:
type: string
- description: License key
- equipment-role:
+ description: Description
+ resource-version:
type: string
- description: Client should send valid enumerated value
- orchestration-status:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-elements:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model-element"
+ metadata:
+ type: array
+ items:
+ $ref: "#/getDefinitions/metadatum"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ model-and-named-query-search:
+ description: |
+ ModelAndNamedQuerySearch holds query-parameters and instance-properties for performing a named-query or model query
+ properties:
+ query-parameters:
+ type: object
+ $ref: "#/getDefinitions/query-parameters"
+ instance-filters:
+ type: object
+ $ref: "#/getDefinitions/instance-filters"
+ top-node-type:
type: string
- description: Orchestration status of this VNF, used by MSO.
- heat-stack-id:
+ model-constraint:
+ description: |
+ This is how we would capture constraints defining allowed sets of elements.
+ ###### Related Nodes
+ - TO model-element( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)
+ - MODEL-CONSTRAINT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET
+ required:
+ - model-constraint-uuid
+ - constrained-element-set-uuid-to-replace
+ properties:
+ model-constraint-uuid:
type: string
- description: Heat stack id corresponding to this instance, managed by MSO
- mso-catalog-key:
+ constrained-element-set-uuid-to-replace:
type: string
- description: Corresponds to the SDN-C catalog id used to configure this VCE
- management-option:
+ constrained-element-sets:
+ type: array
+ items:
+ $ref: "#/getDefinitions/constrained-element-set"
+ model-constraints:
+ properties:
+ model-constraint:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model-constraint"
+ model-element:
+ description: |
+ Defines how other models combine to make up a higher-level model.
+ ###### Related Nodes
+ - TO element-choice-set( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)
+ - TO model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - TO model( model-element isA model, MANY2ONE)
+ - FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM model-constraint( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM model (PARENT of model-element, model startsWith model-element)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - MODEL-ELEMENT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET,MODEL-CONSTRAINT
+ required:
+ - model-element-uuid
+ - new-data-del-flag
+ - cardinality
+ properties:
+ model-element-uuid:
type: string
- description: identifier of managed by company or customer
- ipv4-oam-address:
+ new-data-del-flag:
type: string
- description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by generic-vnf.
- ipv4-loopback0-address:
+ description: Indicates whether this element was created as part of instantiation from this model
+ cardinality:
type: string
- description: v4 Loopback0 address
- nm-lan-v6-address:
+ description: How many of this type of element are required/allowed
+ linkage-points:
type: string
- description: v6 Loopback address
- management-v6-address:
+ resource-version:
type: string
- description: v6 management address
- vcpu:
- type: integer
- format: int64
- description: number of vcpus ordered for this instance of VNF, used for VNFs with no vservers/flavors
- vcpu-units:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-elements:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model-element"
+ description: Defines how other models combine to make up a higher-level model
+ model-constraints:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model-constraint"
+ description: Describes new constraints on this model element that are not part of that model's definition
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ model-elements:
+ properties:
+ model-element:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model-element"
+ model-ver:
+ description: |
+ Subgraph definition provided by ASDC to describe a specific version of an inventory asset and its connections related to ASDC models
+ ###### Related Nodes
+ - TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - MODEL-VER cannot be deleted if linked to MODEL-ELEMENT
+ - MODEL-VER is DELETED when these are DELETED MODEL-ELEMENT,METADATUM
+ required:
+ - model-version-id
+ - model-name
+ - model-version
+ properties:
+ model-version-id:
type: string
- description: units associated with vcpu, used for VNFs with no vservers/flavors
- vmemory:
- type: integer
- format: int64
- description: number of GB of memory ordered for this instance of VNF, used for VNFs with no vservers/flavors
- vmemory-units:
+ description: Unique identifier corresponding to one version of a model in ASDC
+ model-name:
type: string
- description: units associated with vmemory, used for VNFs with no vservers/flavors
- vdisk:
- type: integer
- format: int64
- description: number of vdisks ordered for this instance of VNF, used for VNFs with no vservers/flavors
- vdisk-units:
+ description: Name of the model, which can change from version to version.
+ model-version:
type: string
- description: units associated with vdisk, used for VNFs with no vservers/flavors
- in-maint:
- type: boolean
- is-closed-loop-disabled:
- type: boolean
+ description: Version
+ model-description:
+ type: string
+ description: Description
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- summary-status:
+ model-elements:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model-element"
+ metadata:
+ type: array
+ items:
+ $ref: "#/getDefinitions/metadatum"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ model-vers:
+ properties:
+ model-ver:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model-ver"
+ models:
+ description: |
+ Collection of subgraph definitions provided by ASDC to describe the inventory assets and their connections related to ASDC models
+ properties:
+ model:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model"
+ multicast-configuration:
+ description: |
+ ###### Related Nodes
+ - FROM vlan( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)
+ required:
+ - multicast-configuration-id
+ - multicast-protocol
+ - rp-type
+ properties:
+ multicast-configuration-id:
type: string
- description: details regarding the generic-vnf operation
- encrypted-access-flag:
- type: boolean
- description: indicates whether generic-vnf access uses SSH
- persona-model-id:
+ description: Unique id of multicast configuration.
+ multicast-protocol:
type: string
- description: the ASDC model id for this resource or service model.
- persona-model-version:
+ description: protocol of multicast configuration
+ rp-type:
type: string
- description: the ASDC model version for this resource or service model.
- model-version-id:
+ description: rp type of multicast configuration
+ resource-version:
type: string
- description: the ASDC model version for this resource or service model.
- widget-model-id:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ multicast-configurations:
+ description: |
+ multicast configuration of generic-vnf ip-address
+ properties:
+ multicast-configuration:
+ type: array
+ items:
+ $ref: "#/getDefinitions/multicast-configuration"
+ named-queries:
+ properties:
+ named-query:
+ type: array
+ items:
+ $ref: "#/getDefinitions/named-query"
+ named-query:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - TO model( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - NAMED-QUERY is DELETED when these are DELETED NAMED-QUERY-ELEMENT
+ required:
+ - named-query-uuid
+ - named-query-name
+ - named-query-version
+ properties:
+ named-query-uuid:
type: string
- description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
- widget-model-version:
+ named-query-name:
type: string
- description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
- as-number:
+ named-query-version:
type: string
- description: as-number of the VNF
- regional-resource-subzone:
+ required-input-param:
type: string
- description: represents sub zone of the rr plane
+ description:
+ type: string
+ resource-version:
+ type: string
+ named-query-elements:
+ type: array
+ items:
+ $ref: "#/getDefinitions/named-query-element"
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- l-interfaces:
+ $ref: "#/getDefinitions/relationship"
+ named-query-element:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - TO model( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)
+ - TO named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM property-constraint( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM related-lookup( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - NAMED-QUERY-ELEMENT is DELETED when these are DELETED PROPERTY-CONSTRAINT,RELATED-LOOKUP
+ required:
+ - named-query-element-uuid
+ properties:
+ named-query-element-uuid:
+ type: string
+ property-collect-list:
+ type: string
+ resource-version:
+ type: string
+ property-limit-desc:
+ type: string
+ do-not-output:
+ type: string
+ named-query-elements:
type: array
items:
- $ref: "#/definitions/l-interface"
- lag-interfaces:
+ $ref: "#/getDefinitions/named-query-element"
+ related-lookups:
type: array
items:
- $ref: "#/definitions/lag-interface"
- vf-modules:
+ $ref: "#/getDefinitions/related-lookup"
+ property-constraints:
type: array
items:
- $ref: "#/definitions/vf-module"
- generic-vnfs:
+ $ref: "#/getDefinitions/property-constraint"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ named-query-elements:
+ properties:
+ named-query-element:
+ type: array
+ items:
+ $ref: "#/getDefinitions/named-query-element"
+ network:
description: |
- Collection of VNFs
+ Namespace for network inventory resources.
properties:
- generic-vnf:
+ logical-links:
+ type: array
+ items:
+ $ref: "#/getDefinitions/logical-link"
+ site-pair-sets:
+ type: array
+ items:
+ $ref: "#/getDefinitions/site-pair-set"
+ vpn-bindings:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vpn-binding"
+ vpls-pes:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vpls-pe"
+ multicast-configurations:
+ type: array
+ items:
+ $ref: "#/getDefinitions/multicast-configuration"
+ vces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vce"
+ vnfcs:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vnfc"
+ l3-networks:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l3-network"
+ network-policies:
+ type: array
+ items:
+ $ref: "#/getDefinitions/network-policy"
+ generic-vnfs:
+ type: array
+ items:
+ $ref: "#/getDefinitions/generic-vnf"
+ lag-links:
+ type: array
+ items:
+ $ref: "#/getDefinitions/lag-link"
+ newvces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/newvce"
+ pnfs:
+ type: array
+ items:
+ $ref: "#/getDefinitions/pnf"
+ physical-links:
+ type: array
+ items:
+ $ref: "#/getDefinitions/physical-link"
+ ipsec-configurations:
+ type: array
+ items:
+ $ref: "#/getDefinitions/ipsec-configuration"
+ route-table-references:
+ type: array
+ items:
+ $ref: "#/getDefinitions/route-table-reference"
+ network-policies:
+ properties:
+ network-policy:
type: array
items:
- $ref: "#/definitions/generic-vnf"
- lag-link:
+ $ref: "#/getDefinitions/network-policy"
+ network-policy:
description: |
- LAG links can connect lag-interfaces
###### Related Nodes
- - FROM lag-interface
- - FROM logical-link
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)
required:
- - link-name
+ - network-policy-id
properties:
- link-name:
+ network-policy-id:
type: string
- description: Alphabetical concatenation of lag-interface names
+ description: UUID representing unique key to this instance
+ network-policy-fqdn:
+ type: string
+ description: Contrail FQDN for the policy
+ heat-stack-id:
+ type: string
+ description: ID for the openStack Heat instance
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- lag-links:
+ $ref: "#/getDefinitions/relationship"
+ network-profile:
description: |
- Collection of link aggregation connections
+ Network profile populated by SDN-GP for SNMP
+ ###### Related Nodes
+ - TO generic-vnf( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ required:
+ - nm-profile-name
properties:
- lag-link:
+ nm-profile-name:
+ type: string
+ description: Unique name of network profile.
+ community-string:
+ type: string
+ description: Encrypted SNMP community string
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ network-profiles:
+ description: |
+ Collection of network profiles
+ properties:
+ network-profile:
type: array
items:
- $ref: "#/definitions/lag-link"
+ $ref: "#/getDefinitions/network-profile"
newvce:
description: |
This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce.
###### Related Nodes
- - TO l-interface (comprises newvce, Many2Many)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)
+ - NEWVCE is DELETED when these are DELETED L-INTERFACE
required:
- vnf-id2
- vnf-name
@@ -36977,11 +55261,11 @@ definitions:
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
+ $ref: "#/getDefinitions/relationship"
l-interfaces:
type: array
items:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
newvces:
description: |
This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce.
@@ -36989,17 +55273,355 @@ definitions:
newvce:
type: array
items:
- $ref: "#/definitions/newvce"
+ $ref: "#/getDefinitions/newvce"
+ notification-event:
+ properties:
+ cambria.partition:
+ type: string
+ notification-event-header:
+ type: object
+ $ref: "#/getDefinitions/notification-event-header"
+ notification-event-header:
+ properties:
+ id:
+ type: string
+ timestamp:
+ type: string
+ source-name:
+ type: string
+ domain:
+ type: string
+ sequence-number:
+ type: string
+ severity:
+ type: string
+ event-type:
+ type: string
+ version:
+ type: string
+ action:
+ type: string
+ entity-type:
+ type: string
+ top-entity-type:
+ type: string
+ entity-link:
+ type: string
+ status:
+ type: string
+ notify:
+ required:
+ - event-id
+ properties:
+ event-id:
+ type: string
+ node-type:
+ type: string
+ event-trigger:
+ type: string
+ key-data:
+ type: array
+ items:
+ $ref: "#/getDefinitions/key-data"
+ selflink:
+ type: string
+ oam-network:
+ description: |
+ OAM network, to be deprecated shortly. Do not use for new purposes.
+ ###### Related Nodes
+ - TO cloud-region( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO complex( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)
+ - TO service-capability( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ required:
+ - network-uuid
+ - network-name
+ - cvlan-tag
+ properties:
+ network-uuid:
+ type: string
+ description: UUID of the network. Unique across a cloud-region
+ network-name:
+ type: string
+ description: Name of the network.
+ cvlan-tag:
+ type: integer
+ format: int64
+ description: cvlan-id
+ ipv4-oam-gateway-address:
+ type: string
+ description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
+ ipv4-oam-gateway-address-prefix-length:
+ type: integer
+ format: int32
+ description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ oam-networks:
+ description: |
+ Collection of OAM networks, to be deprecated shortly. Do not use for new purposes.
+ properties:
+ oam-network:
+ type: array
+ items:
+ $ref: "#/getDefinitions/oam-network"
+ operational-environment:
+ description: |
+ It is a logical partition of the cloud which allows to have multiple environments in the production AIC.
+ ###### Related Nodes
+ - TO operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)
+ - FROM operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)
+ required:
+ - operational-environment-id
+ - operational-environment-name
+ - operational-environment-type
+ - operational-environment-status
+ - tenant-context
+ - workload-context
+ properties:
+ operational-environment-id:
+ type: string
+ description: UUID of an operational environment
+ operational-environment-name:
+ type: string
+ description: Operational Environment name
+ operational-environment-type:
+ type: string
+ description: Operational Environment Type.
+ operational-environment-status:
+ type: string
+ description: Status
+ tenant-context:
+ type: string
+ description: Tenant Context.
+ workload-context:
+ type: string
+ description: Workload Context.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ operational-environments:
+ description: |
+ a logical partition of the cloud which allows to have multiple environments in the production AIC.
+ properties:
+ operational-environment:
+ type: array
+ items:
+ $ref: "#/getDefinitions/operational-environment"
+ overloaded-model:
+ description: |
+ Allows for legacy POST of old-style and new-style models
+ required:
+ - model-invariant-id
+ - model-name-version-id
+ - model-type
+ - model-name
+ - model-id
+ - model-version
+ properties:
+ model-invariant-id:
+ type: string
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ model-name-version-id:
+ type: string
+ description: Unique identifier corresponding to one version of a model in ASDC
+ model-type:
+ type: string
+ description: Type of the model, e.g., service, resource, widget, etc.
+ model-name:
+ type: string
+ description: Name of the model, which can change from version to version.
+ model-id:
+ type: string
+ description: Invariant unique ID which does not change from version to version
+ model-version:
+ type: string
+ description: Version
+ model-description:
+ type: string
+ description: Description
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-vers:
+ type: object
+ $ref: "#/getDefinitions/model-vers"
+ relationship-list:
+ type: object
+ $ref: "#/getDefinitions/relationship-list"
+ owning-entities:
+ description: |
+ Collection of owning-entities
+ properties:
+ owning-entity:
+ type: array
+ items:
+ $ref: "#/getDefinitions/owning-entity"
+ owning-entity:
+ description: |
+ describes an owning-entity
+ ###### Related Nodes
+ - FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo owning-entity, MANY2ONE)
+ required:
+ - owning-entity-id
+ - owning-entity-name
+ properties:
+ owning-entity-id:
+ type: string
+ description: UUID of an owning entity
+ owning-entity-name:
+ type: string
+ description: Owning entity name
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ p-interface:
+ description: |
+ Physical interface (e.g., nic)
+ ###### Related Nodes
+ - TO logical-link( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)
+ - TO physical-link( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)
+ - TO pnf( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - TO pserver( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - TO vpls-pe( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM lag-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)
+ - P-INTERFACE is DELETED when these are DELETED L-INTERFACE
+ - P-INTERFACE deletion means associated objects of these types are also DELETED:PHYSICAL-LINK
+ required:
+ - interface-name
+ properties:
+ interface-name:
+ type: string
+ description: Name that identifies the physical interface
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ port-description:
+ type: string
+ description: Nature of the services and connectivity on this port.
+ equipment-identifier:
+ type: string
+ description: CLEI or other specification for p-interface hardware.
+ interface-role:
+ type: string
+ description: Role specification for p-interface hardware.
+ interface-type:
+ type: string
+ description: Indicates the physical properties of the interface.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l-interface"
+ p-interfaces:
+ description: |
+ Collection of physical interfaces.
+ properties:
+ p-interface:
+ type: array
+ items:
+ $ref: "#/getDefinitions/p-interface"
+ physical-link:
+ description: |
+ Collection of physical connections, typically between p-interfaces
+ ###### Related Nodes
+ - FROM p-interface( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)
+ required:
+ - link-name
+ properties:
+ link-name:
+ type: string
+ description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ circuit-id:
+ type: string
+ description: Circuit it
+ dual-mode:
+ type: string
+ description: Dual access mode (e.g., primary, secondary
+ management-option:
+ type: string
+ description: To provide information on who manages this circuit. A&AI or 3rd party transport provider
+ service-provider-name:
+ type: string
+ description: Name of the service Provider on this link.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ physical-links:
+ description: |
+ Collection of physical connections, typically between p-interfaces
+ properties:
+ physical-link:
+ type: array
+ items:
+ $ref: "#/getDefinitions/physical-link"
+ platform:
+ description: |
+ describes a platform
+ ###### Related Nodes
+ - TO generic-vnf( platform org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)
+ required:
+ - platform-name
+ properties:
+ platform-name:
+ type: string
+ description: Name of the platform
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ platforms:
+ description: |
+ Collection of platforms
+ properties:
+ platform:
+ type: array
+ items:
+ $ref: "#/getDefinitions/platform"
pnf:
description: |
PNF represents a physical network function. typically equipment used in the D1 world.
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
###### Related Nodes
- - TO p-interface (comprises pnf, Many2Many)
- - TO lag-interface (comprises pnf, One2Many)
- - TO complex (Many2One)
- - FROM logical-link
+ - TO complex( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - PNF is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
required:
- pnf-name
- in-maint
@@ -37048,15 +55670,15 @@ definitions:
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
+ $ref: "#/getDefinitions/relationship"
p-interfaces:
type: array
items:
- $ref: "#/definitions/p-interface"
+ $ref: "#/getDefinitions/p-interface"
lag-interfaces:
type: array
items:
- $ref: "#/definitions/lag-interface"
+ $ref: "#/getDefinitions/lag-interface"
pnfs:
description: |
Collection of Physical Network Functions.
@@ -37064,177 +55686,347 @@ definitions:
pnf:
type: array
items:
- $ref: "#/definitions/pnf"
- physical-link:
+ $ref: "#/getDefinitions/pnf"
+ port-group:
description: |
- Collection of physical connections, typically between p-interfaces
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Used to capture the network interfaces of this VCE
###### Related Nodes
- - FROM p-interface
+ - TO vce( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM cvlan-tag( cvlan-tag org.onap.relationships.inventory.BelongsTo port-group, MANY2ONE)
+ - PORT-GROUP is DELETED when these are DELETED CVLAN-TAG
required:
- - link-name
+ - interface-id
+ - orchestration-status
properties:
- link-name:
+ interface-id:
type: string
- description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
- speed-value:
+ description: Unique ID of the interface
+ neutron-network-id:
type: string
- description: Captures the numeric part of the speed
- speed-units:
+ description: Neutron network id of this Interface
+ neutron-network-name:
type: string
- description: Captures the units corresponding to the speed
- circuit-id:
+ description: Neutron network name of this Interface
+ interface-role:
type: string
- description: Circuit it
- dual-mode:
+ description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
+ resource-version:
type: string
- description: Dual access mode (e.g., primary, secondary
- management-option:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ port-group-id:
type: string
- description: To provide information on who manages this circuit. A&AI or 3rd party transport provider
- service-provider-name:
+ description: Unique ID for port group in vmware
+ port-group-name:
type: string
- description: Name of the service Provider on this link.
- resource-version:
+ description: Likely to duplicate value of neutron network name
+ switch-name:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ description: DVS or standard switch name (should be non-null for port groups associated with DVS)
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ cvlan-tags:
+ type: array
+ items:
+ $ref: "#/getDefinitions/cvlan-tag-entry"
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- physical-links:
- description: |
- Collection of physical connections, typically between p-interfaces
+ $ref: "#/getDefinitions/relationship"
+ port-groups:
properties:
- physical-link:
+ port-group:
type: array
items:
- $ref: "#/definitions/physical-link"
- vig-server:
+ $ref: "#/getDefinitions/port-group"
+ project:
description: |
- vig-server contains information about a vig server used for IPSec-configuration. Populated by SDN-C from 1607
+ describes the project
###### Related Nodes
- - FROM ipsec-configuration (is composed of vig-server)
+ - TO service-instance( project org.onap.relationships.inventory.Uses service-instance, ONE2MANY)
required:
- - vig-address-type
+ - project-name
properties:
- vig-address-type:
+ project-name:
type: string
- description: indicates whether the VIG is for AVPN or INTERNET
- ipaddress-v4-vig:
- type: string
- description: v4 IP of the vig server
- ipaddress-v6-vig:
- type: string
- description: v6 IP of the vig server
+ description: Name of the project deploying a service
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- vig-servers:
+ $ref: "#/getDefinitions/relationship"
+ projects:
+ description: |
+ Collection of projects
properties:
- vig-server:
+ project:
type: array
items:
- $ref: "#/definitions/vig-server"
- ipsec-configuration:
+ $ref: "#/getDefinitions/project"
+ properties:
description: |
- IPSec configuration node will contain various configuration data for the NMTE VNF. This node will have an edge to the generic-vnf (vnf type = TE). Starting 1607, this data will be populated by SDN-C
+ Property holder for query properties or instance properties
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ property-constraint:
+ description: |
+ TBD
###### Related Nodes
- - TO vig-server (comprises ipsec-configuration, One2Many)
- - FROM generic-vnf
+ - TO named-query-element( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
required:
- - ipsec-configuration-id
+ - property-constraint-uuid
+ - constraint-type
+ - property-name
+ - property-value
properties:
- ipsec-configuration-id:
+ property-constraint-uuid:
type: string
- description: UUID of this configuration
- requested-vig-address-type:
+ constraint-type:
type: string
- description: Indicate the type of VIG server like AVPN, INTERNET, BOTH
- requested-encryption-strength:
+ property-name:
type: string
- description: Encryption values like 3des-cbc, des-cbc, aes-128-cbc, aes-192-cbc, aes-265-cbc
- requested-dmz-type:
+ property-value:
type: string
- description: can offer a shared DMZ or a DMZ specific to a customer
- shared-dmz-network-address:
+ resource-version:
type: string
- description: Network address of shared DMZ
- requested-customer-name:
+ property-constraints:
+ properties:
+ property-constraint:
+ type: array
+ items:
+ $ref: "#/getDefinitions/property-constraint"
+ pserver:
+ description: |
+ Compute host whose hostname must be unique and must exactly match what is sent as a relationship to a vserver.
+ ###### Related Nodes
+ - TO group-assignment( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)
+ - TO availability-zone( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)
+ - TO cloud-region( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)
+ - TO complex( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - FROM vserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)
+ - PSERVER cannot be deleted if linked to GENERIC-VNF,LOGICAL-LINK,VSERVER
+ - PSERVER is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
+ - PSERVER cannot be deleted if linked to GROUP-ASSIGNMENT
+ required:
+ - hostname
+ - in-maint
+ properties:
+ hostname:
type: string
- description: If the DMZ is a custom DMZ, this field will indicate the customer information
- ike-version:
+ description: Value from executing hostname on the compute node.
+ ptnii-equip-name:
type: string
- description: can be 1 or 2
- ikev1-authentication:
+ description: PTNII name
+ number-of-cpus:
+ type: integer
+ format: int32
+ description: Number of cpus
+ disk-in-gigabytes:
+ type: integer
+ format: int32
+ description: Disk size, in GBs
+ ram-in-megabytes:
+ type: integer
+ format: int32
+ description: RAM size, in MBs
+ equip-type:
type: string
- description: Contains values like md5, sha1, sha256, sha384
- ikev1-encryption:
+ description: Equipment type. Source of truth should define valid values.
+ equip-vendor:
type: string
- description: Encyption values like 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
- ikev1-dh-group:
+ description: Equipment vendor. Source of truth should define valid values.
+ equip-model:
type: string
- description: Diffie-Hellman group like DH-GROUP2, DH-GROUP5, DH-GROUP14
- ikev1-am-group-id:
+ description: Equipment model. Source of truth should define valid values.
+ fqdn:
type: string
- description: Group name defined in VIG for clients using aggressive mode
- ikev1-am-password:
+ description: Fully-qualified domain name
+ pserver-selflink:
type: string
- description: pre-shared key for the above group name
- ikev1-sa-lifetime:
+ description: URL to endpoint where AAI can get more details
+ ipv4-oam-address:
type: string
- description: Lifetime for IKEv1 SA
- ipsec-authentication:
+ description: Used to configure device, also used for troubleshooting and is IP used for traps generated by device.
+ serial-number:
type: string
- description: md5, sha1, sha256, sha384
- ipsec-encryption:
+ description: Serial number, may be queried
+ pserver-id:
type: string
- description: 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
- ipsec-sa-lifetime:
+ description: ID of Pserver
+ internet-topology:
type: string
- description: Life time for IPSec SA
- ipsec-pfs:
+ description: internet topology of Pserver
+ in-maint:
+ type: boolean
+ resource-version:
type: string
- description: enable PFS or not
- xauth-userid:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ pserver-name2:
type: string
- description: user ID for xAuth, sm-user, ,nmteHostName
- xauth-user-password:
+ description: alternative pserver name
+ purpose:
type: string
- description: Encrypted using the Juniper $9$ algorithm
- dpd-interval:
+ description: purpose of pserver
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ p-interfaces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/p-interface"
+ lag-interfaces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/lag-interface"
+ pservers:
+ description: |
+ Collection of compute hosts.
+ properties:
+ pserver:
+ type: array
+ items:
+ $ref: "#/getDefinitions/pserver"
+ query-parameters:
+ description: |
+ QueryParameters for performing a named-query or model query
+ properties:
+ named-query:
+ type: object
+ $ref: "#/getDefinitions/named-query"
+ model:
+ type: object
+ $ref: "#/getDefinitions/model"
+ related-lookup:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query-element( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ required:
+ - related-lookup-uuid
+ - source-node-type
+ - source-node-property
+ - target-node-type
+ - target-node-property
+ properties:
+ related-lookup-uuid:
type: string
- description: The time between DPD probe
- dpd-frequency:
+ source-node-type:
+ type: string
+ source-node-property:
+ type: string
+ target-node-type:
+ type: string
+ target-node-property:
+ type: string
+ property-collect-list:
type: string
- description: Maximum number of DPD before claiming the tunnel is down
resource-version:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- vig-servers:
+ $ref: "#/getDefinitions/relationship"
+ related-lookups:
+ properties:
+ related-lookup:
type: array
- items:
- $ref: "#/definitions/vig-server"
- ipsec-configurations:
+ items:
+ $ref: "#/getDefinitions/related-lookup"
+ related-to-property:
properties:
- ipsec-configuration:
+ property-key:
+ type: string
+ description: Key part of a key/value pair
+ property-value:
+ type: string
+ description: Value part of a key/value pair
+ relationship:
+ properties:
+ related-to:
+ type: string
+ description: A keyword provided by A&AI to indicate type of node.
+ related-link:
+ type: string
+ description: URL to the object in A&AI.
+ relationship-data:
type: array
items:
- $ref: "#/definitions/ipsec-configuration"
+ $ref: "#/getDefinitions/relationship-data"
+ related-to-property:
+ type: array
+ items:
+ $ref: "#/getDefinitions/related-to-property"
+ relationship-data:
+ required:
+ - relationship-key
+ - relationship-value
+ properties:
+ relationship-key:
+ type: string
+ description: A keyword provided by A&AI to indicate an attribute.
+ relationship-value:
+ type: string
+ description: Value of the attribute.
+ relationship-list:
+ properties:
+ relationship:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ reserved-prop-names:
+ description: |
+ Internal map to define some reserved properties of a vertex
+ properties:
+ last-mod-source-of-truth:
+ type: string
+ aai-node-type:
+ type: string
+ aai-created-ts:
+ type: integer
+ format: int64
+ aai-unique-key:
+ type: string
+ aai-last-mod-ts:
+ type: integer
+ format: int64
+ source-of-truth:
+ type: string
+ response-list:
+ description: |
+ Response container for the results of a named-query or model query
+ properties:
+ inventory-response-items:
+ type: object
+ $ref: "#/getDefinitions/inventory-response-items"
+ result-data:
+ properties:
+ resource-type:
+ type: string
+ description: The specific type of node in the A&AI graph
+ resource-link:
+ type: string
+ description: The URL to the specific resource
route-table-reference:
description: |
Openstack route table reference.
###### Related Nodes
- - FROM l3-network
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)
required:
- route-table-reference-id
- route-table-reference-fqdn
@@ -37251,7 +56043,7 @@ definitions:
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
+ $ref: "#/getDefinitions/relationship"
route-table-references:
description: |
Collection of openstack route table references
@@ -37259,199 +56051,723 @@ definitions:
route-table-reference:
type: array
items:
- $ref: "#/definitions/route-table-reference"
- network:
+ $ref: "#/getDefinitions/route-table-reference"
+ route-target:
description: |
- Namespace for network inventory resources.
+ Route target information
+ ###### Related Nodes
+ - TO vpn-binding( route-target org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2ONE)
+ required:
+ - global-route-target
+ - route-target-role
properties:
- logical-links:
+ global-route-target:
+ type: string
+ description: Number used to identify an RT, globally unique in the network
+ route-target-role:
+ type: string
+ description: Role assigned to this route target
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/logical-link"
- site-pair-sets:
+ $ref: "#/getDefinitions/relationship"
+ route-targets:
+ description: |
+ Collection of route target information
+ properties:
+ route-target:
type: array
- items:
- $ref: "#/definitions/site-pair-set"
- vpn-bindings:
+ items:
+ $ref: "#/getDefinitions/route-target"
+ routing-instance:
+ description: |
+ ###### Related Nodes
+ - TO site-pair-set( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)
+ - FROM site-pair( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)
+ - ROUTING-INSTANCE is DELETED when these are DELETED SITE-PAIR
+ required:
+ - routing-instance-id
+ properties:
+ routing-instance-id:
+ type: string
+ description: Unique id of routing instance
+ rpm-owner:
+ type: string
+ description: rpm owner
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ site-pairs:
type: array
items:
- $ref: "#/definitions/vpn-binding"
- vpls-pes:
+ $ref: "#/getDefinitions/site-pair"
+ relationship-list:
type: array
items:
- $ref: "#/definitions/vpls-pe"
- multicast-configurations:
+ $ref: "#/getDefinitions/relationship"
+ routing-instances:
+ description: |
+ set of probes related to generic-vnf routing instance
+ properties:
+ routing-instance:
+ type: array
+ items:
+ $ref: "#/getDefinitions/routing-instance"
+ sdn-zone-response:
+ properties:
+ oam-networks:
+ type: object
+ $ref: "#/getDefinitions/oam-networks"
+ az-and-dvs-switches:
+ type: array
+ items:
+ $ref: "#/getDefinitions/az-and-dvs-switches"
+ search:
+ properties:
+ edge-tag-query-result:
+ type: object
+ $ref: "#/getDefinitions/edge-tag-query-result"
+ edge-tag-query-request:
+ type: object
+ $ref: "#/getDefinitions/edge-tag-query-request"
+ search-results:
+ type: object
+ $ref: "#/getDefinitions/search-results"
+ sdn-zone-response:
+ type: object
+ $ref: "#/getDefinitions/sdn-zone-response"
+ search-results:
+ properties:
+ result-data:
+ type: array
+ items:
+ $ref: "#/getDefinitions/result-data"
+ secondary-filt:
+ description: |
+ SecondaryFilt for performing a named-query or model query
+ secondary-filter:
+ properties:
+ property-name:
+ type: string
+ filter-type:
+ type: string
+ property-value:
+ type: string
+ secondary-filts:
+ description: |
+ SecondaryFilts for performing a named-query or model query
+ properties:
+ secondary-filt:
+ type: array
+ items:
+ $ref: "#/getDefinitions/secondary-filt"
+ segmentation-assignment:
+ description: |
+ Openstack segmentation assignment.
+ ###### Related Nodes
+ - TO l3-network( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ required:
+ - segmentation-id
+ properties:
+ segmentation-id:
+ type: string
+ description: Route Table Reference id, UUID assigned to this instance.
+ resource-version:
+ type: string
+ description: Concurrency value
+ relationship-list:
type: array
items:
- $ref: "#/definitions/multicast-configuration"
- vces:
+ $ref: "#/getDefinitions/relationship"
+ segmentation-assignments:
+ description: |
+ Collection of openstack segmentation assignments
+ properties:
+ segmentation-assignment:
+ type: array
+ items:
+ $ref: "#/getDefinitions/segmentation-assignment"
+ service:
+ description: |
+ Stand-in for service model definitions. Likely to be deprecated in favor of models from ASDC.
+ required:
+ - service-id
+ - service-description
+ properties:
+ service-id:
+ type: string
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ service-description:
+ type: string
+ description: Description of the service
+ service-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ service-version:
+ type: string
+ description: service version
+ relationship-list:
type: array
items:
- $ref: "#/definitions/vce"
- vnfcs:
+ $ref: "#/getDefinitions/relationship"
+ service-capabilities:
+ description: |
+ Collection of service capabilities.
+ properties:
+ service-capability:
+ type: array
+ items:
+ $ref: "#/getDefinitions/service-capability"
+ service-capability:
+ description: |
+ Early definition of server/resource pairings, likely to be replaced by models. No new use should be made of this.
+ ###### Related Nodes
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - SERVICE-CAPABILITY cannot be deleted if linked to AVAILABILITY-ZONE,OAM-NETWORK
+ required:
+ - service-type
+ - vnf-type
+ properties:
+ service-type:
+ type: string
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded and clients should expect changes to occur in the future to this field as ASDC matures.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/vnfc"
- l3-networks:
+ $ref: "#/getDefinitions/relationship"
+ service-design-and-creation:
+ description: |
+ Namespace for objects managed by ASDC
+ properties:
+ vnf-images:
type: array
items:
- $ref: "#/definitions/l3-network"
- network-policies:
+ $ref: "#/getDefinitions/vnf-image"
+ services:
type: array
items:
- $ref: "#/definitions/network-policy"
- generic-vnfs:
+ $ref: "#/getDefinitions/service"
+ service-capabilities:
type: array
items:
- $ref: "#/definitions/generic-vnf"
- lag-links:
+ $ref: "#/getDefinitions/service-capability"
+ models:
type: array
items:
- $ref: "#/definitions/lag-link"
- newvces:
+ $ref: "#/getDefinitions/model"
+ named-queries:
type: array
items:
- $ref: "#/definitions/newvce"
- pnfs:
+ $ref: "#/getDefinitions/named-query"
+ service-instance:
+ description: |
+ Instance of a service
+ ###### Related Nodes
+ - TO generic-vnf( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)
+ - TO l3-network( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)
+ - TO connector( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)
+ - TO cvlan-tag( service-instance org.onap.relationships.inventory.ComposedOf cvlan-tag, MANY2MANY)
+ - TO logical-link( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - TO service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)
+ - TO vlan( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)
+ - TO service-subscription( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)
+ - TO vce( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)
+ - SERVICE-INSTANCE is DELETED when these are DELETED METADATUM
+ - SERVICE-INSTANCE deletion means associated objects of these types are also DELETED:LOGICAL-LINK
+ required:
+ - service-instance-id
+ properties:
+ service-instance-id:
+ type: string
+ description: Uniquely identifies this instance of a service
+ service-instance-name:
+ type: string
+ description: This field will store a name assigned to the service-instance.
+ persona-model-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ bandwidth-total:
+ type: string
+ description: Indicates the total bandwidth to be used for this service.
+ bandwidth-up-wan1:
+ type: string
+ description: indicates the upstream bandwidth this service will use on the WAN1 port of the physical device.
+ bandwidth-down-wan1:
+ type: string
+ description: indicates the downstream bandwidth this service will use on the WAN1 port of the physical device.
+ bandwidth-up-wan2:
+ type: string
+ description: indicates the upstream bandwidth this service will use on the WAN2 port of the physical device.
+ bandwidth-down-wan2:
+ type: string
+ description: indicates the downstream bandwidth this service will use on the WAN2 port of the physical device.
+ vhn-portal-url:
+ type: string
+ description: URL customers will use to access the vHN Portal.
+ service-instance-location-id:
+ type: string
+ description: An identifier that customers assign to the location where this service is being used.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/pnf"
- physical-links:
+ $ref: "#/getDefinitions/relationship"
+ metadata:
type: array
items:
- $ref: "#/definitions/physical-link"
- ipsec-configurations:
+ $ref: "#/getDefinitions/metadatum"
+ service-instances:
+ description: |
+ Collection of service instances
+ properties:
+ service-instance:
+ type: array
+ items:
+ $ref: "#/getDefinitions/service-instance"
+ service-subscription:
+ description: |
+ Object that group service instances.
+ ###### Related Nodes
+ - TO customer( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)
+ - TO tenant( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)
+ - SERVICE-SUBSCRIPTION is DELETED when these are DELETED SERVICE-INSTANCE
+ required:
+ - service-type
+ properties:
+ service-type:
+ type: string
+ description: Value defined by orchestration to identify this service across ECOMP.
+ temp-ub-sub-account-id:
+ type: string
+ description: This property will be deleted from A&AI in the near future. Only stop gap solution.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ service-instances:
type: array
items:
- $ref: "#/definitions/ipsec-configuration"
- route-table-references:
+ $ref: "#/getDefinitions/service-instance"
+ relationship-list:
type: array
items:
- $ref: "#/definitions/route-table-reference"
- inventory:
- properties:
- search:
- type: object
- $ref: "#/definitions/search"
- actions:
- type: object
- $ref: "#/definitions/actions"
- cloud-infrastructure:
- type: object
- $ref: "#/definitions/cloud-infrastructure"
- business:
- type: object
- $ref: "#/definitions/business"
- service-design-and-creation:
- type: object
- $ref: "#/definitions/service-design-and-creation"
- network:
- type: object
- $ref: "#/definitions/network"
- aai-internal:
- type: object
- $ref: "#/definitions/aai-internal"
- edge-tag-query-result:
+ $ref: "#/getDefinitions/relationship"
+ service-subscriptions:
+ description: |
+ Collection of objects that group service instances.
properties:
- tagged-inventory-item-list:
+ service-subscription:
type: array
items:
- $ref: "#/definitions/tagged-inventory-item-list"
- tagged-inventory-item-list:
+ $ref: "#/getDefinitions/service-subscription"
+ services:
+ description: |
+ Collection of service model definitions. Likely to be deprecated in favor of models from ASDC.
properties:
- inventory-item:
+ service:
type: array
items:
- $ref: "#/definitions/inventory-item"
- inventory-item:
+ $ref: "#/getDefinitions/service"
+ site-pair:
+ description: |
+ ###### Related Nodes
+ - TO routing-instance( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)
+ - FROM class-of-service( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)
+ - SITE-PAIR is DELETED when these are DELETED CLASS-OF-SERVICE
+ required:
+ - site-pair-id
properties:
- inventory-item-type:
+ site-pair-id:
type: string
- inventory-item-link:
+ description: unique identifier of probe
+ source-ip:
type: string
- inventory-item-data:
+ description: Prefix address
+ destination-ip:
+ type: string
+ description: Prefix address
+ ip-version:
+ type: string
+ description: ip version, v4, v6
+ destination-hostname:
+ type: string
+ description: Hostname of the destination equipment to which SLAs are measured against.
+ destination-equip-type:
+ type: string
+ description: The type of destinatination equipment. Could be Router, etc.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ classes-of-service:
+ type: array
+ items:
+ $ref: "#/getDefinitions/class-of-service"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ site-pair-set:
+ description: |
+ Set of instances for probes used to measure service level agreements
+ ###### Related Nodes
+ - TO generic-vnf( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM routing-instance( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)
+ - SITE-PAIR-SET is DELETED when these are DELETED ROUTING-INSTANCE
+ required:
+ - site-pair-set-id
+ properties:
+ site-pair-set-id:
+ type: string
+ description: Unique id of site pair set.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ routing-instances:
+ type: array
+ items:
+ $ref: "#/getDefinitions/routing-instance"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ site-pair-sets:
+ description: |
+ Collection of sets of instances for probes related to generic-vnf
+ properties:
+ site-pair-set:
type: array
items:
- $ref: "#/definitions/inventory-item-data"
- tagged-inventory-item-list:
+ $ref: "#/getDefinitions/site-pair-set"
+ site-pairs:
+ description: |
+ probe within a set
+ properties:
+ site-pair:
type: array
items:
- $ref: "#/definitions/tagged-inventory-item-list"
- inventory-item-data:
+ $ref: "#/getDefinitions/site-pair"
+ snapshot:
+ description: |
+ Openstack snapshot
+ ###### Related Nodes
+ - TO cloud-region( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)
+ required:
+ - snapshot-id
properties:
- property-name:
+ snapshot-id:
type: string
- property-value:
+ description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
+ snapshot-name:
type: string
- edge-tag-query-request:
- properties:
- edge-tag:
+ description: Snapshot name
+ snapshot-architecture:
type: string
- result-detail:
+ description: Operating system architecture
+ snapshot-os-distro:
type: string
- start-node-type:
+ description: The common name of the operating system distribution in lowercase
+ snapshot-os-version:
type: string
- start-node-filter:
+ description: The operating system version as specified by the distributor.
+ application:
+ type: string
+ description: The application that the image instantiates.
+ application-vendor:
+ type: string
+ description: The vendor of the application.
+ application-version:
+ type: string
+ description: The version of the application.
+ snapshot-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ prev-snapshot-id:
+ type: string
+ description: This field contains the UUID of the previous snapshot (if any).
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ snapshots:
+ description: |
+ Collection of openstack snapshots
+ properties:
+ snapshot:
type: array
items:
- $ref: "#/definitions/start-node-filter"
- include-node-filter:
+ $ref: "#/getDefinitions/snapshot"
+ sriov-pf:
+ description: |
+ SR-IOV Physical Function
+ ###### Related Nodes
+ - TO p-interface( sriov-pf org.onap.relationships.inventory.BelongsTo p-interface, ONE2ONE)
+ - FROM sriov-vf( sriov-vf org.onap.relationships.inventory.Uses sriov-pf, MANY2ONE)
+ required:
+ - pf-pci-id
+ properties:
+ pf-pci-id:
+ type: string
+ description: Identifier for the sriov-pf
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ sriov-pfs:
+ description: |
+ Collection of SR-IOV Physical Functions.
+ properties:
+ sriov-pf:
type: array
items:
- $ref: "#/definitions/include-node-filter"
- secondary-filter:
+ $ref: "#/getDefinitions/sriov-pf"
+ sriov-vf:
+ description: |
+ SR-IOV Virtual Function (not to be confused with virtual network function)
+ ###### Related Nodes
+ - TO l-interface( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)
+ required:
+ - pci-id
+ properties:
+ pci-id:
+ type: string
+ description: PCI ID used to identify the sriov-vf
+ vf-vlan-filter:
+ type: string
+ description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM.
+ vf-mac-filter:
+ type: string
+ description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM.
+ vf-vlan-strip:
+ type: boolean
+ description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM.
+ vf-vlan-anti-spoof-check:
+ type: boolean
+ description: This option ensures anti VLAN spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
+ vf-mac-anti-spoof-check:
+ type: boolean
+ description: This option ensures anti MAC spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
+ vf-mirrors:
+ type: string
+ description: This option defines the set of Mirror objects which essentially mirrors the traffic from source to set of collector VNF Ports.
+ vf-broadcast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows all broadcast traffic to reach the VM
+ vf-unknown-multicast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows unknown multicast traffic to reach the VM
+ vf-unknown-unicast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows unknown unicast traffic to reach the VM
+ vf-insert-stag:
+ type: boolean
+ description: This option, if set to true, instructs to insert outer tag after traffic comes out of VM.
+ vf-link-status:
+ type: string
+ description: This option is used to set the link status. Valid values as of 1607 are on, off, and auto.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
+ type: string
+ description: Neutron network id of the interface
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ sriov-vfs:
+ description: |
+ Collection of SR-IOV Virtual Functions.
+ properties:
+ sriov-vf:
type: array
items:
- $ref: "#/definitions/secondary-filter"
+ $ref: "#/getDefinitions/sriov-vf"
start-node-filter:
properties:
property-name:
type: string
property-value:
type: string
- include-node-filter:
+ subnet:
+ description: |
+ ###### Related Nodes
+ - TO l3-network( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - SUBNET cannot be deleted if linked to L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST
+ required:
+ - subnet-id
+ - dhcp-enabled
properties:
- include-node-type:
+ subnet-id:
type: string
- secondary-filter:
- properties:
- property-name:
+ description: Subnet ID, should be UUID.
+ subnet-name:
type: string
- filter-type:
+ description: Name associated with the subnet.
+ neutron-subnet-id:
type: string
- property-value:
+ description: Neutron id of this subnet
+ gateway-address:
type: string
- search-results:
+ description: gateway ip address
+ network-start-address:
+ type: string
+ description: network start address
+ cidr-mask:
+ type: string
+ description: cidr mask
+ ip-version:
+ type: string
+ description: ip version
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ dhcp-enabled:
+ type: boolean
+ dhcp-start:
+ type: string
+ description: the start address reserved for use by dhcp
+ dhcp-end:
+ type: string
+ description: the last address reserved for use by dhcp
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ subnets:
properties:
- result-data:
+ subnet:
type: array
items:
- $ref: "#/definitions/result-data"
- result-data:
+ $ref: "#/getDefinitions/subnet"
+ tagged-inventory-item-list:
properties:
- resource-type:
+ inventory-item:
+ type: array
+ items:
+ $ref: "#/getDefinitions/inventory-item"
+ tenant:
+ description: |
+ Openstack tenant
+ ###### Related Nodes
+ - TO cloud-region( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO group-assignment( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)
+ - TO l3-network( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO volume-group( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - FROM service-subscription( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)
+ - FROM vserver( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)
+ - TENANT cannot be deleted if linked to VSERVER
+ required:
+ - tenant-id
+ - tenant-name
+ properties:
+ tenant-id:
type: string
- description: The specific type of node in the A&AI graph
- resource-link:
+ description: Unique id relative to the cloud-region.
+ tenant-name:
type: string
- description: The URL to the specific resource
- sdn-zone-response:
+ description: Readable name of tenant
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ vservers:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vserver"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ tenants:
+ description: |
+ Collection of openstack tenants.
properties:
- oam-networks:
- type: object
- $ref: "#/definitions/oam-networks"
- az-and-dvs-switches:
+ tenant:
type: array
items:
- $ref: "#/definitions/az-and-dvs-switches"
- az-and-dvs-switches:
+ $ref: "#/getDefinitions/tenant"
+ tunnel-xconnect:
+ description: |
+ Represents the specifics of a tunnel cross connect piece of a resource that gets separately allotted
+ ###### Related Nodes
+ - TO allotted-resource( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)
+ required:
+ - id
+ - bandwidth-up-wan1
+ - bandwidth-down-wan1
+ - bandwidth-up-wan2
+ - bandwidth-down-wan2
properties:
- dvs-switches:
- type: object
- $ref: "#/definitions/dvs-switches"
- availability-zone:
- type: object
- $ref: "#/definitions/availability-zone"
+ id:
+ type: string
+ description: Allotted Resource id UUID assigned to this instance.
+ bandwidth-up-wan1:
+ type: string
+ description: The WAN uplink bandwidth for WAN1
+ bandwidth-down-wan1:
+ type: string
+ description: The WAN downlink bandwidth for WAN1
+ bandwidth-up-wan2:
+ type: string
+ description: The WAN uplink bandwidth for WAN2
+ bandwidth-down-wan2:
+ type: string
+ description: The WAN downlink bandwidth for WAN2
+ resource-version:
+ type: string
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ tunnel-xconnects:
+ description: |
+ This object is used to store the specific tunnel cross connect aspects of an allotted resource
+ properties:
+ tunnel-xconnect:
+ type: array
+ items:
+ $ref: "#/getDefinitions/tunnel-xconnect"
update:
description: |
Serves a PATCH like function. Does not enforce concurrency control. Clear each usage with AAI team.
@@ -37463,209 +56779,747 @@ definitions:
update-node-key:
type: array
items:
- $ref: "#/definitions/update-node-key"
+ $ref: "#/getDefinitions/update-node-key"
update-node-uri:
type: string
action:
type: array
items:
- $ref: "#/definitions/action"
- action:
+ $ref: "#/getDefinitions/action"
+ update-node-key:
properties:
- action-type:
+ key-name:
type: string
- action-data:
+ key-value:
+ type: string
+ vce:
+ description: |
+ Virtual Customer Edge Router, used specifically for Gamma. This object is deprecated.
+ ###### Related Nodes
+ - TO availability-zone( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - TO complex( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)
+ - TO vserver( vce tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM port-group( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)
+ - VCE is DELETED when these are DELETED PORT-GROUP
+ required:
+ - vnf-id
+ - vnf-name
+ - vnf-type
+ properties:
+ vnf-id:
+ type: string
+ description: Unique id of VNF. This is unique across the graph.
+ vnf-name:
+ type: string
+ description: Name of VNF.
+ vnf-name2:
+ type: string
+ description: Alternate name of VNF.
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded and clients should expect changes to occur in the future to this field as ASDC matures.
+ service-id:
+ type: string
+ description: Unique identifier of service from ASDC. Expect this to change as ASDC matures.
+ regional-resource-zone:
+ type: string
+ description: Regional way of organizing pservers, source of truth should define values
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ operational-state:
+ type: string
+ description: Indicator for whether the resource is considered operational
+ license-key:
+ type: string
+ description: License key
+ equipment-role:
+ type: string
+ description: Network role being played by this VNF
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ vpe-id:
+ type: string
+ description: Unique ID of VPE connected to this VCE.
+ v6-vce-wan-address:
+ type: string
+ description: Valid v6 IP address for the WAN Link on this router. Implied length of /64.
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure vce, also used for troubleshooting and is IP used for traps generated by VCE.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ ipv4-loopback0-address:
+ type: string
+ description: Loopback0 address
+ entitlement-resource-uuid:
+ type: string
+ description: Entitlement resource uuid
+ port-groups:
+ type: array
+ items:
+ $ref: "#/getDefinitions/port-group"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ vces:
+ description: |
+ Collection of Virtual Customer Edge Routers, used specifically for Gamma. This object is deprecated.
+ properties:
+ vce:
type: array
items:
- $ref: "#/definitions/action-data"
- action-data:
+ $ref: "#/getDefinitions/vce"
+ vf-module:
+ description: |
+ a deployment unit of VNFCs
+ ###### Related Nodes
+ - TO generic-vnf( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO l3-network( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)
+ - TO vnfc( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)
+ - TO volume-group( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)
+ - TO vserver( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)
+ - VF-MODULE cannot be deleted if linked to VNFC
+ required:
+ - vf-module-id
+ - is-base-vf-module
properties:
- property-name:
+ vf-module-id:
type: string
- property-value:
+ description: Unique ID of vf-module.
+ vf-module-name:
type: string
- update-node-key:
- properties:
- key-name:
+ description: Name of vf-module
+ heat-stack-id:
type: string
- key-value:
+ description: Heat stack id corresponding to this instance.
+ orchestration-status:
type: string
- notify:
+ description: orchestration status of this vf-module, mastered by MSO
+ is-base-vf-module:
+ type: boolean
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ persona-model-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ contrail-service-instance-fqdn:
+ type: string
+ description: the Contrail unique ID for a service-instance
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ vf-modules:
+ description: |
+ Collection of vf-modules, a deployment unit of VNFCs
+ properties:
+ vf-module:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vf-module"
+ vig-server:
+ description: |
+ vig-server contains information about a vig server used for IPSec-configuration. Populated by SDN-C from 1607
+ ###### Related Nodes
+ - TO ipsec-configuration( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)
required:
- - event-id
+ - vig-address-type
properties:
- event-id:
+ vig-address-type:
type: string
- node-type:
+ description: indicates whether the VIG is for AVPN or INTERNET
+ ipaddress-v4-vig:
type: string
- event-trigger:
+ description: v4 IP of the vig server
+ ipaddress-v6-vig:
type: string
- key-data:
+ description: v6 IP of the vig server
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ vig-servers:
+ properties:
+ vig-server:
type: array
items:
- $ref: "#/definitions/key-data"
- selflink:
- type: string
- key-data:
+ $ref: "#/getDefinitions/vig-server"
+ vip-ipv4-address-list:
+ description: |
+ IPv4 Address Range
+ ###### Related Nodes
+ - TO cloud-region( vip-ipv4-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO instance-group( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO subnet( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv4-address-list, MANY2MANY)
+ required:
+ - vip-ipv4-address
properties:
- key-name:
+ vip-ipv4-address:
type: string
- key-value:
+ description: IP address
+ vip-ipv4-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 32 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ resource-version:
type: string
- notification-event:
- properties:
- cambria.partition:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
type: string
- notification-event-header:
- type: object
- $ref: "#/definitions/notification-event-header"
- notification-event-header:
+ description: Neutron network id of the interface that address belongs to
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of subnet that address belongs to
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ vip-ipv6-address-list:
+ description: |
+ IPv6 Address Range
+ ###### Related Nodes
+ - TO cloud-region( vip-ipv6-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO instance-group( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO subnet( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv6-address-list, MANY2MANY)
+ required:
+ - vip-ipv6-address
properties:
- id:
+ vip-ipv6-address:
type: string
- timestamp:
+ description: IP address
+ vip-ipv6-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 128 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ resource-version:
type: string
- source-name:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
type: string
- domain:
+ description: Neutron network id of the interface that address belongs to
+ neutron-subnet-id:
type: string
- sequence-number:
+ description: Neutron id of subnet that address belongs to
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ virtual-data-center:
+ description: |
+ Virtual organization of cloud infrastructure elements in a data center context
+ ###### Related Nodes
+ - FROM connector( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ required:
+ - vdc-id
+ - vdc-name
+ properties:
+ vdc-id:
type: string
- severity:
+ description: Unique ID of the vdc
+ vdc-name:
type: string
- event-type:
+ description: Name of the virtual data center
+ resource-version:
type: string
- version:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ virtual-data-centers:
+ description: |
+ Virtual organization of cloud infrastructure elements in a data center context
+ properties:
+ virtual-data-center:
+ type: array
+ items:
+ $ref: "#/getDefinitions/virtual-data-center"
+ vlan:
+ description: |
+ Definition of vlan
+ ###### Related Nodes
+ - TO l-interface( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)
+ - TO logical-link( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - TO multicast-configuration( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ - VLAN is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST
+ - VLAN deletion means associated objects of these types are also DELETED:LOGICAL-LINK
+ required:
+ - vlan-interface
+ properties:
+ vlan-interface:
type: string
- action:
+ description: String that identifies the interface
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ resource-version:
type: string
- entity-type:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ speed-value:
type: string
- top-entity-type:
+ description: Captures the numeric part of the speed
+ speed-units:
type: string
- entity-link:
+ description: Captures the units corresponding to the speed
+ vlan-description:
type: string
- status:
+ description: Used to describe (the service associated with) the vlan
+ backdoor-connection:
type: string
- reserved-prop-names:
+ description: Whether customer is going to use this VLAN for backdoor connection to another customer premise device.
+ vpn-id:
+ type: string
+ description: This indicates the customers VPN ID associated with this vlan
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ l3-interface-ipv4-address-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
+ l3-interface-ipv6-address-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
+ vlans:
+ properties:
+ vlan:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vlan"
+ vnf:
description: |
- Internal map to define some reserved properties of a vertex
+ Abstract vnf class
+ required:
+ - vnf-id
properties:
- last-mod-source-of-truth:
+ vnf-id:
type: string
- aai-node-type:
+ description: Unique id of VNF. This is unique across the graph.
+ vnf-image:
+ description: |
+ Image object that pertain to a VNF that doesn't have associated vservers. This is a kludge.
+ ###### Related Nodes
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)
+ - VNF-IMAGE cannot be deleted if linked to GENERIC-VNF
+ required:
+ - vnf-image-uuid
+ - application
+ - application-vendor
+ properties:
+ vnf-image-uuid:
type: string
- aai-created-ts:
- type: integer
- format: int64
- aai-unique-key:
+ description: Unique ID of this asset
+ application:
type: string
- aai-last-mod-ts:
- type: integer
- format: int64
- source-of-truth:
+ description: The application that the image instantiates.
+ application-vendor:
type: string
- edge-prop-names:
+ description: The vendor of the application.
+ application-version:
+ type: string
+ description: The version of the application.
+ selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ vnf-images:
description: |
- Internal map to define the properties of an edge and interpret the map EdgeRules
+ Collection of image objects that pertain to a VNF that doesn't have associated vservers. This is a kludge.
properties:
- edgeLabel:
+ vnf-image:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vnf-image"
+ vnfc:
+ description: |
+ ###### Related Nodes
+ - TO generic-vnf( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vserver( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)
+ required:
+ - vnfc-name
+ - vnfc-function-code
+ - vnfc-type
+ - in-maint
+ - is-closed-loop-disabled
+ properties:
+ vnfc-name:
type: string
- direction:
+ description: Unique ID of vnfc.
+ vnfc-function-code:
type: string
- multiplicityRule:
+ description: function code
+ vnfc-type:
type: string
- isParent:
- type: boolean
- usesResource:
- type: boolean
- hasDelTarget:
- type: boolean
- SVC-INFRA:
+ description: type
+ prov-status:
+ type: string
+ description: prov status of this vnfc
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by APP-C
+ ipaddress-v4-oam-vip:
+ type: string
+ description: Oam V4 vip address of this vnfc
+ in-maint:
type: boolean
- SVC-INFRA-REV:
+ is-closed-loop-disabled:
type: boolean
- model-and-named-query-search:
+ group-notation:
+ type: string
+ description: Group notation of VNFC
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ vnfcs:
description: |
- ModelAndNamedQuerySearch holds query-parameters and instance-properties for performing a named-query or model query
+ virtual network components associated with a vserver from application controller.
properties:
- query-parameters:
- type: object
- $ref: "#/definitions/query-parameters"
- instance-filters:
- type: object
- $ref: "#/definitions/instance-filters"
- top-node-type:
+ vnfc:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vnfc"
+ volume:
+ description: |
+ Ephemeral Block storage volume.
+ ###### Related Nodes
+ - FROM vserver (PARENT of volume, vserver tosca.relationships.AttachesTo volume)
+ required:
+ - volume-id
+ - volume-selflink
+ properties:
+ volume-id:
type: string
- query-parameters:
+ description: Unique ID of block storage volume relative to the vserver.
+ volume-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ volume-group:
description: |
- QueryParameters for performing a named-query or model query
+ Persistent block-level storage.
+ ###### Related Nodes
+ - TO cloud-region( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO complex( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ required:
+ - volume-group-id
+ - volume-group-name
+ - vnf-type
properties:
- named-query:
- type: object
- $ref: "#/definitions/named-query"
- model:
- type: object
- $ref: "#/definitions/model"
- instance-filters:
+ volume-group-id:
+ type: string
+ description: Unique ID of volume-group.
+ volume-group-name:
+ type: string
+ description: Name of the volume group.
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this volume-group
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded and clients should expect changes to occur in the future to this field as ASDC matures.
+ orchestration-status:
+ type: string
+ description: Orchestration status of this volume-group
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ volume-groups:
description: |
- InstanceFilters for performing a named-query or model query
+ Collection of persistent block-level storage.
properties:
- instance-filter:
+ volume-group:
type: array
items:
- $ref: "#/definitions/instance-filter"
- instance-filter:
+ $ref: "#/getDefinitions/volume-group"
+ volumes:
description: |
- InstanceFilter for performing a named-query or model query
- properties:
+ Collection of ephemeral Block storage volumes.
+ properties:
+ volume:
+ type: array
+ items:
+ $ref: "#/getDefinitions/volume"
+ vpls-pe:
description: |
- Property holder for query properties or instance properties
+ VPLS Provider Edge routers.
+ ###### Related Nodes
+ - TO complex( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO ctag-pool( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - VPLS-PE is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
+ required:
+ - equipment-name
properties:
- property-name:
+ equipment-name:
type: string
- property-value:
+ prov-status:
type: string
- response-list:
+ description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address).
+ equipment-role:
+ type: string
+ description: Client should send valid enumerated value, e.g., VPLS-PE.
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Temporary location for stag to get to VCE
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ p-interfaces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/p-interface"
+ lag-interfaces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/lag-interface"
+ vpls-pes:
description: |
- Response container for the results of a named-query or model query
+ Collection of VPLS Provider Edge routers
properties:
- inventory-response-items:
- type: object
- $ref: "#/definitions/inventory-response-items"
- inventory-response-items:
+ vpls-pe:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vpls-pe"
+ vpn-binding:
description: |
- Container for inventory items in response list
+ VPN binding
+ ###### Related Nodes
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - VPN-BINDING cannot be deleted if linked to L3-NETWORK
+ required:
+ - vpn-id
+ - vpn-name
+ - global-route-target
properties:
- inventory-response-item:
+ vpn-id:
+ type: string
+ description: VPN ID, globally unique within A&AI
+ vpn-name:
+ type: string
+ description: VPN Name
+ global-route-target:
+ type: string
+ description: Number used to identify a VPN, globally unique in the network
+ vpn-platform:
+ type: string
+ description: the platform associated with the VPN example AVPN, Mobility
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ description: l3-networks relate to vpn-bindings
+ vpn-bindings:
+ properties:
+ vpn-binding:
type: array
items:
- $ref: "#/definitions/inventory-response-item"
- inventory-response-item:
+ $ref: "#/getDefinitions/vpn-binding"
+ vserver:
description: |
- Inventory item for response list
+ Virtual Servers, aka virtual machine or VM.
+ ###### Related Nodes
+ - TO tenant( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)
+ - TO flavor( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)
+ - TO image( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)
+ - TO pserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)
+ - TO snapshot( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)
+ - TO volume (CHILD of vserver, vserver tosca.relationships.AttachesTo volume, ONE2MANY)
+ - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM vce( vce tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)
+ - FROM vnfc( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)
+ - VSERVER is DELETED when these are DELETED L-INTERFACE
+ - VSERVER deletion means associated objects of these types are also DELETED:VOLUME
+ required:
+ - vserver-id
+ - vserver-name
+ - vserver-selflink
+ - in-maint
+ - is-closed-loop-disabled
properties:
- model-name:
+ vserver-id:
type: string
- extra-properties:
- type: object
- $ref: "#/definitions/extra-properties"
- inventory-response-items:
- type: object
- $ref: "#/definitions/inventory-response-items"
- extra-properties:
+ description: Unique identifier for this vserver relative to its tenant
+ vserver-name:
+ type: string
+ description: Name of vserver
+ vserver-name2:
+ type: string
+ description: Alternative name of vserver
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ vserver-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ volumes:
+ type: array
+ items:
+ $ref: "#/getDefinitions/volume"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l-interface"
+ vservers:
description: |
- Extra properties for inventory item for response list
- extra-property:
+ Collection of virtual Servers, aka virtual machines or VMs.
properties:
- property-name:
- type: string
- vnf:
+ vserver:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vserver"
+ zone:
description: |
- Abstract vnf class
+ A zone is a grouping of assets in a location homing to the same connections into the CBB
+ ###### Related Nodes
+ - TO complex( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM pnf( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
required:
- - vnf-id
+ - zone-id
+ - zone-name
+ - design-type
+ - zone-context
properties:
- vnf-id:
+ zone-id:
type: string
- description: Unique id of VNF. This is unique across the graph.
+ description: Code assigned by AIC to the zone
+ zone-name:
+ type: string
+ description: English name associated with the zone
+ design-type:
+ type: string
+ description: Design of zone [Medium/Large?]
+ zone-context:
+ type: string
+ description: Context of zone [production/test]
+ status:
+ type: string
+ description: Status of a zone.
+ resource-version:
+ type: string
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ zones:
+ description: |
+ Collection of zones
+ properties:
+ zone:
+ type: array
+ items:
+ $ref: "#/getDefinitions/zone"
diff --git a/aai-schema/src/main/resources/aai_swagger_yaml/aai_swagger_v9.yaml b/aai-schema/src/main/resources/aai_swagger_yaml/aai_swagger_v9.yaml
index 905c350b..a793e1b2 100644
--- a/aai-schema/src/main/resources/aai_swagger_yaml/aai_swagger_v9.yaml
+++ b/aai-schema/src/main/resources/aai_swagger_yaml/aai_swagger_v9.yaml
@@ -1,28 +1,9 @@
-#
-# ============LICENSE_START=======================================================
-# org.onap.aai
-# ================================================================================
-# Copyright © 2017 AT&T Intellectual Property. All rights reserved.
-# ================================================================================
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-# http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-# ============LICENSE_END=========================================================
-#
-# ECOMP is a trademark and service mark of AT&T Intellectual Property.
-#
-
swagger: "2.0"
info:
description: |
+
+ [Differences versus the previous schema version](apidocs/aai_swagger_v9.diff)
+
Copyright &copy; 2017 AT&amp;T Intellectual Property. All rights reserved.
Licensed under the Creative Commons License, Attribution 4.0 Intl. (the &quot;License&quot;); you may not use this documentation except in compliance with the License.
@@ -71,19 +52,22 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: target-pe
in: path
description: The Target provider edge router
required: true
type: string
+ example: __TARGET-PE__
- name: availability-zone-name
in: path
description: Name of the availability zone
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureComplexesComplexCtagPoolsCtagPool.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -108,16 +92,19 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: target-pe
in: path
description: The Target provider edge router
required: true
type: string
+ example: __TARGET-PE__
- name: availability-zone-name
in: path
description: Name of the availability zone
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
/cloud-infrastructure/complexes/complex/{physical-location-id}/ctag-pools/ctag-pool/{target-pe}/{availability-zone-name}:
get:
tags:
@@ -132,7 +119,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/ctag-pool"
+ $ref: "#/getDefinitions/ctag-pool"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -141,16 +128,19 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: target-pe
in: path
description: The Target provider edge router
required: true
type: string
+ example: __TARGET-PE__
- name: availability-zone-name
in: path
description: Name of the availability zone
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: data-center-code
in: query
description: Data center code which can be an alternate way to identify a complex
@@ -170,7 +160,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing ctag-pool
- description: create or update an existing ctag-pool
+ description: |
+ Create or update an existing ctag-pool.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureComplexesComplexCtagPoolsCtagPool
consumes:
- application/json
@@ -187,22 +180,76 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: target-pe
in: path
description: The Target provider edge router
required: true
type: string
+ example: __TARGET-PE__
- name: availability-zone-name
in: path
description: Name of the availability zone
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: body
in: body
- description: ctag-pool object that needs to be created or updated
+ description: ctag-pool object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureComplexesComplexCtagPoolsCtagPool.json)
required: true
schema:
$ref: "#/definitions/ctag-pool"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing ctag-pool
+ description: |
+ Update an existing ctag-pool
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureComplexesComplexCtagPoolsCtagPool
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: physical-location-id
+ in: path
+ description: Unique identifier for physical location, e.g., CLLI
+ required: true
+ type: string
+ example: __PHYSICAL-LOCATION-ID__
+ - name: target-pe
+ in: path
+ description: The Target provider edge router
+ required: true
+ type: string
+ example: __TARGET-PE__
+ - name: availability-zone-name
+ in: path
+ description: Name of the availability zone
+ required: true
+ type: string
+ example: __AVAILABILITY-ZONE-NAME__
+ - name: body
+ in: body
+ description: ctag-pool object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/ctag-pool"
delete:
tags:
- CloudInfrastructure
@@ -224,16 +271,19 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: target-pe
in: path
description: The Target provider edge router
required: true
type: string
+ example: __TARGET-PE__
- name: availability-zone-name
in: path
description: Name of the availability zone
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -253,7 +303,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/ctag-pools"
+ $ref: "#/getDefinitions/ctag-pools"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -262,6 +312,7 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: data-center-code
in: query
description: Data center code which can be an alternate way to identify a complex
@@ -298,9 +349,10 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureComplexesComplex.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -325,6 +377,7 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
/cloud-infrastructure/complexes/complex/{physical-location-id}:
get:
tags:
@@ -339,7 +392,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/complex"
+ $ref: "#/getDefinitions/complex"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -348,6 +401,7 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: data-center-code
in: query
description: Data center code which can be an alternate way to identify a complex
@@ -367,7 +421,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing complex
- description: create or update an existing complex
+ description: |
+ Create or update an existing complex.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureComplexesComplex
consumes:
- application/json
@@ -384,12 +441,52 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: body
in: body
- description: complex object that needs to be created or updated
+ description: complex object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureComplexesComplex.json)
required: true
schema:
$ref: "#/definitions/complex"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing complex
+ description: |
+ Update an existing complex
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureComplexesComplex
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: physical-location-id
+ in: path
+ description: Unique identifier for physical location, e.g., CLLI
+ required: true
+ type: string
+ example: __PHYSICAL-LOCATION-ID__
+ - name: body
+ in: body
+ description: complex object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/complex"
delete:
tags:
- CloudInfrastructure
@@ -411,6 +508,7 @@ paths:
description: Unique identifier for physical location, e.g., CLLI
required: true
type: string
+ example: __PHYSICAL-LOCATION-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -430,7 +528,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/complexes"
+ $ref: "#/getDefinitions/complexes"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/volume-groups/volume-group/{volume-group-id}/relationship-list/relationship:
@@ -454,19 +552,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: volume-group-id
in: path
description: Unique ID of volume-group.
required: true
type: string
+ example: __VOLUME-GROUP-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -491,16 +592,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: volume-group-id
in: path
description: Unique ID of volume-group.
required: true
type: string
+ example: __VOLUME-GROUP-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/volume-groups/volume-group/{volume-group-id}:
get:
tags:
@@ -515,7 +619,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/volume-group"
+ $ref: "#/getDefinitions/volume-group"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -524,16 +628,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: volume-group-id
in: path
description: Unique ID of volume-group.
required: true
type: string
+ example: __VOLUME-GROUP-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -563,7 +670,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing volume-group
- description: create or update an existing volume-group
+ description: |
+ Create or update an existing volume-group.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup
consumes:
- application/json
@@ -580,22 +690,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: volume-group-id
in: path
description: Unique ID of volume-group.
required: true
type: string
+ example: __VOLUME-GROUP-ID__
- name: body
in: body
- description: volume-group object that needs to be created or updated
+ description: volume-group object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup.json)
required: true
schema:
$ref: "#/definitions/volume-group"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing volume-group
+ description: |
+ Update an existing volume-group
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: volume-group-id
+ in: path
+ description: Unique ID of volume-group.
+ required: true
+ type: string
+ example: __VOLUME-GROUP-ID__
+ - name: body
+ in: body
+ description: volume-group object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/volume-group"
delete:
tags:
- CloudInfrastructure
@@ -617,16 +781,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: volume-group-id
in: path
description: Unique ID of volume-group.
required: true
type: string
+ example: __VOLUME-GROUP-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -646,7 +813,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/volume-groups"
+ $ref: "#/getDefinitions/volume-groups"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -655,11 +822,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -691,29 +860,34 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: volume-id
in: path
description: Unique ID of block storage volume relative to the vserver.
required: true
type: string
+ example: __VOLUME-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -738,26 +912,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: volume-id
in: path
description: Unique ID of block storage volume relative to the vserver.
required: true
type: string
+ example: __VOLUME-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/volumes/volume/{volume-id}:
get:
tags:
@@ -772,7 +951,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/volume"
+ $ref: "#/getDefinitions/volume"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -781,26 +960,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: volume-id
in: path
description: Unique ID of block storage volume relative to the vserver.
required: true
type: string
+ example: __VOLUME-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -843,7 +1027,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing volume
- description: create or update an existing volume
+ description: |
+ Create or update an existing volume.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume
consumes:
- application/json
@@ -860,32 +1047,100 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: volume-id
in: path
description: Unique ID of block storage volume relative to the vserver.
required: true
type: string
+ example: __VOLUME-ID__
- name: body
in: body
- description: volume object that needs to be created or updated
+ description: volume object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume.json)
required: true
schema:
$ref: "#/definitions/volume"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing volume
+ description: |
+ Update an existing volume
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: volume-id
+ in: path
+ description: Unique ID of block storage volume relative to the vserver.
+ required: true
+ type: string
+ example: __VOLUME-ID__
+ - name: body
+ in: body
+ description: volume object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/volume"
delete:
tags:
- CloudInfrastructure
@@ -907,26 +1162,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: volume-id
in: path
description: Unique ID of block storage volume relative to the vserver.
required: true
type: string
+ example: __VOLUME-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -946,7 +1206,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/volumes"
+ $ref: "#/getDefinitions/volumes"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -955,21 +1215,25 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -1029,24 +1293,28 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -1071,21 +1339,25 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -1107,34 +1379,40 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -1159,31 +1437,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -1205,39 +1489,46 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -1262,36 +1553,43 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -1306,7 +1604,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -1315,36 +1613,43 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -1429,7 +1734,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -1446,42 +1754,124 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- CloudInfrastructure
@@ -1503,36 +1893,43 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -1559,39 +1956,46 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -1616,36 +2020,43 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -1660,7 +2071,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -1669,36 +2080,43 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -1783,7 +2201,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -1800,42 +2221,124 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- CloudInfrastructure
@@ -1857,36 +2360,43 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -1906,7 +2416,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -1915,31 +2425,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -2008,7 +2524,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -2025,37 +2544,112 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- CloudInfrastructure
@@ -2077,31 +2671,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -2121,7 +2721,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -2130,26 +2730,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -2224,34 +2829,40 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -2276,31 +2887,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -2315,7 +2932,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -2324,31 +2941,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -2426,7 +3049,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -2443,37 +3069,112 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- CloudInfrastructure
@@ -2495,31 +3196,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -2539,7 +3246,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -2548,26 +3255,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -2642,29 +3354,34 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -2689,26 +3406,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -2730,34 +3452,40 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -2782,31 +3510,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -2821,7 +3555,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -2830,31 +3564,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -2928,7 +3668,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -2945,37 +3688,112 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- CloudInfrastructure
@@ -2997,31 +3815,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -3048,34 +3872,40 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -3100,31 +3930,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -3139,7 +3975,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -3148,31 +3984,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -3246,7 +4088,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -3263,37 +4108,112 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- CloudInfrastructure
@@ -3315,31 +4235,37 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -3359,7 +4285,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -3368,26 +4294,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -3445,7 +4376,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface
consumes:
- application/json
@@ -3462,32 +4396,100 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- CloudInfrastructure
@@ -3509,26 +4511,31 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -3548,7 +4555,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -3557,21 +4564,25 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -3624,7 +4635,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vserver"
+ $ref: "#/getDefinitions/vserver"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -3633,21 +4644,25 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -3690,7 +4705,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing vserver
- description: create or update an existing vserver
+ description: |
+ Create or update an existing vserver.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver
consumes:
- application/json
@@ -3707,27 +4725,88 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: body
in: body
- description: vserver object that needs to be created or updated
+ description: vserver object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver.json)
required: true
schema:
$ref: "#/definitions/vserver"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing vserver
+ description: |
+ Update an existing vserver
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: vserver-id
+ in: path
+ description: Unique identifier for this vserver relative to its tenant
+ required: true
+ type: string
+ example: __VSERVER-ID__
+ - name: body
+ in: body
+ description: vserver object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vserver"
delete:
tags:
- CloudInfrastructure
@@ -3749,21 +4828,25 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: vserver-id
in: path
description: Unique identifier for this vserver relative to its tenant
required: true
type: string
+ example: __VSERVER-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -3783,7 +4866,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vservers"
+ $ref: "#/getDefinitions/vservers"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -3792,16 +4875,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -3838,19 +4924,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenant.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -3875,16 +4964,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}:
get:
tags:
@@ -3899,7 +4991,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/tenant"
+ $ref: "#/getDefinitions/tenant"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -3908,16 +5000,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -3937,7 +5032,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing tenant
- description: create or update an existing tenant
+ description: |
+ Create or update an existing tenant.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenant
consumes:
- application/json
@@ -3954,22 +5052,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: body
in: body
- description: tenant object that needs to be created or updated
+ description: tenant object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionTenantsTenant.json)
required: true
schema:
$ref: "#/definitions/tenant"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing tenant
+ description: |
+ Update an existing tenant
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenant
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: tenant-id
+ in: path
+ description: Unique id relative to the cloud-region.
+ required: true
+ type: string
+ example: __TENANT-ID__
+ - name: body
+ in: body
+ description: tenant object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/tenant"
delete:
tags:
- CloudInfrastructure
@@ -3991,16 +5143,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: tenant-id
in: path
description: Unique id relative to the cloud-region.
required: true
type: string
+ example: __TENANT-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -4020,7 +5175,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/tenants"
+ $ref: "#/getDefinitions/tenants"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4029,11 +5184,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4065,19 +5222,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: flavor-id
in: path
description: Flavor id, expected to be unique across cloud-region.
required: true
type: string
+ example: __FLAVOR-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -4102,16 +5262,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: flavor-id
in: path
description: Flavor id, expected to be unique across cloud-region.
required: true
type: string
+ example: __FLAVOR-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/flavors/flavor/{flavor-id}:
get:
tags:
@@ -4126,7 +5289,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/flavor"
+ $ref: "#/getDefinitions/flavor"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4135,16 +5298,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: flavor-id
in: path
description: Flavor id, expected to be unique across cloud-region.
required: true
type: string
+ example: __FLAVOR-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4164,7 +5330,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing flavor
- description: create or update an existing flavor
+ description: |
+ Create or update an existing flavor.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor
consumes:
- application/json
@@ -4181,22 +5350,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: flavor-id
in: path
description: Flavor id, expected to be unique across cloud-region.
required: true
type: string
+ example: __FLAVOR-ID__
- name: body
in: body
- description: flavor object that needs to be created or updated
+ description: flavor object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor.json)
required: true
schema:
$ref: "#/definitions/flavor"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing flavor
+ description: |
+ Update an existing flavor
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: flavor-id
+ in: path
+ description: Flavor id, expected to be unique across cloud-region.
+ required: true
+ type: string
+ example: __FLAVOR-ID__
+ - name: body
+ in: body
+ description: flavor object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/flavor"
delete:
tags:
- CloudInfrastructure
@@ -4218,16 +5441,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: flavor-id
in: path
description: Flavor id, expected to be unique across cloud-region.
required: true
type: string
+ example: __FLAVOR-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -4247,7 +5473,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/flavors"
+ $ref: "#/getDefinitions/flavors"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4256,11 +5482,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4292,19 +5520,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: group-id
in: path
description: Group id, expected to be unique across cloud-region.
required: true
type: string
+ example: __GROUP-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -4329,16 +5560,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: group-id
in: path
description: Group id, expected to be unique across cloud-region.
required: true
type: string
+ example: __GROUP-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/group-assignments/group-assignment/{group-id}:
get:
tags:
@@ -4353,7 +5587,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/group-assignment"
+ $ref: "#/getDefinitions/group-assignment"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4362,16 +5596,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: group-id
in: path
description: Group id, expected to be unique across cloud-region.
required: true
type: string
+ example: __GROUP-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4396,7 +5633,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing group-assignment
- description: create or update an existing group-assignment
+ description: |
+ Create or update an existing group-assignment.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment
consumes:
- application/json
@@ -4413,22 +5653,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: group-id
in: path
description: Group id, expected to be unique across cloud-region.
required: true
type: string
+ example: __GROUP-ID__
- name: body
in: body
- description: group-assignment object that needs to be created or updated
+ description: group-assignment object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment.json)
required: true
schema:
$ref: "#/definitions/group-assignment"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing group-assignment
+ description: |
+ Update an existing group-assignment
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: group-id
+ in: path
+ description: Group id, expected to be unique across cloud-region.
+ required: true
+ type: string
+ example: __GROUP-ID__
+ - name: body
+ in: body
+ description: group-assignment object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/group-assignment"
delete:
tags:
- CloudInfrastructure
@@ -4450,16 +5744,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: group-id
in: path
description: Group id, expected to be unique across cloud-region.
required: true
type: string
+ example: __GROUP-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -4479,7 +5776,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/group-assignments"
+ $ref: "#/getDefinitions/group-assignments"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4488,11 +5785,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4524,19 +5823,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: snapshot-id
in: path
description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
required: true
type: string
+ example: __SNAPSHOT-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -4561,16 +5863,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: snapshot-id
in: path
description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
required: true
type: string
+ example: __SNAPSHOT-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/snapshots/snapshot/{snapshot-id}:
get:
tags:
@@ -4585,7 +5890,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/snapshot"
+ $ref: "#/getDefinitions/snapshot"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4594,16 +5899,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: snapshot-id
in: path
description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
required: true
type: string
+ example: __SNAPSHOT-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4643,7 +5951,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing snapshot
- description: create or update an existing snapshot
+ description: |
+ Create or update an existing snapshot.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot
consumes:
- application/json
@@ -4660,22 +5971,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: snapshot-id
in: path
description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
required: true
type: string
+ example: __SNAPSHOT-ID__
- name: body
in: body
- description: snapshot object that needs to be created or updated
+ description: snapshot object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot.json)
required: true
schema:
$ref: "#/definitions/snapshot"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing snapshot
+ description: |
+ Update an existing snapshot
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: snapshot-id
+ in: path
+ description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
+ required: true
+ type: string
+ example: __SNAPSHOT-ID__
+ - name: body
+ in: body
+ description: snapshot object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/snapshot"
delete:
tags:
- CloudInfrastructure
@@ -4697,16 +6062,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: snapshot-id
in: path
description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
required: true
type: string
+ example: __SNAPSHOT-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -4726,7 +6094,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/snapshots"
+ $ref: "#/getDefinitions/snapshots"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4735,11 +6103,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4771,19 +6141,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionImagesImage.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -4808,16 +6181,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}/metadata/metadatum/{metaname}:
get:
tags:
@@ -4832,7 +6208,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadatum"
+ $ref: "#/getDefinitions/metadatum"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4841,20 +6217,24 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -4889,7 +6269,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing metadatum
- description: create or update an existing metadatum
+ description: |
+ Create or update an existing metadatum.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionImagesImageMetadataMetadatum
consumes:
- application/json
@@ -4906,26 +6289,86 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: body
in: body
- description: metadatum object that needs to be created or updated
+ description: metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionImagesImageMetadataMetadatum.json)
required: true
schema:
$ref: "#/definitions/metadatum"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing metadatum
+ description: |
+ Update an existing metadatum
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionImagesImageMetadataMetadatum
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: image-id
+ in: path
+ description: Image id, expected to be unique across cloud region
+ required: true
+ type: string
+ example: __IMAGE-ID__
+ - name: metaname
+ in: path
+ required: true
+ type: string
+ example: __METANAME__
+ - name: body
+ in: body
+ description: metadatum object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/metadatum"
delete:
tags:
- CloudInfrastructure
@@ -4947,20 +6390,24 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -4980,7 +6427,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadata"
+ $ref: "#/getDefinitions/metadata"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -4989,16 +6436,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5043,7 +6493,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/image"
+ $ref: "#/getDefinitions/image"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5052,16 +6502,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5096,7 +6549,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing image
- description: create or update an existing image
+ description: |
+ Create or update an existing image.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionImagesImage
consumes:
- application/json
@@ -5113,22 +6569,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: body
in: body
- description: image object that needs to be created or updated
+ description: image object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionImagesImage.json)
required: true
schema:
$ref: "#/definitions/image"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing image
+ description: |
+ Update an existing image
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionImagesImage
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: image-id
+ in: path
+ description: Image id, expected to be unique across cloud region
+ required: true
+ type: string
+ example: __IMAGE-ID__
+ - name: body
+ in: body
+ description: image object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/image"
delete:
tags:
- CloudInfrastructure
@@ -5150,16 +6660,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: image-id
in: path
description: Image id, expected to be unique across cloud region
required: true
type: string
+ example: __IMAGE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -5179,7 +6692,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/images"
+ $ref: "#/getDefinitions/images"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5188,11 +6701,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5224,19 +6739,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: switch-name
in: path
description: DVS switch name
required: true
type: string
+ example: __SWITCH-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -5261,16 +6779,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: switch-name
in: path
description: DVS switch name
required: true
type: string
+ example: __SWITCH-NAME__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/dvs-switches/dvs-switch/{switch-name}:
get:
tags:
@@ -5285,7 +6806,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/dvs-switch"
+ $ref: "#/getDefinitions/dvs-switch"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5294,16 +6815,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: switch-name
in: path
description: DVS switch name
required: true
type: string
+ example: __SWITCH-NAME__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5323,7 +6847,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing dvs-switch
- description: create or update an existing dvs-switch
+ description: |
+ Create or update an existing dvs-switch.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch
consumes:
- application/json
@@ -5340,22 +6867,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: switch-name
in: path
description: DVS switch name
required: true
type: string
+ example: __SWITCH-NAME__
- name: body
in: body
- description: dvs-switch object that needs to be created or updated
+ description: dvs-switch object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch.json)
required: true
schema:
$ref: "#/definitions/dvs-switch"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing dvs-switch
+ description: |
+ Update an existing dvs-switch
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: switch-name
+ in: path
+ description: DVS switch name
+ required: true
+ type: string
+ example: __SWITCH-NAME__
+ - name: body
+ in: body
+ description: dvs-switch object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/dvs-switch"
delete:
tags:
- CloudInfrastructure
@@ -5377,16 +6958,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: switch-name
in: path
description: DVS switch name
required: true
type: string
+ example: __SWITCH-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -5406,7 +6990,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/dvs-switches"
+ $ref: "#/getDefinitions/dvs-switches"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5415,11 +6999,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5451,19 +7037,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: network-uuid
in: path
description: UUID of the network. Unique across a cloud-region
required: true
type: string
+ example: __NETWORK-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -5488,16 +7077,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: network-uuid
in: path
description: UUID of the network. Unique across a cloud-region
required: true
type: string
+ example: __NETWORK-UUID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/oam-networks/oam-network/{network-uuid}:
get:
tags:
@@ -5512,7 +7104,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/oam-network"
+ $ref: "#/getDefinitions/oam-network"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5521,16 +7113,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: network-uuid
in: path
description: UUID of the network. Unique across a cloud-region
required: true
type: string
+ example: __NETWORK-UUID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5556,7 +7151,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing oam-network
- description: create or update an existing oam-network
+ description: |
+ Create or update an existing oam-network.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork
consumes:
- application/json
@@ -5573,22 +7171,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: network-uuid
in: path
description: UUID of the network. Unique across a cloud-region
required: true
type: string
+ example: __NETWORK-UUID__
- name: body
in: body
- description: oam-network object that needs to be created or updated
+ description: oam-network object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork.json)
required: true
schema:
$ref: "#/definitions/oam-network"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing oam-network
+ description: |
+ Update an existing oam-network
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: network-uuid
+ in: path
+ description: UUID of the network. Unique across a cloud-region
+ required: true
+ type: string
+ example: __NETWORK-UUID__
+ - name: body
+ in: body
+ description: oam-network object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/oam-network"
delete:
tags:
- CloudInfrastructure
@@ -5610,16 +7262,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: network-uuid
in: path
description: UUID of the network. Unique across a cloud-region
required: true
type: string
+ example: __NETWORK-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -5639,7 +7294,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/oam-networks"
+ $ref: "#/getDefinitions/oam-networks"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5648,11 +7303,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5684,19 +7341,22 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: availability-zone-name
in: path
description: Name of the availability zone. Unique across a cloud region
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -5721,16 +7381,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: availability-zone-name
in: path
description: Name of the availability zone. Unique across a cloud region
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/availability-zones/availability-zone/{availability-zone-name}:
get:
tags:
@@ -5745,7 +7408,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/availability-zone"
+ $ref: "#/getDefinitions/availability-zone"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5754,16 +7417,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: availability-zone-name
in: path
description: Name of the availability zone. Unique across a cloud region
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5778,7 +7444,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing availability-zone
- description: create or update an existing availability-zone
+ description: |
+ Create or update an existing availability-zone.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone
consumes:
- application/json
@@ -5795,22 +7464,76 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: availability-zone-name
in: path
description: Name of the availability zone. Unique across a cloud region
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: body
in: body
- description: availability-zone object that needs to be created or updated
+ description: availability-zone object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone.json)
required: true
schema:
$ref: "#/definitions/availability-zone"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing availability-zone
+ description: |
+ Update an existing availability-zone
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: availability-zone-name
+ in: path
+ description: Name of the availability zone. Unique across a cloud region
+ required: true
+ type: string
+ example: __AVAILABILITY-ZONE-NAME__
+ - name: body
+ in: body
+ description: availability-zone object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/availability-zone"
delete:
tags:
- CloudInfrastructure
@@ -5832,16 +7555,19 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: availability-zone-name
in: path
description: Name of the availability zone. Unique across a cloud region
required: true
type: string
+ example: __AVAILABILITY-ZONE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -5861,7 +7587,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/availability-zones"
+ $ref: "#/getDefinitions/availability-zones"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5870,11 +7596,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5906,14 +7634,16 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegion.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -5938,11 +7668,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}:
get:
tags:
@@ -5957,7 +7689,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/cloud-region"
+ $ref: "#/getDefinitions/cloud-region"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -5966,11 +7698,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: cloud-type
in: query
description: Type of the cloud (e.g., openstack)
@@ -5985,7 +7719,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing cloud-region
- description: create or update an existing cloud-region
+ description: |
+ Create or update an existing cloud-region.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegion
consumes:
- application/json
@@ -6002,17 +7739,64 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: body
in: body
- description: cloud-region object that needs to be created or updated
+ description: cloud-region object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureCloudRegionsCloudRegion.json)
required: true
schema:
$ref: "#/definitions/cloud-region"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing cloud-region
+ description: |
+ Update an existing cloud-region
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureCloudRegionsCloudRegion
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: cloud-owner
+ in: path
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ required: true
+ type: string
+ example: __CLOUD-OWNER__
+ - name: cloud-region-id
+ in: path
+ description: Identifier used by the vendor for the region. Second part of composite key
+ required: true
+ type: string
+ example: __CLOUD-REGION-ID__
+ - name: body
+ in: body
+ description: cloud-region object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/cloud-region"
delete:
tags:
- CloudInfrastructure
@@ -6034,11 +7818,13 @@ paths:
description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
required: true
type: string
+ example: __CLOUD-OWNER__
- name: cloud-region-id
in: path
description: Identifier used by the vendor for the region. Second part of composite key
required: true
type: string
+ example: __CLOUD-REGION-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -6058,7 +7844,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/cloud-regions"
+ $ref: "#/getDefinitions/cloud-regions"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/cloud-infrastructure/network-profiles/network-profile/{nm-profile-name}/relationship-list/relationship:
@@ -6082,9 +7868,10 @@ paths:
description: Unique name of network profile.
required: true
type: string
+ example: __NM-PROFILE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureNetworkProfilesNetworkProfile.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -6109,6 +7896,7 @@ paths:
description: Unique name of network profile.
required: true
type: string
+ example: __NM-PROFILE-NAME__
/cloud-infrastructure/network-profiles/network-profile/{nm-profile-name}:
get:
tags:
@@ -6123,7 +7911,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/network-profile"
+ $ref: "#/getDefinitions/network-profile"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -6132,11 +7920,15 @@ paths:
description: Unique name of network profile.
required: true
type: string
+ example: __NM-PROFILE-NAME__
put:
tags:
- CloudInfrastructure
summary: create or update an existing network-profile
- description: create or update an existing network-profile
+ description: |
+ Create or update an existing network-profile.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureNetworkProfilesNetworkProfile
consumes:
- application/json
@@ -6153,12 +7945,52 @@ paths:
description: Unique name of network profile.
required: true
type: string
+ example: __NM-PROFILE-NAME__
- name: body
in: body
- description: network-profile object that needs to be created or updated
+ description: network-profile object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureNetworkProfilesNetworkProfile.json)
required: true
schema:
$ref: "#/definitions/network-profile"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing network-profile
+ description: |
+ Update an existing network-profile
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureNetworkProfilesNetworkProfile
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: nm-profile-name
+ in: path
+ description: Unique name of network profile.
+ required: true
+ type: string
+ example: __NM-PROFILE-NAME__
+ - name: body
+ in: body
+ description: network-profile object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/network-profile"
delete:
tags:
- CloudInfrastructure
@@ -6180,6 +8012,7 @@ paths:
description: Unique name of network profile.
required: true
type: string
+ example: __NM-PROFILE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -6199,7 +8032,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/network-profiles"
+ $ref: "#/getDefinitions/network-profiles"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/cloud-infrastructure/pservers/pserver/{hostname}/relationship-list/relationship:
@@ -6223,9 +8056,10 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserver.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -6250,6 +8084,7 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/relationship-list/relationship:
put:
tags:
@@ -6271,14 +8106,16 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -6303,11 +8140,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -6329,24 +8168,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -6371,21 +8214,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -6407,29 +8254,34 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -6454,26 +8306,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -6488,7 +8345,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -6497,26 +8354,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -6587,7 +8449,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -6604,32 +8469,100 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- CloudInfrastructure
@@ -6651,26 +8584,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -6697,29 +8635,34 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -6744,26 +8687,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -6778,7 +8726,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -6787,26 +8735,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -6877,7 +8830,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -6894,32 +8850,100 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- CloudInfrastructure
@@ -6941,26 +8965,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -6980,7 +9009,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -6989,21 +9018,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -7058,7 +9091,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -7075,27 +9111,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- CloudInfrastructure
@@ -7117,21 +9214,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -7151,7 +9252,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -7160,16 +9261,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -7230,24 +9334,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -7272,21 +9380,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -7301,7 +9413,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -7310,21 +9422,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -7388,7 +9504,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -7405,27 +9524,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- CloudInfrastructure
@@ -7447,21 +9627,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -7481,7 +9665,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -7490,16 +9674,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -7560,19 +9747,22 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -7597,16 +9787,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -7628,24 +9821,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -7670,21 +9867,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -7699,7 +9900,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -7708,21 +9909,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -7782,7 +9987,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -7799,27 +10007,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- CloudInfrastructure
@@ -7841,21 +10110,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -7882,24 +10155,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -7924,21 +10201,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -7953,7 +10234,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -7962,21 +10243,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -8036,7 +10321,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -8053,27 +10341,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- CloudInfrastructure
@@ -8095,21 +10444,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -8129,7 +10482,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -8138,16 +10491,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -8191,7 +10547,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface
consumes:
- application/json
@@ -8208,22 +10567,76 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- CloudInfrastructure
@@ -8245,16 +10658,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -8274,7 +10690,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -8283,11 +10699,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -8326,7 +10744,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/p-interface"
+ $ref: "#/getDefinitions/p-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -8335,11 +10753,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -8368,7 +10788,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing p-interface
- description: create or update an existing p-interface
+ description: |
+ Create or update an existing p-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterface
consumes:
- application/json
@@ -8385,17 +10808,64 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: p-interface object that needs to be created or updated
+ description: p-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverPInterfacesPInterface.json)
required: true
schema:
$ref: "#/definitions/p-interface"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing p-interface
+ description: |
+ Update an existing p-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: p-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/p-interface"
delete:
tags:
- CloudInfrastructure
@@ -8417,11 +10887,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -8441,7 +10913,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/p-interfaces"
+ $ref: "#/getDefinitions/p-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -8450,6 +10922,7 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -8490,14 +10963,16 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -8522,11 +10997,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -8548,24 +11025,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -8590,21 +11071,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -8626,29 +11111,34 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -8673,26 +11163,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -8707,7 +11202,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -8716,26 +11211,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -8811,7 +11311,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -8828,32 +11331,100 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- CloudInfrastructure
@@ -8875,26 +11446,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -8921,29 +11497,34 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -8968,26 +11549,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -9002,7 +11588,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -9011,26 +11597,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -9106,7 +11697,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -9123,32 +11717,100 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- CloudInfrastructure
@@ -9170,26 +11832,31 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -9209,7 +11876,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -9218,21 +11885,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -9292,7 +11963,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -9309,27 +11983,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- CloudInfrastructure
@@ -9351,21 +12086,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -9385,7 +12124,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -9394,16 +12133,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -9469,24 +12211,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -9511,21 +12257,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -9540,7 +12290,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -9549,21 +12299,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -9632,7 +12386,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -9649,27 +12406,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- CloudInfrastructure
@@ -9691,21 +12509,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -9725,7 +12547,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -9734,16 +12556,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -9809,19 +12634,22 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -9846,16 +12674,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -9877,24 +12708,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -9919,21 +12754,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -9948,7 +12787,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -9957,21 +12796,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -10036,7 +12879,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -10053,27 +12899,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- CloudInfrastructure
@@ -10095,21 +13002,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -10136,24 +13047,28 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -10178,21 +13093,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -10207,7 +13126,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -10216,21 +13135,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -10295,7 +13218,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -10312,27 +13238,88 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- CloudInfrastructure
@@ -10354,21 +13341,25 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -10388,7 +13379,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -10397,16 +13388,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -10455,7 +13449,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface
consumes:
- application/json
@@ -10472,22 +13469,76 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- CloudInfrastructure
@@ -10509,16 +13560,19 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -10538,7 +13592,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -10547,11 +13601,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -10595,7 +13651,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interface"
+ $ref: "#/getDefinitions/lag-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -10604,11 +13660,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -10642,7 +13700,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing lag-interface
- description: create or update an existing lag-interface
+ description: |
+ Create or update an existing lag-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterface
consumes:
- application/json
@@ -10659,17 +13720,64 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: lag-interface object that needs to be created or updated
+ description: lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserverLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/lag-interface"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing lag-interface
+ description: |
+ Update an existing lag-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: lag-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/lag-interface"
delete:
tags:
- CloudInfrastructure
@@ -10691,11 +13799,13 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -10715,7 +13825,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interfaces"
+ $ref: "#/getDefinitions/lag-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -10724,6 +13834,7 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -10757,7 +13868,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/pserver"
+ $ref: "#/getDefinitions/pserver"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -10766,6 +13877,7 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -10789,7 +13901,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing pserver
- description: create or update an existing pserver
+ description: |
+ Create or update an existing pserver.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructurePserversPserver
consumes:
- application/json
@@ -10806,12 +13921,52 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: body
in: body
- description: pserver object that needs to be created or updated
+ description: pserver object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructurePserversPserver.json)
required: true
schema:
$ref: "#/definitions/pserver"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing pserver
+ description: |
+ Update an existing pserver
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructurePserversPserver
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: hostname
+ in: path
+ description: Value from executing hostname on the compute node.
+ required: true
+ type: string
+ example: __HOSTNAME__
+ - name: body
+ in: body
+ description: pserver object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/pserver"
delete:
tags:
- CloudInfrastructure
@@ -10833,6 +13988,7 @@ paths:
description: Value from executing hostname on the compute node.
required: true
type: string
+ example: __HOSTNAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -10852,7 +14008,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/pservers"
+ $ref: "#/getDefinitions/pservers"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}/relationship-list/relationship:
@@ -10876,9 +14032,10 @@ paths:
description: Unique ID of the vdc
required: true
type: string
+ example: __VDC-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureVirtualDataCentersVirtualDataCenter.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -10903,6 +14060,7 @@ paths:
description: Unique ID of the vdc
required: true
type: string
+ example: __VDC-ID__
/cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}:
get:
tags:
@@ -10917,7 +14075,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/virtual-data-center"
+ $ref: "#/getDefinitions/virtual-data-center"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -10926,6 +14084,7 @@ paths:
description: Unique ID of the vdc
required: true
type: string
+ example: __VDC-ID__
- name: vdc-name
in: query
description: Name of the virtual data center
@@ -10935,7 +14094,10 @@ paths:
tags:
- CloudInfrastructure
summary: create or update an existing virtual-data-center
- description: create or update an existing virtual-data-center
+ description: |
+ Create or update an existing virtual-data-center.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateCloudInfrastructureVirtualDataCentersVirtualDataCenter
consumes:
- application/json
@@ -10952,12 +14114,52 @@ paths:
description: Unique ID of the vdc
required: true
type: string
+ example: __VDC-ID__
- name: body
in: body
- description: virtual-data-center object that needs to be created or updated
+ description: virtual-data-center object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/CloudInfrastructureVirtualDataCentersVirtualDataCenter.json)
required: true
schema:
$ref: "#/definitions/virtual-data-center"
+ patch:
+ tags:
+ - CloudInfrastructure
+ summary: update an existing virtual-data-center
+ description: |
+ Update an existing virtual-data-center
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateCloudInfrastructureVirtualDataCentersVirtualDataCenter
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vdc-id
+ in: path
+ description: Unique ID of the vdc
+ required: true
+ type: string
+ example: __VDC-ID__
+ - name: body
+ in: body
+ description: virtual-data-center object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/virtual-data-center"
delete:
tags:
- CloudInfrastructure
@@ -10979,6 +14181,7 @@ paths:
description: Unique ID of the vdc
required: true
type: string
+ example: __VDC-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -10998,7 +14201,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/virtual-data-centers"
+ $ref: "#/getDefinitions/virtual-data-centers"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/business/connectors/connector/{resource-instance-id}/relationship-list/relationship:
@@ -11022,9 +14225,10 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/BusinessConnectorsConnector.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -11049,6 +14253,7 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
/business/connectors/connector/{resource-instance-id}/metadata/metadatum/{metaname}:
get:
tags:
@@ -11063,7 +14268,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadatum"
+ $ref: "#/getDefinitions/metadatum"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -11072,10 +14277,12 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: persona-model-id
in: query
description: the ASDC model id for this resource or service model.
@@ -11100,7 +14307,10 @@ paths:
tags:
- Business
summary: create or update an existing metadatum
- description: create or update an existing metadatum
+ description: |
+ Create or update an existing metadatum.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessConnectorsConnectorMetadataMetadatum
consumes:
- application/json
@@ -11117,16 +14327,62 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: body
in: body
- description: metadatum object that needs to be created or updated
+ description: metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/BusinessConnectorsConnectorMetadataMetadatum.json)
required: true
schema:
$ref: "#/definitions/metadatum"
+ patch:
+ tags:
+ - Business
+ summary: update an existing metadatum
+ description: |
+ Update an existing metadatum
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessConnectorsConnectorMetadataMetadatum
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: resource-instance-id
+ in: path
+ description: Unique id of resource instance.
+ required: true
+ type: string
+ example: __RESOURCE-INSTANCE-ID__
+ - name: metaname
+ in: path
+ required: true
+ type: string
+ example: __METANAME__
+ - name: body
+ in: body
+ description: metadatum object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/metadatum"
delete:
tags:
- Business
@@ -11148,10 +14404,12 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -11171,7 +14429,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadata"
+ $ref: "#/getDefinitions/metadata"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -11180,6 +14438,7 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: persona-model-id
in: query
description: the ASDC model id for this resource or service model.
@@ -11214,7 +14473,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/connector"
+ $ref: "#/getDefinitions/connector"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -11223,6 +14482,7 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: persona-model-id
in: query
description: the ASDC model id for this resource or service model.
@@ -11247,7 +14507,10 @@ paths:
tags:
- Business
summary: create or update an existing connector
- description: create or update an existing connector
+ description: |
+ Create or update an existing connector.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessConnectorsConnector
consumes:
- application/json
@@ -11264,12 +14527,52 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: body
in: body
- description: connector object that needs to be created or updated
+ description: connector object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/BusinessConnectorsConnector.json)
required: true
schema:
$ref: "#/definitions/connector"
+ patch:
+ tags:
+ - Business
+ summary: update an existing connector
+ description: |
+ Update an existing connector
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessConnectorsConnector
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: resource-instance-id
+ in: path
+ description: Unique id of resource instance.
+ required: true
+ type: string
+ example: __RESOURCE-INSTANCE-ID__
+ - name: body
+ in: body
+ description: connector object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/connector"
delete:
tags:
- Business
@@ -11291,6 +14594,7 @@ paths:
description: Unique id of resource instance.
required: true
type: string
+ example: __RESOURCE-INSTANCE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -11310,7 +14614,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/connectors"
+ $ref: "#/getDefinitions/connectors"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/relationship-list/relationship:
@@ -11334,19 +14638,22 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -11371,16 +14678,19 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/metadata/metadatum/{metaname}:
get:
tags:
@@ -11395,7 +14705,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadatum"
+ $ref: "#/getDefinitions/metadatum"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -11404,20 +14714,24 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -11467,7 +14781,10 @@ paths:
tags:
- Business
summary: create or update an existing metadatum
- description: create or update an existing metadatum
+ description: |
+ Create or update an existing metadatum.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceMetadataMetadatum
consumes:
- application/json
@@ -11484,26 +14801,86 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: body
in: body
- description: metadatum object that needs to be created or updated
+ description: metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceMetadataMetadatum.json)
required: true
schema:
$ref: "#/definitions/metadatum"
+ patch:
+ tags:
+ - Business
+ summary: update an existing metadatum
+ description: |
+ Update an existing metadatum
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceMetadataMetadatum
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: global-customer-id
+ in: path
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ required: true
+ type: string
+ example: __GLOBAL-CUSTOMER-ID__
+ - name: service-type
+ in: path
+ description: Value defined by orchestration to identify this service across ECOMP.
+ required: true
+ type: string
+ example: __SERVICE-TYPE__
+ - name: service-instance-id
+ in: path
+ description: Uniquely identifies this instance of a service
+ required: true
+ type: string
+ example: __SERVICE-INSTANCE-ID__
+ - name: metaname
+ in: path
+ required: true
+ type: string
+ example: __METANAME__
+ - name: body
+ in: body
+ description: metadatum object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/metadatum"
delete:
tags:
- Business
@@ -11525,20 +14902,24 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -11558,7 +14939,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadata"
+ $ref: "#/getDefinitions/metadata"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -11567,16 +14948,19 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -11643,29 +15027,34 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResourceTunnelXconnectsTunnelXconnect.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -11690,26 +15079,31 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/allotted-resources/allotted-resource/{id}/tunnel-xconnects/tunnel-xconnect/{id}:
get:
tags:
@@ -11724,7 +15118,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/tunnel-xconnect"
+ $ref: "#/getDefinitions/tunnel-xconnect"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -11733,26 +15127,31 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -11812,7 +15211,10 @@ paths:
tags:
- Business
summary: create or update an existing tunnel-xconnect
- description: create or update an existing tunnel-xconnect
+ description: |
+ Create or update an existing tunnel-xconnect.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResourceTunnelXconnectsTunnelXconnect
consumes:
- application/json
@@ -11829,32 +15231,100 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: body
in: body
- description: tunnel-xconnect object that needs to be created or updated
+ description: tunnel-xconnect object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResourceTunnelXconnectsTunnelXconnect.json)
required: true
schema:
$ref: "#/definitions/tunnel-xconnect"
+ patch:
+ tags:
+ - Business
+ summary: update an existing tunnel-xconnect
+ description: |
+ Update an existing tunnel-xconnect
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResourceTunnelXconnectsTunnelXconnect
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: global-customer-id
+ in: path
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ required: true
+ type: string
+ example: __GLOBAL-CUSTOMER-ID__
+ - name: service-type
+ in: path
+ description: Value defined by orchestration to identify this service across ECOMP.
+ required: true
+ type: string
+ example: __SERVICE-TYPE__
+ - name: service-instance-id
+ in: path
+ description: Uniquely identifies this instance of a service
+ required: true
+ type: string
+ example: __SERVICE-INSTANCE-ID__
+ - name: id
+ in: path
+ description: Allotted Resource id UUID assigned to this instance.
+ required: true
+ type: string
+ example: __ID__
+ - name: id
+ in: path
+ description: Allotted Resource id UUID assigned to this instance.
+ required: true
+ type: string
+ example: __ID__
+ - name: body
+ in: body
+ description: tunnel-xconnect object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/tunnel-xconnect"
delete:
tags:
- Business
@@ -11876,26 +15346,31 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -11915,7 +15390,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/tunnel-xconnects"
+ $ref: "#/getDefinitions/tunnel-xconnects"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -11924,21 +15399,25 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -12015,24 +15494,28 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResource.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -12057,21 +15540,25 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/allotted-resources/allotted-resource/{id}:
get:
tags:
@@ -12086,7 +15573,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/allotted-resource"
+ $ref: "#/getDefinitions/allotted-resource"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -12095,21 +15582,25 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -12169,7 +15660,10 @@ paths:
tags:
- Business
summary: create or update an existing allotted-resource
- description: create or update an existing allotted-resource
+ description: |
+ Create or update an existing allotted-resource.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResource
consumes:
- application/json
@@ -12186,27 +15680,88 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: body
in: body
- description: allotted-resource object that needs to be created or updated
+ description: allotted-resource object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResource.json)
required: true
schema:
$ref: "#/definitions/allotted-resource"
+ patch:
+ tags:
+ - Business
+ summary: update an existing allotted-resource
+ description: |
+ Update an existing allotted-resource
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResource
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: global-customer-id
+ in: path
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ required: true
+ type: string
+ example: __GLOBAL-CUSTOMER-ID__
+ - name: service-type
+ in: path
+ description: Value defined by orchestration to identify this service across ECOMP.
+ required: true
+ type: string
+ example: __SERVICE-TYPE__
+ - name: service-instance-id
+ in: path
+ description: Uniquely identifies this instance of a service
+ required: true
+ type: string
+ example: __SERVICE-INSTANCE-ID__
+ - name: id
+ in: path
+ description: Allotted Resource id UUID assigned to this instance.
+ required: true
+ type: string
+ example: __ID__
+ - name: body
+ in: body
+ description: allotted-resource object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/allotted-resource"
delete:
tags:
- Business
@@ -12228,21 +15783,25 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: id
in: path
description: Allotted Resource id UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -12262,7 +15821,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/allotted-resources"
+ $ref: "#/getDefinitions/allotted-resources"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -12271,16 +15830,19 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -12340,7 +15902,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/service-instance"
+ $ref: "#/getDefinitions/service-instance"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -12349,16 +15911,19 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -12408,7 +15973,10 @@ paths:
tags:
- Business
summary: create or update an existing service-instance
- description: create or update an existing service-instance
+ description: |
+ Create or update an existing service-instance.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance
consumes:
- application/json
@@ -12425,22 +15993,76 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: body
in: body
- description: service-instance object that needs to be created or updated
+ description: service-instance object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance.json)
required: true
schema:
$ref: "#/definitions/service-instance"
+ patch:
+ tags:
+ - Business
+ summary: update an existing service-instance
+ description: |
+ Update an existing service-instance
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: global-customer-id
+ in: path
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ required: true
+ type: string
+ example: __GLOBAL-CUSTOMER-ID__
+ - name: service-type
+ in: path
+ description: Value defined by orchestration to identify this service across ECOMP.
+ required: true
+ type: string
+ example: __SERVICE-TYPE__
+ - name: service-instance-id
+ in: path
+ description: Uniquely identifies this instance of a service
+ required: true
+ type: string
+ example: __SERVICE-INSTANCE-ID__
+ - name: body
+ in: body
+ description: service-instance object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/service-instance"
delete:
tags:
- Business
@@ -12462,16 +16084,19 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: service-instance-id
in: path
description: Uniquely identifies this instance of a service
required: true
type: string
+ example: __SERVICE-INSTANCE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -12491,7 +16116,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/service-instances"
+ $ref: "#/getDefinitions/service-instances"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -12500,11 +16125,13 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -12536,14 +16163,16 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/BusinessCustomersCustomerServiceSubscriptionsServiceSubscription.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -12568,11 +16197,13 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
/business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}:
get:
tags:
@@ -12587,7 +16218,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/service-subscription"
+ $ref: "#/getDefinitions/service-subscription"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -12596,11 +16227,13 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -12615,7 +16248,10 @@ paths:
tags:
- Business
summary: create or update an existing service-subscription
- description: create or update an existing service-subscription
+ description: |
+ Create or update an existing service-subscription.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscription
consumes:
- application/json
@@ -12632,17 +16268,64 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: body
in: body
- description: service-subscription object that needs to be created or updated
+ description: service-subscription object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/BusinessCustomersCustomerServiceSubscriptionsServiceSubscription.json)
required: true
schema:
$ref: "#/definitions/service-subscription"
+ patch:
+ tags:
+ - Business
+ summary: update an existing service-subscription
+ description: |
+ Update an existing service-subscription
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscription
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: global-customer-id
+ in: path
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ required: true
+ type: string
+ example: __GLOBAL-CUSTOMER-ID__
+ - name: service-type
+ in: path
+ description: Value defined by orchestration to identify this service across ECOMP.
+ required: true
+ type: string
+ example: __SERVICE-TYPE__
+ - name: body
+ in: body
+ description: service-subscription object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/service-subscription"
delete:
tags:
- Business
@@ -12664,11 +16347,13 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: service-type
in: path
description: Value defined by orchestration to identify this service across ECOMP.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -12688,7 +16373,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/service-subscriptions"
+ $ref: "#/getDefinitions/service-subscriptions"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -12697,6 +16382,7 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -12728,9 +16414,10 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/BusinessCustomersCustomer.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -12755,6 +16442,7 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
/business/customers/customer/{global-customer-id}:
get:
tags:
@@ -12769,7 +16457,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/customer"
+ $ref: "#/getDefinitions/customer"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -12778,6 +16466,7 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: subscriber-name
in: query
description: Subscriber name, an alternate way to retrieve a customer.
@@ -12792,7 +16481,10 @@ paths:
tags:
- Business
summary: create or update an existing customer
- description: create or update an existing customer
+ description: |
+ Create or update an existing customer.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateBusinessCustomersCustomer
consumes:
- application/json
@@ -12809,12 +16501,52 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: body
in: body
- description: customer object that needs to be created or updated
+ description: customer object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/BusinessCustomersCustomer.json)
required: true
schema:
$ref: "#/definitions/customer"
+ patch:
+ tags:
+ - Business
+ summary: update an existing customer
+ description: |
+ Update an existing customer
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateBusinessCustomersCustomer
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: global-customer-id
+ in: path
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ required: true
+ type: string
+ example: __GLOBAL-CUSTOMER-ID__
+ - name: body
+ in: body
+ description: customer object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/customer"
delete:
tags:
- Business
@@ -12836,6 +16568,7 @@ paths:
description: Global customer id used across ECOMP to uniquely identify customer.
required: true
type: string
+ example: __GLOBAL-CUSTOMER-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -12855,7 +16588,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/customers"
+ $ref: "#/getDefinitions/customers"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/service-design-and-creation/vnf-images/vnf-image/{vnf-image-uuid}/relationship-list/relationship:
@@ -12879,9 +16612,10 @@ paths:
description: Unique ID of this asset
required: true
type: string
+ example: __VNF-IMAGE-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationVnfImagesVnfImage.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -12906,6 +16640,7 @@ paths:
description: Unique ID of this asset
required: true
type: string
+ example: __VNF-IMAGE-UUID__
/service-design-and-creation/vnf-images/vnf-image/{vnf-image-uuid}:
get:
tags:
@@ -12920,7 +16655,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vnf-image"
+ $ref: "#/getDefinitions/vnf-image"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -12929,6 +16664,7 @@ paths:
description: Unique ID of this asset
required: true
type: string
+ example: __VNF-IMAGE-UUID__
- name: application
in: query
description: The application that the image instantiates.
@@ -12948,7 +16684,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing vnf-image
- description: create or update an existing vnf-image
+ description: |
+ Create or update an existing vnf-image.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationVnfImagesVnfImage
consumes:
- application/json
@@ -12965,12 +16704,52 @@ paths:
description: Unique ID of this asset
required: true
type: string
+ example: __VNF-IMAGE-UUID__
- name: body
in: body
- description: vnf-image object that needs to be created or updated
+ description: vnf-image object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationVnfImagesVnfImage.json)
required: true
schema:
$ref: "#/definitions/vnf-image"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing vnf-image
+ description: |
+ Update an existing vnf-image
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationVnfImagesVnfImage
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-image-uuid
+ in: path
+ description: Unique ID of this asset
+ required: true
+ type: string
+ example: __VNF-IMAGE-UUID__
+ - name: body
+ in: body
+ description: vnf-image object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vnf-image"
delete:
tags:
- ServiceDesignAndCreation
@@ -12992,6 +16771,7 @@ paths:
description: Unique ID of this asset
required: true
type: string
+ example: __VNF-IMAGE-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -13011,7 +16791,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vnf-images"
+ $ref: "#/getDefinitions/vnf-images"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/service-design-and-creation/services/service/{service-id}/relationship-list/relationship:
@@ -13035,9 +16815,10 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationServicesService.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -13062,6 +16843,7 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-ID__
/service-design-and-creation/services/service/{service-id}:
get:
tags:
@@ -13076,7 +16858,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/service"
+ $ref: "#/getDefinitions/service"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -13085,6 +16867,7 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-ID__
- name: service-description
in: query
description: Description of the service
@@ -13094,7 +16877,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing service
- description: create or update an existing service
+ description: |
+ Create or update an existing service.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationServicesService
consumes:
- application/json
@@ -13111,12 +16897,52 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-ID__
- name: body
in: body
- description: service object that needs to be created or updated
+ description: service object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationServicesService.json)
required: true
schema:
$ref: "#/definitions/service"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing service
+ description: |
+ Update an existing service
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationServicesService
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: service-id
+ in: path
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ required: true
+ type: string
+ example: __SERVICE-ID__
+ - name: body
+ in: body
+ description: service object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/service"
delete:
tags:
- ServiceDesignAndCreation
@@ -13138,6 +16964,7 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -13157,7 +16984,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/services"
+ $ref: "#/getDefinitions/services"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/service-design-and-creation/service-capabilities/service-capability/{service-type}/{vnf-type}/relationship-list/relationship:
@@ -13181,14 +17008,16 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: vnf-type
in: path
description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
required: true
type: string
+ example: __VNF-TYPE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationServiceCapabilitiesServiceCapability.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -13213,11 +17042,13 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: vnf-type
in: path
description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
required: true
type: string
+ example: __VNF-TYPE__
/service-design-and-creation/service-capabilities/service-capability/{service-type}/{vnf-type}:
get:
tags:
@@ -13232,7 +17063,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/service-capability"
+ $ref: "#/getDefinitions/service-capability"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -13241,16 +17072,21 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: vnf-type
in: path
description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
required: true
type: string
+ example: __VNF-TYPE__
put:
tags:
- ServiceDesignAndCreation
summary: create or update an existing service-capability
- description: create or update an existing service-capability
+ description: |
+ Create or update an existing service-capability.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationServiceCapabilitiesServiceCapability
consumes:
- application/json
@@ -13267,17 +17103,64 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: vnf-type
in: path
description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
required: true
type: string
+ example: __VNF-TYPE__
- name: body
in: body
- description: service-capability object that needs to be created or updated
+ description: service-capability object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationServiceCapabilitiesServiceCapability.json)
required: true
schema:
$ref: "#/definitions/service-capability"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing service-capability
+ description: |
+ Update an existing service-capability
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationServiceCapabilitiesServiceCapability
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: service-type
+ in: path
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ required: true
+ type: string
+ example: __SERVICE-TYPE__
+ - name: vnf-type
+ in: path
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ required: true
+ type: string
+ example: __VNF-TYPE__
+ - name: body
+ in: body
+ description: service-capability object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/service-capability"
delete:
tags:
- ServiceDesignAndCreation
@@ -13299,11 +17182,13 @@ paths:
description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
required: true
type: string
+ example: __SERVICE-TYPE__
- name: vnf-type
in: path
description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
required: true
type: string
+ example: __VNF-TYPE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -13323,7 +17208,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/service-capabilities"
+ $ref: "#/getDefinitions/service-capabilities"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}/element-choice-sets/element-choice-set/{element-choice-set-uuid}/relationship-list/relationship:
@@ -13347,30 +17232,36 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: element-choice-set-uuid
in: path
required: true
type: string
+ example: __ELEMENT-CHOICE-SET-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -13395,27 +17286,33 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: element-choice-set-uuid
in: path
required: true
type: string
+ example: __ELEMENT-CHOICE-SET-UUID__
/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}/element-choice-sets/element-choice-set/{element-choice-set-uuid}:
get:
tags:
@@ -13430,7 +17327,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/element-choice-set"
+ $ref: "#/getDefinitions/element-choice-set"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -13439,27 +17336,33 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: element-choice-set-uuid
in: path
required: true
type: string
+ example: __ELEMENT-CHOICE-SET-UUID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -13479,7 +17382,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing element-choice-set
- description: create or update an existing element-choice-set
+ description: |
+ Create or update an existing element-choice-set.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet
consumes:
- application/json
@@ -13496,33 +17402,104 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: element-choice-set-uuid
in: path
required: true
type: string
+ example: __ELEMENT-CHOICE-SET-UUID__
- name: body
in: body
- description: element-choice-set object that needs to be created or updated
+ description: element-choice-set object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet.json)
required: true
schema:
$ref: "#/definitions/element-choice-set"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing element-choice-set
+ description: |
+ Update an existing element-choice-set
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: model-invariant-id
+ in: path
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-INVARIANT-ID__
+ - name: model-version-id
+ in: path
+ description: Unique identifier corresponding to one version of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-VERSION-ID__
+ - name: model-element-uuid
+ in: path
+ required: true
+ type: string
+ example: __MODEL-ELEMENT-UUID__
+ - name: model-constraint-uuid
+ in: path
+ required: true
+ type: string
+ example: __MODEL-CONSTRAINT-UUID__
+ - name: constrained-element-set-uuid
+ in: path
+ required: true
+ type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
+ - name: element-choice-set-uuid
+ in: path
+ required: true
+ type: string
+ example: __ELEMENT-CHOICE-SET-UUID__
+ - name: body
+ in: body
+ description: element-choice-set object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/element-choice-set"
delete:
tags:
- ServiceDesignAndCreation
@@ -13544,27 +17521,33 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: element-choice-set-uuid
in: path
required: true
type: string
+ example: __ELEMENT-CHOICE-SET-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -13584,7 +17567,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/element-choice-sets"
+ $ref: "#/getDefinitions/element-choice-sets"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -13593,23 +17576,28 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -13646,26 +17634,31 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -13690,23 +17683,28 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}:
get:
tags:
@@ -13721,7 +17719,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/constrained-element-set"
+ $ref: "#/getDefinitions/constrained-element-set"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -13730,23 +17728,28 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -13766,7 +17769,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing constrained-element-set
- description: create or update an existing constrained-element-set
+ description: |
+ Create or update an existing constrained-element-set.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet
consumes:
- application/json
@@ -13783,29 +17789,94 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: body
in: body
- description: constrained-element-set object that needs to be created or updated
+ description: constrained-element-set object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet.json)
required: true
schema:
$ref: "#/definitions/constrained-element-set"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing constrained-element-set
+ description: |
+ Update an existing constrained-element-set
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: model-invariant-id
+ in: path
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-INVARIANT-ID__
+ - name: model-version-id
+ in: path
+ description: Unique identifier corresponding to one version of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-VERSION-ID__
+ - name: model-element-uuid
+ in: path
+ required: true
+ type: string
+ example: __MODEL-ELEMENT-UUID__
+ - name: model-constraint-uuid
+ in: path
+ required: true
+ type: string
+ example: __MODEL-CONSTRAINT-UUID__
+ - name: constrained-element-set-uuid
+ in: path
+ required: true
+ type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
+ - name: body
+ in: body
+ description: constrained-element-set object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/constrained-element-set"
delete:
tags:
- ServiceDesignAndCreation
@@ -13827,23 +17898,28 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: constrained-element-set-uuid
in: path
required: true
type: string
+ example: __CONSTRAINED-ELEMENT-SET-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -13863,7 +17939,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/constrained-element-sets"
+ $ref: "#/getDefinitions/constrained-element-sets"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -13872,19 +17948,23 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -13914,7 +17994,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/model-constraint"
+ $ref: "#/getDefinitions/model-constraint"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -13923,19 +18003,23 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -13955,7 +18039,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing model-constraint
- description: create or update an existing model-constraint
+ description: |
+ Create or update an existing model-constraint.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraint
consumes:
- application/json
@@ -13972,25 +18059,84 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: body
in: body
- description: model-constraint object that needs to be created or updated
+ description: model-constraint object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraint.json)
required: true
schema:
$ref: "#/definitions/model-constraint"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing model-constraint
+ description: |
+ Update an existing model-constraint
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraint
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: model-invariant-id
+ in: path
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-INVARIANT-ID__
+ - name: model-version-id
+ in: path
+ description: Unique identifier corresponding to one version of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-VERSION-ID__
+ - name: model-element-uuid
+ in: path
+ required: true
+ type: string
+ example: __MODEL-ELEMENT-UUID__
+ - name: model-constraint-uuid
+ in: path
+ required: true
+ type: string
+ example: __MODEL-CONSTRAINT-UUID__
+ - name: body
+ in: body
+ description: model-constraint object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/model-constraint"
delete:
tags:
- ServiceDesignAndCreation
@@ -14012,19 +18158,23 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-constraint-uuid
in: path
required: true
type: string
+ example: __MODEL-CONSTRAINT-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -14044,7 +18194,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/model-constraints"
+ $ref: "#/getDefinitions/model-constraints"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14053,15 +18203,18 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -14098,18 +18251,21 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElement.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -14134,15 +18290,18 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}:
get:
tags:
@@ -14157,7 +18316,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/model-element"
+ $ref: "#/getDefinitions/model-element"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14166,15 +18325,18 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -14194,7 +18356,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing model-element
- description: create or update an existing model-element
+ description: |
+ Create or update an existing model-element.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElement
consumes:
- application/json
@@ -14211,21 +18376,74 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: body
in: body
- description: model-element object that needs to be created or updated
+ description: model-element object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElement.json)
required: true
schema:
$ref: "#/definitions/model-element"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing model-element
+ description: |
+ Update an existing model-element
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElement
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: model-invariant-id
+ in: path
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-INVARIANT-ID__
+ - name: model-version-id
+ in: path
+ description: Unique identifier corresponding to one version of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-VERSION-ID__
+ - name: model-element-uuid
+ in: path
+ required: true
+ type: string
+ example: __MODEL-ELEMENT-UUID__
+ - name: body
+ in: body
+ description: model-element object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/model-element"
delete:
tags:
- ServiceDesignAndCreation
@@ -14247,15 +18465,18 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-element-uuid
in: path
required: true
type: string
+ example: __MODEL-ELEMENT-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -14275,7 +18496,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/model-elements"
+ $ref: "#/getDefinitions/model-elements"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14284,11 +18505,13 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -14318,7 +18541,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadatum"
+ $ref: "#/getDefinitions/metadatum"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14327,15 +18550,18 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -14355,7 +18581,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing metadatum
- description: create or update an existing metadatum
+ description: |
+ Create or update an existing metadatum.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationModelsModelModelVersModelVerMetadataMetadatum
consumes:
- application/json
@@ -14372,21 +18601,74 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: body
in: body
- description: metadatum object that needs to be created or updated
+ description: metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationModelsModelModelVersModelVerMetadataMetadatum.json)
required: true
schema:
$ref: "#/definitions/metadatum"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing metadatum
+ description: |
+ Update an existing metadatum
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationModelsModelModelVersModelVerMetadataMetadatum
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: model-invariant-id
+ in: path
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-INVARIANT-ID__
+ - name: model-version-id
+ in: path
+ description: Unique identifier corresponding to one version of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-VERSION-ID__
+ - name: metaname
+ in: path
+ required: true
+ type: string
+ example: __METANAME__
+ - name: body
+ in: body
+ description: metadatum object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/metadatum"
delete:
tags:
- ServiceDesignAndCreation
@@ -14408,15 +18690,18 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: metaname
in: path
required: true
type: string
+ example: __METANAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -14436,7 +18721,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/metadata"
+ $ref: "#/getDefinitions/metadata"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14445,11 +18730,13 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -14486,14 +18773,16 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationModelsModelModelVersModelVer.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -14518,11 +18807,13 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
/service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}:
get:
tags:
@@ -14537,7 +18828,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/model-ver"
+ $ref: "#/getDefinitions/model-ver"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14546,11 +18837,13 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -14570,7 +18863,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing model-ver
- description: create or update an existing model-ver
+ description: |
+ Create or update an existing model-ver.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationModelsModelModelVersModelVer
consumes:
- application/json
@@ -14587,17 +18883,64 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: body
in: body
- description: model-ver object that needs to be created or updated
+ description: model-ver object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationModelsModelModelVersModelVer.json)
required: true
schema:
$ref: "#/definitions/model-ver"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing model-ver
+ description: |
+ Update an existing model-ver
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationModelsModelModelVersModelVer
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: model-invariant-id
+ in: path
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-INVARIANT-ID__
+ - name: model-version-id
+ in: path
+ description: Unique identifier corresponding to one version of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-VERSION-ID__
+ - name: body
+ in: body
+ description: model-ver object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/model-ver"
delete:
tags:
- ServiceDesignAndCreation
@@ -14619,11 +18962,13 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-version-id
in: path
description: Unique identifier corresponding to one version of a model in ASDC
required: true
type: string
+ example: __MODEL-VERSION-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -14643,7 +18988,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/model-vers"
+ $ref: "#/getDefinitions/model-vers"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14652,6 +18997,7 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -14678,9 +19024,10 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationModelsModel.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -14705,6 +19052,7 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
/service-design-and-creation/models/model/{model-invariant-id}:
get:
tags:
@@ -14719,7 +19067,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/model"
+ $ref: "#/getDefinitions/model"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14728,6 +19076,7 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: model-type
in: query
description: Type of the model, e.g., service, resource, widget, etc.
@@ -14737,7 +19086,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing model
- description: create or update an existing model
+ description: |
+ Create or update an existing model.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationModelsModel
consumes:
- application/json
@@ -14754,12 +19106,52 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: body
in: body
- description: model object that needs to be created or updated
+ description: model object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationModelsModel.json)
required: true
schema:
$ref: "#/definitions/model"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing model
+ description: |
+ Update an existing model
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationModelsModel
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: model-invariant-id
+ in: path
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ required: true
+ type: string
+ example: __MODEL-INVARIANT-ID__
+ - name: body
+ in: body
+ description: model object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/model"
delete:
tags:
- ServiceDesignAndCreation
@@ -14781,6 +19173,7 @@ paths:
description: Unique identifier corresponding to the main definition of a model in ASDC
required: true
type: string
+ example: __MODEL-INVARIANT-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -14800,7 +19193,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/models"
+ $ref: "#/getDefinitions/models"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/related-lookups/related-lookup/{related-lookup-uuid}/relationship-list/relationship:
@@ -14823,17 +19216,20 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: related-lookup-uuid
in: path
required: true
type: string
+ example: __RELATED-LOOKUP-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -14857,14 +19253,17 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: related-lookup-uuid
in: path
required: true
type: string
+ example: __RELATED-LOOKUP-UUID__
/service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/related-lookups/related-lookup/{related-lookup-uuid}:
get:
tags:
@@ -14879,7 +19278,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/related-lookup"
+ $ref: "#/getDefinitions/related-lookup"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14887,14 +19286,17 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: related-lookup-uuid
in: path
required: true
type: string
+ example: __RELATED-LOOKUP-UUID__
- name: named-query-name
in: query
required: false
@@ -14903,7 +19305,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing related-lookup
- description: create or update an existing related-lookup
+ description: |
+ Create or update an existing related-lookup.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup
consumes:
- application/json
@@ -14919,20 +19324,71 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: related-lookup-uuid
in: path
required: true
type: string
+ example: __RELATED-LOOKUP-UUID__
- name: body
in: body
- description: related-lookup object that needs to be created or updated
+ description: related-lookup object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup.json)
required: true
schema:
$ref: "#/definitions/related-lookup"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing related-lookup
+ description: |
+ Update an existing related-lookup
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: named-query-uuid
+ in: path
+ required: true
+ type: string
+ example: __NAMED-QUERY-UUID__
+ - name: named-query-element-uuid
+ in: path
+ required: true
+ type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
+ - name: related-lookup-uuid
+ in: path
+ required: true
+ type: string
+ example: __RELATED-LOOKUP-UUID__
+ - name: body
+ in: body
+ description: related-lookup object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/related-lookup"
delete:
tags:
- ServiceDesignAndCreation
@@ -14953,14 +19409,17 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: related-lookup-uuid
in: path
required: true
type: string
+ example: __RELATED-LOOKUP-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -14980,7 +19439,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/related-lookups"
+ $ref: "#/getDefinitions/related-lookups"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -14988,10 +19447,12 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: named-query-name
in: query
required: false
@@ -15010,7 +19471,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/property-constraint"
+ $ref: "#/getDefinitions/property-constraint"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -15018,14 +19479,17 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: property-constraint-uuid
in: path
required: true
type: string
+ example: __PROPERTY-CONSTRAINT-UUID__
- name: named-query-name
in: query
required: false
@@ -15034,7 +19498,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing property-constraint
- description: create or update an existing property-constraint
+ description: |
+ Create or update an existing property-constraint.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementPropertyConstraintsPropertyConstraint
consumes:
- application/json
@@ -15050,20 +19517,71 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: property-constraint-uuid
in: path
required: true
type: string
+ example: __PROPERTY-CONSTRAINT-UUID__
- name: body
in: body
- description: property-constraint object that needs to be created or updated
+ description: property-constraint object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementPropertyConstraintsPropertyConstraint.json)
required: true
schema:
$ref: "#/definitions/property-constraint"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing property-constraint
+ description: |
+ Update an existing property-constraint
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementPropertyConstraintsPropertyConstraint
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: named-query-uuid
+ in: path
+ required: true
+ type: string
+ example: __NAMED-QUERY-UUID__
+ - name: named-query-element-uuid
+ in: path
+ required: true
+ type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
+ - name: property-constraint-uuid
+ in: path
+ required: true
+ type: string
+ example: __PROPERTY-CONSTRAINT-UUID__
+ - name: body
+ in: body
+ description: property-constraint object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/property-constraint"
delete:
tags:
- ServiceDesignAndCreation
@@ -15084,14 +19602,17 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: property-constraint-uuid
in: path
required: true
type: string
+ example: __PROPERTY-CONSTRAINT-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -15111,7 +19632,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/property-constraints"
+ $ref: "#/getDefinitions/property-constraints"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -15119,10 +19640,12 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: named-query-name
in: query
required: false
@@ -15147,13 +19670,15 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -15177,10 +19702,12 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
/service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}:
get:
tags:
@@ -15195,7 +19722,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/named-query-element"
+ $ref: "#/getDefinitions/named-query-element"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -15203,10 +19730,12 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: named-query-name
in: query
required: false
@@ -15215,7 +19744,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing named-query-element
- description: create or update an existing named-query-element
+ description: |
+ Create or update an existing named-query-element.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement
consumes:
- application/json
@@ -15231,16 +19763,61 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: body
in: body
- description: named-query-element object that needs to be created or updated
+ description: named-query-element object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement.json)
required: true
schema:
$ref: "#/definitions/named-query-element"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing named-query-element
+ description: |
+ Update an existing named-query-element
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: named-query-uuid
+ in: path
+ required: true
+ type: string
+ example: __NAMED-QUERY-UUID__
+ - name: named-query-element-uuid
+ in: path
+ required: true
+ type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
+ - name: body
+ in: body
+ description: named-query-element object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/named-query-element"
delete:
tags:
- ServiceDesignAndCreation
@@ -15261,10 +19838,12 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-element-uuid
in: path
required: true
type: string
+ example: __NAMED-QUERY-ELEMENT-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -15284,7 +19863,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/named-query-elements"
+ $ref: "#/getDefinitions/named-query-elements"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -15292,6 +19871,7 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-name
in: query
required: false
@@ -15316,9 +19896,10 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationNamedQueriesNamedQuery.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -15342,6 +19923,7 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
/service-design-and-creation/named-queries/named-query/{named-query-uuid}:
get:
tags:
@@ -15356,7 +19938,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/named-query"
+ $ref: "#/getDefinitions/named-query"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -15364,6 +19946,7 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: named-query-name
in: query
required: false
@@ -15372,7 +19955,10 @@ paths:
tags:
- ServiceDesignAndCreation
summary: create or update an existing named-query
- description: create or update an existing named-query
+ description: |
+ Create or update an existing named-query.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateServiceDesignAndCreationNamedQueriesNamedQuery
consumes:
- application/json
@@ -15388,12 +19974,51 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: body
in: body
- description: named-query object that needs to be created or updated
+ description: named-query object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/ServiceDesignAndCreationNamedQueriesNamedQuery.json)
required: true
schema:
$ref: "#/definitions/named-query"
+ patch:
+ tags:
+ - ServiceDesignAndCreation
+ summary: update an existing named-query
+ description: |
+ Update an existing named-query
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateServiceDesignAndCreationNamedQueriesNamedQuery
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: named-query-uuid
+ in: path
+ required: true
+ type: string
+ example: __NAMED-QUERY-UUID__
+ - name: body
+ in: body
+ description: named-query object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/named-query"
delete:
tags:
- ServiceDesignAndCreation
@@ -15414,6 +20039,7 @@ paths:
in: path
required: true
type: string
+ example: __NAMED-QUERY-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -15433,7 +20059,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/named-queries"
+ $ref: "#/getDefinitions/named-queries"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/logical-links/logical-link/{link-name}/relationship-list/relationship:
@@ -15457,9 +20083,10 @@ paths:
description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkLogicalLinksLogicalLink.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -15484,6 +20111,7 @@ paths:
description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
required: true
type: string
+ example: __LINK-NAME__
/network/logical-links/logical-link/{link-name}:
get:
tags:
@@ -15498,7 +20126,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/logical-link"
+ $ref: "#/getDefinitions/logical-link"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -15507,6 +20135,7 @@ paths:
description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: persona-model-id
in: query
description: the ASDC model id for this resource or service model.
@@ -15551,7 +20180,10 @@ paths:
tags:
- Network
summary: create or update an existing logical-link
- description: create or update an existing logical-link
+ description: |
+ Create or update an existing logical-link.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkLogicalLinksLogicalLink
consumes:
- application/json
@@ -15568,12 +20200,52 @@ paths:
description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: body
in: body
- description: logical-link object that needs to be created or updated
+ description: logical-link object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkLogicalLinksLogicalLink.json)
required: true
schema:
$ref: "#/definitions/logical-link"
+ patch:
+ tags:
+ - Network
+ summary: update an existing logical-link
+ description: |
+ Update an existing logical-link
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkLogicalLinksLogicalLink
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: link-name
+ in: path
+ description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
+ required: true
+ type: string
+ example: __LINK-NAME__
+ - name: body
+ in: body
+ description: logical-link object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/logical-link"
delete:
tags:
- Network
@@ -15595,6 +20267,7 @@ paths:
description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -15614,7 +20287,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/logical-links"
+ $ref: "#/getDefinitions/logical-links"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}/classes-of-service/class-of-service/{cos}/relationship-list/relationship:
@@ -15638,24 +20311,28 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: cos
in: path
description: unique identifier of probe
required: true
type: string
+ example: __COS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -15680,21 +20357,25 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: cos
in: path
description: unique identifier of probe
required: true
type: string
+ example: __COS__
/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}/classes-of-service/class-of-service/{cos}:
get:
tags:
@@ -15709,7 +20390,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/class-of-service"
+ $ref: "#/getDefinitions/class-of-service"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -15718,26 +20399,33 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: cos
in: path
description: unique identifier of probe
required: true
type: string
+ example: __COS__
put:
tags:
- Network
summary: create or update an existing class-of-service
- description: create or update an existing class-of-service
+ description: |
+ Create or update an existing class-of-service.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService
consumes:
- application/json
@@ -15754,27 +20442,88 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: cos
in: path
description: unique identifier of probe
required: true
type: string
+ example: __COS__
- name: body
in: body
- description: class-of-service object that needs to be created or updated
+ description: class-of-service object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService.json)
required: true
schema:
$ref: "#/definitions/class-of-service"
+ patch:
+ tags:
+ - Network
+ summary: update an existing class-of-service
+ description: |
+ Update an existing class-of-service
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: site-pair-set-id
+ in: path
+ description: Unique id of site pair set.
+ required: true
+ type: string
+ example: __SITE-PAIR-SET-ID__
+ - name: routing-instance-id
+ in: path
+ description: Unique id of routing instance
+ required: true
+ type: string
+ example: __ROUTING-INSTANCE-ID__
+ - name: site-pair-id
+ in: path
+ description: unique identifier of probe
+ required: true
+ type: string
+ example: __SITE-PAIR-ID__
+ - name: cos
+ in: path
+ description: unique identifier of probe
+ required: true
+ type: string
+ example: __COS__
+ - name: body
+ in: body
+ description: class-of-service object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/class-of-service"
delete:
tags:
- Network
@@ -15796,21 +20545,25 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: cos
in: path
description: unique identifier of probe
required: true
type: string
+ example: __COS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -15830,7 +20583,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/classes-of-service"
+ $ref: "#/getDefinitions/classes-of-service"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -15839,16 +20592,19 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}/relationship-list/relationship:
put:
tags:
@@ -15870,19 +20626,22 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -15907,16 +20666,19 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}:
get:
tags:
@@ -15931,7 +20693,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/site-pair"
+ $ref: "#/getDefinitions/site-pair"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -15940,21 +20702,27 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
put:
tags:
- Network
summary: create or update an existing site-pair
- description: create or update an existing site-pair
+ description: |
+ Create or update an existing site-pair.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair
consumes:
- application/json
@@ -15971,22 +20739,76 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: body
in: body
- description: site-pair object that needs to be created or updated
+ description: site-pair object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair.json)
required: true
schema:
$ref: "#/definitions/site-pair"
+ patch:
+ tags:
+ - Network
+ summary: update an existing site-pair
+ description: |
+ Update an existing site-pair
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: site-pair-set-id
+ in: path
+ description: Unique id of site pair set.
+ required: true
+ type: string
+ example: __SITE-PAIR-SET-ID__
+ - name: routing-instance-id
+ in: path
+ description: Unique id of routing instance
+ required: true
+ type: string
+ example: __ROUTING-INSTANCE-ID__
+ - name: site-pair-id
+ in: path
+ description: unique identifier of probe
+ required: true
+ type: string
+ example: __SITE-PAIR-ID__
+ - name: body
+ in: body
+ description: site-pair object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/site-pair"
delete:
tags:
- Network
@@ -16008,16 +20830,19 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: site-pair-id
in: path
description: unique identifier of probe
required: true
type: string
+ example: __SITE-PAIR-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -16037,7 +20862,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/site-pairs"
+ $ref: "#/getDefinitions/site-pairs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -16046,11 +20871,13 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/relationship-list/relationship:
put:
tags:
@@ -16072,14 +20899,16 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -16104,11 +20933,13 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
/network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}:
get:
tags:
@@ -16123,7 +20954,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/routing-instance"
+ $ref: "#/getDefinitions/routing-instance"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -16132,16 +20963,21 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
put:
tags:
- Network
summary: create or update an existing routing-instance
- description: create or update an existing routing-instance
+ description: |
+ Create or update an existing routing-instance.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance
consumes:
- application/json
@@ -16158,17 +20994,64 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: body
in: body
- description: routing-instance object that needs to be created or updated
+ description: routing-instance object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance.json)
required: true
schema:
$ref: "#/definitions/routing-instance"
+ patch:
+ tags:
+ - Network
+ summary: update an existing routing-instance
+ description: |
+ Update an existing routing-instance
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: site-pair-set-id
+ in: path
+ description: Unique id of site pair set.
+ required: true
+ type: string
+ example: __SITE-PAIR-SET-ID__
+ - name: routing-instance-id
+ in: path
+ description: Unique id of routing instance
+ required: true
+ type: string
+ example: __ROUTING-INSTANCE-ID__
+ - name: body
+ in: body
+ description: routing-instance object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/routing-instance"
delete:
tags:
- Network
@@ -16190,11 +21073,13 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: routing-instance-id
in: path
description: Unique id of routing instance
required: true
type: string
+ example: __ROUTING-INSTANCE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -16214,7 +21099,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/routing-instances"
+ $ref: "#/getDefinitions/routing-instances"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -16223,6 +21108,7 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
/network/site-pair-sets/site-pair-set/{site-pair-set-id}/relationship-list/relationship:
put:
tags:
@@ -16244,9 +21130,10 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkSitePairSetsSitePairSet.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -16271,6 +21158,7 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
/network/site-pair-sets/site-pair-set/{site-pair-set-id}:
get:
tags:
@@ -16285,7 +21173,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/site-pair-set"
+ $ref: "#/getDefinitions/site-pair-set"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -16294,11 +21182,15 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
put:
tags:
- Network
summary: create or update an existing site-pair-set
- description: create or update an existing site-pair-set
+ description: |
+ Create or update an existing site-pair-set.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkSitePairSetsSitePairSet
consumes:
- application/json
@@ -16315,12 +21207,52 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: body
in: body
- description: site-pair-set object that needs to be created or updated
+ description: site-pair-set object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkSitePairSetsSitePairSet.json)
required: true
schema:
$ref: "#/definitions/site-pair-set"
+ patch:
+ tags:
+ - Network
+ summary: update an existing site-pair-set
+ description: |
+ Update an existing site-pair-set
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkSitePairSetsSitePairSet
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: site-pair-set-id
+ in: path
+ description: Unique id of site pair set.
+ required: true
+ type: string
+ example: __SITE-PAIR-SET-ID__
+ - name: body
+ in: body
+ description: site-pair-set object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/site-pair-set"
delete:
tags:
- Network
@@ -16342,6 +21274,7 @@ paths:
description: Unique id of site pair set.
required: true
type: string
+ example: __SITE-PAIR-SET-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -16361,7 +21294,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/site-pair-sets"
+ $ref: "#/getDefinitions/site-pair-sets"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/vpn-bindings/vpn-binding/{vpn-id}/relationship-list/relationship:
@@ -16385,9 +21318,10 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVpnBindingsVpnBinding.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -16412,6 +21346,7 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
/network/vpn-bindings/vpn-binding/{vpn-id}:
get:
tags:
@@ -16426,7 +21361,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vpn-binding"
+ $ref: "#/getDefinitions/vpn-binding"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -16435,6 +21370,7 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
- name: vpn-name
in: query
description: VPN Name
@@ -16454,7 +21390,10 @@ paths:
tags:
- Network
summary: create or update an existing vpn-binding
- description: create or update an existing vpn-binding
+ description: |
+ Create or update an existing vpn-binding.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVpnBindingsVpnBinding
consumes:
- application/json
@@ -16471,12 +21410,52 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
- name: body
in: body
- description: vpn-binding object that needs to be created or updated
+ description: vpn-binding object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVpnBindingsVpnBinding.json)
required: true
schema:
$ref: "#/definitions/vpn-binding"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vpn-binding
+ description: |
+ Update an existing vpn-binding
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVpnBindingsVpnBinding
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vpn-id
+ in: path
+ description: VPN ID, globally unique within A&AI
+ required: true
+ type: string
+ example: __VPN-ID__
+ - name: body
+ in: body
+ description: vpn-binding object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vpn-binding"
delete:
tags:
- Network
@@ -16498,6 +21477,7 @@ paths:
description: VPN ID, globally unique within A&AI
required: true
type: string
+ example: __VPN-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -16517,7 +21497,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vpn-bindings"
+ $ref: "#/getDefinitions/vpn-bindings"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/vpls-pes/vpls-pe/{equipment-name}/relationship-list/relationship:
@@ -16540,9 +21520,10 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPe.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -16566,6 +21547,7 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/relationship-list/relationship:
put:
tags:
@@ -16586,14 +21568,16 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -16617,11 +21601,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -16642,24 +21628,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -16683,21 +21673,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -16718,29 +21712,34 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -16764,26 +21763,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -16798,7 +21802,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -16806,26 +21810,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -16882,7 +21891,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -16898,32 +21910,99 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -16944,26 +22023,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -16989,29 +22073,34 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -17035,26 +22124,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -17069,7 +22163,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -17077,26 +22171,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -17153,7 +22252,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -17169,32 +22271,99 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -17215,26 +22384,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -17254,7 +22428,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -17262,21 +22436,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -17317,7 +22495,10 @@ paths:
tags:
- Network
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -17333,27 +22514,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- Network
@@ -17374,21 +22615,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -17408,7 +22653,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -17416,16 +22661,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -17471,24 +22719,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -17512,21 +22764,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -17541,7 +22797,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -17549,21 +22805,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -17613,7 +22873,10 @@ paths:
tags:
- Network
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -17629,27 +22892,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- Network
@@ -17670,21 +22993,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -17704,7 +23031,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -17712,16 +23039,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -17767,19 +23097,22 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -17803,16 +23136,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -17833,24 +23169,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -17874,21 +23214,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -17903,7 +23247,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -17911,21 +23255,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -17971,7 +23319,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -17987,27 +23338,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -18028,21 +23439,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -18068,24 +23483,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -18109,21 +23528,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -18138,7 +23561,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -18146,21 +23569,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -18206,7 +23633,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -18222,27 +23652,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -18263,21 +23753,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -18297,7 +23791,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -18305,16 +23799,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -18344,7 +23841,10 @@ paths:
tags:
- Network
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface
consumes:
- application/json
@@ -18360,22 +23860,75 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- Network
@@ -18396,16 +23949,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -18425,7 +23981,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -18433,11 +23989,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -18462,7 +24020,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/p-interface"
+ $ref: "#/getDefinitions/p-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -18470,11 +24028,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -18489,7 +24049,10 @@ paths:
tags:
- Network
summary: create or update an existing p-interface
- description: create or update an existing p-interface
+ description: |
+ Create or update an existing p-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterface
consumes:
- application/json
@@ -18505,17 +24068,63 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: p-interface object that needs to be created or updated
+ description: p-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPePInterfacesPInterface.json)
required: true
schema:
$ref: "#/definitions/p-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing p-interface
+ description: |
+ Update an existing p-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: p-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/p-interface"
delete:
tags:
- Network
@@ -18536,11 +24145,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -18560,7 +24171,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/p-interfaces"
+ $ref: "#/getDefinitions/p-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -18568,6 +24179,7 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -18593,14 +24205,16 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -18624,11 +24238,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -18649,24 +24265,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -18690,21 +24310,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -18725,29 +24349,34 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -18771,26 +24400,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -18805,7 +24439,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -18813,26 +24447,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -18894,7 +24533,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -18910,32 +24552,99 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -18956,26 +24665,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -19001,29 +24715,34 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -19047,26 +24766,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -19081,7 +24805,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -19089,26 +24813,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -19170,7 +24899,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -19186,32 +24918,99 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -19232,26 +25031,31 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -19271,7 +25075,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -19279,21 +25083,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -19339,7 +25147,10 @@ paths:
tags:
- Network
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -19355,27 +25166,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- Network
@@ -19396,21 +25267,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -19430,7 +25305,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -19438,16 +25313,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -19498,24 +25376,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -19539,21 +25421,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -19568,7 +25454,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -19576,21 +25462,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -19645,7 +25535,10 @@ paths:
tags:
- Network
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -19661,27 +25554,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- Network
@@ -19702,21 +25655,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -19736,7 +25693,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -19744,16 +25701,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -19804,19 +25764,22 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -19840,16 +25803,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -19870,24 +25836,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -19911,21 +25881,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -19940,7 +25914,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -19948,21 +25922,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -20013,7 +25991,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -20029,27 +26010,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -20070,21 +26111,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -20110,24 +26155,28 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -20151,21 +26200,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -20180,7 +26233,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -20188,21 +26241,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -20253,7 +26310,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -20269,27 +26329,87 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -20310,21 +26430,25 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -20344,7 +26468,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -20352,16 +26476,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -20396,7 +26523,10 @@ paths:
tags:
- Network
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface
consumes:
- application/json
@@ -20412,22 +26542,75 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- Network
@@ -20448,16 +26631,19 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -20477,7 +26663,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -20485,11 +26671,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -20519,7 +26707,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interface"
+ $ref: "#/getDefinitions/lag-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -20527,11 +26715,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -20551,7 +26741,10 @@ paths:
tags:
- Network
summary: create or update an existing lag-interface
- description: create or update an existing lag-interface
+ description: |
+ Create or update an existing lag-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterface
consumes:
- application/json
@@ -20567,17 +26760,63 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: lag-interface object that needs to be created or updated
+ description: lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPeLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/lag-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing lag-interface
+ description: |
+ Update an existing lag-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: lag-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/lag-interface"
delete:
tags:
- Network
@@ -20598,11 +26837,13 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -20622,7 +26863,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interfaces"
+ $ref: "#/getDefinitions/lag-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -20630,6 +26871,7 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -20649,7 +26891,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vpls-pe"
+ $ref: "#/getDefinitions/vpls-pe"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -20657,6 +26899,7 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: prov-status
in: query
description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
@@ -20666,7 +26909,10 @@ paths:
tags:
- Network
summary: create or update an existing vpls-pe
- description: create or update an existing vpls-pe
+ description: |
+ Create or update an existing vpls-pe.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVplsPesVplsPe
consumes:
- application/json
@@ -20682,12 +26928,51 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: body
in: body
- description: vpls-pe object that needs to be created or updated
+ description: vpls-pe object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVplsPesVplsPe.json)
required: true
schema:
$ref: "#/definitions/vpls-pe"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vpls-pe
+ description: |
+ Update an existing vpls-pe
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVplsPesVplsPe
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: equipment-name
+ in: path
+ required: true
+ type: string
+ example: __EQUIPMENT-NAME__
+ - name: body
+ in: body
+ description: vpls-pe object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vpls-pe"
delete:
tags:
- Network
@@ -20708,6 +26993,7 @@ paths:
in: path
required: true
type: string
+ example: __EQUIPMENT-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -20727,7 +27013,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vpls-pes"
+ $ref: "#/getDefinitions/vpls-pes"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/multicast-configurations/multicast-configuration/{multicast-configuration-id}/relationship-list/relationship:
@@ -20751,9 +27037,10 @@ paths:
description: Unique id of multicast configuration.
required: true
type: string
+ example: __MULTICAST-CONFIGURATION-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkMulticastConfigurationsMulticastConfiguration.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -20778,6 +27065,7 @@ paths:
description: Unique id of multicast configuration.
required: true
type: string
+ example: __MULTICAST-CONFIGURATION-ID__
/network/multicast-configurations/multicast-configuration/{multicast-configuration-id}:
get:
tags:
@@ -20792,7 +27080,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/multicast-configuration"
+ $ref: "#/getDefinitions/multicast-configuration"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -20801,11 +27089,15 @@ paths:
description: Unique id of multicast configuration.
required: true
type: string
+ example: __MULTICAST-CONFIGURATION-ID__
put:
tags:
- Network
summary: create or update an existing multicast-configuration
- description: create or update an existing multicast-configuration
+ description: |
+ Create or update an existing multicast-configuration.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkMulticastConfigurationsMulticastConfiguration
consumes:
- application/json
@@ -20822,12 +27114,52 @@ paths:
description: Unique id of multicast configuration.
required: true
type: string
+ example: __MULTICAST-CONFIGURATION-ID__
- name: body
in: body
- description: multicast-configuration object that needs to be created or updated
+ description: multicast-configuration object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkMulticastConfigurationsMulticastConfiguration.json)
required: true
schema:
$ref: "#/definitions/multicast-configuration"
+ patch:
+ tags:
+ - Network
+ summary: update an existing multicast-configuration
+ description: |
+ Update an existing multicast-configuration
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkMulticastConfigurationsMulticastConfiguration
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: multicast-configuration-id
+ in: path
+ description: Unique id of multicast configuration.
+ required: true
+ type: string
+ example: __MULTICAST-CONFIGURATION-ID__
+ - name: body
+ in: body
+ description: multicast-configuration object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/multicast-configuration"
delete:
tags:
- Network
@@ -20849,6 +27181,7 @@ paths:
description: Unique id of multicast configuration.
required: true
type: string
+ example: __MULTICAST-CONFIGURATION-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -20868,7 +27201,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/multicast-configurations"
+ $ref: "#/getDefinitions/multicast-configurations"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}/cvlan-tags/cvlan-tag-entry/{cvlan-tag}/relationship-list/relationship:
@@ -20892,20 +27225,23 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: cvlan-tag
in: path
description: See mis-na-virtualization-platform.yang
required: true
type: integer
format: int64
+ example: __CVLAN-TAG__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -20930,17 +27266,20 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: cvlan-tag
in: path
description: See mis-na-virtualization-platform.yang
required: true
type: integer
format: int64
+ example: __CVLAN-TAG__
/network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}/cvlan-tags/cvlan-tag-entry/{cvlan-tag}:
get:
tags:
@@ -20955,7 +27294,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/cvlan-tag-entry"
+ $ref: "#/getDefinitions/cvlan-tag-entry"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -20964,17 +27303,20 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: cvlan-tag
in: path
description: See mis-na-virtualization-platform.yang
required: true
type: integer
format: int64
+ example: __CVLAN-TAG__
- name: vnf-name
in: query
description: Name of VNF.
@@ -21034,7 +27376,10 @@ paths:
tags:
- Network
summary: create or update an existing cvlan-tag-entry
- description: create or update an existing cvlan-tag-entry
+ description: |
+ Create or update an existing cvlan-tag-entry.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry
consumes:
- application/json
@@ -21051,23 +27396,78 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: cvlan-tag
in: path
description: See mis-na-virtualization-platform.yang
required: true
type: integer
format: int64
+ example: __CVLAN-TAG__
- name: body
in: body
- description: cvlan-tag-entry object that needs to be created or updated
+ description: cvlan-tag-entry object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry.json)
required: true
schema:
$ref: "#/definitions/cvlan-tag-entry"
+ patch:
+ tags:
+ - Network
+ summary: update an existing cvlan-tag-entry
+ description: |
+ Update an existing cvlan-tag-entry
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-id
+ in: path
+ description: Unique ID of the interface
+ required: true
+ type: string
+ example: __INTERFACE-ID__
+ - name: cvlan-tag
+ in: path
+ description: See mis-na-virtualization-platform.yang
+ required: true
+ type: integer
+ format: int64
+ example: __CVLAN-TAG__
+ - name: body
+ in: body
+ description: cvlan-tag-entry object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/cvlan-tag-entry"
delete:
tags:
- Network
@@ -21089,17 +27489,20 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: cvlan-tag
in: path
description: See mis-na-virtualization-platform.yang
required: true
type: integer
format: int64
+ example: __CVLAN-TAG__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -21119,7 +27522,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/cvlan-tags"
+ $ref: "#/getDefinitions/cvlan-tags"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -21128,11 +27531,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -21209,14 +27614,16 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVcesVcePortGroupsPortGroup.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -21241,11 +27648,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
/network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}:
get:
tags:
@@ -21260,7 +27669,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/port-group"
+ $ref: "#/getDefinitions/port-group"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -21269,11 +27678,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -21333,7 +27744,10 @@ paths:
tags:
- Network
summary: create or update an existing port-group
- description: create or update an existing port-group
+ description: |
+ Create or update an existing port-group.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVcesVcePortGroupsPortGroup
consumes:
- application/json
@@ -21350,17 +27764,64 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: body
in: body
- description: port-group object that needs to be created or updated
+ description: port-group object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVcesVcePortGroupsPortGroup.json)
required: true
schema:
$ref: "#/definitions/port-group"
+ patch:
+ tags:
+ - Network
+ summary: update an existing port-group
+ description: |
+ Update an existing port-group
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVcesVcePortGroupsPortGroup
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-id
+ in: path
+ description: Unique ID of the interface
+ required: true
+ type: string
+ example: __INTERFACE-ID__
+ - name: body
+ in: body
+ description: port-group object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/port-group"
delete:
tags:
- Network
@@ -21382,11 +27843,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-id
in: path
description: Unique ID of the interface
required: true
type: string
+ example: __INTERFACE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -21406,7 +27869,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/port-groups"
+ $ref: "#/getDefinitions/port-groups"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -21415,6 +27878,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -21476,19 +27940,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the license group the resource belongs to, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of a license resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVcesVceLicensesLicense.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -21513,16 +27980,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the license group the resource belongs to, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of a license resource.
required: true
type: string
+ example: __RESOURCE-UUID__
/network/vces/vce/{vnf-id}/licenses/license/{group-uuid}/{resource-uuid}:
get:
tags:
@@ -21537,7 +28007,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/license"
+ $ref: "#/getDefinitions/license"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -21546,16 +28016,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the license group the resource belongs to, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of a license resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -21600,7 +28073,10 @@ paths:
tags:
- Network
summary: create or update an existing license
- description: create or update an existing license
+ description: |
+ Create or update an existing license.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVcesVceLicensesLicense
consumes:
- application/json
@@ -21617,22 +28093,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the license group the resource belongs to, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of a license resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: body
in: body
- description: license object that needs to be created or updated
+ description: license object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVcesVceLicensesLicense.json)
required: true
schema:
$ref: "#/definitions/license"
+ patch:
+ tags:
+ - Network
+ summary: update an existing license
+ description: |
+ Update an existing license
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVcesVceLicensesLicense
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: group-uuid
+ in: path
+ description: Unique ID for the license group the resource belongs to, should be uuid.
+ required: true
+ type: string
+ example: __GROUP-UUID__
+ - name: resource-uuid
+ in: path
+ description: Unique ID of a license resource.
+ required: true
+ type: string
+ example: __RESOURCE-UUID__
+ - name: body
+ in: body
+ description: license object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/license"
delete:
tags:
- Network
@@ -21654,16 +28184,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the license group the resource belongs to, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of a license resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -21683,7 +28216,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/licenses"
+ $ref: "#/getDefinitions/licenses"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -21692,6 +28225,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -21753,19 +28287,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the entitlement group the resource comes from, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of an entitlement resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVcesVceEntitlementsEntitlement.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -21790,16 +28327,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the entitlement group the resource comes from, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of an entitlement resource.
required: true
type: string
+ example: __RESOURCE-UUID__
/network/vces/vce/{vnf-id}/entitlements/entitlement/{group-uuid}/{resource-uuid}:
get:
tags:
@@ -21814,7 +28354,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/entitlement"
+ $ref: "#/getDefinitions/entitlement"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -21823,16 +28363,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the entitlement group the resource comes from, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of an entitlement resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -21877,7 +28420,10 @@ paths:
tags:
- Network
summary: create or update an existing entitlement
- description: create or update an existing entitlement
+ description: |
+ Create or update an existing entitlement.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVcesVceEntitlementsEntitlement
consumes:
- application/json
@@ -21894,22 +28440,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the entitlement group the resource comes from, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of an entitlement resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: body
in: body
- description: entitlement object that needs to be created or updated
+ description: entitlement object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVcesVceEntitlementsEntitlement.json)
required: true
schema:
$ref: "#/definitions/entitlement"
+ patch:
+ tags:
+ - Network
+ summary: update an existing entitlement
+ description: |
+ Update an existing entitlement
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVcesVceEntitlementsEntitlement
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: group-uuid
+ in: path
+ description: Unique ID for the entitlement group the resource comes from, should be uuid.
+ required: true
+ type: string
+ example: __GROUP-UUID__
+ - name: resource-uuid
+ in: path
+ description: Unique ID of an entitlement resource.
+ required: true
+ type: string
+ example: __RESOURCE-UUID__
+ - name: body
+ in: body
+ description: entitlement object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/entitlement"
delete:
tags:
- Network
@@ -21931,16 +28531,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the entitlement group the resource comes from, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of an entitlement resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -21960,7 +28563,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/entitlements"
+ $ref: "#/getDefinitions/entitlements"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -21969,6 +28572,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -22030,9 +28634,10 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVcesVce.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -22057,6 +28662,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
/network/vces/vce/{vnf-id}:
get:
tags:
@@ -22071,7 +28677,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vce"
+ $ref: "#/getDefinitions/vce"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -22080,6 +28686,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -22124,7 +28731,10 @@ paths:
tags:
- Network
summary: create or update an existing vce
- description: create or update an existing vce
+ description: |
+ Create or update an existing vce.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVcesVce
consumes:
- application/json
@@ -22141,12 +28751,52 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: body
in: body
- description: vce object that needs to be created or updated
+ description: vce object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVcesVce.json)
required: true
schema:
$ref: "#/definitions/vce"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vce
+ description: |
+ Update an existing vce
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVcesVce
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: body
+ in: body
+ description: vce object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vce"
delete:
tags:
- Network
@@ -22168,6 +28818,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -22187,7 +28838,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vces"
+ $ref: "#/getDefinitions/vces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/vnfcs/vnfc/{vnfc-name}/relationship-list/relationship:
@@ -22211,9 +28862,10 @@ paths:
description: Unique ID of vnfc.
required: true
type: string
+ example: __VNFC-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVnfcsVnfc.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -22238,6 +28890,7 @@ paths:
description: Unique ID of vnfc.
required: true
type: string
+ example: __VNFC-NAME__
/network/vnfcs/vnfc/{vnfc-name}:
get:
tags:
@@ -22252,7 +28905,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vnfc"
+ $ref: "#/getDefinitions/vnfc"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -22261,6 +28914,7 @@ paths:
description: Unique ID of vnfc.
required: true
type: string
+ example: __VNFC-NAME__
- name: vnfc-function-code
in: query
description: function code
@@ -22298,7 +28952,10 @@ paths:
tags:
- Network
summary: create or update an existing vnfc
- description: create or update an existing vnfc
+ description: |
+ Create or update an existing vnfc.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkVnfcsVnfc
consumes:
- application/json
@@ -22315,12 +28972,52 @@ paths:
description: Unique ID of vnfc.
required: true
type: string
+ example: __VNFC-NAME__
- name: body
in: body
- description: vnfc object that needs to be created or updated
+ description: vnfc object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkVnfcsVnfc.json)
required: true
schema:
$ref: "#/definitions/vnfc"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vnfc
+ description: |
+ Update an existing vnfc
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkVnfcsVnfc
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnfc-name
+ in: path
+ description: Unique ID of vnfc.
+ required: true
+ type: string
+ example: __VNFC-NAME__
+ - name: body
+ in: body
+ description: vnfc object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vnfc"
delete:
tags:
- Network
@@ -22342,6 +29039,7 @@ paths:
description: Unique ID of vnfc.
required: true
type: string
+ example: __VNFC-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -22361,7 +29059,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vnfcs"
+ $ref: "#/getDefinitions/vnfcs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/l3-networks/l3-network/{network-id}/subnets/subnet/{subnet-id}/relationship-list/relationship:
@@ -22385,14 +29083,16 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: subnet-id
in: path
description: Subnet ID, should be UUID.
required: true
type: string
+ example: __SUBNET-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkL3NetworksL3NetworkSubnetsSubnet.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -22417,11 +29117,13 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: subnet-id
in: path
description: Subnet ID, should be UUID.
required: true
type: string
+ example: __SUBNET-ID__
/network/l3-networks/l3-network/{network-id}/subnets/subnet/{subnet-id}:
get:
tags:
@@ -22436,7 +29138,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/subnet"
+ $ref: "#/getDefinitions/subnet"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -22445,11 +29147,13 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: subnet-id
in: path
description: Subnet ID, should be UUID.
required: true
type: string
+ example: __SUBNET-ID__
- name: network-name
in: query
description: Name of the network, governed by some naming convention..
@@ -22504,7 +29208,10 @@ paths:
tags:
- Network
summary: create or update an existing subnet
- description: create or update an existing subnet
+ description: |
+ Create or update an existing subnet.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkL3NetworksL3NetworkSubnetsSubnet
consumes:
- application/json
@@ -22521,17 +29228,64 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: subnet-id
in: path
description: Subnet ID, should be UUID.
required: true
type: string
+ example: __SUBNET-ID__
- name: body
in: body
- description: subnet object that needs to be created or updated
+ description: subnet object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkL3NetworksL3NetworkSubnetsSubnet.json)
required: true
schema:
$ref: "#/definitions/subnet"
+ patch:
+ tags:
+ - Network
+ summary: update an existing subnet
+ description: |
+ Update an existing subnet
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkL3NetworksL3NetworkSubnetsSubnet
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: network-id
+ in: path
+ description: Network ID, should be uuid. Unique across A&AI.
+ required: true
+ type: string
+ example: __NETWORK-ID__
+ - name: subnet-id
+ in: path
+ description: Subnet ID, should be UUID.
+ required: true
+ type: string
+ example: __SUBNET-ID__
+ - name: body
+ in: body
+ description: subnet object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/subnet"
delete:
tags:
- Network
@@ -22553,11 +29307,13 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: subnet-id
in: path
description: Subnet ID, should be UUID.
required: true
type: string
+ example: __SUBNET-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -22577,7 +29333,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/subnets"
+ $ref: "#/getDefinitions/subnets"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -22586,6 +29342,7 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: network-name
in: query
description: Name of the network, governed by some naming convention..
@@ -22652,15 +29409,17 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: vlan-id-inner
in: path
description: id.
required: true
type: integer
format: int64
+ example: __VLAN-ID-INNER__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -22685,12 +29444,14 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: vlan-id-inner
in: path
description: id.
required: true
type: integer
format: int64
+ example: __VLAN-ID-INNER__
/network/l3-networks/l3-network/{network-id}/ctag-assignments/ctag-assignment/{vlan-id-inner}:
get:
tags:
@@ -22705,7 +29466,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/ctag-assignment"
+ $ref: "#/getDefinitions/ctag-assignment"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -22714,12 +29475,14 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: vlan-id-inner
in: path
description: id.
required: true
type: integer
format: int64
+ example: __VLAN-ID-INNER__
- name: network-name
in: query
description: Name of the network, governed by some naming convention..
@@ -22769,7 +29532,10 @@ paths:
tags:
- Network
summary: create or update an existing ctag-assignment
- description: create or update an existing ctag-assignment
+ description: |
+ Create or update an existing ctag-assignment.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment
consumes:
- application/json
@@ -22786,18 +29552,66 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: vlan-id-inner
in: path
description: id.
required: true
type: integer
format: int64
+ example: __VLAN-ID-INNER__
- name: body
in: body
- description: ctag-assignment object that needs to be created or updated
+ description: ctag-assignment object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment.json)
required: true
schema:
$ref: "#/definitions/ctag-assignment"
+ patch:
+ tags:
+ - Network
+ summary: update an existing ctag-assignment
+ description: |
+ Update an existing ctag-assignment
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: network-id
+ in: path
+ description: Network ID, should be uuid. Unique across A&AI.
+ required: true
+ type: string
+ example: __NETWORK-ID__
+ - name: vlan-id-inner
+ in: path
+ description: id.
+ required: true
+ type: integer
+ format: int64
+ example: __VLAN-ID-INNER__
+ - name: body
+ in: body
+ description: ctag-assignment object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/ctag-assignment"
delete:
tags:
- Network
@@ -22819,12 +29633,14 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: vlan-id-inner
in: path
description: id.
required: true
type: integer
format: int64
+ example: __VLAN-ID-INNER__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -22844,7 +29660,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/ctag-assignments"
+ $ref: "#/getDefinitions/ctag-assignments"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -22853,6 +29669,7 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: network-name
in: query
description: Name of the network, governed by some naming convention..
@@ -22919,14 +29736,16 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: segmentation-id
in: path
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __SEGMENTATION-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -22951,11 +29770,13 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: segmentation-id
in: path
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __SEGMENTATION-ID__
/network/l3-networks/l3-network/{network-id}/segmentation-assignments/segmentation-assignment/{segmentation-id}:
get:
tags:
@@ -22970,7 +29791,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/segmentation-assignment"
+ $ref: "#/getDefinitions/segmentation-assignment"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -22979,11 +29800,13 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: segmentation-id
in: path
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __SEGMENTATION-ID__
- name: network-name
in: query
description: Name of the network, governed by some naming convention..
@@ -23033,7 +29856,10 @@ paths:
tags:
- Network
summary: create or update an existing segmentation-assignment
- description: create or update an existing segmentation-assignment
+ description: |
+ Create or update an existing segmentation-assignment.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment
consumes:
- application/json
@@ -23050,17 +29876,64 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: segmentation-id
in: path
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __SEGMENTATION-ID__
- name: body
in: body
- description: segmentation-assignment object that needs to be created or updated
+ description: segmentation-assignment object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment.json)
required: true
schema:
$ref: "#/definitions/segmentation-assignment"
+ patch:
+ tags:
+ - Network
+ summary: update an existing segmentation-assignment
+ description: |
+ Update an existing segmentation-assignment
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: network-id
+ in: path
+ description: Network ID, should be uuid. Unique across A&AI.
+ required: true
+ type: string
+ example: __NETWORK-ID__
+ - name: segmentation-id
+ in: path
+ description: Route Table Reference id, UUID assigned to this instance.
+ required: true
+ type: string
+ example: __SEGMENTATION-ID__
+ - name: body
+ in: body
+ description: segmentation-assignment object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/segmentation-assignment"
delete:
tags:
- Network
@@ -23082,11 +29955,13 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: segmentation-id
in: path
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __SEGMENTATION-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -23106,7 +29981,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/segmentation-assignments"
+ $ref: "#/getDefinitions/segmentation-assignments"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -23115,6 +29990,7 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: network-name
in: query
description: Name of the network, governed by some naming convention..
@@ -23181,9 +30057,10 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkL3NetworksL3Network.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -23208,6 +30085,7 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
/network/l3-networks/l3-network/{network-id}:
get:
tags:
@@ -23222,7 +30100,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-network"
+ $ref: "#/getDefinitions/l3-network"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -23231,6 +30109,7 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: network-name
in: query
description: Name of the network, governed by some naming convention..
@@ -23280,7 +30159,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-network
- description: create or update an existing l3-network
+ description: |
+ Create or update an existing l3-network.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkL3NetworksL3Network
consumes:
- application/json
@@ -23297,12 +30179,52 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: body
in: body
- description: l3-network object that needs to be created or updated
+ description: l3-network object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkL3NetworksL3Network.json)
required: true
schema:
$ref: "#/definitions/l3-network"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-network
+ description: |
+ Update an existing l3-network
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkL3NetworksL3Network
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: network-id
+ in: path
+ description: Network ID, should be uuid. Unique across A&AI.
+ required: true
+ type: string
+ example: __NETWORK-ID__
+ - name: body
+ in: body
+ description: l3-network object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-network"
delete:
tags:
- Network
@@ -23324,6 +30246,7 @@ paths:
description: Network ID, should be uuid. Unique across A&AI.
required: true
type: string
+ example: __NETWORK-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -23343,7 +30266,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-networks"
+ $ref: "#/getDefinitions/l3-networks"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/network-policies/network-policy/{network-policy-id}/relationship-list/relationship:
@@ -23367,9 +30290,10 @@ paths:
description: UUID representing unique key to this instance
required: true
type: string
+ example: __NETWORK-POLICY-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNetworkPoliciesNetworkPolicy.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -23394,6 +30318,7 @@ paths:
description: UUID representing unique key to this instance
required: true
type: string
+ example: __NETWORK-POLICY-ID__
/network/network-policies/network-policy/{network-policy-id}:
get:
tags:
@@ -23408,7 +30333,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/network-policy"
+ $ref: "#/getDefinitions/network-policy"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -23417,6 +30342,7 @@ paths:
description: UUID representing unique key to this instance
required: true
type: string
+ example: __NETWORK-POLICY-ID__
- name: network-policy-fqdn
in: query
description: Contrail FQDN for the policy
@@ -23426,7 +30352,10 @@ paths:
tags:
- Network
summary: create or update an existing network-policy
- description: create or update an existing network-policy
+ description: |
+ Create or update an existing network-policy.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNetworkPoliciesNetworkPolicy
consumes:
- application/json
@@ -23443,12 +30372,52 @@ paths:
description: UUID representing unique key to this instance
required: true
type: string
+ example: __NETWORK-POLICY-ID__
- name: body
in: body
- description: network-policy object that needs to be created or updated
+ description: network-policy object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNetworkPoliciesNetworkPolicy.json)
required: true
schema:
$ref: "#/definitions/network-policy"
+ patch:
+ tags:
+ - Network
+ summary: update an existing network-policy
+ description: |
+ Update an existing network-policy
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNetworkPoliciesNetworkPolicy
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: network-policy-id
+ in: path
+ description: UUID representing unique key to this instance
+ required: true
+ type: string
+ example: __NETWORK-POLICY-ID__
+ - name: body
+ in: body
+ description: network-policy object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/network-policy"
delete:
tags:
- Network
@@ -23470,6 +30439,7 @@ paths:
description: UUID representing unique key to this instance
required: true
type: string
+ example: __NETWORK-POLICY-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -23489,7 +30459,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/network-policies"
+ $ref: "#/getDefinitions/network-policies"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/generic-vnfs/generic-vnf/{vnf-id}/relationship-list/relationship:
@@ -23513,9 +30483,10 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -23540,6 +30511,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -23561,19 +30533,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -23598,16 +30573,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -23629,24 +30607,28 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -23671,21 +30653,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -23700,7 +30686,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -23709,21 +30695,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -23833,7 +30823,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -23850,27 +30843,88 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -23892,21 +30946,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -23933,24 +30991,28 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -23975,21 +31037,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -24004,7 +31070,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -24013,21 +31079,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -24137,7 +31207,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -24154,27 +31227,88 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -24196,21 +31330,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -24230,7 +31368,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -24239,16 +31377,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: vnf-name
in: query
description: Name of VNF.
@@ -24342,7 +31483,10 @@ paths:
tags:
- Network
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -24359,22 +31503,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- Network
@@ -24396,16 +31594,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -24425,7 +31626,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -24434,11 +31635,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -24538,19 +31741,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -24575,16 +31781,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -24599,7 +31808,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -24608,16 +31817,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -24720,7 +31932,10 @@ paths:
tags:
- Network
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -24737,22 +31952,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- Network
@@ -24774,16 +32043,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -24803,7 +32075,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -24812,11 +32084,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -24916,14 +32190,16 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -24948,11 +32224,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -24974,19 +32252,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -25011,16 +32292,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -25035,7 +32319,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -25044,16 +32328,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -25152,7 +32439,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -25169,22 +32459,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -25206,16 +32550,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -25242,19 +32589,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -25279,16 +32629,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -25303,7 +32656,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -25312,16 +32665,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -25420,7 +32776,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -25437,22 +32796,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -25474,16 +32887,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -25503,7 +32919,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -25512,11 +32928,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -25599,7 +33017,10 @@ paths:
tags:
- Network
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterface
consumes:
- application/json
@@ -25616,17 +33037,64 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- Network
@@ -25648,11 +33116,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -25672,7 +33142,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -25681,6 +33151,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -25765,14 +33236,16 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -25797,11 +33270,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -25823,24 +33298,28 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -25865,21 +33344,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -25901,29 +33384,34 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -25948,26 +33436,31 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -25982,7 +33475,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -25991,26 +33484,31 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -26130,7 +33628,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -26147,32 +33648,100 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -26194,26 +33763,31 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -26240,29 +33814,34 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -26287,26 +33866,31 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -26321,7 +33905,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -26330,26 +33914,31 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -26469,7 +34058,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -26486,32 +34078,100 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -26533,26 +34193,31 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -26572,7 +34237,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -26581,21 +34246,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: vnf-name
in: query
description: Name of VNF.
@@ -26699,7 +34368,10 @@ paths:
tags:
- Network
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -26716,27 +34388,88 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- Network
@@ -26758,21 +34491,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -26792,7 +34529,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -26801,16 +34538,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -26920,24 +34660,28 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -26962,21 +34706,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -26991,7 +34739,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -27000,21 +34748,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -27127,7 +34879,10 @@ paths:
tags:
- Network
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -27144,27 +34899,88 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- Network
@@ -27186,21 +35002,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -27220,7 +35040,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -27229,16 +35049,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -27348,19 +35171,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -27385,16 +35211,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -27416,24 +35245,28 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -27458,21 +35291,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -27487,7 +35324,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -27496,21 +35333,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -27619,7 +35460,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -27636,27 +35480,88 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -27678,21 +35583,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -27719,24 +35628,28 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -27761,21 +35674,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -27790,7 +35707,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -27799,21 +35716,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -27922,7 +35843,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -27939,27 +35863,88 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -27981,21 +35966,25 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -28015,7 +36004,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -28024,16 +36013,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -28126,7 +36118,10 @@ paths:
tags:
- Network
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface
consumes:
- application/json
@@ -28143,22 +36138,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- Network
@@ -28180,16 +36229,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -28209,7 +36261,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -28218,11 +36270,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -28310,7 +36364,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interface"
+ $ref: "#/getDefinitions/lag-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -28319,11 +36373,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -28401,7 +36457,10 @@ paths:
tags:
- Network
summary: create or update an existing lag-interface
- description: create or update an existing lag-interface
+ description: |
+ Create or update an existing lag-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterface
consumes:
- application/json
@@ -28418,17 +36477,64 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: lag-interface object that needs to be created or updated
+ description: lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/lag-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing lag-interface
+ description: |
+ Update an existing lag-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: lag-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/lag-interface"
delete:
tags:
- Network
@@ -28450,11 +36556,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -28474,7 +36582,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interfaces"
+ $ref: "#/getDefinitions/lag-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -28483,6 +36591,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -28567,14 +36676,16 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vf-module-id
in: path
description: Unique ID of vf-module.
required: true
type: string
+ example: __VF-MODULE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfVfModulesVfModule.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -28599,11 +36710,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vf-module-id
in: path
description: Unique ID of vf-module.
required: true
type: string
+ example: __VF-MODULE-ID__
/network/generic-vnfs/generic-vnf/{vnf-id}/vf-modules/vf-module/{vf-module-id}:
get:
tags:
@@ -28618,7 +36731,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vf-module"
+ $ref: "#/getDefinitions/vf-module"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -28627,11 +36740,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vf-module-id
in: path
description: Unique ID of vf-module.
required: true
type: string
+ example: __VF-MODULE-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -28734,7 +36849,10 @@ paths:
tags:
- Network
summary: create or update an existing vf-module
- description: create or update an existing vf-module
+ description: |
+ Create or update an existing vf-module.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfVfModulesVfModule
consumes:
- application/json
@@ -28751,17 +36869,64 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vf-module-id
in: path
description: Unique ID of vf-module.
required: true
type: string
+ example: __VF-MODULE-ID__
- name: body
in: body
- description: vf-module object that needs to be created or updated
+ description: vf-module object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfVfModulesVfModule.json)
required: true
schema:
$ref: "#/definitions/vf-module"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vf-module
+ description: |
+ Update an existing vf-module
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfVfModulesVfModule
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: vf-module-id
+ in: path
+ description: Unique ID of vf-module.
+ required: true
+ type: string
+ example: __VF-MODULE-ID__
+ - name: body
+ in: body
+ description: vf-module object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vf-module"
delete:
tags:
- Network
@@ -28783,11 +36948,13 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vf-module-id
in: path
description: Unique ID of vf-module.
required: true
type: string
+ example: __VF-MODULE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -28807,7 +36974,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vf-modules"
+ $ref: "#/getDefinitions/vf-modules"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -28816,6 +36983,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -28900,19 +37068,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the license group the resource belongs to, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of a license resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLicensesLicense.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -28937,16 +37108,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the license group the resource belongs to, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of a license resource.
required: true
type: string
+ example: __RESOURCE-UUID__
/network/generic-vnfs/generic-vnf/{vnf-id}/licenses/license/{group-uuid}/{resource-uuid}:
get:
tags:
@@ -28961,7 +37135,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/license"
+ $ref: "#/getDefinitions/license"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -28970,16 +37144,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the license group the resource belongs to, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of a license resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -29047,7 +37224,10 @@ paths:
tags:
- Network
summary: create or update an existing license
- description: create or update an existing license
+ description: |
+ Create or update an existing license.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfLicensesLicense
consumes:
- application/json
@@ -29064,22 +37244,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the license group the resource belongs to, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of a license resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: body
in: body
- description: license object that needs to be created or updated
+ description: license object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfLicensesLicense.json)
required: true
schema:
$ref: "#/definitions/license"
+ patch:
+ tags:
+ - Network
+ summary: update an existing license
+ description: |
+ Update an existing license
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfLicensesLicense
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: group-uuid
+ in: path
+ description: Unique ID for the license group the resource belongs to, should be uuid.
+ required: true
+ type: string
+ example: __GROUP-UUID__
+ - name: resource-uuid
+ in: path
+ description: Unique ID of a license resource.
+ required: true
+ type: string
+ example: __RESOURCE-UUID__
+ - name: body
+ in: body
+ description: license object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/license"
delete:
tags:
- Network
@@ -29101,16 +37335,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the license group the resource belongs to, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of a license resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -29130,7 +37367,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/licenses"
+ $ref: "#/getDefinitions/licenses"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -29139,6 +37376,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -29223,19 +37461,22 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the entitlement group the resource comes from, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of an entitlement resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfEntitlementsEntitlement.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -29260,16 +37501,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the entitlement group the resource comes from, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of an entitlement resource.
required: true
type: string
+ example: __RESOURCE-UUID__
/network/generic-vnfs/generic-vnf/{vnf-id}/entitlements/entitlement/{group-uuid}/{resource-uuid}:
get:
tags:
@@ -29284,7 +37528,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/entitlement"
+ $ref: "#/getDefinitions/entitlement"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -29293,16 +37537,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the entitlement group the resource comes from, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of an entitlement resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -29370,7 +37617,10 @@ paths:
tags:
- Network
summary: create or update an existing entitlement
- description: create or update an existing entitlement
+ description: |
+ Create or update an existing entitlement.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnfEntitlementsEntitlement
consumes:
- application/json
@@ -29387,22 +37637,76 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the entitlement group the resource comes from, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of an entitlement resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: body
in: body
- description: entitlement object that needs to be created or updated
+ description: entitlement object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnfEntitlementsEntitlement.json)
required: true
schema:
$ref: "#/definitions/entitlement"
+ patch:
+ tags:
+ - Network
+ summary: update an existing entitlement
+ description: |
+ Update an existing entitlement
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnfEntitlementsEntitlement
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: group-uuid
+ in: path
+ description: Unique ID for the entitlement group the resource comes from, should be uuid.
+ required: true
+ type: string
+ example: __GROUP-UUID__
+ - name: resource-uuid
+ in: path
+ description: Unique ID of an entitlement resource.
+ required: true
+ type: string
+ example: __RESOURCE-UUID__
+ - name: body
+ in: body
+ description: entitlement object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/entitlement"
delete:
tags:
- Network
@@ -29424,16 +37728,19 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: group-uuid
in: path
description: Unique ID for the entitlement group the resource comes from, should be uuid.
required: true
type: string
+ example: __GROUP-UUID__
- name: resource-uuid
in: path
description: Unique ID of an entitlement resource.
required: true
type: string
+ example: __RESOURCE-UUID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -29453,7 +37760,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/entitlements"
+ $ref: "#/getDefinitions/entitlements"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -29462,6 +37769,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -29539,7 +37847,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/generic-vnf"
+ $ref: "#/getDefinitions/generic-vnf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -29548,6 +37856,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -29615,7 +37924,10 @@ paths:
tags:
- Network
summary: create or update an existing generic-vnf
- description: create or update an existing generic-vnf
+ description: |
+ Create or update an existing generic-vnf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkGenericVnfsGenericVnf
consumes:
- application/json
@@ -29632,12 +37944,52 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: body
in: body
- description: generic-vnf object that needs to be created or updated
+ description: generic-vnf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkGenericVnfsGenericVnf.json)
required: true
schema:
$ref: "#/definitions/generic-vnf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing generic-vnf
+ description: |
+ Update an existing generic-vnf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkGenericVnfsGenericVnf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id
+ in: path
+ description: Unique id of VNF. This is unique across the graph.
+ required: true
+ type: string
+ example: __VNF-ID__
+ - name: body
+ in: body
+ description: generic-vnf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/generic-vnf"
delete:
tags:
- Network
@@ -29659,6 +38011,7 @@ paths:
description: Unique id of VNF. This is unique across the graph.
required: true
type: string
+ example: __VNF-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -29678,7 +38031,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/generic-vnfs"
+ $ref: "#/getDefinitions/generic-vnfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/lag-links/lag-link/{link-name}/relationship-list/relationship:
@@ -29702,9 +38055,10 @@ paths:
description: Alphabetical concatenation of lag-interface names
required: true
type: string
+ example: __LINK-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkLagLinksLagLink.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -29729,6 +38083,7 @@ paths:
description: Alphabetical concatenation of lag-interface names
required: true
type: string
+ example: __LINK-NAME__
/network/lag-links/lag-link/{link-name}:
get:
tags:
@@ -29743,7 +38098,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-link"
+ $ref: "#/getDefinitions/lag-link"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -29752,11 +38107,15 @@ paths:
description: Alphabetical concatenation of lag-interface names
required: true
type: string
+ example: __LINK-NAME__
put:
tags:
- Network
summary: create or update an existing lag-link
- description: create or update an existing lag-link
+ description: |
+ Create or update an existing lag-link.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkLagLinksLagLink
consumes:
- application/json
@@ -29773,12 +38132,52 @@ paths:
description: Alphabetical concatenation of lag-interface names
required: true
type: string
+ example: __LINK-NAME__
- name: body
in: body
- description: lag-link object that needs to be created or updated
+ description: lag-link object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkLagLinksLagLink.json)
required: true
schema:
$ref: "#/definitions/lag-link"
+ patch:
+ tags:
+ - Network
+ summary: update an existing lag-link
+ description: |
+ Update an existing lag-link
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkLagLinksLagLink
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: link-name
+ in: path
+ description: Alphabetical concatenation of lag-interface names
+ required: true
+ type: string
+ example: __LINK-NAME__
+ - name: body
+ in: body
+ description: lag-link object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/lag-link"
delete:
tags:
- Network
@@ -29800,6 +38199,7 @@ paths:
description: Alphabetical concatenation of lag-interface names
required: true
type: string
+ example: __LINK-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -29819,7 +38219,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-links"
+ $ref: "#/getDefinitions/lag-links"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/newvces/newvce/{vnf-id2}/relationship-list/relationship:
@@ -29843,9 +38243,10 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvce.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -29870,6 +38271,7 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -29891,19 +38293,22 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -29928,16 +38333,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -29959,24 +38367,28 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -30001,21 +38413,25 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -30030,7 +38446,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -30039,21 +38455,25 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -30125,7 +38545,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -30142,27 +38565,88 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -30184,21 +38668,25 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -30225,24 +38713,28 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -30267,21 +38759,25 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -30296,7 +38792,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -30305,21 +38801,25 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -30391,7 +38891,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -30408,27 +38911,88 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -30450,21 +39014,25 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -30484,7 +39052,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -30493,16 +39061,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: vnf-name
in: query
description: Name of VNF.
@@ -30558,7 +39129,10 @@ paths:
tags:
- Network
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -30575,22 +39149,76 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- Network
@@ -30612,16 +39240,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -30641,7 +39272,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -30650,11 +39281,13 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -30716,19 +39349,22 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -30753,16 +39389,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -30777,7 +39416,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -30786,16 +39425,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: vnf-name
in: query
description: Name of VNF.
@@ -30860,7 +39502,10 @@ paths:
tags:
- Network
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -30877,22 +39522,76 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- Network
@@ -30914,16 +39613,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -30943,7 +39645,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -30952,11 +39654,13 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -31018,14 +39722,16 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -31050,11 +39756,13 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -31076,19 +39784,22 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -31113,16 +39824,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -31137,7 +39851,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -31146,16 +39860,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -31216,7 +39933,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -31233,22 +39953,76 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -31270,16 +40044,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -31306,19 +40083,22 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -31343,16 +40123,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -31367,7 +40150,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -31376,16 +40159,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: vnf-name
in: query
description: Name of VNF.
@@ -31446,7 +40232,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -31463,22 +40252,76 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -31500,16 +40343,19 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -31529,7 +40375,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -31538,11 +40384,13 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vnf-name
in: query
description: Name of VNF.
@@ -31587,7 +40435,10 @@ paths:
tags:
- Network
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterface
consumes:
- application/json
@@ -31604,17 +40455,64 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- Network
@@ -31636,11 +40534,13 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -31660,7 +40560,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -31669,6 +40569,7 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: vnf-name
in: query
description: Name of VNF.
@@ -31708,7 +40609,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/newvce"
+ $ref: "#/getDefinitions/newvce"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -31717,6 +40618,7 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: vnf-name
in: query
description: Name of VNF.
@@ -31746,7 +40648,10 @@ paths:
tags:
- Network
summary: create or update an existing newvce
- description: create or update an existing newvce
+ description: |
+ Create or update an existing newvce.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkNewvcesNewvce
consumes:
- application/json
@@ -31763,12 +40668,52 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: body
in: body
- description: newvce object that needs to be created or updated
+ description: newvce object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkNewvcesNewvce.json)
required: true
schema:
$ref: "#/definitions/newvce"
+ patch:
+ tags:
+ - Network
+ summary: update an existing newvce
+ description: |
+ Update an existing newvce
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkNewvcesNewvce
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: vnf-id2
+ in: path
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ required: true
+ type: string
+ example: __VNF-ID2__
+ - name: body
+ in: body
+ description: newvce object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/newvce"
delete:
tags:
- Network
@@ -31790,6 +40735,7 @@ paths:
description: Unique id of VNF, can't use same attribute name right now until we promote this new object
required: true
type: string
+ example: __VNF-ID2__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -31809,7 +40755,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/newvces"
+ $ref: "#/getDefinitions/newvces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/pnfs/pnf/{pnf-name}/relationship-list/relationship:
@@ -31833,9 +40779,10 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -31860,6 +40807,7 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/relationship-list/relationship:
put:
tags:
@@ -31881,14 +40829,16 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -31913,11 +40863,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -31939,24 +40891,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -31981,21 +40937,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -32017,29 +40977,34 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -32064,26 +41029,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -32098,7 +41068,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -32107,26 +41077,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -32183,7 +41158,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -32200,32 +41178,100 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -32247,26 +41293,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -32293,29 +41344,34 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -32340,26 +41396,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -32374,7 +41435,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -32383,26 +41444,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -32459,7 +41525,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -32476,32 +41545,100 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -32523,26 +41660,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -32562,7 +41704,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -32571,21 +41713,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -32626,7 +41772,10 @@ paths:
tags:
- Network
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -32643,27 +41792,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- Network
@@ -32685,21 +41895,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -32719,7 +41933,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -32728,16 +41942,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -32784,24 +42001,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -32826,21 +42047,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -32855,7 +42080,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -32864,21 +42089,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -32928,7 +42157,10 @@ paths:
tags:
- Network
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -32945,27 +42177,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- Network
@@ -32987,21 +42280,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -33021,7 +42318,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -33030,16 +42327,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -33086,19 +42386,22 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -33123,16 +42426,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -33154,24 +42460,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -33196,21 +42506,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -33225,7 +42539,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -33234,21 +42548,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -33294,7 +42612,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -33311,27 +42632,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -33353,21 +42735,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -33394,24 +42780,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -33436,21 +42826,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -33465,7 +42859,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -33474,21 +42868,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -33534,7 +42932,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -33551,27 +42952,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -33593,21 +43055,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -33627,7 +43093,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -33636,16 +43102,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -33675,7 +43144,10 @@ paths:
tags:
- Network
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface
consumes:
- application/json
@@ -33692,22 +43164,76 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- Network
@@ -33729,16 +43255,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -33758,7 +43287,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -33767,11 +43296,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -33796,7 +43327,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/p-interface"
+ $ref: "#/getDefinitions/p-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -33805,11 +43336,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -33824,7 +43357,10 @@ paths:
tags:
- Network
summary: create or update an existing p-interface
- description: create or update an existing p-interface
+ description: |
+ Create or update an existing p-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterface
consumes:
- application/json
@@ -33841,17 +43377,64 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: p-interface object that needs to be created or updated
+ description: p-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfPInterfacesPInterface.json)
required: true
schema:
$ref: "#/definitions/p-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing p-interface
+ description: |
+ Update an existing p-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfPInterfacesPInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the physical interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: p-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/p-interface"
delete:
tags:
- Network
@@ -33873,11 +43456,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the physical interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -33897,7 +43482,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/p-interfaces"
+ $ref: "#/getDefinitions/p-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -33906,6 +43491,7 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -33932,14 +43518,16 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -33964,11 +43552,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
put:
tags:
@@ -33990,24 +43580,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -34032,21 +43626,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -34068,29 +43666,34 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -34115,26 +43718,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -34149,7 +43757,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -34158,26 +43766,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -34239,7 +43852,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -34256,32 +43872,100 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -34303,26 +43987,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -34349,29 +44038,34 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -34396,26 +44090,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -34430,7 +44129,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -34439,26 +44138,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -34520,7 +44224,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -34537,32 +44244,100 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -34584,26 +44359,31 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -34623,7 +44403,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlan"
+ $ref: "#/getDefinitions/vlan"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -34632,21 +44412,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -34692,7 +44476,10 @@ paths:
tags:
- Network
summary: create or update an existing vlan
- description: create or update an existing vlan
+ description: |
+ Create or update an existing vlan.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
consumes:
- application/json
@@ -34709,27 +44496,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: body
in: body
- description: vlan object that needs to be created or updated
+ description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
required: true
schema:
$ref: "#/definitions/vlan"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vlan
+ description: |
+ Update an existing vlan
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: vlan-interface
+ in: path
+ description: String that identifies the interface
+ required: true
+ type: string
+ example: __VLAN-INTERFACE__
+ - name: body
+ in: body
+ description: vlan object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vlan"
delete:
tags:
- Network
@@ -34751,21 +44599,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: vlan-interface
in: path
description: String that identifies the interface
required: true
type: string
+ example: __VLAN-INTERFACE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -34785,7 +44637,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vlans"
+ $ref: "#/getDefinitions/vlans"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -34794,16 +44646,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -34855,24 +44710,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -34897,21 +44756,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
get:
tags:
@@ -34926,7 +44789,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/getDefinitions/sriov-vf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -34935,21 +44798,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -35004,7 +44871,10 @@ paths:
tags:
- Network
summary: create or update an existing sriov-vf
- description: create or update an existing sriov-vf
+ description: |
+ Create or update an existing sriov-vf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
consumes:
- application/json
@@ -35021,27 +44891,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: body
in: body
- description: sriov-vf object that needs to be created or updated
+ description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
required: true
schema:
$ref: "#/definitions/sriov-vf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing sriov-vf
+ description: |
+ Update an existing sriov-vf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: pci-id
+ in: path
+ description: PCI ID used to identify the sriov-vf
+ required: true
+ type: string
+ example: __PCI-ID__
+ - name: body
+ in: body
+ description: sriov-vf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/sriov-vf"
delete:
tags:
- Network
@@ -35063,21 +44994,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: pci-id
in: path
description: PCI ID used to identify the sriov-vf
required: true
type: string
+ example: __PCI-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -35097,7 +45032,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/sriov-vfs"
+ $ref: "#/getDefinitions/sriov-vfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -35106,16 +45041,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -35167,19 +45105,22 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -35204,16 +45145,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
put:
tags:
@@ -35235,24 +45179,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -35277,21 +45225,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
get:
tags:
@@ -35306,7 +45258,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -35315,21 +45267,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -35380,7 +45336,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv4-address-list
- description: create or update an existing l3-interface-ipv4-address-list
+ description: |
+ Create or update an existing l3-interface-ipv4-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
consumes:
- application/json
@@ -35397,27 +45356,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv4-address-list object that needs to be created or updated
+ description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv4-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv4-address-list
+ description: |
+ Update an existing l3-interface-ipv4-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv4-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv4-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
delete:
tags:
- Network
@@ -35439,21 +45459,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv4-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV4-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -35480,24 +45504,28 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -35522,21 +45550,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
/network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
get:
tags:
@@ -35551,7 +45583,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -35560,21 +45592,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -35625,7 +45661,10 @@ paths:
tags:
- Network
summary: create or update an existing l3-interface-ipv6-address-list
- description: create or update an existing l3-interface-ipv6-address-list
+ description: |
+ Create or update an existing l3-interface-ipv6-address-list.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
consumes:
- application/json
@@ -35642,27 +45681,88 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: body
in: body
- description: l3-interface-ipv6-address-list object that needs to be created or updated
+ description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
required: true
schema:
$ref: "#/definitions/l3-interface-ipv6-address-list"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l3-interface-ipv6-address-list
+ description: |
+ Update an existing l3-interface-ipv6-address-list
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: l3-interface-ipv6-address
+ in: path
+ description: IP address
+ required: true
+ type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
+ - name: body
+ in: body
+ description: l3-interface-ipv6-address-list object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
delete:
tags:
- Network
@@ -35684,21 +45784,25 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: l3-interface-ipv6-address
in: path
description: IP address
required: true
type: string
+ example: __L3-INTERFACE-IPV6-ADDRESS__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -35718,7 +45822,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -35727,16 +45831,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -35771,7 +45878,10 @@ paths:
tags:
- Network
summary: create or update an existing l-interface
- description: create or update an existing l-interface
+ description: |
+ Create or update an existing l-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface
consumes:
- application/json
@@ -35788,22 +45898,76 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: l-interface object that needs to be created or updated
+ description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface.json)
required: true
schema:
$ref: "#/definitions/l-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing l-interface
+ description: |
+ Update an existing l-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: interface-name
+ in: path
+ description: Name given to the interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: l-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/l-interface"
delete:
tags:
- Network
@@ -35825,16 +45989,19 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: interface-name
in: path
description: Name given to the interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -35854,7 +46021,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/l-interfaces"
+ $ref: "#/getDefinitions/l-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -35863,11 +46030,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -35897,7 +46066,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interface"
+ $ref: "#/getDefinitions/lag-interface"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -35906,11 +46075,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -35930,7 +46101,10 @@ paths:
tags:
- Network
summary: create or update an existing lag-interface
- description: create or update an existing lag-interface
+ description: |
+ Create or update an existing lag-interface.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterface
consumes:
- application/json
@@ -35947,17 +46121,64 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: body
in: body
- description: lag-interface object that needs to be created or updated
+ description: lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnfLagInterfacesLagInterface.json)
required: true
schema:
$ref: "#/definitions/lag-interface"
+ patch:
+ tags:
+ - Network
+ summary: update an existing lag-interface
+ description: |
+ Update an existing lag-interface
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterface
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: interface-name
+ in: path
+ description: Name that identifies the link aggregate interface
+ required: true
+ type: string
+ example: __INTERFACE-NAME__
+ - name: body
+ in: body
+ description: lag-interface object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/lag-interface"
delete:
tags:
- Network
@@ -35979,11 +46200,13 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: interface-name
in: path
description: Name that identifies the link aggregate interface
required: true
type: string
+ example: __INTERFACE-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -36003,7 +46226,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/lag-interfaces"
+ $ref: "#/getDefinitions/lag-interfaces"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -36012,6 +46235,7 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -36031,7 +46255,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/pnf"
+ $ref: "#/getDefinitions/pnf"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -36040,6 +46264,7 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: inv-status
in: query
description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
@@ -36049,7 +46274,10 @@ paths:
tags:
- Network
summary: create or update an existing pnf
- description: create or update an existing pnf
+ description: |
+ Create or update an existing pnf.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPnfsPnf
consumes:
- application/json
@@ -36066,12 +46294,52 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: body
in: body
- description: pnf object that needs to be created or updated
+ description: pnf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPnfsPnf.json)
required: true
schema:
$ref: "#/definitions/pnf"
+ patch:
+ tags:
+ - Network
+ summary: update an existing pnf
+ description: |
+ Update an existing pnf
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPnfsPnf
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: pnf-name
+ in: path
+ description: unique name of Physical Network Function.
+ required: true
+ type: string
+ example: __PNF-NAME__
+ - name: body
+ in: body
+ description: pnf object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/pnf"
delete:
tags:
- Network
@@ -36093,6 +46361,7 @@ paths:
description: unique name of Physical Network Function.
required: true
type: string
+ example: __PNF-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -36112,7 +46381,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/pnfs"
+ $ref: "#/getDefinitions/pnfs"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/physical-links/physical-link/{link-name}/relationship-list/relationship:
@@ -36136,9 +46405,10 @@ paths:
description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPhysicalLinksPhysicalLink.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -36163,6 +46433,7 @@ paths:
description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
required: true
type: string
+ example: __LINK-NAME__
/network/physical-links/physical-link/{link-name}:
get:
tags:
@@ -36177,7 +46448,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/physical-link"
+ $ref: "#/getDefinitions/physical-link"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -36186,6 +46457,7 @@ paths:
description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: circuit-id
in: query
description: Circuit it
@@ -36195,7 +46467,10 @@ paths:
tags:
- Network
summary: create or update an existing physical-link
- description: create or update an existing physical-link
+ description: |
+ Create or update an existing physical-link.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkPhysicalLinksPhysicalLink
consumes:
- application/json
@@ -36212,12 +46487,52 @@ paths:
description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: body
in: body
- description: physical-link object that needs to be created or updated
+ description: physical-link object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkPhysicalLinksPhysicalLink.json)
required: true
schema:
$ref: "#/definitions/physical-link"
+ patch:
+ tags:
+ - Network
+ summary: update an existing physical-link
+ description: |
+ Update an existing physical-link
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkPhysicalLinksPhysicalLink
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: link-name
+ in: path
+ description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
+ required: true
+ type: string
+ example: __LINK-NAME__
+ - name: body
+ in: body
+ description: physical-link object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/physical-link"
delete:
tags:
- Network
@@ -36239,6 +46554,7 @@ paths:
description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
required: true
type: string
+ example: __LINK-NAME__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -36258,7 +46574,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/physical-links"
+ $ref: "#/getDefinitions/physical-links"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}/relationship-list/relationship:
@@ -36282,9 +46598,10 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkIpsecConfigurationsIpsecConfiguration.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -36309,6 +46626,7 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
/network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}/vig-servers/vig-server/{vig-address-type}/relationship-list/relationship:
put:
tags:
@@ -36330,14 +46648,16 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: vig-address-type
in: path
description: indicates whether the VIG is for AVPN or INTERNET
required: true
type: string
+ example: __VIG-ADDRESS-TYPE__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -36362,11 +46682,13 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: vig-address-type
in: path
description: indicates whether the VIG is for AVPN or INTERNET
required: true
type: string
+ example: __VIG-ADDRESS-TYPE__
/network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}/vig-servers/vig-server/{vig-address-type}:
get:
tags:
@@ -36381,7 +46703,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vig-server"
+ $ref: "#/getDefinitions/vig-server"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -36390,16 +46712,21 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: vig-address-type
in: path
description: indicates whether the VIG is for AVPN or INTERNET
required: true
type: string
+ example: __VIG-ADDRESS-TYPE__
put:
tags:
- Network
summary: create or update an existing vig-server
- description: create or update an existing vig-server
+ description: |
+ Create or update an existing vig-server.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer
consumes:
- application/json
@@ -36416,17 +46743,64 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: vig-address-type
in: path
description: indicates whether the VIG is for AVPN or INTERNET
required: true
type: string
+ example: __VIG-ADDRESS-TYPE__
- name: body
in: body
- description: vig-server object that needs to be created or updated
+ description: vig-server object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer.json)
required: true
schema:
$ref: "#/definitions/vig-server"
+ patch:
+ tags:
+ - Network
+ summary: update an existing vig-server
+ description: |
+ Update an existing vig-server
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: ipsec-configuration-id
+ in: path
+ description: UUID of this configuration
+ required: true
+ type: string
+ example: __IPSEC-CONFIGURATION-ID__
+ - name: vig-address-type
+ in: path
+ description: indicates whether the VIG is for AVPN or INTERNET
+ required: true
+ type: string
+ example: __VIG-ADDRESS-TYPE__
+ - name: body
+ in: body
+ description: vig-server object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/vig-server"
delete:
tags:
- Network
@@ -36448,11 +46822,13 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: vig-address-type
in: path
description: indicates whether the VIG is for AVPN or INTERNET
required: true
type: string
+ example: __VIG-ADDRESS-TYPE__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -36472,7 +46848,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/vig-servers"
+ $ref: "#/getDefinitions/vig-servers"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -36481,6 +46857,7 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
/network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}:
get:
tags:
@@ -36495,7 +46872,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/ipsec-configuration"
+ $ref: "#/getDefinitions/ipsec-configuration"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -36504,11 +46881,15 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
put:
tags:
- Network
summary: create or update an existing ipsec-configuration
- description: create or update an existing ipsec-configuration
+ description: |
+ Create or update an existing ipsec-configuration.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkIpsecConfigurationsIpsecConfiguration
consumes:
- application/json
@@ -36525,12 +46906,52 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: body
in: body
- description: ipsec-configuration object that needs to be created or updated
+ description: ipsec-configuration object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkIpsecConfigurationsIpsecConfiguration.json)
required: true
schema:
$ref: "#/definitions/ipsec-configuration"
+ patch:
+ tags:
+ - Network
+ summary: update an existing ipsec-configuration
+ description: |
+ Update an existing ipsec-configuration
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkIpsecConfigurationsIpsecConfiguration
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: ipsec-configuration-id
+ in: path
+ description: UUID of this configuration
+ required: true
+ type: string
+ example: __IPSEC-CONFIGURATION-ID__
+ - name: body
+ in: body
+ description: ipsec-configuration object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/ipsec-configuration"
delete:
tags:
- Network
@@ -36552,6 +46973,7 @@ paths:
description: UUID of this configuration
required: true
type: string
+ example: __IPSEC-CONFIGURATION-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -36571,7 +46993,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/ipsec-configurations"
+ $ref: "#/getDefinitions/ipsec-configurations"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/route-table-references/route-table-reference/{route-table-reference-id}/relationship-list/relationship:
@@ -36595,9 +47017,10 @@ paths:
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __ROUTE-TABLE-REFERENCE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkRouteTableReferencesRouteTableReference.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -36622,6 +47045,7 @@ paths:
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __ROUTE-TABLE-REFERENCE-ID__
/network/route-table-references/route-table-reference/{route-table-reference-id}:
get:
tags:
@@ -36636,7 +47060,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/route-table-reference"
+ $ref: "#/getDefinitions/route-table-reference"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -36645,6 +47069,7 @@ paths:
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __ROUTE-TABLE-REFERENCE-ID__
- name: route-table-reference-fqdn
in: query
description: FQDN entry in the route table.
@@ -36654,7 +47079,10 @@ paths:
tags:
- Network
summary: create or update an existing route-table-reference
- description: create or update an existing route-table-reference
+ description: |
+ Create or update an existing route-table-reference.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkRouteTableReferencesRouteTableReference
consumes:
- application/json
@@ -36671,12 +47099,52 @@ paths:
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __ROUTE-TABLE-REFERENCE-ID__
- name: body
in: body
- description: route-table-reference object that needs to be created or updated
+ description: route-table-reference object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkRouteTableReferencesRouteTableReference.json)
required: true
schema:
$ref: "#/definitions/route-table-reference"
+ patch:
+ tags:
+ - Network
+ summary: update an existing route-table-reference
+ description: |
+ Update an existing route-table-reference
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkRouteTableReferencesRouteTableReference
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: route-table-reference-id
+ in: path
+ description: Route Table Reference id, UUID assigned to this instance.
+ required: true
+ type: string
+ example: __ROUTE-TABLE-REFERENCE-ID__
+ - name: body
+ in: body
+ description: route-table-reference object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/route-table-reference"
delete:
tags:
- Network
@@ -36698,6 +47166,7 @@ paths:
description: Route Table Reference id, UUID assigned to this instance.
required: true
type: string
+ example: __ROUTE-TABLE-REFERENCE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -36717,7 +47186,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/route-table-references"
+ $ref: "#/getDefinitions/route-table-references"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/instance-groups/instance-group/{id}/relationship-list/relationship:
@@ -36741,9 +47210,10 @@ paths:
description: Instance Group ID, UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkInstanceGroupsInstanceGroup.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -36768,6 +47238,7 @@ paths:
description: Instance Group ID, UUID assigned to this instance.
required: true
type: string
+ example: __ID__
/network/instance-groups/instance-group/{id}:
get:
tags:
@@ -36782,7 +47253,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/instance-group"
+ $ref: "#/getDefinitions/instance-group"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -36791,6 +47262,7 @@ paths:
description: Instance Group ID, UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: description
in: query
description: Descriptive text to help identify the usage of this instance-group
@@ -36810,7 +47282,10 @@ paths:
tags:
- Network
summary: create or update an existing instance-group
- description: create or update an existing instance-group
+ description: |
+ Create or update an existing instance-group.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkInstanceGroupsInstanceGroup
consumes:
- application/json
@@ -36827,12 +47302,52 @@ paths:
description: Instance Group ID, UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: body
in: body
- description: instance-group object that needs to be created or updated
+ description: instance-group object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkInstanceGroupsInstanceGroup.json)
required: true
schema:
$ref: "#/definitions/instance-group"
+ patch:
+ tags:
+ - Network
+ summary: update an existing instance-group
+ description: |
+ Update an existing instance-group
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkInstanceGroupsInstanceGroup
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: id
+ in: path
+ description: Instance Group ID, UUID assigned to this instance.
+ required: true
+ type: string
+ example: __ID__
+ - name: body
+ in: body
+ description: instance-group object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/instance-group"
delete:
tags:
- Network
@@ -36854,6 +47369,7 @@ paths:
description: Instance Group ID, UUID assigned to this instance.
required: true
type: string
+ example: __ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -36873,7 +47389,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/instance-groups"
+ $ref: "#/getDefinitions/instance-groups"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
/network/zones/zone/{zone-id}/relationship-list/relationship:
@@ -36897,9 +47413,10 @@ paths:
description: Code assigned by AIC to the zone
required: true
type: string
+ example: __ZONE-ID__
- name: body
in: body
- description: relationship object that needs to be created or updated
+ description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkZonesZone.json)
required: true
schema:
$ref: "#/definitions/relationship"
@@ -36924,6 +47441,7 @@ paths:
description: Code assigned by AIC to the zone
required: true
type: string
+ example: __ZONE-ID__
/network/zones/zone/{zone-id}:
get:
tags:
@@ -36938,7 +47456,7 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/zone"
+ $ref: "#/getDefinitions/zone"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
parameters:
@@ -36947,6 +47465,7 @@ paths:
description: Code assigned by AIC to the zone
required: true
type: string
+ example: __ZONE-ID__
- name: design-type
in: query
description: Design of zone [Medium/Large?]
@@ -36961,7 +47480,10 @@ paths:
tags:
- Network
summary: create or update an existing zone
- description: create or update an existing zone
+ description: |
+ Create or update an existing zone.
+ #
+ Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement. An example can be found in the [PATCH section] below
operationId: createOrUpdateNetworkZonesZone
consumes:
- application/json
@@ -36978,12 +47500,52 @@ paths:
description: Code assigned by AIC to the zone
required: true
type: string
+ example: __ZONE-ID__
- name: body
in: body
- description: zone object that needs to be created or updated
+ description: zone object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v9/NetworkZonesZone.json)
required: true
schema:
$ref: "#/definitions/zone"
+ patch:
+ tags:
+ - Network
+ summary: update an existing zone
+ description: |
+ Update an existing zone
+ #
+ Note: Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+ The PUT operation will entirely replace an existing object.
+ The PATCH operation sends a "description of changes" for an existing object. The entire set of changes must be applied. An error result means no change occurs.
+ #
+ Other differences between PUT and PATCH are:
+ #
+ - For PATCH, you can send any of the values shown in sample REQUEST body. There are no required values.
+ - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+ - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+ operationId: UpdateNetworkZonesZone
+ consumes:
+ - application/json
+ - application/xml
+ produces:
+ - application/json
+ - application/xml
+ responses:
+ "default":
+ description: Response codes found in [response codes](https://wiki.onap.org/).
+ parameters:
+ - name: zone-id
+ in: path
+ description: Code assigned by AIC to the zone
+ required: true
+ type: string
+ example: __ZONE-ID__
+ - name: body
+ in: body
+ description: zone object that needs to be created or updated.
+ required: true
+ schema:
+ $ref: "#/patchDefinitions/zone"
delete:
tags:
- Network
@@ -37005,6 +47567,7 @@ paths:
description: Code assigned by AIC to the zone
required: true
type: string
+ example: __ZONE-ID__
- name: resource-version
in: query
description: resource-version for concurrency
@@ -37024,24 +47587,30 @@ paths:
"200":
description: successful operation
schema:
- $ref: "#/definitions/zones"
+ $ref: "#/getDefinitions/zones"
"default":
description: Response codes found in [response codes](https://wiki.onap.org/).
definitions:
- search:
+ aai-internal:
properties:
- edge-tag-query-result:
- type: object
- $ref: "#/definitions/edge-tag-query-result"
- edge-tag-query-request:
- type: object
- $ref: "#/definitions/edge-tag-query-request"
- search-results:
- type: object
- $ref: "#/definitions/search-results"
- sdn-zone-response:
- type: object
- $ref: "#/definitions/sdn-zone-response"
+ property-name:
+ type: string
+ property-value:
+ type: string
+ action:
+ properties:
+ action-type:
+ type: string
+ action-data:
+ type: array
+ items:
+ $ref: "#/definitions/action-data"
+ action-data:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
actions:
description: |
APIs that are more action related than REST (e.g., notify, update).
@@ -37052,103 +47621,291 @@ definitions:
notify:
type: object
$ref: "#/definitions/notify"
- relationship-data:
+ allotted-resource:
+ description: |
+ Represents a slice or partial piece of a resource that gets separately allotted
+ ###### Related Nodes
+ - TO generic-vnf( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY)
+ - TO instance-group( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO l3-network( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY)
+ - TO vlan( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY)
+ - TO service-instance( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM tunnel-xconnect( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY)
+ - ALLOTTED-RESOURCE is DELETED when these are DELETED TUNNEL-XCONNECT
required:
- - relationship-key
- - relationship-value
+ - id
properties:
- relationship-key:
+ id:
type: string
- description: A keyword provided by A&AI to indicate an attribute.
- relationship-value:
+ description: Allotted Resource id UUID assigned to this instance.
+ description:
type: string
- description: Value of the attribute.
- related-to-property:
- properties:
- property-key:
+ description: The descriptive information assigned to this allotted resource instance
+ selflink:
type: string
- description: Key part of a key/value pair
- property-value:
+ description: Link back to more information in the controller
+ persona-model-id:
type: string
- description: Value part of a key/value pair
- relationship:
- properties:
- related-to:
+ description: the ASDC model id for this resource or service model.
+ persona-model-version:
type: string
- description: A keyword provided by A&AI to indicate type of node.
- related-link:
+ description: the ASDC model version for this resource or service model.
+ model-version-id:
type: string
- description: URL to the object in A&AI.
- relationship-data:
+ description: the ASDC model version for this resource or service model.
+ persona-model-customization-id:
+ type: string
+ description: captures the id of all the configuration used to customize the resource for the service.
+ resource-version:
+ type: string
+ description: Concurrency value
+ tunnel-xconnects:
type: array
- items:
- $ref: "#/definitions/relationship-data"
- related-to-property:
+ items:
+ $ref: "#/definitions/tunnel-xconnect"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ allotted-resources:
+ description: |
+ This object is used to store slices of services being offered
+ properties:
+ allotted-resource:
type: array
items:
- $ref: "#/definitions/related-to-property"
- relationship-list:
+ $ref: "#/definitions/allotted-resource"
+ availability-zone:
+ description: |
+ Availability zone, a collection of compute hosts/pservers
+ ###### Related Nodes
+ - TO complex( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO service-capability( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - TO cloud-region( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM ctag-pool( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM dvs-switch( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - FROM pserver( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)
+ - FROM vce( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - AVAILABILITY-ZONE cannot be deleted if linked to CTAG-POOL,DVS-SWITCH,GENERIC-VNF,PSERVER,VCE
+ required:
+ - availability-zone-name
+ - hypervisor-type
properties:
- relationship:
+ availability-zone-name:
+ type: string
+ description: Name of the availability zone. Unique across a cloud region
+ hypervisor-type:
+ type: string
+ description: Type of hypervisor. Source of truth should define valid values.
+ operational-state:
+ type: string
+ description: State that indicates whether the availability zone should be used, etc. Source of truth should define valid values.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ availability-zones:
+ description: |
+ Collection of availability zones
+ properties:
+ availability-zone:
type: array
items:
+ $ref: "#/definitions/availability-zone"
+ az-and-dvs-switches:
+ properties:
+ dvs-switches:
+ type: object
+ $ref: "#/definitions/dvs-switches"
+ availability-zone:
+ type: object
+ $ref: "#/definitions/availability-zone"
+ business:
+ description: |
+ Namespace for business related constructs
+ properties:
+ connectors:
+ type: array
+ items:
+ $ref: "#/definitions/connector"
+ customers:
+ type: array
+ items:
+ $ref: "#/definitions/customer"
+ class-of-service:
+ description: |
+ ###### Related Nodes
+ - TO site-pair( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)
+ required:
+ - cos
+ properties:
+ cos:
+ type: string
+ description: unique identifier of probe
+ probe-id:
+ type: string
+ description: identifier of probe
+ probe-type:
+ type: string
+ description: type of probe
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
$ref: "#/definitions/relationship"
- ctag-pool:
+ classes-of-service:
description: |
- A collection of C tags (vlan tags) grouped for a specific purpose.
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ class-of-service of probe
+ properties:
+ class-of-service:
+ type: array
+ items:
+ $ref: "#/definitions/class-of-service"
+ cloud-infrastructure:
+ description: |
+ Namespace for cloud infrastructure.
+ properties:
+ complexes:
+ type: array
+ items:
+ $ref: "#/definitions/complex"
+ cloud-regions:
+ type: array
+ items:
+ $ref: "#/definitions/cloud-region"
+ network-profiles:
+ type: array
+ items:
+ $ref: "#/definitions/network-profile"
+ pservers:
+ type: array
+ items:
+ $ref: "#/definitions/pserver"
+ virtual-data-centers:
+ type: array
+ items:
+ $ref: "#/definitions/virtual-data-center"
+ cloud-region:
+ description: |
+ cloud-region designates an installation of a cloud cluster or region or instantiation.
###### Related Nodes
- - TO availability-zone (Many2Many)
- - FROM complex (is composed of ctag-pool)
- - FROM vpls-pe
+ - TO complex( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO l3-network( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO zone( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM dvs-switch( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM flavor( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM group-assignment( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM image( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM snapshot( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM volume-group( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn cloud-region, MANY2MANY)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)
+ - CLOUD-REGION cannot be deleted if linked to DVS-SWITCH,FLAVOR,GROUP-ASSIGNMENT,IMAGE,OAM-NETWORK,SNAPSHOT,TENANT,VOLUME-GROUP
+ - CLOUD-REGION is DELETED when these are DELETED AVAILABILITY-ZONE
required:
- - target-pe
- - availability-zone-name
- - ctag-pool-purpose
+ - cloud-owner
+ - cloud-region-id
properties:
- target-pe:
+ cloud-owner:
type: string
- description: The Target provider edge router
- availability-zone-name:
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ cloud-region-id:
type: string
- description: Name of the availability zone
- ctag-pool-purpose:
+ description: Identifier used by the vendor for the region. Second part of composite key
+ cloud-type:
type: string
- description: Describes what the intended purpose of this pool is.
- ctag-values:
+ description: Type of the cloud (e.g., openstack)
+ owner-defined-type:
type: string
- description: Comma separated list of ctags
+ description: Cloud-owner defined type indicator (e.g., dcp, lcp)
+ cloud-region-version:
+ type: string
+ description: Software version employed at the site. NOTE - THIS FIELD IS NOT KEPT UP TO DATE.
+ identity-url:
+ type: string
+ description: URL of the keystone identity service
+ cloud-zone:
+ type: string
+ description: Zone where the cloud is homed. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
+ complex-name:
+ type: string
+ description: complex name for cloud-region instance. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ volume-groups:
+ type: array
+ items:
+ $ref: "#/definitions/volume-group"
+ tenants:
+ type: array
+ items:
+ $ref: "#/definitions/tenant"
+ flavors:
+ type: array
+ items:
+ $ref: "#/definitions/flavor"
+ group-assignments:
+ type: array
+ items:
+ $ref: "#/definitions/group-assignment"
+ snapshots:
+ type: array
+ items:
+ $ref: "#/definitions/snapshot"
+ images:
+ type: array
+ items:
+ $ref: "#/definitions/image"
+ dvs-switches:
+ type: array
+ items:
+ $ref: "#/definitions/dvs-switch"
+ oam-networks:
+ type: array
+ items:
+ $ref: "#/definitions/oam-network"
+ availability-zones:
+ type: array
+ items:
+ $ref: "#/definitions/availability-zone"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- ctag-pools:
+ cloud-regions:
properties:
- ctag-pool:
+ cloud-region:
type: array
items:
- $ref: "#/definitions/ctag-pool"
+ $ref: "#/definitions/cloud-region"
complex:
description: |
Collection of physical locations that can house cloud-regions.
- ###### Default Delete Scope
- ERROR_4_IN_EDGES_OR_CASCADE
- ###### Related Nodes
- - TO ctag-pool (comprises complex, Many2Many)
- - TO l3-network (Many2Many)
- - FROM availability-zone
- - FROM cloud-region
- - FROM oam-network
- - FROM pserver
- - FROM pnf
- - FROM vce
- - FROM vpls-pe
- - FROM volume-group
- - FROM zone
+ ###### Related Nodes
+ - TO l3-network( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM ctag-pool( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)
+ - FROM pnf( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM vce( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)
+ - FROM volume-group( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM vpls-pe( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM zone( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - COMPLEX cannot be deleted if linked to AVAILABILITY-ZONE,CLOUD-REGION,OAM-NETWORK,PNF,PSERVER,VCE,VOLUME-GROUP,VPLS-PE,ZONE
+ - COMPLEX is DELETED when these are DELETED CTAG-POOL
required:
- physical-location-id
- physical-location-type
@@ -37214,43 +47971,59 @@ definitions:
type: array
items:
$ref: "#/definitions/complex"
- volume-group:
+ configuration:
description: |
- Persistent block-level storage.
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Port Mirror Configuration.
###### Related Nodes
- - TO complex (Many2Many)
- - TO tenant (Many2Many)
- - FROM cloud-region (is composed of volume-group)
- - FROM vf-module
- - FROM generic-vnf
+ - TO allotted-resource( configuration org.onap.relationships.inventory.Uses allotted-resource, ONE2ONE)
+ - TO logical-link( configuration org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo configuration, MANY2ONE)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses configuration, ONE2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses configuration, ONE2MANY)
+ - CONFIGURATION is DELETED when these are DELETED METADATUM
+ - CONFIGURATION deletion means associated objects of these types are also DELETED:ALLOTTED-RESOURCE,LOGICAL-LINK
required:
- - volume-group-id
- - volume-group-name
- - vnf-type
+ - configuration-id
+ - configuration-type
+ - configuration-sub-type
+ - orchestration-status
+ - operational-status
+ - configuration-selflink
+ - model-customization-id
properties:
- volume-group-id:
+ configuration-id:
type: string
- description: Unique ID of volume-group.
- volume-group-name:
+ description: UUID assigned to configuration.
+ management-option:
type: string
- description: Name of the volume group.
- heat-stack-id:
+ description: Indicates the entity that will manage this feature. Could be an organization or the name of the application as well.
+ configuration-name:
type: string
- description: Heat stack id corresponding to this volume-group
- vnf-type:
+ description: Name of the configuration.
+ configuration-type:
type: string
- description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ description: port-mirroring-configuration.
+ configuration-sub-type:
+ type: string
+ description: vprobe, pprobe.
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
orchestration-status:
type: string
- description: Orchestration status of this volume-group
- persona-model-customization-id:
+ description: Orchestration status of the configuration.
+ operational-status:
type: string
- description: captures the id of all the configuration used to customize the resource for the service.
- vf-module-persona-model-customization-id:
+ description: Indicator for whether the resource is considered operational.
+ configuration-selflink:
type: string
- description: helps relate the volume group to the vf-module whose components will require the volume group
+ description: URL to endpoint where AAI can get more details from SDN-GC.
+ model-customization-id:
+ type: string
+ description: id of the configuration used to customize the resource
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
@@ -37258,456 +48031,634 @@ definitions:
type: array
items:
$ref: "#/definitions/relationship"
- volume-groups:
+ metadata:
+ type: array
+ items:
+ $ref: "#/definitions/metadatum"
+ configurations:
description: |
- Collection of persistent block-level storage.
+ Collection of configurations
properties:
- volume-group:
+ configuration:
type: array
items:
- $ref: "#/definitions/volume-group"
- volume:
+ $ref: "#/definitions/configuration"
+ connector:
description: |
- Ephemeral Block storage volume.
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Collection of resource instances used to connect a variety of disparate inventory widgets
###### Related Nodes
- - FROM vserver (is composed of volume)
+ - TO virtual-data-center( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)
+ - CONNECTOR is DELETED when these are DELETED METADATUM
required:
- - volume-id
- - volume-selflink
+ - resource-instance-id
properties:
- volume-id:
- type: string
- description: Unique ID of block storage volume relative to the vserver.
- volume-selflink:
+ resource-instance-id:
type: string
- description: URL to endpoint where AAI can get more details
+ description: Unique id of resource instance.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ persona-model-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- volumes:
+ metadata:
+ type: array
+ items:
+ $ref: "#/definitions/metadatum"
+ connectors:
description: |
- Collection of ephemeral Block storage volumes.
+ Collection of resource instances used to connect a variety of disparate inventory widgets
properties:
- volume:
+ connector:
type: array
items:
- $ref: "#/definitions/volume"
- l3-interface-ipv4-address-list:
+ $ref: "#/definitions/connector"
+ constrained-element-set:
description: |
- IPv4 Address Range
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ This is how we would capture constraints defining allowed sets of elements.
###### Related Nodes
- - TO l3-network (Many2Many)
- - TO subnet (Many2Many)
- - FROM l-interface (is composed of l3-interface-ipv4-address-list)
- - FROM vlan (is composed of l3-interface-ipv4-address-list)
+ - TO model-constraint( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)
+ - TO model-element( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM element-choice-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)
+ - CONSTRAINED-ELEMENT-SET is DELETED when these are DELETED ELEMENT-CHOICE-SET
required:
- - l3-interface-ipv4-address
+ - constrained-element-set-uuid
+ - constraint-type
+ - check-type
properties:
- l3-interface-ipv4-address:
+ constrained-element-set-uuid:
type: string
- description: IP address
- l3-interface-ipv4-prefix-length:
- type: integer
- format: int64
- description: Prefix length, 32 for single address
- vlan-id-inner:
- type: integer
- format: int64
- description: Inner VLAN tag
- vlan-id-outer:
- type: integer
- format: int64
- description: Outer VLAN tag
- is-floating:
- type: boolean
- description: Indicator of fixed or floating address
- resource-version:
+ constraint-type:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- neutron-network-id:
+ check-type:
type: string
- description: Neutron network id of the interface that address belongs to
- neutron-subnet-id:
+ resource-version:
type: string
- description: Neutron id of subnet that address belongs to
+ element-choice-sets:
+ type: array
+ items:
+ $ref: "#/definitions/element-choice-set"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- l3-interface-ipv6-address-list:
+ constrained-element-sets:
+ properties:
+ constrained-element-set:
+ type: array
+ items:
+ $ref: "#/definitions/constrained-element-set"
+ ctag-assignment:
description: |
- IPv6 Address Range
- ###### Default Delete Scope
- THIS_NODE_ONLY
###### Related Nodes
- - TO l3-network (Many2Many)
- - TO subnet (Many2Many)
- - FROM l-interface (is composed of l3-interface-ipv6-address-list)
- - FROM vlan (is composed of l3-interface-ipv6-address-list)
+ - TO l3-network( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses ctag-assignment, ONE2MANY)
required:
- - l3-interface-ipv6-address
+ - vlan-id-inner
properties:
- l3-interface-ipv6-address:
- type: string
- description: IP address
- l3-interface-ipv6-prefix-length:
- type: integer
- format: int64
- description: Prefix length, 128 for single address
vlan-id-inner:
type: integer
format: int64
- description: Inner VLAN tag
- vlan-id-outer:
- type: integer
- format: int64
- description: Outer VLAN tag
- is-floating:
- type: boolean
- description: Indicator of fixed or floating address
+ description: id.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- neutron-network-id:
- type: string
- description: Neutron network id of the interface that address belongs to
- neutron-subnet-id:
- type: string
- description: Neutron id of subnet that address belongs to
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- vlan:
+ ctag-assignments:
+ properties:
+ ctag-assignment:
+ type: array
+ items:
+ $ref: "#/definitions/ctag-assignment"
+ ctag-pool:
description: |
- Definition of vlan
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
+ A collection of C tags (vlan tags) grouped for a specific purpose.
###### Related Nodes
- - TO l3-interface-ipv4-address-list (comprises vlan, Many2Many)
- - TO l3-interface-ipv6-address-list (comprises vlan, Many2Many)
- - TO multicast-configuration (Many2Many)
- - TO logical-link (Many2Many)
- - FROM l-interface (is composed of vlan)
- - FROM service-instance
- - FROM allotted-resource
+ - TO complex( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)
+ - TO availability-zone( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM vpls-pe( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)
required:
- - vlan-interface
+ - target-pe
+ - availability-zone-name
+ - ctag-pool-purpose
properties:
- vlan-interface:
+ target-pe:
type: string
- description: String that identifies the interface
- vlan-id-inner:
- type: integer
- format: int64
- description: Inner VLAN tag
- vlan-id-outer:
- type: integer
- format: int64
- description: Outer VLAN tag
- resource-version:
+ description: The Target provider edge router
+ availability-zone-name:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- speed-value:
+ description: Name of the availability zone
+ ctag-pool-purpose:
type: string
- description: Captures the numeric part of the speed
- speed-units:
+ description: Describes what the intended purpose of this pool is.
+ ctag-values:
type: string
- description: Captures the units corresponding to the speed
- vlan-description:
+ description: Comma separated list of ctags
+ resource-version:
type: string
- description: Used to describe (the service associated with) the vlan
- backdoor-connection:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ ctag-pools:
+ properties:
+ ctag-pool:
+ type: array
+ items:
+ $ref: "#/definitions/ctag-pool"
+ customer:
+ description: |
+ customer identifiers to provide linkage back to BSS information.
+ ###### Related Nodes
+ - FROM service-subscription( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)
+ - CUSTOMER is DELETED when these are DELETED SERVICE-SUBSCRIPTION
+ required:
+ - global-customer-id
+ - subscriber-name
+ - subscriber-type
+ properties:
+ global-customer-id:
type: string
- description: Whether customer is going to use this VLAN for backdoor connection to another customer premise device.
- vpn-id:
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ subscriber-name:
type: string
- description: This indicates the customers VPN ID associated with this vlan
- orchestration-status:
+ description: Subscriber name, an alternate way to retrieve a customer.
+ subscriber-type:
type: string
- description: Status of a vnf's vlan interface, on which the customer circuit resides, mastered by SDN-C.
+ description: Subscriber type, a way to provide VID with only the INFRA customers.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ service-subscriptions:
+ type: array
+ items:
+ $ref: "#/definitions/service-subscription"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- l3-interface-ipv4-address-list:
+ customers:
+ description: |
+ Collection of customer identifiers to provide linkage back to BSS information.
+ properties:
+ customer:
type: array
items:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
- l3-interface-ipv6-address-list:
+ $ref: "#/definitions/customer"
+ cvlan-tag-entry:
+ required:
+ - cvlan-tag
+ properties:
+ cvlan-tag:
+ type: integer
+ format: int64
+ description: See mis-na-virtualization-platform.yang
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
- items:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
- vlans:
+ items:
+ $ref: "#/definitions/relationship"
+ cvlan-tags:
properties:
- vlan:
+ cvlan-tag-entry:
type: array
items:
- $ref: "#/definitions/vlan"
- sriov-vf:
+ $ref: "#/definitions/cvlan-tag-entry"
+ dvs-switch:
description: |
- SR-IOV Virtual Function (not to be confused with virtual network function)
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Digital virtual switch metadata, used by SDN-C to configure VCEs. A&AI needs to receive this data from the PO deployment team and administer it using the provisioningTool.sh into A&AI.
###### Related Nodes
- - FROM l-interface (is composed of sriov-vf)
+ - TO cloud-region( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO availability-zone( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
required:
- - pci-id
+ - switch-name
+ - vcenter-url
properties:
- pci-id:
- type: string
- description: PCI ID used to identify the sriov-vf
- vf-vlan-filter:
- type: string
- description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM.
- vf-mac-filter:
- type: string
- description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM.
- vf-vlan-strip:
- type: boolean
- description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM.
- vf-vlan-anti-spoof-check:
- type: boolean
- description: This option ensures anti VLAN spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
- vf-mac-anti-spoof-check:
- type: boolean
- description: This option ensures anti MAC spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
- vf-mirrors:
+ switch-name:
type: string
- description: This option defines the set of Mirror objects which essentially mirrors the traffic from source to set of collector VNF Ports.
- vf-broadcast-allow:
- type: boolean
- description: This option, if set to true, sets the VF in promiscuous mode and allows all broadcast traffic to reach the VM
- vf-unknown-multicast-allow:
- type: boolean
- description: This option, if set to true, sets the VF in promiscuous mode and allows unknown multicast traffic to reach the VM
- vf-unknown-unicast-allow:
- type: boolean
- description: This option, if set to true, sets the VF in promiscuous mode and allows unknown unicast traffic to reach the VM
- vf-insert-stag:
- type: boolean
- description: This option, if set to true, instructs to insert outer tag after traffic comes out of VM.
- vf-link-status:
+ description: DVS switch name
+ vcenter-url:
type: string
- description: This option is used to set the link status. Valid values as of 1607 are on, off, and auto.
+ description: URL used to reach the vcenter
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- neutron-network-id:
- type: string
- description: Neutron network id of the interface
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- sriov-vfs:
+ dvs-switches:
description: |
- Collection of SR-IOV Virtual Functions.
+ Collection of digital virtual switch metadata used for vmWare VCEs and GenericVnfs.
properties:
- sriov-vf:
+ dvs-switch:
type: array
items:
- $ref: "#/definitions/sriov-vf"
- l-interface:
+ $ref: "#/definitions/dvs-switch"
+ edge-prop-names:
description: |
- Logical interfaces, e.g., a vnic.
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
- ###### Related Nodes
- - TO l3-interface-ipv4-address-list (comprises l-interface, Many2Many)
- - TO l3-interface-ipv6-address-list (comprises l-interface, Many2Many)
- - TO logical-link (Many2Many)
- - TO vlan (comprises l-interface, Many2Many)
- - TO sriov-vf (comprises l-interface, One2One)
- - FROM generic-vnf (is composed of l-interface)
- - FROM lag-interface (is composed of l-interface)
- - FROM newvce (is composed of l-interface)
- - FROM p-interface (is composed of l-interface)
- - FROM vserver (is composed of l-interface)
- required:
- - interface-name
+ Internal map to define the properties of an edge and interpret the map EdgeRules
properties:
- interface-name:
+ edgeLabel:
type: string
- description: Name given to the interface
- interface-role:
+ direction:
type: string
- description: E.g., CUSTOMER, UPLINK, etc.
- v6-wan-link-ip:
+ multiplicityRule:
type: string
- description: Questionably placed - v6 ip addr of this interface (is in vr-lan-interface from Mary B.
- selflink:
+ isParent:
+ type: boolean
+ usesResource:
+ type: boolean
+ hasDelTarget:
+ type: boolean
+ SVC-INFRA:
+ type: boolean
+ SVC-INFRA-REV:
+ type: boolean
+ edge-tag-query-request:
+ properties:
+ edge-tag:
type: string
- description: URL to endpoint where AAI can get more details
- interface-id:
+ result-detail:
type: string
- description: ID of interface
- macaddr:
+ start-node-type:
type: string
- description: MAC address for the interface
- network-name:
+ start-node-filter:
+ type: array
+ items:
+ $ref: "#/definitions/start-node-filter"
+ include-node-filter:
+ type: array
+ items:
+ $ref: "#/definitions/include-node-filter"
+ secondary-filter:
+ type: array
+ items:
+ $ref: "#/definitions/secondary-filter"
+ edge-tag-query-result:
+ properties:
+ tagged-inventory-item-list:
+ type: array
+ items:
+ $ref: "#/definitions/tagged-inventory-item-list"
+ element-choice-set:
+ description: |
+ This is how we would capture constraints defining allowed sets of elements.
+ ###### Related Nodes
+ - TO constrained-element-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)
+ - ELEMENT-CHOICE-SET is DELETED when these are DELETED MODEL-ELEMENT
+ required:
+ - element-choice-set-uuid
+ - element-choice-set-name
+ properties:
+ element-choice-set-uuid:
type: string
- description: Name of the network
- management-option:
+ element-choice-set-name:
type: string
- description: Whether A&AI should be managing this interface of not. Could have value like CUSTOMER
- interface-description:
+ cardinality:
type: string
- description: Human friendly text regarding this interface.
resource-version:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- vlans:
- type: array
- items:
- $ref: "#/definitions/vlan"
- sriov-vfs:
+ model-elements:
type: array
items:
- $ref: "#/definitions/sriov-vf"
+ $ref: "#/definitions/model-element"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- l3-interface-ipv4-address-list:
+ element-choice-sets:
+ properties:
+ element-choice-set:
type: array
items:
- $ref: "#/definitions/l3-interface-ipv4-address-list"
- l3-interface-ipv6-address-list:
+ $ref: "#/definitions/element-choice-set"
+ entitlement:
+ description: |
+ Metadata for entitlement group.
+ ###### Related Nodes
+ - TO generic-vnf( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vce( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ required:
+ - group-uuid
+ - resource-uuid
+ properties:
+ group-uuid:
+ type: string
+ description: Unique ID for the entitlement group the resource comes from, should be uuid.
+ resource-uuid:
+ type: string
+ description: Unique ID of an entitlement resource.
+ resource-version:
+ type: string
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ entitlements:
+ description: |
+ Entitlements, keyed by group-uuid and resource-uuid, related to license management
+ properties:
+ entitlement:
type: array
items:
- $ref: "#/definitions/l3-interface-ipv6-address-list"
- l-interfaces:
+ $ref: "#/definitions/entitlement"
+ esr-ems:
description: |
- Collection of logical interfaces.
+ Persist EMS address information used by EMS driver.
+ ###### Related Nodes
+ - TO esr-system-info (CHILD of esr-ems, esr-ems has esr-system-info, One2Many)
+ - ESR-EMS deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
+ required:
+ - ems-id
properties:
- l-interface:
+ ems-id:
+ type: string
+ description: Unique ID of EMS.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ esr-system-info-list:
+ type: object
+ $ref: "#/definitions/esr-system-info-list"
+ relationship-list:
+ type: object
+ $ref: "#/definitions/relationship-list"
+ esr-ems-list:
+ properties:
+ esr-ems:
type: array
items:
- $ref: "#/definitions/l-interface"
- vserver:
+ $ref: "#/definitions/esr-ems"
+ esr-system-info:
description: |
- Virtual Servers, aka virtual machine or VM.
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
- ###### Related Nodes
- - TO flavor (Many2One)
- - TO image (Many2One)
- - TO l-interface (comprises vserver, Many2Many)
- - TO pserver (Many2One)
- - TO volume (comprises vserver, Many2Many)
- - TO vnfc (Many2Many)
- - TO snapshot (One2One)
- - TO vf-module (Many2One)
- - FROM generic-vnf
- - FROM tenant (is composed of vserver)
- - FROM vce
+ Persist common address information of external systems.
+ ###### Related Nodes
+ - FROM esr-ems (PARENT of esr-system-info, esr-ems has esr-system-info)
+ - FROM esr-vnfm (PARENT of esr-system-info, esr-vnfm has esr-system-info)
+ - FROM esr-thirdparty-sdnc (PARENT of esr-system-info, esr-thirdparty-sdnc has esr-system-info)
+ - FROM cloud-region (PARENT of esr-system-info, cloud-region has esr-system-info)
required:
- - vserver-id
- - vserver-name
- - vserver-selflink
- - in-maint
- - is-closed-loop-disabled
+ - esr-system-info-id
+ - user-name
+ - password
+ - system-type
properties:
- vserver-id:
+ esr-system-info-id:
type: string
- description: Unique identifier for this vserver relative to its tenant
- vserver-name:
+ description: Unique ID of esr system info.
+ system-name:
type: string
- description: Name of vserver
- vserver-name2:
+ description: name of external system.
+ type:
type: string
- description: Alternative name of vserver
- prov-status:
+ description: type of external systems.
+ vendor:
type: string
- description: Trigger for operational monitoring of this resource by Service Assurance systems.
- vserver-selflink:
+ description: vendor of external systems.
+ version:
type: string
- description: URL to endpoint where AAI can get more details
- in-maint:
+ description: version of external systems.
+ service-url:
+ type: string
+ description: url used to access external systems.
+ user-name:
+ type: string
+ description: username used to access external systems.
+ password:
+ type: string
+ description: password used to access external systems.
+ system-type:
+ type: string
+ description: it could be vim/vnfm/thirdparty-sdnc/ems-resource/ems-performance/ems-alarm.
+ protocol:
+ type: string
+ description: protocol of third party SDNC, for example netconf/snmp.
+ ssl-cacert:
+ type: string
+ description: ca file content if enabled ssl on auth-url.
+ ssl-insecure:
type: boolean
- is-closed-loop-disabled:
+ description: Whether to verify VIM's certificate.
+ ip-address:
+ type: string
+ description: service IP of ftp server.
+ port:
+ type: string
+ description: service port of ftp server.
+ cloud-domain:
+ type: string
+ description: domain info for authentication.
+ default-tenant:
+ type: string
+ description: default tenant of VIM.
+ passive:
type: boolean
+ description: ftp passive mode or not.
+ remote-path:
+ type: string
+ description: resource or performance data file path.
+ system-status:
+ type: string
+ description: the status of external system.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- volumes:
- type: array
- items:
- $ref: "#/definitions/volume"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- l-interfaces:
+ esr-system-info-list:
+ description: |
+ Collection of persistent block-level external system auth info.
+ properties:
+ esr-system-info:
type: array
- items:
- $ref: "#/definitions/l-interface"
- vservers:
+ items:
+ $ref: "#/definitions/esr-system-info"
+ esr-thirdparty-sdnc:
description: |
- Collection of virtual Servers, aka virtual machines or VMs.
+ Persist SDNC address information used by ONAP SDNC.
+ ###### Related Nodes
+ - TO esr-system-info (CHILD of esr-thirdparty-sdnc, esr-thirdparty-sdnc has esr-system-info, One2One)
+ - TO pnf( esr-thirdparty-sdnc has pnf, One2Many)
+ - ESR-THIRDPARTY-SDNC deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
+ required:
+ - thirdparty-sdnc-id
properties:
- vserver:
+ thirdparty-sdnc-id:
+ type: string
+ description: Unique ID of SDNC.
+ location:
+ type: string
+ description: used for DC type to indicate the location of SDNC, such as Core or Edge.
+ product-name:
+ type: string
+ description: password used to access SDNC server.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ esr-system-info-list:
+ type: object
+ $ref: "#/definitions/esr-system-info-list"
+ relationship-list:
+ type: object
+ $ref: "#/definitions/relationship-list"
+ esr-thirdparty-sdnc-list:
+ properties:
+ esr-thirdparty-sdnc:
type: array
items:
- $ref: "#/definitions/vserver"
- tenant:
+ $ref: "#/definitions/esr-thirdparty-sdnc"
+ esr-vnfm:
description: |
- Openstack tenant
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Persist VNFM address information used by VF-C.
###### Related Nodes
- - TO l3-network (Many2Many)
- - TO service-subscription (Many2Many)
- - TO vserver (comprises tenant, One2Many)
- - FROM cloud-region (is composed of tenant)
- - FROM group-assignment
- - FROM volume-group
+ - TO esr-system-info (CHILD of esr-vnfm, esr-vnfm has esr-system-info, One2One)
+ - ESR-VNFM deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
required:
- - tenant-id
- - tenant-name
+ - vnfm-id
properties:
- tenant-id:
+ vnfm-id:
type: string
- description: Unique id relative to the cloud-region.
- tenant-name:
+ description: Unique ID of VNFM.
+ vim-id:
type: string
- description: Readable name of tenant
+ description: indecate the VIM to deploy VNF.
+ certificate-url:
+ type: string
+ description: certificate url of VNFM.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- vservers:
+ esr-system-info-list:
+ type: object
+ $ref: "#/definitions/esr-system-info-list"
+ relationship-list:
+ type: object
+ $ref: "#/definitions/relationship-list"
+ esr-vnfm-list:
+ properties:
+ esr-vnfm:
type: array
- items:
- $ref: "#/definitions/vserver"
+ items:
+ $ref: "#/definitions/esr-vnfm"
+ evc:
+ description: |
+ evc object is an optional child object of the Configuration object.
+ ###### Related Nodes
+ - TO configuration( evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)
+ required:
+ - evc-id
+ properties:
+ evc-id:
+ type: string
+ description: Unique/key field for the evc object
+ forwarding-path-topology:
+ type: string
+ description: Point-to-Point, Multi-Point
+ cir-value:
+ type: string
+ description: Commited Information Rate
+ cir-units:
+ type: string
+ description: CIR units
+ connection-diversity-group-id:
+ type: string
+ description: Diversity Group ID
+ service-hours:
+ type: string
+ description: formerly Performance Group
+ esp-evc-circuit-id:
+ type: string
+ description: EVC Circuit ID of ESP EVC
+ esp-evc-cir-value:
+ type: string
+ description: Committed Information Rate (For ESP)
+ esp-evc-cir-units:
+ type: string
+ description: CIR units (For ESP)
+ esp-itu-code:
+ type: string
+ description: Identifies ESP
+ collector-pop-clli:
+ type: string
+ description: Collector POP CLLI (from the hostname of the access pnf)
+ inter-connect-type-ingress:
+ type: string
+ description: Interconnect type on ingress side of EVC.
+ tagmode-access-ingress:
+ type: string
+ description: tagode for collector side of EVC
+ tagmode-access-egress:
+ type: string
+ description: tagMode for network side of EVC
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- tenants:
- description: |
- Collection of openstack tenants.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ evcs:
properties:
- tenant:
+ evc:
type: array
items:
- $ref: "#/definitions/tenant"
+ $ref: "#/definitions/evc"
+ external-system:
+ description: |
+ Namespace for external system.
+ properties:
+ esr-ems-list:
+ type: object
+ $ref: "#/definitions/esr-ems-list"
+ esr-vnfm-list:
+ type: object
+ $ref: "#/definitions/esr-vnfm-list"
+ esr-thirdparty-sdnc-list:
+ type: object
+ $ref: "#/definitions/esr-thirdparty-sdnc-list"
+ extra-properties:
+ description: |
+ Extra properties for inventory item for response list
+ extra-property:
+ properties:
+ property-name:
+ type: string
flavor:
description: |
Openstack flavor.
- ###### Default Delete Scope
- ERROR_IF_ANY_IN_EDGES
###### Related Nodes
- - FROM cloud-region (is composed of flavor)
- - FROM vserver
+ - TO cloud-region( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)
+ - FLAVOR cannot be deleted if linked to VSERVER
required:
- flavor-id
- flavor-name
@@ -37762,143 +48713,376 @@ definitions:
type: array
items:
$ref: "#/definitions/flavor"
- group-assignment:
+ forwarder:
description: |
- Openstack group-assignment used to store exclusivity groups (EG).
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Entity describing a sequenced segment of forwarding path
###### Related Nodes
- - TO tenant (Many2Many)
- - TO pserver (One2Many)
- - FROM cloud-region (is composed of group-assignment)
+ - TO forwarding-path( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)
+ - TO l-interface( forwarder org.onap.relationships.inventory.ForwardsTo l-interface, MANY2ONE)
+ - TO configuration( forwarder org.onap.relationships.inventory.Uses configuration, ONE2ONE)
+ - TO lag-interface( forwarder org.onap.relationships.inventory.ForwardsTo lag-interface, MANY2ONE)
+ - TO p-interface( forwarder org.onap.relationships.inventory.ForwardsTo p-interface, MANY2ONE)
+ - FORWARDER deletion means associated objects of these types are also DELETED:CONFIGURATION
required:
- - group-id
- - group-type
- - group-name
+ - sequence
properties:
- group-id:
+ sequence:
+ type: integer
+ format: int32
+ description: Unique ID of this segmentation
+ forwarder-role:
type: string
- description: Group id, expected to be unique across cloud-region.
- group-type:
+ description: ingress, intermediate, egress
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ resource-version:
type: string
- description: Group type - the type of group this instance refers to
- group-name:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ forwarder-evc:
+ description: |
+ forwarder object is an optional child object of the Configuration object.
+ ###### Related Nodes
+ - TO configuration( forwarder-evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)
+ required:
+ - forwarder-evc-id
+ properties:
+ forwarder-evc-id:
type: string
- description: Group name - name assigned to the group
- group-description:
+ description: Key for forwarder-evc object
+ circuit-id:
type: string
- description: Group description - description of the group
- resource-version:
+ description: Circuit ID from customer/ESP/ingress end of EVC, or reference to beater circuit on gateway/network/egress end of EVC
+ ivlan:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ description: Internal VLAN.
+ svlan:
+ type: string
+ description: SVLAN value for ingress of egress forwarder.
+ cvlan:
+ type: string
+ description: CVLAN value for ingress of egress forwarder.
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- group-assignments:
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ forwarder-evcs:
+ properties:
+ forwarder-evc:
+ type: array
+ items:
+ $ref: "#/definitions/forwarder-evc"
+ forwarders:
+ properties:
+ forwarder:
+ type: array
+ items:
+ $ref: "#/definitions/forwarder"
+ forwarding-path:
description: |
- Collection of openstack group assignments
+ Entity that describes the sequenced forwarding path between interfaces of services or resources
+ ###### Related Nodes
+ - TO service-instance( forwarding-path org.onap.relationships.inventory.AppliesTo service-instance, MANY2ONE)
+ - TO configuration( forwarding-path org.onap.relationships.inventory.Uses configuration, ONE2ONE)
+ - FROM forwarder( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)
+ - FORWARDING-PATH is DELETED when these are DELETED FORWARDER
+ - FORWARDING-PATH deletion means associated objects of these types are also DELETED:CONFIGURATION
+ required:
+ - forwarding-path-id
+ - forwarding-path-name
properties:
- group-assignment:
+ forwarding-path-id:
+ type: string
+ description: Unique ID of this FP
+ forwarding-path-name:
+ type: string
+ description: Name of the FP
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ selflink:
+ type: string
+ description: the self link for this FP
+ forwarders:
+ type: array
+ items:
+ $ref: "#/definitions/forwarder"
+ forwarding-paths:
+ properties:
+ forwarding-path:
type: array
items:
- $ref: "#/definitions/group-assignment"
- snapshot:
+ $ref: "#/definitions/forwarding-path"
+ generic-vnf:
description: |
- Openstack snapshot
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ General purpose VNF
###### Related Nodes
- - FROM cloud-region (is composed of snapshot)
- - FROM vserver
+ - TO availability-zone( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - TO instance-group( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO ipsec-configuration( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)
+ - TO l3-network( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO license-key-resource( generic-vnf org.onap.relationships.inventory.Uses license-key-resource, MANY2MANY)
+ - TO pserver( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)
+ - TO vnf-image( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)
+ - TO volume-group( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - TO vserver( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)
+ - TO virtual-data-center( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY)
+ - FROM entitlement( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM lag-interface( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM license( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM network-profile( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)
+ - FROM site-pair-set( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)
+ - GENERIC-VNF is DELETED when these are DELETED ENTITLEMENT,VNFC,LAG-INTERFACE,LICENSE,L-INTERFACE,VF-MODULE
required:
- - snapshot-id
+ - vnf-id
+ - vnf-name
+ - vnf-type
+ - in-maint
+ - is-closed-loop-disabled
properties:
- snapshot-id:
+ vnf-id:
type: string
- description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
- snapshot-name:
+ description: Unique id of VNF. This is unique across the graph.
+ vnf-name:
type: string
- description: Snapshot name
- snapshot-architecture:
+ description: Name of VNF.
+ vnf-name2:
type: string
- description: Operating system architecture
- snapshot-os-distro:
+ description: Alternate name of VNF.
+ vnf-type:
type: string
- description: The common name of the operating system distribution in lowercase
- snapshot-os-version:
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ service-id:
type: string
- description: The operating system version as specified by the distributor.
- application:
+ description: Unique identifier of service, does not necessarily map to ASDC service models. SOON TO BE DEPRECATED
+ regional-resource-zone:
type: string
- description: The application that the image instantiates.
- application-vendor:
+ description: Regional way of organizing pservers, source of truth should define values
+ prov-status:
type: string
- description: The vendor of the application.
- application-version:
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ operational-state:
type: string
- description: The version of the application.
- snapshot-selflink:
+ description: Indicator for whether the resource is considered operational. Valid values are in-service-path and out-of-service-path.
+ license-key:
type: string
- description: URL to endpoint where AAI can get more details
- prev-snapshot-id:
+ description: OBSOLETE - do not use
+ equipment-role:
type: string
- description: This field contains the UUID of the previous snapshot (if any).
+ description: Client should send valid enumerated value
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, used by MSO.
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ management-option:
+ type: string
+ description: identifier of managed by company or customer
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by generic-vnf.
+ ipv4-loopback0-address:
+ type: string
+ description: v4 Loopback0 address
+ nm-lan-v6-address:
+ type: string
+ description: v6 Loopback address
+ management-v6-address:
+ type: string
+ description: v6 management address
+ vcpu:
+ type: integer
+ format: int64
+ description: number of vcpus ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases
+ vcpu-units:
+ type: string
+ description: units associated with vcpu, used for VNFs with no vservers/flavors, to be used only in some usecases
+ vmemory:
+ type: integer
+ format: int64
+ description: number of GB of memory ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases
+ vmemory-units:
+ type: string
+ description: units associated with vmemory, used for VNFs with no vservers/flavors, to be used only in some usecases
+ vdisk:
+ type: integer
+ format: int64
+ description: number of vdisks ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases
+ vdisk-units:
+ type: string
+ description: units associated with vdisk, used for VNFs with no vservers/flavors, to be used only in some usecases
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ summary-status:
+ type: string
+ description: details regarding the generic-vnf operation, PLEASE DISCONTINUE USE OF THIS FIELD.
+ encrypted-access-flag:
+ type: boolean
+ description: indicates whether generic-vnf access uses SSH
+ persona-model-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ persona-model-customization-id:
+ type: string
+ description: captures the id of all the configuration used to customize the resource for the service.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ as-number:
+ type: string
+ description: as-number of the VNF
+ regional-resource-subzone:
+ type: string
+ description: represents sub zone of the rr plane
+ selflink:
+ type: string
+ description: Path to the controller object.
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- snapshots:
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/l-interface"
+ lag-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/lag-interface"
+ vf-modules:
+ type: array
+ items:
+ $ref: "#/definitions/vf-module"
+ licenses:
+ type: array
+ items:
+ $ref: "#/definitions/license"
+ entitlements:
+ type: array
+ items:
+ $ref: "#/definitions/entitlement"
+ generic-vnfs:
description: |
- Collection of openstack snapshots
+ Collection of VNFs
properties:
- snapshot:
+ generic-vnf:
type: array
items:
- $ref: "#/definitions/snapshot"
- metadatum:
+ $ref: "#/definitions/generic-vnf"
+ group-assignment:
description: |
- Key/value pairs
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Openstack group-assignment used to store exclusivity groups (EG).
###### Related Nodes
- - FROM image (is composed of metadatum)
- - FROM model-ver (is composed of metadatum)
- - FROM service-instance (is composed of metadatum)
- - FROM connector (is composed of metadatum)
+ - TO cloud-region( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)
required:
- - metaname
- - metaval
+ - group-id
+ - group-type
+ - group-name
properties:
- metaname:
+ group-id:
type: string
- metaval:
+ description: Group id, expected to be unique across cloud-region.
+ group-type:
+ type: string
+ description: Group type - the type of group this instance refers to
+ group-name:
type: string
+ description: Group name - name assigned to the group
+ group-description:
+ type: string
+ description: Group description - description of the group
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- metadata:
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ group-assignments:
description: |
- Collection of metadatum (key/value pairs)
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Collection of openstack group assignments
properties:
- metadatum:
+ group-assignment:
type: array
items:
- $ref: "#/definitions/metadatum"
+ $ref: "#/definitions/group-assignment"
+ host-route:
+ description: |
+ ###### Related Nodes
+ - TO subnet( host-route org.onap.relationships.inventory.BelongsTo subnet, MANY2ONE)
+ required:
+ - host-route-id
+ - route-prefix
+ - next-hop
+ properties:
+ host-route-id:
+ type: string
+ description: host-route id
+ route-prefix:
+ type: string
+ description: subnet prefix
+ next-hop:
+ type: string
+ description: Could be ip-address, hostname, or service-instance
+ next-hop-type:
+ type: string
+ description: Should be ip-address, hostname, or service-instance to match next-hop
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ host-routes:
+ properties:
+ host-route:
+ type: array
+ items:
+ $ref: "#/definitions/host-route"
image:
description: |
Openstack image.
- ###### Default Delete Scope
- ERROR_4_IN_EDGES_OR_CASCADE
###### Related Nodes
- - TO metadatum (comprises image, Many2Many)
- - FROM cloud-region (is composed of image)
- - FROM vserver
+ - TO cloud-region( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)
+ - IMAGE cannot be deleted if linked to VSERVER
+ - IMAGE is DELETED when these are DELETED METADATUM
required:
- image-id
- image-name
@@ -37952,24 +49136,202 @@ definitions:
type: array
items:
$ref: "#/definitions/image"
- dvs-switch:
+ include-node-filter:
+ properties:
+ include-node-type:
+ type: string
+ instance-filter:
description: |
- Digital virtual switch metadata, used by SDN-C to configure VCEs. A&AI needs to receive this data from the PO deployment team and administer it using the provisioningTool.sh into A&AI.
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ InstanceFilter for performing a named-query or model query
+ instance-filters:
+ description: |
+ InstanceFilters for performing a named-query or model query
+ properties:
+ instance-filter:
+ type: array
+ items:
+ $ref: "#/definitions/instance-filter"
+ instance-group:
+ description: |
+ General mechanism for grouping instances
###### Related Nodes
- - TO availability-zone (Many2Many)
- - FROM cloud-region (is composed of dvs-switch)
+ - TO model( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM pnf( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
required:
- - switch-name
- - vcenter-url
+ - id
+ - description
+ - type
properties:
- switch-name:
+ id:
type: string
- description: DVS switch name
- vcenter-url:
+ description: Instance Group ID, UUID assigned to this instance.
+ description:
type: string
- description: URL used to reach the vcenter
+ description: Descriptive text to help identify the usage of this instance-group
+ type:
+ type: string
+ description: Only valid value today is lower case ha for high availability
+ sub-type:
+ type: string
+ description: Valid values for ha type are [geo-activeactive, geo-activestandby, local-activeactive, local-activestandby]
+ resource-version:
+ type: string
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ instance-groups:
+ description: |
+ Collection of openstack route table references
+ properties:
+ instance-group:
+ type: array
+ items:
+ $ref: "#/definitions/instance-group"
+ inventory:
+ properties:
+ search:
+ type: object
+ $ref: "#/definitions/search"
+ actions:
+ type: object
+ $ref: "#/definitions/actions"
+ cloud-infrastructure:
+ type: object
+ $ref: "#/definitions/cloud-infrastructure"
+ business:
+ type: object
+ $ref: "#/definitions/business"
+ service-design-and-creation:
+ type: object
+ $ref: "#/definitions/service-design-and-creation"
+ network:
+ type: object
+ $ref: "#/definitions/network"
+ aai-internal:
+ type: object
+ $ref: "#/definitions/aai-internal"
+ nodes:
+ type: array
+ items:
+ $ref: "#/definitions/aai-internal"
+ inventory-item:
+ properties:
+ inventory-item-type:
+ type: string
+ inventory-item-link:
+ type: string
+ inventory-item-data:
+ type: array
+ items:
+ $ref: "#/definitions/inventory-item-data"
+ tagged-inventory-item-list:
+ type: array
+ items:
+ $ref: "#/definitions/tagged-inventory-item-list"
+ inventory-item-data:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ inventory-response-item:
+ description: |
+ Inventory item for response list
+ properties:
+ model-name:
+ type: string
+ extra-properties:
+ type: object
+ $ref: "#/definitions/extra-properties"
+ inventory-response-items:
+ type: object
+ $ref: "#/definitions/inventory-response-items"
+ inventory-response-items:
+ description: |
+ Container for inventory items in response list
+ properties:
+ inventory-response-item:
+ type: array
+ items:
+ $ref: "#/definitions/inventory-response-item"
+ ipsec-configuration:
+ description: |
+ IPSec configuration node will contain various configuration data for the NMTE VNF. This node will have an edge to the generic-vnf (vnf type = TE). Starting 1607, this data will be populated by SDN-C
+ ###### Related Nodes
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)
+ - FROM vig-server( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)
+ - IPSEC-CONFIGURATION is DELETED when these are DELETED VIG-SERVER
+ required:
+ - ipsec-configuration-id
+ properties:
+ ipsec-configuration-id:
+ type: string
+ description: UUID of this configuration
+ requested-vig-address-type:
+ type: string
+ description: Indicate the type of VIG server like AVPN, INTERNET, BOTH
+ requested-encryption-strength:
+ type: string
+ description: Encryption values like 3des-cbc, des-cbc, aes-128-cbc, aes-192-cbc, aes-265-cbc
+ requested-dmz-type:
+ type: string
+ description: can offer a shared DMZ or a DMZ specific to a customer
+ shared-dmz-network-address:
+ type: string
+ description: Network address of shared DMZ
+ requested-customer-name:
+ type: string
+ description: If the DMZ is a custom DMZ, this field will indicate the customer information
+ ike-version:
+ type: string
+ description: can be 1 or 2
+ ikev1-authentication:
+ type: string
+ description: Contains values like md5, sha1, sha256, sha384
+ ikev1-encryption:
+ type: string
+ description: Encyption values like 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
+ ikev1-dh-group:
+ type: string
+ description: Diffie-Hellman group like DH-GROUP2, DH-GROUP5, DH-GROUP14
+ ikev1-am-group-id:
+ type: string
+ description: Group name defined in VIG for clients using aggressive mode
+ ikev1-am-password:
+ type: string
+ description: pre-shared key for the above group name
+ ikev1-sa-lifetime:
+ type: string
+ description: Lifetime for IKEv1 SA
+ ipsec-authentication:
+ type: string
+ description: md5, sha1, sha256, sha384
+ ipsec-encryption:
+ type: string
+ description: 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
+ ipsec-sa-lifetime:
+ type: string
+ description: Life time for IPSec SA
+ ipsec-pfs:
+ type: string
+ description: enable PFS or not
+ xauth-userid:
+ type: string
+ description: user ID for xAuth, sm-user, ,nmteHostName
+ xauth-user-password:
+ type: string
+ description: Encrypted using the Juniper $9$ algorithm
+ dpd-interval:
+ type: string
+ description: The time between DPD probe
+ dpd-frequency:
+ type: string
+ description: Maximum number of DPD before claiming the tunnel is down
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
@@ -37977,87 +49339,431 @@ definitions:
type: array
items:
$ref: "#/definitions/relationship"
- dvs-switches:
+ vig-servers:
+ type: array
+ items:
+ $ref: "#/definitions/vig-server"
+ ipsec-configurations:
+ properties:
+ ipsec-configuration:
+ type: array
+ items:
+ $ref: "#/definitions/ipsec-configuration"
+ key-data:
+ properties:
+ key-name:
+ type: string
+ key-value:
+ type: string
+ l-interface:
description: |
- Collection of digital virtual switch metadata used for vmWare VCEs and GenericVnfs.
+ Logical interfaces, e.g., a vnic.
+ ###### Related Nodes
+ - TO generic-vnf( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO lag-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)
+ - TO logical-link( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)
+ - TO newvce( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)
+ - TO p-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)
+ - TO vserver( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - FROM sriov-vf( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)
+ - FROM vlan( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)
+ - L-INTERFACE is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST,SRIOV-VF,VLAN
+ - L-INTERFACE deletion means associated objects of these types are also DELETED:LOGICAL-LINK
+ required:
+ - interface-name
properties:
- dvs-switch:
+ interface-name:
+ type: string
+ description: Name given to the interface
+ interface-role:
+ type: string
+ description: E.g., CUSTOMER, UPLINK, etc.
+ v6-wan-link-ip:
+ type: string
+ description: Questionably placed - v6 ip addr of this interface (is in vr-lan-interface from Mary B.
+ selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ interface-id:
+ type: string
+ description: ID of interface
+ macaddr:
+ type: string
+ description: MAC address for the interface
+ network-name:
+ type: string
+ description: Name of the network
+ management-option:
+ type: string
+ description: Whether A&AI should be managing this interface of not. Could have value like CUSTOMER
+ interface-description:
+ type: string
+ description: Human friendly text regarding this interface.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ vlans:
+ type: array
+ items:
+ $ref: "#/definitions/vlan"
+ sriov-vfs:
+ type: array
+ items:
+ $ref: "#/definitions/sriov-vf"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ l3-interface-ipv4-address-list:
type: array
items:
- $ref: "#/definitions/dvs-switch"
- oam-network:
+ $ref: "#/definitions/l3-interface-ipv4-address-list"
+ l3-interface-ipv6-address-list:
+ type: array
+ items:
+ $ref: "#/definitions/l3-interface-ipv6-address-list"
+ l-interfaces:
description: |
- OAM network, to be deprecated shortly. Do not use for new purposes.
- ###### Default Delete Scope
- ERROR_IF_ANY_IN_EDGES
+ Collection of logical interfaces.
+ properties:
+ l-interface:
+ type: array
+ items:
+ $ref: "#/definitions/l-interface"
+ l3-interface-ipv4-address-list:
+ description: |
+ IPv4 Address Range
###### Related Nodes
- - TO complex (Many2Many)
- - TO service-capability (Many2Many)
- - FROM cloud-region (is composed of oam-network)
+ - TO l3-network( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - TO subnet( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - TO l-interface( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - TO vlan( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
required:
- - network-uuid
+ - l3-interface-ipv4-address
+ properties:
+ l3-interface-ipv4-address:
+ type: string
+ description: IP address
+ l3-interface-ipv4-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 32 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
+ type: string
+ description: Neutron network id of the interface that address belongs to
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of subnet that address belongs to
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ l3-interface-ipv6-address-list:
+ description: |
+ IPv6 Address Range
+ ###### Related Nodes
+ - TO l3-network( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - TO subnet( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - TO l-interface( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - TO vlan( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ required:
+ - l3-interface-ipv6-address
+ properties:
+ l3-interface-ipv6-address:
+ type: string
+ description: IP address
+ l3-interface-ipv6-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 128 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
+ type: string
+ description: Neutron network id of the interface that address belongs to
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of subnet that address belongs to
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ l3-network:
+ description: |
+ Generic network definition
+ ###### Related Nodes
+ - TO network-policy( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)
+ - TO route-table-reference( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)
+ - TO vpn-binding( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM complex( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - FROM ctag-assignment( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM segmentation-assignment( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)
+ - FROM subnet( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)
+ - L3-NETWORK is DELETED when these are DELETED CTAG-ASSIGNMENT,SEGMENTATION-ASSIGNMENT,SUBNET
+ required:
+ - network-id
- network-name
- - cvlan-tag
+ - is-bound-to-vpn
+ - is-provider-network
+ - is-shared-network
+ - is-external-network
properties:
- network-uuid:
+ network-id:
type: string
- description: UUID of the network. Unique across a cloud-region
+ description: Network ID, should be uuid. Unique across A&AI.
network-name:
type: string
- description: Name of the network.
- cvlan-tag:
+ description: Name of the network, governed by some naming convention..
+ network-type:
+ type: string
+ description: Type of the network - who defines these values?
+ network-role:
+ type: string
+ description: Role the network plans - who defines these values?
+ network-technology:
+ type: string
+ description: Network technology - who defines these values?
+ neutron-network-id:
+ type: string
+ description: Neutron network id of this Interface
+ is-bound-to-vpn:
+ type: boolean
+ service-id:
+ type: string
+ description: Unique identifier of service from ASDC. Does not strictly map to ASDC services. SOON TO BE DEPRECATED
+ network-role-instance:
type: integer
format: int64
- description: cvlan-id
- ipv4-oam-gateway-address:
+ description: network role instance
+ resource-version:
type: string
- description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
- ipv4-oam-gateway-address-prefix-length:
- type: integer
- format: int32
- description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ contrail-network-fqdn:
+ type: string
+ description: Contrail FQDN for the network
+ persona-model-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ persona-model-customization-id:
+ type: string
+ description: captures the id of all the configuration used to customize the resource for the service.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ physical-network-name:
+ type: string
+ description: Name associated with the physical network.
+ is-provider-network:
+ type: boolean
+ is-shared-network:
+ type: boolean
+ is-external-network:
+ type: boolean
+ selflink:
+ type: string
+ description: Path to the controller object.
+ subnets:
+ type: array
+ items:
+ $ref: "#/definitions/subnet"
+ ctag-assignments:
+ type: array
+ items:
+ $ref: "#/definitions/ctag-assignment"
+ segmentation-assignments:
+ type: array
+ items:
+ $ref: "#/definitions/segmentation-assignment"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ description: Relates to tenant (or is it a child of tenant), complex, service, vpn-binding
+ l3-networks:
+ properties:
+ l3-network:
+ type: array
+ items:
+ $ref: "#/definitions/l3-network"
+ lag-interface:
+ description: |
+ Link aggregate interface
+ ###### Related Nodes
+ - TO generic-vnf( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO lag-link( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)
+ - TO p-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)
+ - TO pnf( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - TO pserver( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - TO vpls-pe( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)
+ - LAG-INTERFACE is DELETED when these are DELETED L-INTERFACE
+ - LAG-INTERFACE deletion means associated objects of these types are also DELETED:LAG-LINK
+ required:
+ - interface-name
+ properties:
+ interface-name:
+ type: string
+ description: Name that identifies the link aggregate interface
+ interface-description:
+ type: string
+ description: Human friendly text regarding this interface.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ interface-id:
+ type: string
+ description: ID of interface
+ interface-role:
+ type: string
+ description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- oam-networks:
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/l-interface"
+ lag-interfaces:
description: |
- Collection of OAM networks, to be deprecated shortly. Do not use for new purposes.
+ Collection of link aggregate interfaces.
properties:
- oam-network:
+ lag-interface:
type: array
items:
- $ref: "#/definitions/oam-network"
- availability-zone:
+ $ref: "#/definitions/lag-interface"
+ lag-link:
description: |
- Availability zone, a collection of compute hosts/pservers
- ###### Default Delete Scope
- ERROR_IF_ANY_IN_EDGES
- ###### Related Nodes
- - TO complex (Many2Many)
- - TO service-capability (Many2Many)
- - FROM cloud-region (is composed of availability-zone)
- - FROM ctag-pool
- - FROM dvs-switch
- - FROM generic-vnf
- - FROM pserver
- - FROM vce
+ LAG links can connect lag-interfaces
+ ###### Related Nodes
+ - FROM lag-interface( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)
required:
- - availability-zone-name
- - hypervisor-type
+ - link-name
properties:
- availability-zone-name:
+ link-name:
type: string
- description: Name of the availability zone. Unique across a cloud region
- hypervisor-type:
+ description: Alphabetical concatenation of lag-interface names
+ resource-version:
type: string
- description: Type of hypervisor. Source of truth should define valid values.
- operational-state:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ lag-links:
+ description: |
+ Collection of link aggregation connections
+ properties:
+ lag-link:
+ type: array
+ items:
+ $ref: "#/definitions/lag-link"
+ license:
+ description: |
+ Metadata for license group.
+ ###### Related Nodes
+ - TO generic-vnf( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vce( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ required:
+ - group-uuid
+ - resource-uuid
+ properties:
+ group-uuid:
type: string
- description: State that indicates whether the availability zone should be used, etc. Source of truth should define valid values.
+ description: Unique ID for the license group the resource belongs to, should be uuid.
+ resource-uuid:
+ type: string
+ description: Unique ID of a license resource.
+ resource-version:
+ type: string
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ licenses:
+ description: |
+ Licenses to be allocated across resources, keyed by group-uuid and resource-uuid, related to license management
+ properties:
+ license:
+ type: array
+ items:
+ $ref: "#/definitions/license"
+ line-of-business:
+ description: |
+ describes a line-of-business
+ ###### Related Nodes
+ - TO generic-vnf( line-of-business org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)
+ required:
+ - line-of-business-name
+ properties:
+ line-of-business-name:
+ type: string
+ description: Name of the line-of-business (product)
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
@@ -38065,118 +49771,542 @@ definitions:
type: array
items:
$ref: "#/definitions/relationship"
- availability-zones:
+ lines-of-business:
description: |
- Collection of availability zones
+ Collection of lines-of-business
properties:
- availability-zone:
+ line-of-business:
type: array
items:
- $ref: "#/definitions/availability-zone"
- cloud-region:
+ $ref: "#/definitions/line-of-business"
+ logical-link:
description: |
- cloud-region designates an installation of a cloud cluster or region or instantiation.
- ###### Default Delete Scope
- THIS_NODE_ONLY
- ###### Related Nodes
- - TO complex (Many2One)
- - TO l3-network (Many2Many)
- - TO tenant (comprises cloud-region, One2Many)
- - TO image (comprises cloud-region, One2Many)
- - TO flavor (comprises cloud-region, One2Many)
- - TO availability-zone (comprises cloud-region, One2Many)
- - TO oam-network (comprises cloud-region, One2Many)
- - TO dvs-switch (comprises cloud-region, One2Many)
- - TO volume-group (comprises cloud-region, One2Many)
- - TO group-assignment (comprises cloud-region, One2Many)
- - TO snapshot (comprises cloud-region, One2Many)
- - TO zone (Many2One)
- - FROM pserver
- - FROM logical-link
+ Logical links generally connect l-interfaces but are used to express logical connectivity between two points
+ ###### Related Nodes
+ - TO cloud-region( logical-link org.onap.relationships.inventory.LocatedIn cloud-region, MANY2MANY)
+ - TO generic-vnf( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)
+ - TO lag-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)
+ - TO logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - TO pnf( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)
+ - TO pserver( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)
+ - TO vpn-binding( logical-link org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - TO virtual-data-center( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)
+ - FROM p-interface( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - FROM vlan( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
required:
- - cloud-owner
- - cloud-region-id
+ - link-name
+ - link-type
properties:
- cloud-owner:
+ link-name:
type: string
- description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
- cloud-region-id:
+ description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
+ link-type:
type: string
- description: Identifier used by the vendor for the region. Second part of composite key
- cloud-type:
+ description: Type of logical link, e.g., evc
+ speed-value:
type: string
- description: Type of the cloud (e.g., openstack)
- owner-defined-type:
+ description: Captures the numeric part of the speed
+ speed-units:
type: string
- description: Cloud-owner defined type indicator (e.g., dcp, lcp)
- cloud-region-version:
+ description: Captures the units corresponding to the speed
+ ip-version:
type: string
- description: Software version employed at the site. NOTE - THIS FIELD IS NOT KEPT UP TO DATE.
- identity-url:
+ description: v4, v6, or ds for dual stack
+ routing-protocol:
type: string
- description: URL of the keystone identity service
- cloud-zone:
+ description: For example, static or BGP
+ resource-version:
type: string
- description: Zone where the cloud is homed. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
- complex-name:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ persona-model-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ operational-status:
+ type: string
+ description: Indication of operational status of the logical link.
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+ link-role:
+ type: string
+ description: Indication of the network use of the logical link.
+ link-name2:
+ type: string
+ description: Alias or alternate name (CLCI or D1 name).
+ link-id:
+ type: string
+ description: UUID of the logical-link, SDNC generates this.
+ circuit-id:
+ type: string
+ description: Circuit id
+ purpose:
+ type: string
+ description: Reason for this entity, role it is playing
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ logical-links:
+ description: |
+ Collection of logical connections
+ properties:
+ logical-link:
+ type: array
+ items:
+ $ref: "#/definitions/logical-link"
+ metadata:
+ description: |
+ Collection of metadatum (key/value pairs)
+ properties:
+ metadatum:
+ type: array
+ items:
+ $ref: "#/definitions/metadatum"
+ metadatum:
+ description: |
+ Key/value pairs
+ ###### Related Nodes
+ - TO connector( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)
+ - TO image( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)
+ - TO service-instance( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - TO model-ver( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ required:
+ - metaname
+ - metaval
+ properties:
+ metaname:
+ type: string
+ metaval:
type: string
- description: complex name for cloud-region instance. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- volume-groups:
+ model:
+ description: |
+ Subgraph definition provided by ASDC to describe an inventory asset and its connections related to ASDC models, independent of version
+ ###### Related Nodes
+ - TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - FROM instance-group( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY)
+ - FROM model-ver( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - FROM named-query( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)
+ - MODEL cannot be deleted if linked to INSTANCE-GROUP,NAMED-QUERY,NAMED-QUERY-ELEMENT
+ - MODEL is DELETED when these are DELETED MODEL-VER
+ required:
+ - model-invariant-id
+ - model-type
+ properties:
+ model-invariant-id:
+ type: string
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ model-type:
+ type: string
+ description: Type of the model, e.g., service, resource, widget, etc.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-vers:
type: array
items:
- $ref: "#/definitions/volume-group"
- tenants:
+ $ref: "#/definitions/model-ver"
+ relationship-list:
type: array
items:
- $ref: "#/definitions/tenant"
- flavors:
+ $ref: "#/definitions/relationship"
+ model-and-named-query-search:
+ description: |
+ ModelAndNamedQuerySearch holds query-parameters and instance-properties for performing a named-query or model query
+ properties:
+ query-parameters:
+ type: object
+ $ref: "#/definitions/query-parameters"
+ instance-filters:
+ type: object
+ $ref: "#/definitions/instance-filters"
+ secondary-filts:
+ type: object
+ $ref: "#/definitions/secondary-filts"
+ top-node-type:
+ type: string
+ secondary-filter-cut-point:
+ type: string
+ model-constraint:
+ description: |
+ This is how we would capture constraints defining allowed sets of elements.
+ ###### Related Nodes
+ - TO model-element( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)
+ - MODEL-CONSTRAINT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET
+ required:
+ - model-constraint-uuid
+ - constrained-element-set-uuid-to-replace
+ properties:
+ model-constraint-uuid:
+ type: string
+ constrained-element-set-uuid-to-replace:
+ type: string
+ constrained-element-sets:
type: array
items:
- $ref: "#/definitions/flavor"
- group-assignments:
+ $ref: "#/definitions/constrained-element-set"
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-constraints:
+ properties:
+ model-constraint:
+ type: array
+ items:
+ $ref: "#/definitions/model-constraint"
+ model-element:
+ description: |
+ Defines how other models combine to make up a higher-level model.
+ ###### Related Nodes
+ - TO element-choice-set( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)
+ - TO model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - TO model-ver( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE)
+ - TO model-ver( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM model-constraint( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - MODEL-ELEMENT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET,MODEL-CONSTRAINT
+ required:
+ - model-element-uuid
+ - new-data-del-flag
+ - cardinality
+ properties:
+ model-element-uuid:
+ type: string
+ new-data-del-flag:
+ type: string
+ description: Indicates whether this element was created as part of instantiation from this model
+ cardinality:
+ type: string
+ description: How many of this type of element are required/allowed
+ linkage-points:
+ type: string
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-elements:
type: array
items:
- $ref: "#/definitions/group-assignment"
- snapshots:
+ $ref: "#/definitions/model-element"
+ description: Defines how other models combine to make up a higher-level model
+ model-constraints:
type: array
items:
- $ref: "#/definitions/snapshot"
- images:
+ $ref: "#/definitions/model-constraint"
+ description: Describes new constraints on this model element that are not part of that model's definition
+ relationship-list:
type: array
items:
- $ref: "#/definitions/image"
- dvs-switches:
+ $ref: "#/definitions/relationship"
+ model-elements:
+ properties:
+ model-element:
+ type: array
+ items:
+ $ref: "#/definitions/model-element"
+ model-ver:
+ description: |
+ Subgraph definition provided by ASDC to describe a specific version of an inventory asset and its connections related to ASDC models
+ ###### Related Nodes
+ - TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - MODEL-VER cannot be deleted if linked to MODEL-ELEMENT
+ - MODEL-VER is DELETED when these are DELETED MODEL-ELEMENT,METADATUM
+ required:
+ - model-version-id
+ - model-name
+ - model-version
+ properties:
+ model-version-id:
+ type: string
+ description: Unique identifier corresponding to one version of a model in ASDC
+ model-name:
+ type: string
+ description: Name of the model, which can change from version to version.
+ model-version:
+ type: string
+ description: Version
+ model-description:
+ type: string
+ description: Description
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-elements:
type: array
items:
- $ref: "#/definitions/dvs-switch"
- oam-networks:
+ $ref: "#/definitions/model-element"
+ metadata:
type: array
items:
- $ref: "#/definitions/oam-network"
- availability-zones:
+ $ref: "#/definitions/metadatum"
+ relationship-list:
type: array
items:
- $ref: "#/definitions/availability-zone"
+ $ref: "#/definitions/relationship"
+ model-vers:
+ properties:
+ model-ver:
+ type: array
+ items:
+ $ref: "#/definitions/model-ver"
+ models:
+ description: |
+ Collection of subgraph definitions provided by ASDC to describe the inventory assets and their connections related to ASDC models
+ properties:
+ model:
+ type: array
+ items:
+ $ref: "#/definitions/model"
+ multicast-configuration:
+ description: |
+ ###### Related Nodes
+ - FROM vlan( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)
+ required:
+ - multicast-configuration-id
+ - multicast-protocol
+ - rp-type
+ properties:
+ multicast-configuration-id:
+ type: string
+ description: Unique id of multicast configuration.
+ multicast-protocol:
+ type: string
+ description: protocol of multicast configuration
+ rp-type:
+ type: string
+ description: rp type of multicast configuration
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- cloud-regions:
+ multicast-configurations:
+ description: |
+ multicast configuration of generic-vnf ip-address
properties:
- cloud-region:
+ multicast-configuration:
type: array
items:
- $ref: "#/definitions/cloud-region"
+ $ref: "#/definitions/multicast-configuration"
+ named-queries:
+ properties:
+ named-query:
+ type: array
+ items:
+ $ref: "#/definitions/named-query"
+ named-query:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - TO model( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - NAMED-QUERY is DELETED when these are DELETED NAMED-QUERY-ELEMENT
+ required:
+ - named-query-uuid
+ - named-query-name
+ - named-query-version
+ properties:
+ named-query-uuid:
+ type: string
+ named-query-name:
+ type: string
+ named-query-version:
+ type: string
+ required-input-param:
+ type: string
+ description:
+ type: string
+ resource-version:
+ type: string
+ named-query-elements:
+ type: array
+ items:
+ $ref: "#/definitions/named-query-element"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ named-query-element:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - TO model( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)
+ - TO named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM property-constraint( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM related-lookup( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - NAMED-QUERY-ELEMENT is DELETED when these are DELETED PROPERTY-CONSTRAINT,RELATED-LOOKUP
+ required:
+ - named-query-element-uuid
+ properties:
+ named-query-element-uuid:
+ type: string
+ property-collect-list:
+ type: string
+ resource-version:
+ type: string
+ property-limit-desc:
+ type: string
+ do-not-output:
+ type: string
+ named-query-elements:
+ type: array
+ items:
+ $ref: "#/definitions/named-query-element"
+ related-lookups:
+ type: array
+ items:
+ $ref: "#/definitions/related-lookup"
+ property-constraints:
+ type: array
+ items:
+ $ref: "#/definitions/property-constraint"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ named-query-elements:
+ properties:
+ named-query-element:
+ type: array
+ items:
+ $ref: "#/definitions/named-query-element"
+ network:
+ description: |
+ Namespace for network inventory resources.
+ properties:
+ logical-links:
+ type: array
+ items:
+ $ref: "#/definitions/logical-link"
+ site-pair-sets:
+ type: array
+ items:
+ $ref: "#/definitions/site-pair-set"
+ vpn-bindings:
+ type: array
+ items:
+ $ref: "#/definitions/vpn-binding"
+ vpls-pes:
+ type: array
+ items:
+ $ref: "#/definitions/vpls-pe"
+ multicast-configurations:
+ type: array
+ items:
+ $ref: "#/definitions/multicast-configuration"
+ vces:
+ type: array
+ items:
+ $ref: "#/definitions/vce"
+ vnfcs:
+ type: array
+ items:
+ $ref: "#/definitions/vnfc"
+ l3-networks:
+ type: array
+ items:
+ $ref: "#/definitions/l3-network"
+ network-policies:
+ type: array
+ items:
+ $ref: "#/definitions/network-policy"
+ generic-vnfs:
+ type: array
+ items:
+ $ref: "#/definitions/generic-vnf"
+ lag-links:
+ type: array
+ items:
+ $ref: "#/definitions/lag-link"
+ newvces:
+ type: array
+ items:
+ $ref: "#/definitions/newvce"
+ pnfs:
+ type: array
+ items:
+ $ref: "#/definitions/pnf"
+ physical-links:
+ type: array
+ items:
+ $ref: "#/definitions/physical-link"
+ ipsec-configurations:
+ type: array
+ items:
+ $ref: "#/definitions/ipsec-configuration"
+ route-table-references:
+ type: array
+ items:
+ $ref: "#/definitions/route-table-reference"
+ instance-groups:
+ type: array
+ items:
+ $ref: "#/definitions/instance-group"
+ zones:
+ type: array
+ items:
+ $ref: "#/definitions/zone"
+ network-policies:
+ properties:
+ network-policy:
+ type: array
+ items:
+ $ref: "#/definitions/network-policy"
+ network-policy:
+ description: |
+ ###### Related Nodes
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)
+ required:
+ - network-policy-id
+ properties:
+ network-policy-id:
+ type: string
+ description: UUID representing unique key to this instance
+ network-policy-fqdn:
+ type: string
+ description: Contrail FQDN for the policy
+ heat-stack-id:
+ type: string
+ description: ID for the openStack Heat instance
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
network-profile:
description: |
Network profile populated by SDN-GP for SNMP
- ###### Default Delete Scope
- THIS_NODE_ONLY
###### Related Nodes
- - FROM generic-vnf
+ - TO generic-vnf( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
required:
- nm-profile-name
properties:
@@ -38201,19 +50331,301 @@ definitions:
type: array
items:
$ref: "#/definitions/network-profile"
+ newvce:
+ description: |
+ This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce.
+ ###### Related Nodes
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)
+ - NEWVCE is DELETED when these are DELETED L-INTERFACE
+ required:
+ - vnf-id2
+ - vnf-name
+ - vnf-type
+ properties:
+ vnf-id2:
+ type: string
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ vnf-name:
+ type: string
+ description: Name of VNF.
+ vnf-name2:
+ type: string
+ description: Alternate name of VNF.
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+ operational-state:
+ type: string
+ description: Indicator for whether the resource is considered operational
+ license-key:
+ type: string
+ description: OBSOLETE - do not use
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by VPE (v4-loopback0-ip-address).
+ equipment-role:
+ type: string
+ description: Client should send valid enumerated value.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ ipv4-loopback0-address:
+ type: string
+ description: v4 Loopback0 address
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO.
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/l-interface"
+ newvces:
+ description: |
+ This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce.
+ properties:
+ newvce:
+ type: array
+ items:
+ $ref: "#/definitions/newvce"
+ notification-event:
+ properties:
+ cambria.partition:
+ type: string
+ notification-event-header:
+ type: object
+ $ref: "#/definitions/notification-event-header"
+ notification-event-header:
+ properties:
+ id:
+ type: string
+ timestamp:
+ type: string
+ source-name:
+ type: string
+ domain:
+ type: string
+ sequence-number:
+ type: string
+ severity:
+ type: string
+ event-type:
+ type: string
+ version:
+ type: string
+ action:
+ type: string
+ entity-type:
+ type: string
+ top-entity-type:
+ type: string
+ entity-link:
+ type: string
+ status:
+ type: string
+ notify:
+ required:
+ - event-id
+ properties:
+ event-id:
+ type: string
+ node-type:
+ type: string
+ event-trigger:
+ type: string
+ key-data:
+ type: array
+ items:
+ $ref: "#/definitions/key-data"
+ selflink:
+ type: string
+ oam-network:
+ description: |
+ OAM network, to be deprecated shortly. Do not use for new purposes.
+ ###### Related Nodes
+ - TO cloud-region( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO complex( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)
+ - TO service-capability( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ required:
+ - network-uuid
+ - network-name
+ - cvlan-tag
+ properties:
+ network-uuid:
+ type: string
+ description: UUID of the network. Unique across a cloud-region
+ network-name:
+ type: string
+ description: Name of the network.
+ cvlan-tag:
+ type: integer
+ format: int64
+ description: cvlan-id
+ ipv4-oam-gateway-address:
+ type: string
+ description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
+ ipv4-oam-gateway-address-prefix-length:
+ type: integer
+ format: int32
+ description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ oam-networks:
+ description: |
+ Collection of OAM networks, to be deprecated shortly. Do not use for new purposes.
+ properties:
+ oam-network:
+ type: array
+ items:
+ $ref: "#/definitions/oam-network"
+ operational-environment:
+ description: |
+ It is a logical partition of the cloud which allows to have multiple environments in the production AIC.
+ ###### Related Nodes
+ - TO operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)
+ - FROM operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)
+ required:
+ - operational-environment-id
+ - operational-environment-name
+ - operational-environment-type
+ - operational-environment-status
+ - tenant-context
+ - workload-context
+ properties:
+ operational-environment-id:
+ type: string
+ description: UUID of an operational environment
+ operational-environment-name:
+ type: string
+ description: Operational Environment name
+ operational-environment-type:
+ type: string
+ description: Operational Environment Type.
+ operational-environment-status:
+ type: string
+ description: Status
+ tenant-context:
+ type: string
+ description: Tenant Context.
+ workload-context:
+ type: string
+ description: Workload Context.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ operational-environments:
+ description: |
+ a logical partition of the cloud which allows to have multiple environments in the production AIC.
+ properties:
+ operational-environment:
+ type: array
+ items:
+ $ref: "#/definitions/operational-environment"
+ overloaded-model:
+ description: |
+ Allows for legacy POST of old-style and new-style models
+ required:
+ - model-invariant-id
+ - model-name-version-id
+ - model-type
+ - model-name
+ - model-id
+ - model-version
+ properties:
+ model-invariant-id:
+ type: string
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ model-name-version-id:
+ type: string
+ description: Unique identifier corresponding to one version of a model in ASDC
+ model-type:
+ type: string
+ description: Type of the model, e.g., service, resource, widget, etc.
+ model-name:
+ type: string
+ description: Name of the model, which can change from version to version.
+ model-id:
+ type: string
+ description: Invariant unique ID which does not change from version to version
+ model-version:
+ type: string
+ description: Version
+ model-description:
+ type: string
+ description: Description
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-vers:
+ type: object
+ $ref: "#/definitions/model-vers"
+ relationship-list:
+ type: object
+ $ref: "#/definitions/relationship-list"
+ owning-entities:
+ description: |
+ Collection of owning-entities
+ properties:
+ owning-entity:
+ type: array
+ items:
+ $ref: "#/definitions/owning-entity"
+ owning-entity:
+ description: |
+ describes an owning-entity
+ ###### Related Nodes
+ - FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo owning-entity, MANY2ONE)
+ required:
+ - owning-entity-id
+ - owning-entity-name
+ properties:
+ owning-entity-id:
+ type: string
+ description: UUID of an owning entity
+ owning-entity-name:
+ type: string
+ description: Owning entity name
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
p-interface:
description: |
Physical interface (e.g., nic)
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
###### Related Nodes
- - TO l-interface (comprises p-interface, Many2Many)
- - TO physical-link (Many2Many)
- - TO logical-link (Many2One)
- - FROM lag-interface
- - FROM pserver (is composed of p-interface)
- - FROM pnf (is composed of p-interface)
- - FROM vpls-pe (is composed of p-interface)
+ - TO logical-link( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)
+ - TO physical-link( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)
+ - TO pnf( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - TO pserver( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - TO vpls-pe( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM lag-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)
+ - P-INTERFACE is DELETED when these are DELETED L-INTERFACE
+ - P-INTERFACE deletion means associated objects of these types are also DELETED:PHYSICAL-LINK
required:
- interface-name
properties:
@@ -38260,78 +50672,313 @@ definitions:
type: array
items:
$ref: "#/definitions/p-interface"
- lag-interface:
+ physical-link:
description: |
- Link aggregate interface
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
+ Collection of physical connections, typically between p-interfaces
###### Related Nodes
- - TO lag-link (Many2Many)
- - TO p-interface (Many2Many)
- - TO l-interface (comprises lag-interface, Many2Many)
- - FROM generic-vnf (is composed of lag-interface)
- - FROM pserver (is composed of lag-interface)
- - FROM pnf (is composed of lag-interface)
- - FROM vpls-pe (is composed of lag-interface)
+ - FROM p-interface( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)
required:
- - interface-name
+ - link-name
properties:
- interface-name:
- type: string
- description: Name that identifies the link aggregate interface
- interface-description:
- type: string
- description: Human friendly text regarding this interface.
- resource-version:
+ link-name:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
speed-value:
type: string
description: Captures the numeric part of the speed
speed-units:
type: string
description: Captures the units corresponding to the speed
+ circuit-id:
+ type: string
+ description: Circuit it
+ dual-mode:
+ type: string
+ description: Dual access mode (e.g., primary, secondary
+ management-option:
+ type: string
+ description: To provide information on who manages this circuit. A&AI or 3rd party transport provider
+ service-provider-name:
+ type: string
+ description: Name of the service Provider on this link.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ physical-links:
+ description: |
+ Collection of physical connections, typically between p-interfaces
+ properties:
+ physical-link:
+ type: array
+ items:
+ $ref: "#/definitions/physical-link"
+ platform:
+ description: |
+ describes a platform
+ ###### Related Nodes
+ - TO generic-vnf( platform org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)
+ required:
+ - platform-name
+ properties:
+ platform-name:
+ type: string
+ description: Name of the platform
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ platforms:
+ description: |
+ Collection of platforms
+ properties:
+ platform:
+ type: array
+ items:
+ $ref: "#/definitions/platform"
+ pnf:
+ description: |
+ PNF represents a physical network function. typically equipment used in the D1 world.
+ ###### Related Nodes
+ - TO complex( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO instance-group( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO zone( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf pnf, ONE2MANY)
+ - PNF is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
+ required:
+ - pnf-name
+ - in-maint
+ properties:
+ pnf-name:
+ type: string
+ description: unique name of Physical Network Function.
+ pnf-name2:
+ type: string
+ description: name of Physical Network Function.
+ pnf-name2-source:
+ type: string
+ description: source of name2
+ pnf-id:
+ type: string
+ description: id of pnf
+ equip-type:
+ type: string
+ description: Equipment type. Source of truth should define valid values.
+ equip-vendor:
+ type: string
+ description: Equipment vendor. Source of truth should define valid values.
+ equip-model:
+ type: string
+ description: Equipment model. Source of truth should define valid values.
+ management-option:
+ type: string
+ description: identifier of managed by company or customer
+ ipaddress-v4-oam:
+ type: string
+ description: ipv4-oam-address with new naming convention for IP addresses
+ sw-version:
+ type: string
+ description: sw-version is the version of SW for the hosted application on the PNF.
+ in-maint:
+ type: boolean
+ frame-id:
+ type: string
+ description: ID of the physical frame (relay rack) where pnf is installed.
+ serial-number:
+ type: string
+ description: Serial number of the device
+ ipaddress-v4-loopback-0:
+ type: string
+ description: IPV4 Loopback 0 address
+ ipaddress-v6-loopback-0:
+ type: string
+ description: IPV6 Loopback 0 address
+ ipaddress-v4-aim:
+ type: string
+ description: IPV4 AIM address
+ ipaddress-v6-aim:
+ type: string
+ description: IPV6 AIM address
+ ipaddress-v6-oam:
+ type: string
+ description: IPV6 OAM address
+ inv-status:
+ type: string
+ description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ prov-status:
+ type: string
+ description: Prov Status of this device (not under canopi control) Valid values [PREPROV/NVTPROV/PROV]
+ nf-role:
+ type: string
+ description: Nf Role is the role performed by this instance in the network.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ p-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/p-interface"
+ lag-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/lag-interface"
+ pnfs:
+ description: |
+ Collection of Physical Network Functions.
+ properties:
+ pnf:
+ type: array
+ items:
+ $ref: "#/definitions/pnf"
+ port-group:
+ description: |
+ Used to capture the network interfaces of this VCE
+ ###### Related Nodes
+ - TO vce( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM cvlan-tag( cvlan-tag org.onap.relationships.inventory.BelongsTo port-group, MANY2ONE)
+ - PORT-GROUP is DELETED when these are DELETED CVLAN-TAG
+ required:
+ - interface-id
+ - orchestration-status
+ properties:
interface-id:
type: string
- description: ID of interface
+ description: Unique ID of the interface
+ neutron-network-id:
+ type: string
+ description: Neutron network id of this Interface
+ neutron-network-name:
+ type: string
+ description: Neutron network name of this Interface
interface-role:
type: string
description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
- prov-status:
+ resource-version:
type: string
- description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ port-group-id:
+ type: string
+ description: Unique ID for port group in vmware
+ port-group-name:
+ type: string
+ description: Likely to duplicate value of neutron network name
+ switch-name:
+ type: string
+ description: DVS or standard switch name (should be non-null for port groups associated with DVS)
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ cvlan-tags:
+ type: array
+ items:
+ $ref: "#/definitions/cvlan-tag-entry"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- l-interfaces:
+ port-groups:
+ properties:
+ port-group:
+ type: array
+ items:
+ $ref: "#/definitions/port-group"
+ project:
+ description: |
+ describes the project
+ ###### Related Nodes
+ - TO service-instance( project org.onap.relationships.inventory.Uses service-instance, ONE2MANY)
+ required:
+ - project-name
+ properties:
+ project-name:
+ type: string
+ description: Name of the project deploying a service
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/l-interface"
- lag-interfaces:
+ $ref: "#/definitions/relationship"
+ projects:
description: |
- Collection of link aggregate interfaces.
+ Collection of projects
properties:
- lag-interface:
+ project:
type: array
items:
- $ref: "#/definitions/lag-interface"
+ $ref: "#/definitions/project"
+ properties:
+ description: |
+ Property holder for query properties or instance properties
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ property-constraint:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query-element( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ required:
+ - property-constraint-uuid
+ - constraint-type
+ - property-name
+ - property-value
+ properties:
+ property-constraint-uuid:
+ type: string
+ constraint-type:
+ type: string
+ property-name:
+ type: string
+ property-value:
+ type: string
+ resource-version:
+ type: string
+ property-constraints:
+ properties:
+ property-constraint:
+ type: array
+ items:
+ $ref: "#/definitions/property-constraint"
pserver:
description: |
Compute host whose hostname must be unique and must exactly match what is sent as a relationship to a vserver.
- ###### Default Delete Scope
- ERROR_4_IN_EDGES_OR_CASCADE
- ###### Related Nodes
- - TO complex (Many2One)
- - TO cloud-region (Many2One)
- - TO availability-zone (Many2One)
- - TO lag-interface (comprises pserver, Many2Many)
- - TO p-interface (comprises pserver, Many2Many)
- - TO zone (Many2One)
- - FROM generic-vnf
- - FROM group-assignment
- - FROM vserver
- - FROM logical-link
+ ###### Related Nodes
+ - TO group-assignment( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)
+ - TO availability-zone( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)
+ - TO cloud-region( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)
+ - TO complex( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO zone( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - FROM vserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)
+ - PSERVER cannot be deleted if linked to GENERIC-VNF,LOGICAL-LINK,VSERVER
+ - PSERVER is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
+ - PSERVER cannot be deleted if linked to GROUP-ASSIGNMENT
required:
- hostname
- in-maint
@@ -38433,142 +51080,277 @@ definitions:
type: array
items:
$ref: "#/definitions/pserver"
- virtual-data-center:
+ query-parameters:
description: |
- Virtual organization of cloud infrastructure elements in a data center context
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
+ QueryParameters for performing a named-query or model query
+ properties:
+ named-query:
+ type: object
+ $ref: "#/definitions/named-query"
+ overloaded-model:
+ type: object
+ $ref: "#/definitions/overloaded-model"
+ related-lookup:
+ description: |
+ TBD
###### Related Nodes
- - TO generic-vnf (Many2Many)
- - TO logical-link (Many2Many)
- - FROM connector
+ - TO named-query-element( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
required:
- - vdc-id
- - vdc-name
+ - related-lookup-uuid
+ - source-node-type
+ - source-node-property
+ - target-node-type
+ - target-node-property
properties:
- vdc-id:
+ related-lookup-uuid:
type: string
- description: Unique ID of the vdc
- vdc-name:
+ source-node-type:
+ type: string
+ source-node-property:
+ type: string
+ target-node-type:
+ type: string
+ target-node-property:
+ type: string
+ property-collect-list:
type: string
- description: Name of the virtual data center
resource-version:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- virtual-data-centers:
- description: |
- Virtual organization of cloud infrastructure elements in a data center context
+ related-lookups:
properties:
- virtual-data-center:
+ related-lookup:
type: array
items:
- $ref: "#/definitions/virtual-data-center"
- cloud-infrastructure:
- description: |
- Namespace for cloud infrastructure.
+ $ref: "#/definitions/related-lookup"
+ related-to-property:
properties:
- complexes:
- type: array
- items:
- $ref: "#/definitions/complex"
- cloud-regions:
- type: array
- items:
- $ref: "#/definitions/cloud-region"
- network-profiles:
- type: array
- items:
- $ref: "#/definitions/network-profile"
- pservers:
+ property-key:
+ type: string
+ description: Key part of a key/value pair
+ property-value:
+ type: string
+ description: Value part of a key/value pair
+ relationship:
+ properties:
+ related-to:
+ type: string
+ description: A keyword provided by A&AI to indicate type of node.
+ related-link:
+ type: string
+ description: URL to the object in A&AI.
+ relationship-data:
type: array
- items:
- $ref: "#/definitions/pserver"
- virtual-data-centers:
+ items:
+ $ref: "#/definitions/relationship-data"
+ relationship-data:
+ required:
+ - relationship-key
+ - relationship-value
+ properties:
+ relationship-key:
+ type: string
+ description: A keyword provided by A&AI to indicate an attribute.
+ relationship-value:
+ type: string
+ description: Value of the attribute.
+ relationship-list:
+ properties:
+ relationship:
type: array
- items:
- $ref: "#/definitions/virtual-data-center"
- connector:
+ items:
+ $ref: "#/definitions/relationship"
+ reserved-prop-names:
description: |
- Collection of resource instances used to connect a variety of disparate inventory widgets
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
- ###### Related Nodes
- - TO virtual-data-center (Many2Many)
- - TO metadatum (comprises connector, Many2Many)
- - FROM service-instance
- required:
- - resource-instance-id
+ Internal map to define some reserved properties of a vertex
properties:
- resource-instance-id:
+ last-mod-source-of-truth:
type: string
- description: Unique id of resource instance.
- resource-version:
+ aai-node-type:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- persona-model-id:
+ aai-created-ts:
+ type: integer
+ format: int64
+ aai-unique-key:
type: string
- description: the ASDC model id for this resource or service model.
- persona-model-version:
+ aai-last-mod-ts:
+ type: integer
+ format: int64
+ source-of-truth:
type: string
- description: the ASDC model version for this resource or service model.
- model-version-id:
+ aai-uri:
type: string
- description: the ASDC model version for this resource or service model.
- widget-model-id:
+ response-list:
+ description: |
+ Response container for the results of a named-query or model query
+ properties:
+ inventory-response-items:
+ type: object
+ $ref: "#/definitions/inventory-response-items"
+ result-data:
+ properties:
+ resource-type:
type: string
- description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
- widget-model-version:
+ description: The specific type of node in the A&AI graph
+ resource-link:
type: string
- description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ description: The URL to the specific resource
+ route-table-reference:
+ description: |
+ Openstack route table reference.
+ ###### Related Nodes
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)
+ required:
+ - route-table-reference-id
+ - route-table-reference-fqdn
+ properties:
+ route-table-reference-id:
+ type: string
+ description: Route Table Reference id, UUID assigned to this instance.
+ route-table-reference-fqdn:
+ type: string
+ description: FQDN entry in the route table.
+ resource-version:
+ type: string
+ description: Concurrency value
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- metadata:
+ route-table-references:
+ description: |
+ Collection of openstack route table references
+ properties:
+ route-table-reference:
+ type: array
+ items:
+ $ref: "#/definitions/route-table-reference"
+ route-target:
+ description: |
+ Route target information
+ ###### Related Nodes
+ - TO vpn-binding( route-target org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2ONE)
+ required:
+ - global-route-target
+ - route-target-role
+ properties:
+ global-route-target:
+ type: string
+ description: Number used to identify an RT, globally unique in the network
+ route-target-role:
+ type: string
+ description: Role assigned to this route target
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/metadatum"
- connectors:
+ $ref: "#/definitions/relationship"
+ route-targets:
description: |
- Collection of resource instances used to connect a variety of disparate inventory widgets
+ Collection of route target information
properties:
- connector:
+ route-target:
type: array
items:
- $ref: "#/definitions/connector"
- tunnel-xconnect:
+ $ref: "#/definitions/route-target"
+ routing-instance:
description: |
- Represents the specifics of a tunnel cross connect piece of a resource that gets separately allotted
- ###### Default Delete Scope
- THIS_NODE_ONLY
###### Related Nodes
- - FROM allotted-resource (is composed of tunnel-xconnect)
+ - TO site-pair-set( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)
+ - FROM site-pair( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)
+ - ROUTING-INSTANCE is DELETED when these are DELETED SITE-PAIR
required:
- - id
- - bandwidth-up-wan1
- - bandwidth-down-wan1
- - bandwidth-up-wan2
- - bandwidth-down-wan2
+ - routing-instance-id
properties:
- id:
+ routing-instance-id:
type: string
- description: Allotted Resource id UUID assigned to this instance.
- bandwidth-up-wan1:
+ description: Unique id of routing instance
+ rpm-owner:
type: string
- description: The WAN uplink bandwidth for WAN1
- bandwidth-down-wan1:
+ description: rpm owner
+ resource-version:
type: string
- description: The WAN downlink bandwidth for WAN1
- bandwidth-up-wan2:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ site-pairs:
+ type: array
+ items:
+ $ref: "#/definitions/site-pair"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ routing-instances:
+ description: |
+ set of probes related to generic-vnf routing instance
+ properties:
+ routing-instance:
+ type: array
+ items:
+ $ref: "#/definitions/routing-instance"
+ sdn-zone-response:
+ properties:
+ oam-networks:
+ type: object
+ $ref: "#/definitions/oam-networks"
+ az-and-dvs-switches:
+ type: array
+ items:
+ $ref: "#/definitions/az-and-dvs-switches"
+ search:
+ properties:
+ edge-tag-query-result:
+ type: object
+ $ref: "#/definitions/edge-tag-query-result"
+ edge-tag-query-request:
+ type: object
+ $ref: "#/definitions/edge-tag-query-request"
+ search-results:
+ type: object
+ $ref: "#/definitions/search-results"
+ sdn-zone-response:
+ type: object
+ $ref: "#/definitions/sdn-zone-response"
+ search-results:
+ properties:
+ result-data:
+ type: array
+ items:
+ $ref: "#/definitions/result-data"
+ secondary-filt:
+ description: |
+ SecondaryFilt for performing a named-query or model query
+ secondary-filter:
+ properties:
+ property-name:
type: string
- description: The WAN uplink bandwidth for WAN2
- bandwidth-down-wan2:
+ filter-type:
type: string
- description: The WAN downlink bandwidth for WAN2
+ property-value:
+ type: string
+ secondary-filts:
+ description: |
+ SecondaryFilts for performing a named-query or model query
+ properties:
+ secondary-filt:
+ type: array
+ items:
+ $ref: "#/definitions/secondary-filt"
+ segmentation-assignment:
+ description: |
+ Openstack segmentation assignment.
+ ###### Related Nodes
+ - TO l3-network( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ required:
+ - segmentation-id
+ properties:
+ segmentation-id:
+ type: string
+ description: Route Table Reference id, UUID assigned to this instance.
resource-version:
type: string
description: Concurrency value
@@ -38576,92 +51358,118 @@ definitions:
type: array
items:
$ref: "#/definitions/relationship"
- tunnel-xconnects:
+ segmentation-assignments:
description: |
- This object is used to store the specific tunnel cross connect aspects of an allotted resource
+ Collection of openstack segmentation assignments
properties:
- tunnel-xconnect:
+ segmentation-assignment:
type: array
items:
- $ref: "#/definitions/tunnel-xconnect"
- allotted-resource:
+ $ref: "#/definitions/segmentation-assignment"
+ service:
description: |
- Represents a slice or partial piece of a resource that gets separately allotted
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
- ###### Related Nodes
- - TO generic-vnf (Many2Many)
- - TO l3-network (Many2Many)
- - TO instance-group (Many2Many)
- - TO vlan (Many2Many)
- - TO tunnel-xconnect (comprises allotted-resource, One2One)
- - FROM service-instance (is composed of allotted-resource)
- - FROM service-instance
+ Stand-in for service model definitions. Likely to be deprecated in favor of models from ASDC. Does not strictly map to ASDC services.
required:
- - id
+ - service-id
+ - service-description
properties:
- id:
+ service-id:
type: string
- description: Allotted Resource id UUID assigned to this instance.
- description:
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ service-description:
type: string
- description: The descriptive information assigned to this allotted resource instance
- selflink:
+ description: Description of the service
+ service-selflink:
type: string
- description: Link back to more information in the controller
- persona-model-id:
+ description: URL to endpoint where AAI can get more details
+ resource-version:
type: string
- description: the ASDC model id for this resource or service model.
- persona-model-version:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ service-version:
type: string
- description: the ASDC model version for this resource or service model.
- model-version-id:
+ description: service version
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ service-capabilities:
+ description: |
+ Collection of service capabilities.
+ properties:
+ service-capability:
+ type: array
+ items:
+ $ref: "#/definitions/service-capability"
+ service-capability:
+ description: |
+ Early definition of server/resource pairings, likely to be replaced by models. No new use should be made of this.
+ ###### Related Nodes
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - SERVICE-CAPABILITY cannot be deleted if linked to AVAILABILITY-ZONE,OAM-NETWORK
+ required:
+ - service-type
+ - vnf-type
+ properties:
+ service-type:
type: string
- description: the ASDC model version for this resource or service model.
- persona-model-customization-id:
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ vnf-type:
type: string
- description: captures the id of all the configuration used to customize the resource for the service.
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
resource-version:
type: string
- description: Concurrency value
- tunnel-xconnects:
- type: array
- items:
- $ref: "#/definitions/tunnel-xconnect"
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- allotted-resources:
+ service-design-and-creation:
description: |
- This object is used to store slices of services being offered
+ Namespace for objects managed by ASDC
properties:
- allotted-resource:
+ vnf-images:
type: array
- items:
- $ref: "#/definitions/allotted-resource"
+ items:
+ $ref: "#/definitions/vnf-image"
+ services:
+ type: array
+ items:
+ $ref: "#/definitions/service"
+ service-capabilities:
+ type: array
+ items:
+ $ref: "#/definitions/service-capability"
+ models:
+ type: array
+ items:
+ $ref: "#/definitions/model"
+ named-queries:
+ type: array
+ items:
+ $ref: "#/definitions/named-query"
service-instance:
description: |
Instance of a service
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
- ###### Related Nodes
- - TO cvlan-tag (Many2Many)
- - TO pnf (One2Many)
- - TO connector (Many2Many)
- - TO metadatum (comprises service-instance, Many2Many)
- - TO logical-link (Many2Many)
- - TO vlan (One2Many)
- - TO service-instance (One2Many)
- - TO ctag-assignment (One2Many)
- - TO instance-group (Many2Many)
- - TO allotted-resource (comprises service-instance, Many2Many)
- - TO allotted-resource (Many2Many)
- - FROM generic-vnf
- - FROM l3-network
- - FROM service-subscription (is composed of service-instance)
- - FROM vce
- - FROM service-instance
+ ###### Related Nodes
+ - TO generic-vnf( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)
+ - TO l3-network( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)
+ - TO allotted-resource( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY)
+ - TO connector( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)
+ - TO ctag-assignment( service-instance org.onap.relationships.inventory.Uses ctag-assignment, ONE2MANY)
+ - TO cvlan-tag( service-instance org.onap.relationships.inventory.ComposedOf cvlan-tag, MANY2MANY)
+ - TO instance-group( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO logical-link( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - TO pnf( service-instance org.onap.relationships.inventory.ComposedOf pnf, ONE2MANY)
+ - TO service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)
+ - TO vlan( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)
+ - TO service-subscription( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)
+ - TO vce( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)
+ - SERVICE-INSTANCE is DELETED when these are DELETED ALLOTTED-RESOURCE,METADATUM
+ - SERVICE-INSTANCE deletion means associated objects of these types are also DELETED:LOGICAL-LINK
required:
- service-instance-id
properties:
@@ -38739,12 +51547,11 @@ definitions:
service-subscription:
description: |
Object that group service instances.
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
###### Related Nodes
- - TO service-instance (comprises service-subscription, Many2Many)
- - FROM customer (is composed of service-subscription)
- - FROM tenant
+ - TO customer( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)
+ - TO tenant( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)
+ - SERVICE-SUBSCRIPTION is DELETED when these are DELETED SERVICE-INSTANCE
required:
- service-type
properties:
@@ -38773,65 +51580,805 @@ definitions:
type: array
items:
$ref: "#/definitions/service-subscription"
- customer:
+ services:
+ description: |
+ Collection of service model definitions. Likely to be deprecated in favor of models from ASDC.
+ properties:
+ service:
+ type: array
+ items:
+ $ref: "#/definitions/service"
+ site-pair:
description: |
- customer identifiers to provide linkage back to BSS information.
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
###### Related Nodes
- - TO service-subscription (comprises customer, Many2Many)
+ - TO routing-instance( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)
+ - FROM class-of-service( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)
+ - SITE-PAIR is DELETED when these are DELETED CLASS-OF-SERVICE
required:
- - global-customer-id
- - subscriber-name
- - subscriber-type
+ - site-pair-id
properties:
- global-customer-id:
+ site-pair-id:
type: string
- description: Global customer id used across ECOMP to uniquely identify customer.
- subscriber-name:
+ description: unique identifier of probe
+ source-ip:
type: string
- description: Subscriber name, an alternate way to retrieve a customer.
- subscriber-type:
+ description: Prefix address
+ destination-ip:
type: string
- description: Subscriber type, a way to provide VID with only the INFRA customers.
+ description: Prefix address
+ ip-version:
+ type: string
+ description: ip version, v4, v6
+ destination-hostname:
+ type: string
+ description: Hostname of the destination equipment to which SLAs are measured against.
+ destination-equip-type:
+ type: string
+ description: The type of destinatination equipment. Could be Router, etc.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- service-subscriptions:
+ classes-of-service:
type: array
items:
- $ref: "#/definitions/service-subscription"
+ $ref: "#/definitions/class-of-service"
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- customers:
+ site-pair-set:
description: |
- Collection of customer identifiers to provide linkage back to BSS information.
+ Set of instances for probes used to measure service level agreements
+ ###### Related Nodes
+ - TO generic-vnf( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM routing-instance( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)
+ - SITE-PAIR-SET is DELETED when these are DELETED ROUTING-INSTANCE
+ required:
+ - site-pair-set-id
properties:
- customer:
+ site-pair-set-id:
+ type: string
+ description: Unique id of site pair set.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ routing-instances:
+ type: array
+ items:
+ $ref: "#/definitions/routing-instance"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ site-pair-sets:
+ description: |
+ Collection of sets of instances for probes related to generic-vnf
+ properties:
+ site-pair-set:
type: array
items:
- $ref: "#/definitions/customer"
- business:
+ $ref: "#/definitions/site-pair-set"
+ site-pairs:
description: |
- Namespace for business related constructs
+ probe within a set
properties:
- connectors:
+ site-pair:
+ type: array
+ items:
+ $ref: "#/definitions/site-pair"
+ snapshot:
+ description: |
+ Openstack snapshot
+ ###### Related Nodes
+ - TO cloud-region( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)
+ required:
+ - snapshot-id
+ properties:
+ snapshot-id:
+ type: string
+ description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
+ snapshot-name:
+ type: string
+ description: Snapshot name
+ snapshot-architecture:
+ type: string
+ description: Operating system architecture
+ snapshot-os-distro:
+ type: string
+ description: The common name of the operating system distribution in lowercase
+ snapshot-os-version:
+ type: string
+ description: The operating system version as specified by the distributor.
+ application:
+ type: string
+ description: The application that the image instantiates.
+ application-vendor:
+ type: string
+ description: The vendor of the application.
+ application-version:
+ type: string
+ description: The version of the application.
+ snapshot-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ prev-snapshot-id:
+ type: string
+ description: This field contains the UUID of the previous snapshot (if any).
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/connector"
- customers:
+ $ref: "#/definitions/relationship"
+ snapshots:
+ description: |
+ Collection of openstack snapshots
+ properties:
+ snapshot:
+ type: array
+ items:
+ $ref: "#/definitions/snapshot"
+ sriov-pf:
+ description: |
+ SR-IOV Physical Function
+ ###### Related Nodes
+ - TO p-interface( sriov-pf org.onap.relationships.inventory.BelongsTo p-interface, ONE2ONE)
+ - FROM sriov-vf( sriov-vf org.onap.relationships.inventory.Uses sriov-pf, MANY2ONE)
+ required:
+ - pf-pci-id
+ properties:
+ pf-pci-id:
+ type: string
+ description: Identifier for the sriov-pf
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/customer"
+ $ref: "#/definitions/relationship"
+ sriov-pfs:
+ description: |
+ Collection of SR-IOV Physical Functions.
+ properties:
+ sriov-pf:
+ type: array
+ items:
+ $ref: "#/definitions/sriov-pf"
+ sriov-vf:
+ description: |
+ SR-IOV Virtual Function (not to be confused with virtual network function)
+ ###### Related Nodes
+ - TO l-interface( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)
+ required:
+ - pci-id
+ properties:
+ pci-id:
+ type: string
+ description: PCI ID used to identify the sriov-vf
+ vf-vlan-filter:
+ type: string
+ description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM.
+ vf-mac-filter:
+ type: string
+ description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM.
+ vf-vlan-strip:
+ type: boolean
+ description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM.
+ vf-vlan-anti-spoof-check:
+ type: boolean
+ description: This option ensures anti VLAN spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
+ vf-mac-anti-spoof-check:
+ type: boolean
+ description: This option ensures anti MAC spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
+ vf-mirrors:
+ type: string
+ description: This option defines the set of Mirror objects which essentially mirrors the traffic from source to set of collector VNF Ports.
+ vf-broadcast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows all broadcast traffic to reach the VM
+ vf-unknown-multicast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows unknown multicast traffic to reach the VM
+ vf-unknown-unicast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows unknown unicast traffic to reach the VM
+ vf-insert-stag:
+ type: boolean
+ description: This option, if set to true, instructs to insert outer tag after traffic comes out of VM.
+ vf-link-status:
+ type: string
+ description: This option is used to set the link status. Valid values as of 1607 are on, off, and auto.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
+ type: string
+ description: Neutron network id of the interface
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ sriov-vfs:
+ description: |
+ Collection of SR-IOV Virtual Functions.
+ properties:
+ sriov-vf:
+ type: array
+ items:
+ $ref: "#/definitions/sriov-vf"
+ start-node-filter:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ subnet:
+ description: |
+ ###### Related Nodes
+ - TO l3-network( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - SUBNET cannot be deleted if linked to L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST
+ required:
+ - subnet-id
+ - dhcp-enabled
+ properties:
+ subnet-id:
+ type: string
+ description: Subnet ID, should be UUID.
+ subnet-name:
+ type: string
+ description: Name associated with the subnet.
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of this subnet
+ gateway-address:
+ type: string
+ description: gateway ip address
+ network-start-address:
+ type: string
+ description: network start address
+ cidr-mask:
+ type: string
+ description: cidr mask
+ ip-version:
+ type: string
+ description: ip version
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ dhcp-enabled:
+ type: boolean
+ dhcp-start:
+ type: string
+ description: the start address reserved for use by dhcp
+ dhcp-end:
+ type: string
+ description: the last address reserved for use by dhcp
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ subnets:
+ properties:
+ subnet:
+ type: array
+ items:
+ $ref: "#/definitions/subnet"
+ tagged-inventory-item-list:
+ properties:
+ inventory-item:
+ type: array
+ items:
+ $ref: "#/definitions/inventory-item"
+ tenant:
+ description: |
+ Openstack tenant
+ ###### Related Nodes
+ - TO cloud-region( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO group-assignment( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)
+ - TO l3-network( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO volume-group( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - FROM service-subscription( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)
+ - FROM vserver( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)
+ - TENANT cannot be deleted if linked to VSERVER
+ required:
+ - tenant-id
+ - tenant-name
+ properties:
+ tenant-id:
+ type: string
+ description: Unique id relative to the cloud-region.
+ tenant-name:
+ type: string
+ description: Readable name of tenant
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ vservers:
+ type: array
+ items:
+ $ref: "#/definitions/vserver"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ tenants:
+ description: |
+ Collection of openstack tenants.
+ properties:
+ tenant:
+ type: array
+ items:
+ $ref: "#/definitions/tenant"
+ tunnel-xconnect:
+ description: |
+ Represents the specifics of a tunnel cross connect piece of a resource that gets separately allotted
+ ###### Related Nodes
+ - TO allotted-resource( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)
+ required:
+ - id
+ - bandwidth-up-wan1
+ - bandwidth-down-wan1
+ - bandwidth-up-wan2
+ - bandwidth-down-wan2
+ properties:
+ id:
+ type: string
+ description: Allotted Resource id UUID assigned to this instance.
+ bandwidth-up-wan1:
+ type: string
+ description: The WAN uplink bandwidth for WAN1
+ bandwidth-down-wan1:
+ type: string
+ description: The WAN downlink bandwidth for WAN1
+ bandwidth-up-wan2:
+ type: string
+ description: The WAN uplink bandwidth for WAN2
+ bandwidth-down-wan2:
+ type: string
+ description: The WAN downlink bandwidth for WAN2
+ resource-version:
+ type: string
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ tunnel-xconnects:
+ description: |
+ This object is used to store the specific tunnel cross connect aspects of an allotted resource
+ properties:
+ tunnel-xconnect:
+ type: array
+ items:
+ $ref: "#/definitions/tunnel-xconnect"
+ update:
+ description: |
+ Serves a PATCH like function. Does not enforce concurrency control. Clear each usage with AAI team.
+ required:
+ - update-node-type
+ properties:
+ update-node-type:
+ type: string
+ update-node-key:
+ type: array
+ items:
+ $ref: "#/definitions/update-node-key"
+ update-node-uri:
+ type: string
+ action:
+ type: array
+ items:
+ $ref: "#/definitions/action"
+ update-node-key:
+ properties:
+ key-name:
+ type: string
+ key-value:
+ type: string
+ vce:
+ description: |
+ Virtual Customer Edge Router, used specifically for Gamma. This object is deprecated.
+ ###### Related Nodes
+ - TO availability-zone( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - TO complex( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)
+ - TO vserver( vce tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM entitlement( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM license( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM port-group( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)
+ - VCE is DELETED when these are DELETED ENTITLEMENT,LICENSE,PORT-GROUP
+ required:
+ - vnf-id
+ - vnf-name
+ - vnf-type
+ properties:
+ vnf-id:
+ type: string
+ description: Unique id of VNF. This is unique across the graph.
+ vnf-name:
+ type: string
+ description: Name of VNF.
+ vnf-name2:
+ type: string
+ description: Alternate name of VNF.
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ service-id:
+ type: string
+ description: Unique identifier of service, does not strictly map to ASDC services, SOON TO BE DEPRECATED.
+ regional-resource-zone:
+ type: string
+ description: Regional way of organizing pservers, source of truth should define values
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ operational-state:
+ type: string
+ description: Indicator for whether the resource is considered operational
+ license-key:
+ type: string
+ description: OBSOLETE - do not use
+ equipment-role:
+ type: string
+ description: Network role being played by this VNF
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ vpe-id:
+ type: string
+ description: Unique ID of VPE connected to this VCE.
+ v6-vce-wan-address:
+ type: string
+ description: Valid v6 IP address for the WAN Link on this router. Implied length of /64.
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure vce, also used for troubleshooting and is IP used for traps generated by VCE.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ ipv4-loopback0-address:
+ type: string
+ description: Loopback0 address
+ entitlement-resource-uuid:
+ type: string
+ description: OBSOLETE - see child relationships
+ port-groups:
+ type: array
+ items:
+ $ref: "#/definitions/port-group"
+ licenses:
+ type: array
+ items:
+ $ref: "#/definitions/license"
+ entitlements:
+ type: array
+ items:
+ $ref: "#/definitions/entitlement"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ vces:
+ description: |
+ Collection of Virtual Customer Edge Routers, used specifically for Gamma. This object is deprecated.
+ properties:
+ vce:
+ type: array
+ items:
+ $ref: "#/definitions/vce"
+ vf-module:
+ description: |
+ a deployment unit of VNFCs
+ ###### Related Nodes
+ - TO generic-vnf( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO l3-network( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)
+ - TO vnfc( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)
+ - TO volume-group( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)
+ - TO vserver( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)
+ - VF-MODULE cannot be deleted if linked to VNFC
+ required:
+ - vf-module-id
+ - is-base-vf-module
+ properties:
+ vf-module-id:
+ type: string
+ description: Unique ID of vf-module.
+ vf-module-name:
+ type: string
+ description: Name of vf-module
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance.
+ orchestration-status:
+ type: string
+ description: orchestration status of this vf-module, mastered by MSO
+ is-base-vf-module:
+ type: boolean
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ persona-model-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ persona-model-customization-id:
+ type: string
+ description: captures the id of all the configuration used to customize the resource for the service.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ contrail-service-instance-fqdn:
+ type: string
+ description: the Contrail unique ID for a service-instance
+ module-index:
+ type: integer
+ format: int32
+ description: the index will track the number of modules of a given type that have been deployed in a VNF, starting with 0, and always choosing the lowest available digit
+ selflink:
+ type: string
+ description: Path to the controller object.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ vf-modules:
+ description: |
+ Collection of vf-modules, a deployment unit of VNFCs
+ properties:
+ vf-module:
+ type: array
+ items:
+ $ref: "#/definitions/vf-module"
+ vig-server:
+ description: |
+ vig-server contains information about a vig server used for IPSec-configuration. Populated by SDN-C from 1607
+ ###### Related Nodes
+ - TO ipsec-configuration( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)
+ required:
+ - vig-address-type
+ properties:
+ vig-address-type:
+ type: string
+ description: indicates whether the VIG is for AVPN or INTERNET
+ ipaddress-v4-vig:
+ type: string
+ description: v4 IP of the vig server
+ ipaddress-v6-vig:
+ type: string
+ description: v6 IP of the vig server
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ vig-servers:
+ properties:
+ vig-server:
+ type: array
+ items:
+ $ref: "#/definitions/vig-server"
+ vip-ipv4-address-list:
+ description: |
+ IPv4 Address Range
+ ###### Related Nodes
+ - TO cloud-region( vip-ipv4-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO instance-group( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO subnet( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv4-address-list, MANY2MANY)
+ required:
+ - vip-ipv4-address
+ properties:
+ vip-ipv4-address:
+ type: string
+ description: IP address
+ vip-ipv4-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 32 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
+ type: string
+ description: Neutron network id of the interface that address belongs to
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of subnet that address belongs to
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ vip-ipv6-address-list:
+ description: |
+ IPv6 Address Range
+ ###### Related Nodes
+ - TO cloud-region( vip-ipv6-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO instance-group( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO subnet( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv6-address-list, MANY2MANY)
+ required:
+ - vip-ipv6-address
+ properties:
+ vip-ipv6-address:
+ type: string
+ description: IP address
+ vip-ipv6-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 128 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
+ type: string
+ description: Neutron network id of the interface that address belongs to
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of subnet that address belongs to
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ virtual-data-center:
+ description: |
+ Virtual organization of cloud infrastructure elements in a data center context
+ ###### Related Nodes
+ - FROM connector( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ required:
+ - vdc-id
+ - vdc-name
+ properties:
+ vdc-id:
+ type: string
+ description: Unique ID of the vdc
+ vdc-name:
+ type: string
+ description: Name of the virtual data center
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ virtual-data-centers:
+ description: |
+ Virtual organization of cloud infrastructure elements in a data center context
+ properties:
+ virtual-data-center:
+ type: array
+ items:
+ $ref: "#/definitions/virtual-data-center"
+ vlan:
+ description: |
+ Definition of vlan
+ ###### Related Nodes
+ - TO l-interface( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)
+ - TO logical-link( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - TO multicast-configuration( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ - VLAN is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST
+ - VLAN deletion means associated objects of these types are also DELETED:LOGICAL-LINK
+ required:
+ - vlan-interface
+ properties:
+ vlan-interface:
+ type: string
+ description: String that identifies the interface
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ vlan-description:
+ type: string
+ description: Used to describe (the service associated with) the vlan
+ backdoor-connection:
+ type: string
+ description: Whether customer is going to use this VLAN for backdoor connection to another customer premise device.
+ vpn-id:
+ type: string
+ description: This indicates the customers VPN ID associated with this vlan
+ orchestration-status:
+ type: string
+ description: Status of a vnf's vlan interface, on which the customer circuit resides, mastered by SDN-C.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ l3-interface-ipv4-address-list:
+ type: array
+ items:
+ $ref: "#/definitions/l3-interface-ipv4-address-list"
+ l3-interface-ipv6-address-list:
+ type: array
+ items:
+ $ref: "#/definitions/l3-interface-ipv6-address-list"
+ vlans:
+ properties:
+ vlan:
+ type: array
+ items:
+ $ref: "#/definitions/vlan"
+ vnf:
+ description: |
+ Abstract vnf class
+ required:
+ - vnf-id
+ properties:
+ vnf-id:
+ type: string
+ description: Unique id of VNF. This is unique across the graph.
vnf-image:
description: |
Image object that pertain to a VNF that doesn't have associated vservers. This is a kludge.
- ###### Default Delete Scope
- ERROR_IF_ANY_IN_EDGES
###### Related Nodes
- - FROM generic-vnf
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)
+ - VNF-IMAGE cannot be deleted if linked to GENERIC-VNF
required:
- vnf-image-uuid
- application
@@ -38867,60 +52414,116 @@ definitions:
type: array
items:
$ref: "#/definitions/vnf-image"
- service:
+ vnfc:
description: |
- Stand-in for service model definitions. Likely to be deprecated in favor of models from ASDC. Does not strictly map to ASDC services.
- ###### Default Delete Scope
- ERROR_IF_ANY_IN_EDGES
+ ###### Related Nodes
+ - TO generic-vnf( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vserver( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)
required:
- - service-id
- - service-description
+ - vnfc-name
+ - vnfc-function-code
+ - vnfc-type
+ - in-maint
+ - is-closed-loop-disabled
properties:
- service-id:
+ vnfc-name:
type: string
- description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
- service-description:
+ description: Unique ID of vnfc.
+ vnfc-function-code:
type: string
- description: Description of the service
- service-selflink:
+ description: function code
+ vnfc-type:
type: string
- description: URL to endpoint where AAI can get more details
+ description: type
+ prov-status:
+ type: string
+ description: prov status of this vnfc
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by APP-C
+ ipaddress-v4-oam-vip:
+ type: string
+ description: Oam V4 vip address of this vnfc
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
+ group-notation:
+ type: string
+ description: Group notation of VNFC
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- service-version:
- type: string
- description: service version
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- services:
+ vnfcs:
description: |
- Collection of service model definitions. Likely to be deprecated in favor of models from ASDC.
+ virtual network components associated with a vserver from application controller.
properties:
- service:
+ vnfc:
type: array
items:
- $ref: "#/definitions/service"
- service-capability:
+ $ref: "#/definitions/vnfc"
+ volume:
description: |
- Early definition of server/resource pairings, likely to be replaced by models. No new use should be made of this.
- ###### Default Delete Scope
- ERROR_IF_ANY_IN_EDGES
+ Ephemeral Block storage volume.
###### Related Nodes
- - FROM availability-zone
- - FROM oam-network
+ - FROM vserver (PARENT of volume, vserver tosca.relationships.AttachesTo volume)
required:
- - service-type
+ - volume-id
+ - volume-selflink
+ properties:
+ volume-id:
+ type: string
+ description: Unique ID of block storage volume relative to the vserver.
+ volume-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ volume-group:
+ description: |
+ Persistent block-level storage.
+ ###### Related Nodes
+ - TO cloud-region( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO complex( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ required:
+ - volume-group-id
+ - volume-group-name
- vnf-type
properties:
- service-type:
+ volume-group-id:
type: string
- description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ description: Unique ID of volume-group.
+ volume-group-name:
+ type: string
+ description: Name of the volume group.
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this volume-group
vnf-type:
type: string
description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ orchestration-status:
+ type: string
+ description: Orchestration status of this volume-group
+ persona-model-customization-id:
+ type: string
+ description: captures the id of all the configuration used to customize the resource for the service.
+ vf-module-persona-model-customization-id:
+ type: string
+ description: helps relate the volume group to the vf-module whose components will require the volume group
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
@@ -38928,57 +52531,598 @@ definitions:
type: array
items:
$ref: "#/definitions/relationship"
- service-capabilities:
+ volume-groups:
description: |
- Collection of service capabilities.
+ Collection of persistent block-level storage.
properties:
- service-capability:
+ volume-group:
type: array
items:
- $ref: "#/definitions/service-capability"
- element-choice-set:
+ $ref: "#/definitions/volume-group"
+ volumes:
description: |
- This is how we would capture constraints defining allowed sets of elements.
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
+ Collection of ephemeral Block storage volumes.
+ properties:
+ volume:
+ type: array
+ items:
+ $ref: "#/definitions/volume"
+ vpls-pe:
+ description: |
+ VPLS Provider Edge routers.
###### Related Nodes
- - TO model-element (comprises element-choice-set, One2Many)
- - FROM constrained-element-set (is composed of element-choice-set)
+ - TO complex( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO ctag-pool( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - VPLS-PE is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
required:
- - element-choice-set-uuid
- - element-choice-set-name
+ - equipment-name
properties:
- element-choice-set-uuid:
+ equipment-name:
type: string
- element-choice-set-name:
+ prov-status:
type: string
- cardinality:
+ description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by VPE (v4-loopback0-ip-address).
+ equipment-role:
type: string
+ description: Client should send valid enumerated value, e.g., VPLS-PE.
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Temporary location for stag to get to VCE
resource-version:
type: string
- model-elements:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/model-element"
+ $ref: "#/definitions/relationship"
+ p-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/p-interface"
+ lag-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/lag-interface"
+ vpls-pes:
+ description: |
+ Collection of VPLS Provider Edge routers
+ properties:
+ vpls-pe:
+ type: array
+ items:
+ $ref: "#/definitions/vpls-pe"
+ vpn-binding:
+ description: |
+ VPN binding
+ ###### Related Nodes
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - VPN-BINDING cannot be deleted if linked to L3-NETWORK,LOGICAL-LINK
+ required:
+ - vpn-id
+ - vpn-name
+ - global-route-target
+ - route-target-role
+ properties:
+ vpn-id:
+ type: string
+ description: VPN ID, globally unique within A&AI
+ vpn-name:
+ type: string
+ description: VPN Name
+ global-route-target:
+ type: string
+ description: Number used to identify a VPN, globally unique in the network
+ vpn-platform:
+ type: string
+ description: the platform associated with the VPN example AVPN, Mobility
+ vpn-type:
+ type: string
+ description: Type of the vpn, should be taken from enumerated/valid values
+ route-distinguisher:
+ type: string
+ description: Used to distinguish the distinct VPN routes of separate customers who connect to the provider in an MPLS network.
+ route-target-role:
+ type: string
+ description: Role assigned to this route target
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
$ref: "#/definitions/relationship"
- element-choice-sets:
+ description: l3-networks relate to vpn-bindings
+ vpn-bindings:
properties:
- element-choice-set:
+ vpn-binding:
type: array
items:
- $ref: "#/definitions/element-choice-set"
+ $ref: "#/definitions/vpn-binding"
+ vserver:
+ description: |
+ Virtual Servers, aka virtual machine or VM.
+ ###### Related Nodes
+ - TO tenant( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)
+ - TO flavor( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)
+ - TO image( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)
+ - TO pserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)
+ - TO snapshot( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)
+ - TO volume (CHILD of vserver, vserver tosca.relationships.AttachesTo volume, ONE2MANY)
+ - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM vce( vce tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)
+ - FROM vnfc( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)
+ - VSERVER is DELETED when these are DELETED L-INTERFACE
+ - VSERVER deletion means associated objects of these types are also DELETED:VOLUME
+ required:
+ - vserver-id
+ - vserver-name
+ - vserver-selflink
+ - in-maint
+ - is-closed-loop-disabled
+ properties:
+ vserver-id:
+ type: string
+ description: Unique identifier for this vserver relative to its tenant
+ vserver-name:
+ type: string
+ description: Name of vserver
+ vserver-name2:
+ type: string
+ description: Alternative name of vserver
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ vserver-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ volumes:
+ type: array
+ items:
+ $ref: "#/definitions/volume"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/definitions/l-interface"
+ vservers:
+ description: |
+ Collection of virtual Servers, aka virtual machines or VMs.
+ properties:
+ vserver:
+ type: array
+ items:
+ $ref: "#/definitions/vserver"
+ zone:
+ description: |
+ A zone is a grouping of assets in a location homing to the same connections into the CBB
+ ###### Related Nodes
+ - TO complex( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM pnf( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ required:
+ - zone-id
+ - zone-name
+ - design-type
+ - zone-context
+ properties:
+ zone-id:
+ type: string
+ description: Code assigned by AIC to the zone
+ zone-name:
+ type: string
+ description: English name associated with the zone
+ design-type:
+ type: string
+ description: Design of zone [Medium/Large?]
+ zone-context:
+ type: string
+ description: Context of zone [production/test]
+ status:
+ type: string
+ description: Status of a zone.
+ resource-version:
+ type: string
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/definitions/relationship"
+ zones:
+ description: |
+ Collection of zones
+ properties:
+ zone:
+ type: array
+ items:
+ $ref: "#/definitions/zone"
+patchDefinitions:
+ aai-internal:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ action:
+ properties:
+ action-type:
+ type: string
+ action-data:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/action-data"
+ action-data:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ actions:
+ description: |
+ APIs that are more action related than REST (e.g., notify, update).
+ properties:
+ update:
+ type: object
+ $ref: "#/patchDefinitions/update"
+ notify:
+ type: object
+ $ref: "#/patchDefinitions/notify"
+ allotted-resource:
+ description: |
+ Represents a slice or partial piece of a resource that gets separately allotted
+ ###### Related Nodes
+ - TO generic-vnf( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY)
+ - TO instance-group( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO l3-network( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY)
+ - TO vlan( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY)
+ - TO service-instance( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM tunnel-xconnect( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY)
+ - ALLOTTED-RESOURCE is DELETED when these are DELETED TUNNEL-XCONNECT
+ required:
+ - id
+ properties:
+ id:
+ type: string
+ description: Allotted Resource id UUID assigned to this instance.
+ description:
+ type: string
+ description: The descriptive information assigned to this allotted resource instance
+ selflink:
+ type: string
+ description: Link back to more information in the controller
+ persona-model-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ persona-model-customization-id:
+ type: string
+ description: captures the id of all the configuration used to customize the resource for the service.
+ allotted-resources:
+ description: |
+ This object is used to store slices of services being offered
+ properties:
+ allotted-resource:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/allotted-resource"
+ availability-zone:
+ description: |
+ Availability zone, a collection of compute hosts/pservers
+ ###### Related Nodes
+ - TO complex( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO service-capability( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - TO cloud-region( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM ctag-pool( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM dvs-switch( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - FROM pserver( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)
+ - FROM vce( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - AVAILABILITY-ZONE cannot be deleted if linked to CTAG-POOL,DVS-SWITCH,GENERIC-VNF,PSERVER,VCE
+ required:
+ - availability-zone-name
+ - hypervisor-type
+ properties:
+ availability-zone-name:
+ type: string
+ description: Name of the availability zone. Unique across a cloud region
+ hypervisor-type:
+ type: string
+ description: Type of hypervisor. Source of truth should define valid values.
+ operational-state:
+ type: string
+ description: State that indicates whether the availability zone should be used, etc. Source of truth should define valid values.
+ availability-zones:
+ description: |
+ Collection of availability zones
+ properties:
+ availability-zone:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/availability-zone"
+ az-and-dvs-switches:
+ properties:
+ dvs-switches:
+ type: object
+ $ref: "#/patchDefinitions/dvs-switches"
+ availability-zone:
+ type: object
+ $ref: "#/patchDefinitions/availability-zone"
+ business:
+ description: |
+ Namespace for business related constructs
+ properties:
+ connectors:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/connector"
+ customers:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/customer"
+ class-of-service:
+ description: |
+ ###### Related Nodes
+ - TO site-pair( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)
+ required:
+ - cos
+ properties:
+ cos:
+ type: string
+ description: unique identifier of probe
+ probe-id:
+ type: string
+ description: identifier of probe
+ probe-type:
+ type: string
+ description: type of probe
+ classes-of-service:
+ description: |
+ class-of-service of probe
+ properties:
+ class-of-service:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/class-of-service"
+ cloud-infrastructure:
+ description: |
+ Namespace for cloud infrastructure.
+ properties:
+ complexes:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/complex"
+ cloud-regions:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/cloud-region"
+ network-profiles:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/network-profile"
+ pservers:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/pserver"
+ virtual-data-centers:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/virtual-data-center"
+ cloud-region:
+ description: |
+ cloud-region designates an installation of a cloud cluster or region or instantiation.
+ ###### Related Nodes
+ - TO complex( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO l3-network( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO zone( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM dvs-switch( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM flavor( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM group-assignment( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM image( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM snapshot( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM volume-group( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn cloud-region, MANY2MANY)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)
+ - CLOUD-REGION cannot be deleted if linked to DVS-SWITCH,FLAVOR,GROUP-ASSIGNMENT,IMAGE,OAM-NETWORK,SNAPSHOT,TENANT,VOLUME-GROUP
+ - CLOUD-REGION is DELETED when these are DELETED AVAILABILITY-ZONE
+ required:
+ - cloud-owner
+ - cloud-region-id
+ properties:
+ cloud-owner:
+ type: string
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ cloud-region-id:
+ type: string
+ description: Identifier used by the vendor for the region. Second part of composite key
+ cloud-type:
+ type: string
+ description: Type of the cloud (e.g., openstack)
+ owner-defined-type:
+ type: string
+ description: Cloud-owner defined type indicator (e.g., dcp, lcp)
+ cloud-region-version:
+ type: string
+ description: Software version employed at the site. NOTE - THIS FIELD IS NOT KEPT UP TO DATE.
+ identity-url:
+ type: string
+ description: URL of the keystone identity service
+ cloud-zone:
+ type: string
+ description: Zone where the cloud is homed. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
+ complex-name:
+ type: string
+ description: complex name for cloud-region instance. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
+ cloud-regions:
+ properties:
+ cloud-region:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/cloud-region"
+ complex:
+ description: |
+ Collection of physical locations that can house cloud-regions.
+ ###### Related Nodes
+ - TO l3-network( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM ctag-pool( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)
+ - FROM pnf( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM vce( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)
+ - FROM volume-group( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM vpls-pe( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM zone( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - COMPLEX cannot be deleted if linked to AVAILABILITY-ZONE,CLOUD-REGION,OAM-NETWORK,PNF,PSERVER,VCE,VOLUME-GROUP,VPLS-PE,ZONE
+ - COMPLEX is DELETED when these are DELETED CTAG-POOL
+ required:
+ - physical-location-id
+ - physical-location-type
+ - street1
+ - city
+ - postal-code
+ - country
+ - region
+ properties:
+ physical-location-id:
+ type: string
+ description: Unique identifier for physical location, e.g., CLLI
+ data-center-code:
+ type: string
+ description: Data center code which can be an alternate way to identify a complex
+ complex-name:
+ type: string
+ description: Gamma complex name for LCP instance.
+ identity-url:
+ type: string
+ description: URL of the keystone identity service
+ complexes:
+ description: |
+ Collection of physical locations that can house cloud-regions.
+ properties:
+ complex:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/complex"
+ configuration:
+ description: |
+ Port Mirror Configuration.
+ ###### Related Nodes
+ - TO allotted-resource( configuration org.onap.relationships.inventory.Uses allotted-resource, ONE2ONE)
+ - TO logical-link( configuration org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo configuration, MANY2ONE)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses configuration, ONE2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses configuration, ONE2MANY)
+ - CONFIGURATION is DELETED when these are DELETED METADATUM
+ - CONFIGURATION deletion means associated objects of these types are also DELETED:ALLOTTED-RESOURCE,LOGICAL-LINK
+ required:
+ - configuration-id
+ - configuration-type
+ - configuration-sub-type
+ - orchestration-status
+ - operational-status
+ - configuration-selflink
+ - model-customization-id
+ properties:
+ configuration-id:
+ type: string
+ description: UUID assigned to configuration.
+ management-option:
+ type: string
+ description: Indicates the entity that will manage this feature. Could be an organization or the name of the application as well.
+ configuration-name:
+ type: string
+ description: Name of the configuration.
+ configuration-type:
+ type: string
+ description: port-mirroring-configuration.
+ configuration-sub-type:
+ type: string
+ description: vprobe, pprobe.
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ orchestration-status:
+ type: string
+ description: Orchestration status of the configuration.
+ operational-status:
+ type: string
+ description: Indicator for whether the resource is considered operational.
+ configuration-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details from SDN-GC.
+ model-customization-id:
+ type: string
+ description: id of the configuration used to customize the resource
+ configurations:
+ description: |
+ Collection of configurations
+ properties:
+ configuration:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/configuration"
+ connector:
+ description: |
+ Collection of resource instances used to connect a variety of disparate inventory widgets
+ ###### Related Nodes
+ - TO virtual-data-center( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)
+ - CONNECTOR is DELETED when these are DELETED METADATUM
+ required:
+ - resource-instance-id
+ properties:
+ resource-instance-id:
+ type: string
+ description: Unique id of resource instance.
+ connectors:
+ description: |
+ Collection of resource instances used to connect a variety of disparate inventory widgets
+ properties:
+ connector:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/connector"
constrained-element-set:
description: |
This is how we would capture constraints defining allowed sets of elements.
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
###### Related Nodes
- - TO element-choice-set (comprises constrained-element-set, One2Many)
- - FROM model-element (is composed of constrained-element-set)
- - FROM model-constraint (is composed of constrained-element-set)
+ - TO model-constraint( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)
+ - TO model-element( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM element-choice-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)
+ - CONSTRAINED-ELEMENT-SET is DELETED when these are DELETED ELEMENT-CHOICE-SET
required:
- constrained-element-set-uuid
- constraint-type
@@ -38990,30 +53134,1388 @@ definitions:
type: string
check-type:
type: string
- resource-version:
+ constrained-element-sets:
+ properties:
+ constrained-element-set:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/constrained-element-set"
+ ctag-assignment:
+ description: |
+ ###### Related Nodes
+ - TO l3-network( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses ctag-assignment, ONE2MANY)
+ required:
+ - vlan-id-inner
+ properties:
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: id.
+ ctag-assignments:
+ properties:
+ ctag-assignment:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/ctag-assignment"
+ ctag-pool:
+ description: |
+ A collection of C tags (vlan tags) grouped for a specific purpose.
+ ###### Related Nodes
+ - TO complex( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)
+ - TO availability-zone( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM vpls-pe( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)
+ required:
+ - target-pe
+ - availability-zone-name
+ - ctag-pool-purpose
+ properties:
+ target-pe:
type: string
- element-choice-sets:
+ description: The Target provider edge router
+ availability-zone-name:
+ type: string
+ description: Name of the availability zone
+ ctag-pool-purpose:
+ type: string
+ description: Describes what the intended purpose of this pool is.
+ ctag-values:
+ type: string
+ description: Comma separated list of ctags
+ ctag-pools:
+ properties:
+ ctag-pool:
type: array
- items:
- $ref: "#/definitions/element-choice-set"
- relationship-list:
+ items:
+ $ref: "#/patchDefinitions/ctag-pool"
+ customer:
+ description: |
+ customer identifiers to provide linkage back to BSS information.
+ ###### Related Nodes
+ - FROM service-subscription( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)
+ - CUSTOMER is DELETED when these are DELETED SERVICE-SUBSCRIPTION
+ required:
+ - global-customer-id
+ - subscriber-name
+ - subscriber-type
+ properties:
+ global-customer-id:
+ type: string
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ subscriber-name:
+ type: string
+ description: Subscriber name, an alternate way to retrieve a customer.
+ subscriber-type:
+ type: string
+ description: Subscriber type, a way to provide VID with only the INFRA customers.
+ customers:
+ description: |
+ Collection of customer identifiers to provide linkage back to BSS information.
+ properties:
+ customer:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/customer"
+ cvlan-tag-entry:
+ required:
+ - cvlan-tag
+ properties:
+ cvlan-tag:
+ type: integer
+ format: int64
+ description: See mis-na-virtualization-platform.yang
+ cvlan-tags:
+ properties:
+ cvlan-tag-entry:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/cvlan-tag-entry"
+ dvs-switch:
+ description: |
+ Digital virtual switch metadata, used by SDN-C to configure VCEs. A&AI needs to receive this data from the PO deployment team and administer it using the provisioningTool.sh into A&AI.
+ ###### Related Nodes
+ - TO cloud-region( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO availability-zone( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ required:
+ - switch-name
+ - vcenter-url
+ properties:
+ switch-name:
+ type: string
+ description: DVS switch name
+ vcenter-url:
+ type: string
+ description: URL used to reach the vcenter
+ dvs-switches:
+ description: |
+ Collection of digital virtual switch metadata used for vmWare VCEs and GenericVnfs.
+ properties:
+ dvs-switch:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/dvs-switch"
+ edge-prop-names:
+ description: |
+ Internal map to define the properties of an edge and interpret the map EdgeRules
+ properties:
+ edgeLabel:
+ type: string
+ direction:
+ type: string
+ multiplicityRule:
+ type: string
+ isParent:
+ type: boolean
+ usesResource:
+ type: boolean
+ hasDelTarget:
+ type: boolean
+ SVC-INFRA:
+ type: boolean
+ SVC-INFRA-REV:
+ type: boolean
+ edge-tag-query-request:
+ properties:
+ edge-tag:
+ type: string
+ result-detail:
+ type: string
+ start-node-type:
+ type: string
+ start-node-filter:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/start-node-filter"
+ include-node-filter:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/include-node-filter"
+ secondary-filter:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/secondary-filter"
+ edge-tag-query-result:
+ properties:
+ tagged-inventory-item-list:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/tagged-inventory-item-list"
+ element-choice-set:
+ description: |
+ This is how we would capture constraints defining allowed sets of elements.
+ ###### Related Nodes
+ - TO constrained-element-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)
+ - ELEMENT-CHOICE-SET is DELETED when these are DELETED MODEL-ELEMENT
+ required:
+ - element-choice-set-uuid
+ - element-choice-set-name
+ properties:
+ element-choice-set-uuid:
+ type: string
+ element-choice-set-name:
+ type: string
+ cardinality:
+ type: string
+ element-choice-sets:
+ properties:
+ element-choice-set:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/element-choice-set"
+ entitlement:
+ description: |
+ Metadata for entitlement group.
+ ###### Related Nodes
+ - TO generic-vnf( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vce( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ required:
+ - group-uuid
+ - resource-uuid
+ properties:
+ group-uuid:
+ type: string
+ description: Unique ID for the entitlement group the resource comes from, should be uuid.
+ resource-uuid:
+ type: string
+ description: Unique ID of an entitlement resource.
+ entitlements:
+ description: |
+ Entitlements, keyed by group-uuid and resource-uuid, related to license management
+ properties:
+ entitlement:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/entitlement"
+ esr-ems:
+ description: |
+ Persist EMS address information used by EMS driver.
+ ###### Related Nodes
+ - TO esr-system-info (CHILD of esr-ems, esr-ems has esr-system-info, One2Many)
+ - ESR-EMS deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
+ required:
+ - ems-id
+ properties:
+ ems-id:
+ type: string
+ description: Unique ID of EMS.
+ esr-ems-list:
+ properties:
+ esr-ems:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/esr-ems"
+ esr-system-info:
+ description: |
+ Persist common address information of external systems.
+ ###### Related Nodes
+ - FROM esr-ems (PARENT of esr-system-info, esr-ems has esr-system-info)
+ - FROM esr-vnfm (PARENT of esr-system-info, esr-vnfm has esr-system-info)
+ - FROM esr-thirdparty-sdnc (PARENT of esr-system-info, esr-thirdparty-sdnc has esr-system-info)
+ - FROM cloud-region (PARENT of esr-system-info, cloud-region has esr-system-info)
+ required:
+ - esr-system-info-id
+ - user-name
+ - password
+ - system-type
+ properties:
+ esr-system-info-id:
+ type: string
+ description: Unique ID of esr system info.
+ system-name:
+ type: string
+ description: name of external system.
+ type:
+ type: string
+ description: type of external systems.
+ vendor:
+ type: string
+ description: vendor of external systems.
+ version:
+ type: string
+ description: version of external systems.
+ service-url:
+ type: string
+ description: url used to access external systems.
+ user-name:
+ type: string
+ description: username used to access external systems.
+ password:
+ type: string
+ description: password used to access external systems.
+ system-type:
+ type: string
+ description: it could be vim/vnfm/thirdparty-sdnc/ems-resource/ems-performance/ems-alarm.
+ protocol:
+ type: string
+ description: protocol of third party SDNC, for example netconf/snmp.
+ ssl-cacert:
+ type: string
+ description: ca file content if enabled ssl on auth-url.
+ ssl-insecure:
+ type: boolean
+ description: Whether to verify VIM's certificate.
+ ip-address:
+ type: string
+ description: service IP of ftp server.
+ port:
+ type: string
+ description: service port of ftp server.
+ cloud-domain:
+ type: string
+ description: domain info for authentication.
+ default-tenant:
+ type: string
+ description: default tenant of VIM.
+ passive:
+ type: boolean
+ description: ftp passive mode or not.
+ remote-path:
+ type: string
+ description: resource or performance data file path.
+ system-status:
+ type: string
+ description: the status of external system.
+ esr-system-info-list:
+ description: |
+ Collection of persistent block-level external system auth info.
+ properties:
+ esr-system-info:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/esr-system-info"
+ esr-thirdparty-sdnc:
+ description: |
+ Persist SDNC address information used by ONAP SDNC.
+ ###### Related Nodes
+ - TO esr-system-info (CHILD of esr-thirdparty-sdnc, esr-thirdparty-sdnc has esr-system-info, One2One)
+ - TO pnf( esr-thirdparty-sdnc has pnf, One2Many)
+ - ESR-THIRDPARTY-SDNC deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
+ required:
+ - thirdparty-sdnc-id
+ properties:
+ thirdparty-sdnc-id:
+ type: string
+ description: Unique ID of SDNC.
+ location:
+ type: string
+ description: used for DC type to indicate the location of SDNC, such as Core or Edge.
+ product-name:
+ type: string
+ description: password used to access SDNC server.
+ esr-thirdparty-sdnc-list:
+ properties:
+ esr-thirdparty-sdnc:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/esr-thirdparty-sdnc"
+ esr-vnfm:
+ description: |
+ Persist VNFM address information used by VF-C.
+ ###### Related Nodes
+ - TO esr-system-info (CHILD of esr-vnfm, esr-vnfm has esr-system-info, One2One)
+ - ESR-VNFM deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
+ required:
+ - vnfm-id
+ properties:
+ vnfm-id:
+ type: string
+ description: Unique ID of VNFM.
+ vim-id:
+ type: string
+ description: indecate the VIM to deploy VNF.
+ certificate-url:
+ type: string
+ description: certificate url of VNFM.
+ esr-vnfm-list:
+ properties:
+ esr-vnfm:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/esr-vnfm"
+ evc:
+ description: |
+ evc object is an optional child object of the Configuration object.
+ ###### Related Nodes
+ - TO configuration( evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)
+ required:
+ - evc-id
+ properties:
+ evc-id:
+ type: string
+ description: Unique/key field for the evc object
+ forwarding-path-topology:
+ type: string
+ description: Point-to-Point, Multi-Point
+ cir-value:
+ type: string
+ description: Commited Information Rate
+ cir-units:
+ type: string
+ description: CIR units
+ connection-diversity-group-id:
+ type: string
+ description: Diversity Group ID
+ service-hours:
+ type: string
+ description: formerly Performance Group
+ esp-evc-circuit-id:
+ type: string
+ description: EVC Circuit ID of ESP EVC
+ esp-evc-cir-value:
+ type: string
+ description: Committed Information Rate (For ESP)
+ esp-evc-cir-units:
+ type: string
+ description: CIR units (For ESP)
+ esp-itu-code:
+ type: string
+ description: Identifies ESP
+ collector-pop-clli:
+ type: string
+ description: Collector POP CLLI (from the hostname of the access pnf)
+ inter-connect-type-ingress:
+ type: string
+ description: Interconnect type on ingress side of EVC.
+ tagmode-access-ingress:
+ type: string
+ description: tagode for collector side of EVC
+ tagmode-access-egress:
+ type: string
+ description: tagMode for network side of EVC
+ evcs:
+ properties:
+ evc:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/evc"
+ external-system:
+ description: |
+ Namespace for external system.
+ properties:
+ esr-ems-list:
+ type: object
+ $ref: "#/patchDefinitions/esr-ems-list"
+ esr-vnfm-list:
+ type: object
+ $ref: "#/patchDefinitions/esr-vnfm-list"
+ esr-thirdparty-sdnc-list:
+ type: object
+ $ref: "#/patchDefinitions/esr-thirdparty-sdnc-list"
+ extra-properties:
+ description: |
+ Extra properties for inventory item for response list
+ extra-property:
+ properties:
+ property-name:
+ type: string
+ flavor:
+ description: |
+ Openstack flavor.
+ ###### Related Nodes
+ - TO cloud-region( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)
+ - FLAVOR cannot be deleted if linked to VSERVER
+ required:
+ - flavor-id
+ - flavor-name
+ - flavor-selflink
+ properties:
+ flavor-id:
+ type: string
+ description: Flavor id, expected to be unique across cloud-region.
+ flavor-name:
+ type: string
+ description: Flavor name
+ flavor-vcpus:
+ type: integer
+ format: int32
+ description: Number of CPUs
+ flavor-ram:
+ type: integer
+ format: int32
+ description: Amount of memory
+ flavor-disk:
+ type: integer
+ format: int32
+ description: Disk space
+ flavor-ephemeral:
+ type: integer
+ format: int32
+ description: Amount of ephemeral disk space
+ flavor-swap:
+ type: string
+ description: amount of swap space allocation
+ flavor-is-public:
+ type: boolean
+ description: whether flavor is available to all users or private to the tenant it was created in.
+ flavor-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ flavor-disabled:
+ type: boolean
+ description: Boolean as to whether this flavor is no longer enabled
+ flavors:
+ description: |
+ Collection of openstack flavors.
+ properties:
+ flavor:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/flavor"
+ forwarder:
+ description: |
+ Entity describing a sequenced segment of forwarding path
+ ###### Related Nodes
+ - TO forwarding-path( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)
+ - TO l-interface( forwarder org.onap.relationships.inventory.ForwardsTo l-interface, MANY2ONE)
+ - TO configuration( forwarder org.onap.relationships.inventory.Uses configuration, ONE2ONE)
+ - TO lag-interface( forwarder org.onap.relationships.inventory.ForwardsTo lag-interface, MANY2ONE)
+ - TO p-interface( forwarder org.onap.relationships.inventory.ForwardsTo p-interface, MANY2ONE)
+ - FORWARDER deletion means associated objects of these types are also DELETED:CONFIGURATION
+ required:
+ - sequence
+ properties:
+ sequence:
+ type: integer
+ format: int32
+ description: Unique ID of this segmentation
+ forwarder-role:
+ type: string
+ description: ingress, intermediate, egress
+ forwarder-evc:
+ description: |
+ forwarder object is an optional child object of the Configuration object.
+ ###### Related Nodes
+ - TO configuration( forwarder-evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)
+ required:
+ - forwarder-evc-id
+ properties:
+ forwarder-evc-id:
+ type: string
+ description: Key for forwarder-evc object
+ circuit-id:
+ type: string
+ description: Circuit ID from customer/ESP/ingress end of EVC, or reference to beater circuit on gateway/network/egress end of EVC
+ ivlan:
+ type: string
+ description: Internal VLAN.
+ svlan:
+ type: string
+ description: SVLAN value for ingress of egress forwarder.
+ cvlan:
+ type: string
+ description: CVLAN value for ingress of egress forwarder.
+ forwarder-evcs:
+ properties:
+ forwarder-evc:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/forwarder-evc"
+ forwarders:
+ properties:
+ forwarder:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/forwarder"
+ forwarding-path:
+ description: |
+ Entity that describes the sequenced forwarding path between interfaces of services or resources
+ ###### Related Nodes
+ - TO service-instance( forwarding-path org.onap.relationships.inventory.AppliesTo service-instance, MANY2ONE)
+ - TO configuration( forwarding-path org.onap.relationships.inventory.Uses configuration, ONE2ONE)
+ - FROM forwarder( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)
+ - FORWARDING-PATH is DELETED when these are DELETED FORWARDER
+ - FORWARDING-PATH deletion means associated objects of these types are also DELETED:CONFIGURATION
+ required:
+ - forwarding-path-id
+ - forwarding-path-name
+ properties:
+ forwarding-path-id:
+ type: string
+ description: Unique ID of this FP
+ forwarding-path-name:
+ type: string
+ description: Name of the FP
+ forwarding-paths:
+ properties:
+ forwarding-path:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/forwarding-path"
+ generic-vnf:
+ description: |
+ General purpose VNF
+ ###### Related Nodes
+ - TO availability-zone( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - TO instance-group( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO ipsec-configuration( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)
+ - TO l3-network( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO license-key-resource( generic-vnf org.onap.relationships.inventory.Uses license-key-resource, MANY2MANY)
+ - TO pserver( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)
+ - TO vnf-image( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)
+ - TO volume-group( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - TO vserver( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)
+ - TO virtual-data-center( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY)
+ - FROM entitlement( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM lag-interface( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM license( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM network-profile( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)
+ - FROM site-pair-set( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)
+ - GENERIC-VNF is DELETED when these are DELETED ENTITLEMENT,VNFC,LAG-INTERFACE,LICENSE,L-INTERFACE,VF-MODULE
+ required:
+ - vnf-id
+ - vnf-name
+ - vnf-type
+ - in-maint
+ - is-closed-loop-disabled
+ properties:
+ vnf-id:
+ type: string
+ description: Unique id of VNF. This is unique across the graph.
+ vnf-name:
+ type: string
+ description: Name of VNF.
+ vnf-name2:
+ type: string
+ description: Alternate name of VNF.
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ service-id:
+ type: string
+ description: Unique identifier of service, does not necessarily map to ASDC service models. SOON TO BE DEPRECATED
+ regional-resource-zone:
+ type: string
+ description: Regional way of organizing pservers, source of truth should define values
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ operational-state:
+ type: string
+ description: Indicator for whether the resource is considered operational. Valid values are in-service-path and out-of-service-path.
+ license-key:
+ type: string
+ description: OBSOLETE - do not use
+ equipment-role:
+ type: string
+ description: Client should send valid enumerated value
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, used by MSO.
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ management-option:
+ type: string
+ description: identifier of managed by company or customer
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by generic-vnf.
+ ipv4-loopback0-address:
+ type: string
+ description: v4 Loopback0 address
+ nm-lan-v6-address:
+ type: string
+ description: v6 Loopback address
+ management-v6-address:
+ type: string
+ description: v6 management address
+ vcpu:
+ type: integer
+ format: int64
+ description: number of vcpus ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases
+ vcpu-units:
+ type: string
+ description: units associated with vcpu, used for VNFs with no vservers/flavors, to be used only in some usecases
+ vmemory:
+ type: integer
+ format: int64
+ description: number of GB of memory ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases
+ vmemory-units:
+ type: string
+ description: units associated with vmemory, used for VNFs with no vservers/flavors, to be used only in some usecases
+ vdisk:
+ type: integer
+ format: int64
+ description: number of vdisks ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases
+ vdisk-units:
+ type: string
+ description: units associated with vdisk, used for VNFs with no vservers/flavors, to be used only in some usecases
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
+ generic-vnfs:
+ description: |
+ Collection of VNFs
+ properties:
+ generic-vnf:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/generic-vnf"
+ group-assignment:
+ description: |
+ Openstack group-assignment used to store exclusivity groups (EG).
+ ###### Related Nodes
+ - TO cloud-region( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)
+ required:
+ - group-id
+ - group-type
+ - group-name
+ properties:
+ group-id:
+ type: string
+ description: Group id, expected to be unique across cloud-region.
+ group-type:
+ type: string
+ description: Group type - the type of group this instance refers to
+ group-name:
+ type: string
+ description: Group name - name assigned to the group
+ group-description:
+ type: string
+ description: Group description - description of the group
+ group-assignments:
+ description: |
+ Collection of openstack group assignments
+ properties:
+ group-assignment:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/group-assignment"
+ host-route:
+ description: |
+ ###### Related Nodes
+ - TO subnet( host-route org.onap.relationships.inventory.BelongsTo subnet, MANY2ONE)
+ required:
+ - host-route-id
+ - route-prefix
+ - next-hop
+ properties:
+ host-route-id:
+ type: string
+ description: host-route id
+ route-prefix:
+ type: string
+ description: subnet prefix
+ next-hop:
+ type: string
+ description: Could be ip-address, hostname, or service-instance
+ next-hop-type:
+ type: string
+ description: Should be ip-address, hostname, or service-instance to match next-hop
+ host-routes:
+ properties:
+ host-route:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/host-route"
+ image:
+ description: |
+ Openstack image.
+ ###### Related Nodes
+ - TO cloud-region( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)
+ - IMAGE cannot be deleted if linked to VSERVER
+ - IMAGE is DELETED when these are DELETED METADATUM
+ required:
+ - image-id
+ - image-name
+ - image-os-distro
+ - image-os-version
+ - image-selflink
+ properties:
+ image-id:
+ type: string
+ description: Image id, expected to be unique across cloud region
+ image-name:
+ type: string
+ description: Image name
+ image-architecture:
+ type: string
+ description: Operating system architecture.
+ image-os-distro:
+ type: string
+ description: The common name of the operating system distribution in lowercase
+ image-os-version:
+ type: string
+ description: The operating system version as specified by the distributor.
+ application:
+ type: string
+ description: The application that the image instantiates.
+ application-vendor:
+ type: string
+ description: The vendor of the application.
+ application-version:
+ type: string
+ description: The version of the application.
+ image-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ images:
+ description: |
+ Collectio of Openstack images.
+ properties:
+ image:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/image"
+ include-node-filter:
+ properties:
+ include-node-type:
+ type: string
+ instance-filter:
+ description: |
+ InstanceFilter for performing a named-query or model query
+ instance-filters:
+ description: |
+ InstanceFilters for performing a named-query or model query
+ properties:
+ instance-filter:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/instance-filter"
+ instance-group:
+ description: |
+ General mechanism for grouping instances
+ ###### Related Nodes
+ - TO model( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM pnf( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ required:
+ - id
+ - description
+ - type
+ properties:
+ id:
+ type: string
+ description: Instance Group ID, UUID assigned to this instance.
+ description:
+ type: string
+ description: Descriptive text to help identify the usage of this instance-group
+ type:
+ type: string
+ description: Only valid value today is lower case ha for high availability
+ sub-type:
+ type: string
+ description: Valid values for ha type are [geo-activeactive, geo-activestandby, local-activeactive, local-activestandby]
+ instance-groups:
+ description: |
+ Collection of openstack route table references
+ properties:
+ instance-group:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/instance-group"
+ inventory:
+ properties:
+ search:
+ type: object
+ $ref: "#/patchDefinitions/search"
+ actions:
+ type: object
+ $ref: "#/patchDefinitions/actions"
+ cloud-infrastructure:
+ type: object
+ $ref: "#/patchDefinitions/cloud-infrastructure"
+ business:
+ type: object
+ $ref: "#/patchDefinitions/business"
+ service-design-and-creation:
+ type: object
+ $ref: "#/patchDefinitions/service-design-and-creation"
+ network:
+ type: object
+ $ref: "#/patchDefinitions/network"
+ aai-internal:
+ type: object
+ $ref: "#/patchDefinitions/aai-internal"
+ nodes:
type: array
items:
- $ref: "#/definitions/relationship"
- constrained-element-sets:
+ $ref: "#/patchDefinitions/aai-internal"
+ inventory-item:
properties:
- constrained-element-set:
+ inventory-item-type:
+ type: string
+ inventory-item-link:
+ type: string
+ inventory-item-data:
type: array
items:
- $ref: "#/definitions/constrained-element-set"
+ $ref: "#/patchDefinitions/inventory-item-data"
+ tagged-inventory-item-list:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/tagged-inventory-item-list"
+ inventory-item-data:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ inventory-response-item:
+ description: |
+ Inventory item for response list
+ properties:
+ model-name:
+ type: string
+ extra-properties:
+ type: object
+ $ref: "#/patchDefinitions/extra-properties"
+ inventory-response-items:
+ type: object
+ $ref: "#/patchDefinitions/inventory-response-items"
+ inventory-response-items:
+ description: |
+ Container for inventory items in response list
+ properties:
+ inventory-response-item:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/inventory-response-item"
+ ipsec-configuration:
+ description: |
+ IPSec configuration node will contain various configuration data for the NMTE VNF. This node will have an edge to the generic-vnf (vnf type = TE). Starting 1607, this data will be populated by SDN-C
+ ###### Related Nodes
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)
+ - FROM vig-server( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)
+ - IPSEC-CONFIGURATION is DELETED when these are DELETED VIG-SERVER
+ required:
+ - ipsec-configuration-id
+ properties:
+ ipsec-configuration-id:
+ type: string
+ description: UUID of this configuration
+ requested-vig-address-type:
+ type: string
+ description: Indicate the type of VIG server like AVPN, INTERNET, BOTH
+ requested-encryption-strength:
+ type: string
+ description: Encryption values like 3des-cbc, des-cbc, aes-128-cbc, aes-192-cbc, aes-265-cbc
+ requested-dmz-type:
+ type: string
+ description: can offer a shared DMZ or a DMZ specific to a customer
+ shared-dmz-network-address:
+ type: string
+ description: Network address of shared DMZ
+ requested-customer-name:
+ type: string
+ description: If the DMZ is a custom DMZ, this field will indicate the customer information
+ ike-version:
+ type: string
+ description: can be 1 or 2
+ ikev1-authentication:
+ type: string
+ description: Contains values like md5, sha1, sha256, sha384
+ ikev1-encryption:
+ type: string
+ description: Encyption values like 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
+ ikev1-dh-group:
+ type: string
+ description: Diffie-Hellman group like DH-GROUP2, DH-GROUP5, DH-GROUP14
+ ikev1-am-group-id:
+ type: string
+ description: Group name defined in VIG for clients using aggressive mode
+ ikev1-am-password:
+ type: string
+ description: pre-shared key for the above group name
+ ikev1-sa-lifetime:
+ type: string
+ description: Lifetime for IKEv1 SA
+ ipsec-authentication:
+ type: string
+ description: md5, sha1, sha256, sha384
+ ipsec-encryption:
+ type: string
+ description: 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
+ ipsec-sa-lifetime:
+ type: string
+ description: Life time for IPSec SA
+ ipsec-pfs:
+ type: string
+ description: enable PFS or not
+ xauth-userid:
+ type: string
+ description: user ID for xAuth, sm-user, ,nmteHostName
+ xauth-user-password:
+ type: string
+ description: Encrypted using the Juniper $9$ algorithm
+ dpd-interval:
+ type: string
+ description: The time between DPD probe
+ dpd-frequency:
+ type: string
+ description: Maximum number of DPD before claiming the tunnel is down
+ ipsec-configurations:
+ properties:
+ ipsec-configuration:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/ipsec-configuration"
+ key-data:
+ properties:
+ key-name:
+ type: string
+ key-value:
+ type: string
+ l-interface:
+ description: |
+ Logical interfaces, e.g., a vnic.
+ ###### Related Nodes
+ - TO generic-vnf( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO lag-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)
+ - TO logical-link( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)
+ - TO newvce( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)
+ - TO p-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)
+ - TO vserver( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - FROM sriov-vf( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)
+ - FROM vlan( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)
+ - L-INTERFACE is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST,SRIOV-VF,VLAN
+ - L-INTERFACE deletion means associated objects of these types are also DELETED:LOGICAL-LINK
+ required:
+ - interface-name
+ properties:
+ interface-name:
+ type: string
+ description: Name given to the interface
+ interface-role:
+ type: string
+ description: E.g., CUSTOMER, UPLINK, etc.
+ v6-wan-link-ip:
+ type: string
+ description: Questionably placed - v6 ip addr of this interface (is in vr-lan-interface from Mary B.
+ selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ interface-id:
+ type: string
+ description: ID of interface
+ macaddr:
+ type: string
+ description: MAC address for the interface
+ network-name:
+ type: string
+ description: Name of the network
+ management-option:
+ type: string
+ description: Whether A&AI should be managing this interface of not. Could have value like CUSTOMER
+ interface-description:
+ type: string
+ description: Human friendly text regarding this interface.
+ l-interfaces:
+ description: |
+ Collection of logical interfaces.
+ properties:
+ l-interface:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/l-interface"
+ l3-interface-ipv4-address-list:
+ description: |
+ IPv4 Address Range
+ ###### Related Nodes
+ - TO l3-network( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - TO subnet( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - TO l-interface( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - TO vlan( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ required:
+ - l3-interface-ipv4-address
+ properties:
+ l3-interface-ipv4-address:
+ type: string
+ description: IP address
+ l3-interface-ipv4-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 32 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ l3-interface-ipv6-address-list:
+ description: |
+ IPv6 Address Range
+ ###### Related Nodes
+ - TO l3-network( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - TO subnet( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - TO l-interface( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - TO vlan( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ required:
+ - l3-interface-ipv6-address
+ properties:
+ l3-interface-ipv6-address:
+ type: string
+ description: IP address
+ l3-interface-ipv6-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 128 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ l3-network:
+ description: |
+ Generic network definition
+ ###### Related Nodes
+ - TO network-policy( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)
+ - TO route-table-reference( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)
+ - TO vpn-binding( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM complex( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - FROM ctag-assignment( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM segmentation-assignment( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)
+ - FROM subnet( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)
+ - L3-NETWORK is DELETED when these are DELETED CTAG-ASSIGNMENT,SEGMENTATION-ASSIGNMENT,SUBNET
+ required:
+ - network-id
+ - network-name
+ - is-bound-to-vpn
+ - is-provider-network
+ - is-shared-network
+ - is-external-network
+ properties:
+ network-id:
+ type: string
+ description: Network ID, should be uuid. Unique across A&AI.
+ network-name:
+ type: string
+ description: Name of the network, governed by some naming convention..
+ network-type:
+ type: string
+ description: Type of the network - who defines these values?
+ network-role:
+ type: string
+ description: Role the network plans - who defines these values?
+ network-technology:
+ type: string
+ description: Network technology - who defines these values?
+ neutron-network-id:
+ type: string
+ description: Neutron network id of this Interface
+ is-bound-to-vpn:
+ type: boolean
+ service-id:
+ type: string
+ description: Unique identifier of service from ASDC. Does not strictly map to ASDC services. SOON TO BE DEPRECATED
+ network-role-instance:
+ type: integer
+ format: int64
+ description: network role instance
+ l3-networks:
+ properties:
+ l3-network:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/l3-network"
+ lag-interface:
+ description: |
+ Link aggregate interface
+ ###### Related Nodes
+ - TO generic-vnf( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO lag-link( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)
+ - TO p-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)
+ - TO pnf( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - TO pserver( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - TO vpls-pe( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)
+ - LAG-INTERFACE is DELETED when these are DELETED L-INTERFACE
+ - LAG-INTERFACE deletion means associated objects of these types are also DELETED:LAG-LINK
+ required:
+ - interface-name
+ properties:
+ interface-name:
+ type: string
+ description: Name that identifies the link aggregate interface
+ interface-description:
+ type: string
+ description: Human friendly text regarding this interface.
+ lag-interfaces:
+ description: |
+ Collection of link aggregate interfaces.
+ properties:
+ lag-interface:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/lag-interface"
+ lag-link:
+ description: |
+ LAG links can connect lag-interfaces
+ ###### Related Nodes
+ - FROM lag-interface( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)
+ required:
+ - link-name
+ properties:
+ link-name:
+ type: string
+ description: Alphabetical concatenation of lag-interface names
+ lag-links:
+ description: |
+ Collection of link aggregation connections
+ properties:
+ lag-link:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/lag-link"
+ license:
+ description: |
+ Metadata for license group.
+ ###### Related Nodes
+ - TO generic-vnf( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vce( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ required:
+ - group-uuid
+ - resource-uuid
+ properties:
+ group-uuid:
+ type: string
+ description: Unique ID for the license group the resource belongs to, should be uuid.
+ resource-uuid:
+ type: string
+ description: Unique ID of a license resource.
+ licenses:
+ description: |
+ Licenses to be allocated across resources, keyed by group-uuid and resource-uuid, related to license management
+ properties:
+ license:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/license"
+ line-of-business:
+ description: |
+ describes a line-of-business
+ ###### Related Nodes
+ - TO generic-vnf( line-of-business org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)
+ required:
+ - line-of-business-name
+ properties:
+ line-of-business-name:
+ type: string
+ description: Name of the line-of-business (product)
+ lines-of-business:
+ description: |
+ Collection of lines-of-business
+ properties:
+ line-of-business:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/line-of-business"
+ logical-link:
+ description: |
+ Logical links generally connect l-interfaces but are used to express logical connectivity between two points
+ ###### Related Nodes
+ - TO cloud-region( logical-link org.onap.relationships.inventory.LocatedIn cloud-region, MANY2MANY)
+ - TO generic-vnf( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)
+ - TO lag-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)
+ - TO logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - TO pnf( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)
+ - TO pserver( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)
+ - TO vpn-binding( logical-link org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - TO virtual-data-center( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)
+ - FROM p-interface( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - FROM vlan( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ required:
+ - link-name
+ - link-type
+ properties:
+ link-name:
+ type: string
+ description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
+ link-type:
+ type: string
+ description: Type of logical link, e.g., evc
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ ip-version:
+ type: string
+ description: v4, v6, or ds for dual stack
+ routing-protocol:
+ type: string
+ description: For example, static or BGP
+ logical-links:
+ description: |
+ Collection of logical connections
+ properties:
+ logical-link:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/logical-link"
+ metadata:
+ description: |
+ Collection of metadatum (key/value pairs)
+ properties:
+ metadatum:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/metadatum"
+ metadatum:
+ description: |
+ Key/value pairs
+ ###### Related Nodes
+ - TO connector( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)
+ - TO image( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)
+ - TO service-instance( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - TO model-ver( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ required:
+ - metaname
+ - metaval
+ properties:
+ metaname:
+ type: string
+ metaval:
+ type: string
+ model:
+ description: |
+ Subgraph definition provided by ASDC to describe an inventory asset and its connections related to ASDC models, independent of version
+ ###### Related Nodes
+ - TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - FROM instance-group( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY)
+ - FROM model-ver( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - FROM named-query( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)
+ - MODEL cannot be deleted if linked to INSTANCE-GROUP,NAMED-QUERY,NAMED-QUERY-ELEMENT
+ - MODEL is DELETED when these are DELETED MODEL-VER
+ required:
+ - model-invariant-id
+ - model-type
+ properties:
+ model-invariant-id:
+ type: string
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ model-type:
+ type: string
+ description: Type of the model, e.g., service, resource, widget, etc.
+ model-and-named-query-search:
+ description: |
+ ModelAndNamedQuerySearch holds query-parameters and instance-properties for performing a named-query or model query
+ properties:
+ query-parameters:
+ type: object
+ $ref: "#/patchDefinitions/query-parameters"
+ instance-filters:
+ type: object
+ $ref: "#/patchDefinitions/instance-filters"
+ secondary-filts:
+ type: object
+ $ref: "#/patchDefinitions/secondary-filts"
+ top-node-type:
+ type: string
+ secondary-filter-cut-point:
+ type: string
model-constraint:
description: |
This is how we would capture constraints defining allowed sets of elements.
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
###### Related Nodes
- - TO constrained-element-set (comprises model-constraint, One2Many)
- - FROM model-element (is composed of model-constraint)
+ - TO model-element( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)
+ - MODEL-CONSTRAINT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET
required:
- model-constraint-uuid
- constrained-element-set-uuid-to-replace
@@ -39025,29 +54527,25 @@ definitions:
constrained-element-sets:
type: array
items:
- $ref: "#/definitions/constrained-element-set"
- resource-version:
- type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ $ref: "#/patchDefinitions/constrained-element-set"
model-constraints:
properties:
model-constraint:
type: array
items:
- $ref: "#/definitions/model-constraint"
+ $ref: "#/patchDefinitions/model-constraint"
model-element:
description: |
Defines how other models combine to make up a higher-level model.
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
###### Related Nodes
- - TO model-ver (Many2One)
- - TO model-element (comprises model-element, One2Many)
- - TO model-constraint (comprises model-element, One2Many)
- - TO constrained-element-set (comprises model-element, One2Many)
- - FROM model-ver (is composed of model-element)
- - FROM element-choice-set (is composed of model-element)
- - FROM model-element (is composed of model-element)
+ - TO element-choice-set( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)
+ - TO model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - TO model-ver( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE)
+ - TO model-ver( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM model-constraint( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - MODEL-ELEMENT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET,MODEL-CONSTRAINT
required:
- model-element-uuid
- new-data-del-flag
@@ -39063,39 +54561,22 @@ definitions:
description: How many of this type of element are required/allowed
linkage-points:
type: string
- resource-version:
- type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- model-elements:
- type: array
- items:
- $ref: "#/definitions/model-element"
- description: Defines how other models combine to make up a higher-level model
- model-constraints:
- type: array
- items:
- $ref: "#/definitions/model-constraint"
- description: Describes new constraints on this model element that are not part of that model's definition
- relationship-list:
- type: array
- items:
- $ref: "#/definitions/relationship"
model-elements:
properties:
model-element:
type: array
items:
- $ref: "#/definitions/model-element"
+ $ref: "#/patchDefinitions/model-element"
model-ver:
description: |
Subgraph definition provided by ASDC to describe a specific version of an inventory asset and its connections related to ASDC models
- ###### Default Delete Scope
- ERROR_4_IN_EDGES_OR_CASCADE
###### Related Nodes
- - TO model-element (comprises model-ver, One2Many)
- - TO metadatum (comprises model-ver, One2Many)
- - FROM model (is composed of model-ver)
- - FROM model-element
+ - TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - MODEL-VER cannot be deleted if linked to MODEL-ELEMENT
+ - MODEL-VER is DELETED when these are DELETED MODEL-ELEMENT,METADATUM
required:
- model-version-id
- model-name
@@ -39113,111 +54594,693 @@ definitions:
model-description:
type: string
description: Description
- resource-version:
+ model-vers:
+ properties:
+ model-ver:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/model-ver"
+ models:
+ description: |
+ Collection of subgraph definitions provided by ASDC to describe the inventory assets and their connections related to ASDC models
+ properties:
+ model:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/model"
+ multicast-configuration:
+ description: |
+ ###### Related Nodes
+ - FROM vlan( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)
+ required:
+ - multicast-configuration-id
+ - multicast-protocol
+ - rp-type
+ properties:
+ multicast-configuration-id:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- model-elements:
+ description: Unique id of multicast configuration.
+ multicast-protocol:
+ type: string
+ description: protocol of multicast configuration
+ rp-type:
+ type: string
+ description: rp type of multicast configuration
+ multicast-configurations:
+ description: |
+ multicast configuration of generic-vnf ip-address
+ properties:
+ multicast-configuration:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/multicast-configuration"
+ named-queries:
+ properties:
+ named-query:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/named-query"
+ named-query:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - TO model( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - NAMED-QUERY is DELETED when these are DELETED NAMED-QUERY-ELEMENT
+ required:
+ - named-query-uuid
+ - named-query-name
+ - named-query-version
+ properties:
+ named-query-uuid:
+ type: string
+ named-query-name:
+ type: string
+ named-query-version:
+ type: string
+ required-input-param:
+ type: string
+ description:
+ type: string
+ named-query-element:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - TO model( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)
+ - TO named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM property-constraint( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM related-lookup( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - NAMED-QUERY-ELEMENT is DELETED when these are DELETED PROPERTY-CONSTRAINT,RELATED-LOOKUP
+ required:
+ - named-query-element-uuid
+ properties:
+ named-query-element-uuid:
+ type: string
+ property-collect-list:
+ type: string
+ named-query-elements:
+ properties:
+ named-query-element:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/named-query-element"
+ network:
+ description: |
+ Namespace for network inventory resources.
+ properties:
+ logical-links:
type: array
items:
- $ref: "#/definitions/model-element"
- metadata:
+ $ref: "#/patchDefinitions/logical-link"
+ site-pair-sets:
type: array
items:
- $ref: "#/definitions/metadatum"
- relationship-list:
+ $ref: "#/patchDefinitions/site-pair-set"
+ vpn-bindings:
type: array
items:
- $ref: "#/definitions/relationship"
- model-vers:
+ $ref: "#/patchDefinitions/vpn-binding"
+ vpls-pes:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vpls-pe"
+ multicast-configurations:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/multicast-configuration"
+ vces:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vce"
+ vnfcs:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vnfc"
+ l3-networks:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/l3-network"
+ network-policies:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/network-policy"
+ generic-vnfs:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/generic-vnf"
+ lag-links:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/lag-link"
+ newvces:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/newvce"
+ pnfs:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/pnf"
+ physical-links:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/physical-link"
+ ipsec-configurations:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/ipsec-configuration"
+ route-table-references:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/route-table-reference"
+ instance-groups:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/instance-group"
+ zones:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/zone"
+ network-policies:
properties:
- model-ver:
+ network-policy:
type: array
items:
- $ref: "#/definitions/model-ver"
- model:
+ $ref: "#/patchDefinitions/network-policy"
+ network-policy:
description: |
- Subgraph definition provided by ASDC to describe an inventory asset and its connections related to ASDC models, independent of version
- ###### Default Delete Scope
- ERROR_4_IN_EDGES_OR_CASCADE
###### Related Nodes
- - TO model-ver (comprises model, One2Many)
- - FROM named-query
- - FROM named-query-element
- - FROM instance-group
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)
+ required:
+ - network-policy-id
+ properties:
+ network-policy-id:
+ type: string
+ description: UUID representing unique key to this instance
+ network-policy-fqdn:
+ type: string
+ description: Contrail FQDN for the policy
+ heat-stack-id:
+ type: string
+ description: ID for the openStack Heat instance
+ network-profile:
+ description: |
+ Network profile populated by SDN-GP for SNMP
+ ###### Related Nodes
+ - TO generic-vnf( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ required:
+ - nm-profile-name
+ properties:
+ nm-profile-name:
+ type: string
+ description: Unique name of network profile.
+ community-string:
+ type: string
+ description: Encrypted SNMP community string
+ network-profiles:
+ description: |
+ Collection of network profiles
+ properties:
+ network-profile:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/network-profile"
+ newvce:
+ description: |
+ This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce.
+ ###### Related Nodes
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)
+ - NEWVCE is DELETED when these are DELETED L-INTERFACE
+ required:
+ - vnf-id2
+ - vnf-name
+ - vnf-type
+ properties:
+ vnf-id2:
+ type: string
+ description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+ vnf-name:
+ type: string
+ description: Name of VNF.
+ vnf-name2:
+ type: string
+ description: Alternate name of VNF.
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+ operational-state:
+ type: string
+ description: Indicator for whether the resource is considered operational
+ license-key:
+ type: string
+ description: OBSOLETE - do not use
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by VPE (v4-loopback0-ip-address).
+ equipment-role:
+ type: string
+ description: Client should send valid enumerated value.
+ newvces:
+ description: |
+ This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce.
+ properties:
+ newvce:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/newvce"
+ notification-event:
+ properties:
+ cambria.partition:
+ type: string
+ notification-event-header:
+ type: object
+ $ref: "#/patchDefinitions/notification-event-header"
+ notification-event-header:
+ properties:
+ id:
+ type: string
+ timestamp:
+ type: string
+ source-name:
+ type: string
+ domain:
+ type: string
+ sequence-number:
+ type: string
+ severity:
+ type: string
+ event-type:
+ type: string
+ version:
+ type: string
+ action:
+ type: string
+ entity-type:
+ type: string
+ top-entity-type:
+ type: string
+ entity-link:
+ type: string
+ status:
+ type: string
+ notify:
+ required:
+ - event-id
+ properties:
+ event-id:
+ type: string
+ node-type:
+ type: string
+ event-trigger:
+ type: string
+ key-data:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/key-data"
+ selflink:
+ type: string
+ oam-network:
+ description: |
+ OAM network, to be deprecated shortly. Do not use for new purposes.
+ ###### Related Nodes
+ - TO cloud-region( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO complex( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)
+ - TO service-capability( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ required:
+ - network-uuid
+ - network-name
+ - cvlan-tag
+ properties:
+ network-uuid:
+ type: string
+ description: UUID of the network. Unique across a cloud-region
+ network-name:
+ type: string
+ description: Name of the network.
+ cvlan-tag:
+ type: integer
+ format: int64
+ description: cvlan-id
+ ipv4-oam-gateway-address:
+ type: string
+ description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
+ ipv4-oam-gateway-address-prefix-length:
+ type: integer
+ format: int32
+ description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
+ oam-networks:
+ description: |
+ Collection of OAM networks, to be deprecated shortly. Do not use for new purposes.
+ properties:
+ oam-network:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/oam-network"
+ operational-environment:
+ description: |
+ It is a logical partition of the cloud which allows to have multiple environments in the production AIC.
+ ###### Related Nodes
+ - TO operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)
+ - FROM operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)
+ required:
+ - operational-environment-id
+ - operational-environment-name
+ - operational-environment-type
+ - operational-environment-status
+ - tenant-context
+ - workload-context
+ properties:
+ operational-environment-id:
+ type: string
+ description: UUID of an operational environment
+ operational-environment-name:
+ type: string
+ description: Operational Environment name
+ operational-environment-type:
+ type: string
+ description: Operational Environment Type.
+ operational-environment-status:
+ type: string
+ description: Status
+ tenant-context:
+ type: string
+ description: Tenant Context.
+ workload-context:
+ type: string
+ description: Workload Context.
+ operational-environments:
+ description: |
+ a logical partition of the cloud which allows to have multiple environments in the production AIC.
+ properties:
+ operational-environment:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/operational-environment"
+ overloaded-model:
+ description: |
+ Allows for legacy POST of old-style and new-style models
required:
- model-invariant-id
+ - model-name-version-id
- model-type
+ - model-name
+ - model-id
+ - model-version
properties:
model-invariant-id:
type: string
description: Unique identifier corresponding to the main definition of a model in ASDC
+ model-name-version-id:
+ type: string
+ description: Unique identifier corresponding to one version of a model in ASDC
model-type:
type: string
description: Type of the model, e.g., service, resource, widget, etc.
- resource-version:
+ model-name:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- model-vers:
+ description: Name of the model, which can change from version to version.
+ model-id:
+ type: string
+ description: Invariant unique ID which does not change from version to version
+ model-version:
+ type: string
+ description: Version
+ model-description:
+ type: string
+ description: Description
+ owning-entities:
+ description: |
+ Collection of owning-entities
+ properties:
+ owning-entity:
type: array
- items:
- $ref: "#/definitions/model-ver"
- relationship-list:
+ items:
+ $ref: "#/patchDefinitions/owning-entity"
+ owning-entity:
+ description: |
+ describes an owning-entity
+ ###### Related Nodes
+ - FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo owning-entity, MANY2ONE)
+ required:
+ - owning-entity-id
+ - owning-entity-name
+ properties:
+ owning-entity-id:
+ type: string
+ description: UUID of an owning entity
+ owning-entity-name:
+ type: string
+ description: Owning entity name
+ p-interface:
+ description: |
+ Physical interface (e.g., nic)
+ ###### Related Nodes
+ - TO logical-link( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)
+ - TO physical-link( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)
+ - TO pnf( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - TO pserver( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - TO vpls-pe( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM lag-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)
+ - P-INTERFACE is DELETED when these are DELETED L-INTERFACE
+ - P-INTERFACE deletion means associated objects of these types are also DELETED:PHYSICAL-LINK
+ required:
+ - interface-name
+ properties:
+ interface-name:
+ type: string
+ description: Name that identifies the physical interface
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ port-description:
+ type: string
+ description: Nature of the services and connectivity on this port.
+ equipment-identifier:
+ type: string
+ description: CLEI or other specification for p-interface hardware.
+ interface-role:
+ type: string
+ description: Role specification for p-interface hardware.
+ interface-type:
+ type: string
+ description: Indicates the physical properties of the interface.
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ p-interfaces:
+ description: |
+ Collection of physical interfaces.
+ properties:
+ p-interface:
type: array
- items:
- $ref: "#/definitions/relationship"
- models:
+ items:
+ $ref: "#/patchDefinitions/p-interface"
+ physical-link:
description: |
- Collection of subgraph definitions provided by ASDC to describe the inventory assets and their connections related to ASDC models
+ Collection of physical connections, typically between p-interfaces
+ ###### Related Nodes
+ - FROM p-interface( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)
+ required:
+ - link-name
properties:
- model:
+ link-name:
+ type: string
+ description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ circuit-id:
+ type: string
+ description: Circuit it
+ dual-mode:
+ type: string
+ description: Dual access mode (e.g., primary, secondary
+ management-option:
+ type: string
+ description: To provide information on who manages this circuit. A&AI or 3rd party transport provider
+ service-provider-name:
+ type: string
+ description: Name of the service Provider on this link.
+ physical-links:
+ description: |
+ Collection of physical connections, typically between p-interfaces
+ properties:
+ physical-link:
type: array
items:
- $ref: "#/definitions/model"
- related-lookup:
+ $ref: "#/patchDefinitions/physical-link"
+ platform:
description: |
- TBD
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
+ describes a platform
###### Related Nodes
- - FROM named-query-element (is composed of related-lookup)
+ - TO generic-vnf( platform org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)
required:
- - related-lookup-uuid
- - source-node-type
- - source-node-property
- - target-node-type
- - target-node-property
+ - platform-name
properties:
- related-lookup-uuid:
+ platform-name:
type: string
- source-node-type:
+ description: Name of the platform
+ platforms:
+ description: |
+ Collection of platforms
+ properties:
+ platform:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/platform"
+ pnf:
+ description: |
+ PNF represents a physical network function. typically equipment used in the D1 world.
+ ###### Related Nodes
+ - TO complex( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO instance-group( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO zone( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf pnf, ONE2MANY)
+ - PNF is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
+ required:
+ - pnf-name
+ - in-maint
+ properties:
+ pnf-name:
type: string
- source-node-property:
+ description: unique name of Physical Network Function.
+ pnf-name2:
type: string
- target-node-type:
+ description: name of Physical Network Function.
+ pnf-name2-source:
type: string
- target-node-property:
+ description: source of name2
+ pnf-id:
type: string
- property-collect-list:
+ description: id of pnf
+ equip-type:
type: string
- resource-version:
+ description: Equipment type. Source of truth should define valid values.
+ equip-vendor:
type: string
- relationship-list:
+ description: Equipment vendor. Source of truth should define valid values.
+ equip-model:
+ type: string
+ description: Equipment model. Source of truth should define valid values.
+ management-option:
+ type: string
+ description: identifier of managed by company or customer
+ ipaddress-v4-oam:
+ type: string
+ description: ipv4-oam-address with new naming convention for IP addresses
+ sw-version:
+ type: string
+ description: sw-version is the version of SW for the hosted application on the PNF.
+ in-maint:
+ type: boolean
+ frame-id:
+ type: string
+ description: ID of the physical frame (relay rack) where pnf is installed.
+ serial-number:
+ type: string
+ description: Serial number of the device
+ ipaddress-v4-loopback-0:
+ type: string
+ description: IPV4 Loopback 0 address
+ ipaddress-v6-loopback-0:
+ type: string
+ description: IPV6 Loopback 0 address
+ ipaddress-v4-aim:
+ type: string
+ description: IPV4 AIM address
+ ipaddress-v6-aim:
+ type: string
+ description: IPV6 AIM address
+ ipaddress-v6-oam:
+ type: string
+ description: IPV6 OAM address
+ inv-status:
+ type: string
+ description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
+ pnfs:
+ description: |
+ Collection of Physical Network Functions.
+ properties:
+ pnf:
type: array
- items:
- $ref: "#/definitions/relationship"
- related-lookups:
+ items:
+ $ref: "#/patchDefinitions/pnf"
+ port-group:
+ description: |
+ Used to capture the network interfaces of this VCE
+ ###### Related Nodes
+ - TO vce( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM cvlan-tag( cvlan-tag org.onap.relationships.inventory.BelongsTo port-group, MANY2ONE)
+ - PORT-GROUP is DELETED when these are DELETED CVLAN-TAG
+ required:
+ - interface-id
+ - orchestration-status
properties:
- related-lookup:
+ interface-id:
+ type: string
+ description: Unique ID of the interface
+ neutron-network-id:
+ type: string
+ description: Neutron network id of this Interface
+ neutron-network-name:
+ type: string
+ description: Neutron network name of this Interface
+ interface-role:
+ type: string
+ description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
+ port-groups:
+ properties:
+ port-group:
type: array
items:
- $ref: "#/definitions/related-lookup"
+ $ref: "#/patchDefinitions/port-group"
+ project:
+ description: |
+ describes the project
+ ###### Related Nodes
+ - TO service-instance( project org.onap.relationships.inventory.Uses service-instance, ONE2MANY)
+ required:
+ - project-name
+ properties:
+ project-name:
+ type: string
+ description: Name of the project deploying a service
+ projects:
+ description: |
+ Collection of projects
+ properties:
+ project:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/project"
+ properties:
+ description: |
+ Property holder for query properties or instance properties
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
property-constraint:
description: |
TBD
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
###### Related Nodes
- - FROM named-query-element (is composed of property-constraint)
+ - TO named-query-element( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
required:
- property-constraint-uuid
- constraint-type
@@ -39232,100 +55295,393 @@ definitions:
type: string
property-value:
type: string
- resource-version:
- type: string
property-constraints:
properties:
property-constraint:
type: array
items:
- $ref: "#/definitions/property-constraint"
- named-query-element:
+ $ref: "#/patchDefinitions/property-constraint"
+ pserver:
description: |
- TBD
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
+ Compute host whose hostname must be unique and must exactly match what is sent as a relationship to a vserver.
###### Related Nodes
- - TO named-query-element (comprises named-query-element, Many2Many)
- - TO model (Many2One)
- - TO property-constraint (comprises named-query-element, One2Many)
- - TO related-lookup (comprises named-query-element, One2Many)
- - FROM named-query (is composed of named-query-element)
- - FROM named-query-element (is composed of named-query-element)
+ - TO group-assignment( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)
+ - TO availability-zone( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)
+ - TO cloud-region( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)
+ - TO complex( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO zone( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - FROM vserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)
+ - PSERVER cannot be deleted if linked to GENERIC-VNF,LOGICAL-LINK,VSERVER
+ - PSERVER is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
+ - PSERVER cannot be deleted if linked to GROUP-ASSIGNMENT
required:
- - named-query-element-uuid
+ - hostname
+ - in-maint
properties:
- named-query-element-uuid:
+ hostname:
type: string
- property-collect-list:
+ description: Value from executing hostname on the compute node.
+ ptnii-equip-name:
type: string
- resource-version:
+ description: PTNII name
+ number-of-cpus:
+ type: integer
+ format: int32
+ description: Number of cpus
+ disk-in-gigabytes:
+ type: integer
+ format: int32
+ description: Disk size, in GBs
+ ram-in-megabytes:
+ type: integer
+ format: int32
+ description: RAM size, in MBs
+ equip-type:
type: string
- property-limit-desc:
+ description: Equipment type. Source of truth should define valid values.
+ equip-vendor:
type: string
- do-not-output:
+ description: Equipment vendor. Source of truth should define valid values.
+ equip-model:
type: string
- named-query-elements:
+ description: Equipment model. Source of truth should define valid values.
+ fqdn:
+ type: string
+ description: Fully-qualified domain name
+ pserver-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ ipv4-oam-address:
+ type: string
+ description: Used to configure device, also used for troubleshooting and is IP used for traps generated by device.
+ serial-number:
+ type: string
+ description: Serial number, may be queried
+ ipaddress-v4-loopback-0:
+ type: string
+ description: IPV4 Loopback 0 address
+ ipaddress-v6-loopback-0:
+ type: string
+ description: IPV6 Loopback 0 address
+ ipaddress-v4-aim:
+ type: string
+ description: IPV4 AIM address
+ ipaddress-v6-aim:
+ type: string
+ description: IPV6 AIM address
+ ipaddress-v6-oam:
+ type: string
+ description: IPV6 OAM address
+ inv-status:
+ type: string
+ description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
+ pserver-id:
+ type: string
+ description: ID of Pserver
+ internet-topology:
+ type: string
+ description: internet topology of Pserver
+ in-maint:
+ type: boolean
+ pservers:
+ description: |
+ Collection of compute hosts.
+ properties:
+ pserver:
type: array
- items:
- $ref: "#/definitions/named-query-element"
- related-lookups:
+ items:
+ $ref: "#/patchDefinitions/pserver"
+ query-parameters:
+ description: |
+ QueryParameters for performing a named-query or model query
+ properties:
+ named-query:
+ type: object
+ $ref: "#/patchDefinitions/named-query"
+ overloaded-model:
+ type: object
+ $ref: "#/patchDefinitions/overloaded-model"
+ related-lookup:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query-element( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ required:
+ - related-lookup-uuid
+ - source-node-type
+ - source-node-property
+ - target-node-type
+ - target-node-property
+ properties:
+ related-lookup-uuid:
+ type: string
+ source-node-type:
+ type: string
+ source-node-property:
+ type: string
+ target-node-type:
+ type: string
+ target-node-property:
+ type: string
+ property-collect-list:
+ type: string
+ related-lookups:
+ properties:
+ related-lookup:
type: array
- items:
- $ref: "#/definitions/related-lookup"
- property-constraints:
+ items:
+ $ref: "#/patchDefinitions/related-lookup"
+ related-to-property:
+ properties:
+ property-key:
+ type: string
+ description: Key part of a key/value pair
+ property-value:
+ type: string
+ description: Value part of a key/value pair
+ relationship:
+ properties:
+ related-to:
+ type: string
+ description: A keyword provided by A&AI to indicate type of node.
+ related-link:
+ type: string
+ description: URL to the object in A&AI.
+ relationship-data:
type: array
- items:
- $ref: "#/definitions/property-constraint"
- relationship-list:
+ items:
+ $ref: "#/patchDefinitions/relationship-data"
+ related-to-property:
type: array
- items:
- $ref: "#/definitions/relationship"
- named-query-elements:
+ items:
+ $ref: "#/patchDefinitions/related-to-property"
+ relationship-data:
+ required:
+ - relationship-key
+ - relationship-value
properties:
- named-query-element:
+ relationship-key:
+ type: string
+ description: A keyword provided by A&AI to indicate an attribute.
+ relationship-value:
+ type: string
+ description: Value of the attribute.
+ reserved-prop-names:
+ description: |
+ Internal map to define some reserved properties of a vertex
+ properties:
+ last-mod-source-of-truth:
+ type: string
+ aai-node-type:
+ type: string
+ aai-created-ts:
+ type: integer
+ format: int64
+ aai-unique-key:
+ type: string
+ aai-last-mod-ts:
+ type: integer
+ format: int64
+ source-of-truth:
+ type: string
+ aai-uri:
+ type: string
+ response-list:
+ description: |
+ Response container for the results of a named-query or model query
+ properties:
+ inventory-response-items:
+ type: object
+ $ref: "#/patchDefinitions/inventory-response-items"
+ result-data:
+ properties:
+ resource-type:
+ type: string
+ description: The specific type of node in the A&AI graph
+ resource-link:
+ type: string
+ description: The URL to the specific resource
+ route-table-reference:
+ description: |
+ Openstack route table reference.
+ ###### Related Nodes
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)
+ required:
+ - route-table-reference-id
+ - route-table-reference-fqdn
+ properties:
+ route-table-reference-id:
+ type: string
+ description: Route Table Reference id, UUID assigned to this instance.
+ route-table-reference-fqdn:
+ type: string
+ description: FQDN entry in the route table.
+ route-table-references:
+ description: |
+ Collection of openstack route table references
+ properties:
+ route-table-reference:
type: array
items:
- $ref: "#/definitions/named-query-element"
- named-query:
+ $ref: "#/patchDefinitions/route-table-reference"
+ route-target:
description: |
- TBD
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
+ Route target information
###### Related Nodes
- - TO model (One2Many)
- - TO named-query-element (comprises named-query, One2One)
+ - TO vpn-binding( route-target org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2ONE)
required:
- - named-query-uuid
- - named-query-name
- - named-query-version
+ - global-route-target
+ - route-target-role
properties:
- named-query-uuid:
+ global-route-target:
type: string
- named-query-name:
+ description: Number used to identify an RT, globally unique in the network
+ route-target-role:
type: string
- named-query-version:
+ description: Role assigned to this route target
+ route-targets:
+ description: |
+ Collection of route target information
+ properties:
+ route-target:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/route-target"
+ routing-instance:
+ description: |
+ ###### Related Nodes
+ - TO site-pair-set( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)
+ - FROM site-pair( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)
+ - ROUTING-INSTANCE is DELETED when these are DELETED SITE-PAIR
+ required:
+ - routing-instance-id
+ properties:
+ routing-instance-id:
type: string
- required-input-param:
+ description: Unique id of routing instance
+ rpm-owner:
type: string
- description:
+ description: rpm owner
+ routing-instances:
+ description: |
+ set of probes related to generic-vnf routing instance
+ properties:
+ routing-instance:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/routing-instance"
+ sdn-zone-response:
+ properties:
+ oam-networks:
+ type: object
+ $ref: "#/patchDefinitions/oam-networks"
+ az-and-dvs-switches:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/az-and-dvs-switches"
+ search:
+ properties:
+ edge-tag-query-result:
+ type: object
+ $ref: "#/patchDefinitions/edge-tag-query-result"
+ edge-tag-query-request:
+ type: object
+ $ref: "#/patchDefinitions/edge-tag-query-request"
+ search-results:
+ type: object
+ $ref: "#/patchDefinitions/search-results"
+ sdn-zone-response:
+ type: object
+ $ref: "#/patchDefinitions/sdn-zone-response"
+ search-results:
+ properties:
+ result-data:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/result-data"
+ secondary-filt:
+ description: |
+ SecondaryFilt for performing a named-query or model query
+ secondary-filter:
+ properties:
+ property-name:
type: string
- resource-version:
+ filter-type:
type: string
- named-query-elements:
+ property-value:
+ type: string
+ secondary-filts:
+ description: |
+ SecondaryFilts for performing a named-query or model query
+ properties:
+ secondary-filt:
type: array
- items:
- $ref: "#/definitions/named-query-element"
- relationship-list:
+ items:
+ $ref: "#/patchDefinitions/secondary-filt"
+ segmentation-assignment:
+ description: |
+ Openstack segmentation assignment.
+ ###### Related Nodes
+ - TO l3-network( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ required:
+ - segmentation-id
+ properties:
+ segmentation-id:
+ type: string
+ description: Route Table Reference id, UUID assigned to this instance.
+ segmentation-assignments:
+ description: |
+ Collection of openstack segmentation assignments
+ properties:
+ segmentation-assignment:
type: array
- items:
- $ref: "#/definitions/relationship"
- named-queries:
+ items:
+ $ref: "#/patchDefinitions/segmentation-assignment"
+ service:
+ description: |
+ Stand-in for service model definitions. Likely to be deprecated in favor of models from ASDC. Does not strictly map to ASDC services.
+ required:
+ - service-id
+ - service-description
properties:
- named-query:
+ service-id:
+ type: string
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ service-description:
+ type: string
+ description: Description of the service
+ service-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ service-capabilities:
+ description: |
+ Collection of service capabilities.
+ properties:
+ service-capability:
type: array
items:
- $ref: "#/definitions/named-query"
+ $ref: "#/patchDefinitions/service-capability"
+ service-capability:
+ description: |
+ Early definition of server/resource pairings, likely to be replaced by models. No new use should be made of this.
+ ###### Related Nodes
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - SERVICE-CAPABILITY cannot be deleted if linked to AVAILABILITY-ZONE,OAM-NETWORK
+ required:
+ - service-type
+ - vnf-type
+ properties:
+ service-type:
+ type: string
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
service-design-and-creation:
description: |
Namespace for objects managed by ASDC
@@ -39333,67 +55689,54 @@ definitions:
vnf-images:
type: array
items:
- $ref: "#/definitions/vnf-image"
+ $ref: "#/patchDefinitions/vnf-image"
services:
type: array
items:
- $ref: "#/definitions/service"
+ $ref: "#/patchDefinitions/service"
service-capabilities:
type: array
items:
- $ref: "#/definitions/service-capability"
+ $ref: "#/patchDefinitions/service-capability"
models:
type: array
items:
- $ref: "#/definitions/model"
+ $ref: "#/patchDefinitions/model"
named-queries:
type: array
items:
- $ref: "#/definitions/named-query"
- logical-link:
+ $ref: "#/patchDefinitions/named-query"
+ service-instance:
description: |
- Logical links generally connect l-interfaces but are used to express logical connectivity between two points
- ###### Default Delete Scope
- THIS_NODE_ONLY
- ###### Related Nodes
- - TO lag-link (Many2Many)
- - TO pnf (Many2Many)
- - TO logical-link (One2Many)
- - TO generic-vnf (Many2Many)
- - TO pserver (Many2Many)
- - TO cloud-region (Many2Many)
- - TO vpn-binding (Many2Many)
- - FROM l-interface
- - FROM p-interface
- - FROM service-instance
- - FROM virtual-data-center
- - FROM vlan
- - FROM logical-link
+ Instance of a service
+ ###### Related Nodes
+ - TO generic-vnf( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)
+ - TO l3-network( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)
+ - TO allotted-resource( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY)
+ - TO connector( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)
+ - TO ctag-assignment( service-instance org.onap.relationships.inventory.Uses ctag-assignment, ONE2MANY)
+ - TO cvlan-tag( service-instance org.onap.relationships.inventory.ComposedOf cvlan-tag, MANY2MANY)
+ - TO instance-group( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO logical-link( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - TO pnf( service-instance org.onap.relationships.inventory.ComposedOf pnf, ONE2MANY)
+ - TO service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)
+ - TO vlan( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)
+ - TO service-subscription( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)
+ - TO vce( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)
+ - SERVICE-INSTANCE is DELETED when these are DELETED ALLOTTED-RESOURCE,METADATUM
+ - SERVICE-INSTANCE deletion means associated objects of these types are also DELETED:LOGICAL-LINK
required:
- - link-name
- - link-type
+ - service-instance-id
properties:
- link-name:
- type: string
- description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
- link-type:
- type: string
- description: Type of logical link, e.g., evc
- speed-value:
- type: string
- description: Captures the numeric part of the speed
- speed-units:
- type: string
- description: Captures the units corresponding to the speed
- ip-version:
- type: string
- description: v4, v6, or ds for dual stack
- routing-protocol:
+ service-instance-id:
type: string
- description: For example, static or BGP
- resource-version:
+ description: Uniquely identifies this instance of a service
+ service-instance-name:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ description: This field will store a name assigned to the service-instance.
persona-model-id:
type: string
description: the ASDC model id for this resource or service model.
@@ -39409,79 +55752,74 @@ definitions:
widget-model-version:
type: string
description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
- operational-status:
+ bandwidth-total:
type: string
- description: Indication of operational status of the logical link.
- prov-status:
+ description: Indicates the total bandwidth to be used for this service.
+ bandwidth-up-wan1:
type: string
- description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
- link-role:
+ description: indicates the upstream bandwidth this service will use on the WAN1 port of the physical device.
+ bandwidth-down-wan1:
type: string
- description: Indication of the network use of the logical link.
- link-name2:
+ description: indicates the downstream bandwidth this service will use on the WAN1 port of the physical device.
+ bandwidth-up-wan2:
type: string
- description: Alias or alternate name (CLCI or D1 name).
- link-id:
+ description: indicates the upstream bandwidth this service will use on the WAN2 port of the physical device.
+ bandwidth-down-wan2:
type: string
- description: UUID of the logical-link, SDNC generates this.
- circuit-id:
+ description: indicates the downstream bandwidth this service will use on the WAN2 port of the physical device.
+ vhn-portal-url:
type: string
- description: Circuit id
- purpose:
+ description: URL customers will use to access the vHN Portal.
+ service-instance-location-id:
type: string
- description: Reason for this entity, role it is playing
- relationship-list:
- type: array
- items:
- $ref: "#/definitions/relationship"
- logical-links:
+ description: An identifier that customers assign to the location where this service is being used.
+ service-instances:
description: |
- Collection of logical connections
+ Collection of service instances
properties:
- logical-link:
+ service-instance:
type: array
items:
- $ref: "#/definitions/logical-link"
- class-of-service:
+ $ref: "#/patchDefinitions/service-instance"
+ service-subscription:
description: |
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Object that group service instances.
###### Related Nodes
- - FROM site-pair (is composed of class-of-service)
+ - TO customer( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)
+ - TO tenant( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)
+ - SERVICE-SUBSCRIPTION is DELETED when these are DELETED SERVICE-INSTANCE
required:
- - cos
+ - service-type
properties:
- cos:
- type: string
- description: unique identifier of probe
- probe-id:
- type: string
- description: identifier of probe
- probe-type:
+ service-type:
type: string
- description: type of probe
- resource-version:
+ description: Value defined by orchestration to identify this service across ECOMP.
+ temp-ub-sub-account-id:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- relationship-list:
+ description: This property will be deleted from A&AI in the near future. Only stop gap solution.
+ service-subscriptions:
+ description: |
+ Collection of objects that group service instances.
+ properties:
+ service-subscription:
type: array
- items:
- $ref: "#/definitions/relationship"
- classes-of-service:
+ items:
+ $ref: "#/patchDefinitions/service-subscription"
+ services:
description: |
- class-of-service of probe
+ Collection of service model definitions. Likely to be deprecated in favor of models from ASDC.
properties:
- class-of-service:
+ service:
type: array
items:
- $ref: "#/definitions/class-of-service"
+ $ref: "#/patchDefinitions/service"
site-pair:
description: |
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
###### Related Nodes
- - TO class-of-service (comprises site-pair, Many2Many)
- - FROM routing-instance (is composed of site-pair)
+ - TO routing-instance( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)
+ - FROM class-of-service( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)
+ - SITE-PAIR is DELETED when these are DELETED CLASS-OF-SERVICE
required:
- site-pair-id
properties:
@@ -39503,17 +55841,27 @@ definitions:
destination-equip-type:
type: string
description: The type of destinatination equipment. Could be Router, etc.
- resource-version:
+ site-pair-set:
+ description: |
+ Set of instances for probes used to measure service level agreements
+ ###### Related Nodes
+ - TO generic-vnf( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM routing-instance( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)
+ - SITE-PAIR-SET is DELETED when these are DELETED ROUTING-INSTANCE
+ required:
+ - site-pair-set-id
+ properties:
+ site-pair-set-id:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- classes-of-service:
- type: array
- items:
- $ref: "#/definitions/class-of-service"
- relationship-list:
+ description: Unique id of site pair set.
+ site-pair-sets:
+ description: |
+ Collection of sets of instances for probes related to generic-vnf
+ properties:
+ site-pair-set:
type: array
- items:
- $ref: "#/definitions/relationship"
+ items:
+ $ref: "#/patchDefinitions/site-pair-set"
site-pairs:
description: |
probe within a set
@@ -39521,83 +55869,720 @@ definitions:
site-pair:
type: array
items:
- $ref: "#/definitions/site-pair"
- routing-instance:
+ $ref: "#/patchDefinitions/site-pair"
+ snapshot:
description: |
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
+ Openstack snapshot
###### Related Nodes
- - TO site-pair (comprises routing-instance, Many2Many)
- - FROM site-pair-set (is composed of routing-instance)
+ - TO cloud-region( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)
required:
- - routing-instance-id
+ - snapshot-id
properties:
- routing-instance-id:
+ snapshot-id:
type: string
- description: Unique id of routing instance
- rpm-owner:
+ description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
+ snapshot-name:
type: string
- description: rpm owner
- resource-version:
+ description: Snapshot name
+ snapshot-architecture:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- site-pairs:
+ description: Operating system architecture
+ snapshot-os-distro:
+ type: string
+ description: The common name of the operating system distribution in lowercase
+ snapshot-os-version:
+ type: string
+ description: The operating system version as specified by the distributor.
+ application:
+ type: string
+ description: The application that the image instantiates.
+ application-vendor:
+ type: string
+ description: The vendor of the application.
+ application-version:
+ type: string
+ description: The version of the application.
+ snapshot-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ prev-snapshot-id:
+ type: string
+ description: This field contains the UUID of the previous snapshot (if any).
+ snapshots:
+ description: |
+ Collection of openstack snapshots
+ properties:
+ snapshot:
type: array
- items:
- $ref: "#/definitions/site-pair"
- relationship-list:
+ items:
+ $ref: "#/patchDefinitions/snapshot"
+ sriov-pf:
+ description: |
+ SR-IOV Physical Function
+ ###### Related Nodes
+ - TO p-interface( sriov-pf org.onap.relationships.inventory.BelongsTo p-interface, ONE2ONE)
+ - FROM sriov-vf( sriov-vf org.onap.relationships.inventory.Uses sriov-pf, MANY2ONE)
+ required:
+ - pf-pci-id
+ properties:
+ pf-pci-id:
+ type: string
+ description: Identifier for the sriov-pf
+ sriov-pfs:
+ description: |
+ Collection of SR-IOV Physical Functions.
+ properties:
+ sriov-pf:
type: array
- items:
- $ref: "#/definitions/relationship"
- routing-instances:
+ items:
+ $ref: "#/patchDefinitions/sriov-pf"
+ sriov-vf:
description: |
- set of probes related to generic-vnf routing instance
+ SR-IOV Virtual Function (not to be confused with virtual network function)
+ ###### Related Nodes
+ - TO l-interface( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)
+ required:
+ - pci-id
properties:
- routing-instance:
+ pci-id:
+ type: string
+ description: PCI ID used to identify the sriov-vf
+ vf-vlan-filter:
+ type: string
+ description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM.
+ vf-mac-filter:
+ type: string
+ description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM.
+ vf-vlan-strip:
+ type: boolean
+ description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM.
+ vf-vlan-anti-spoof-check:
+ type: boolean
+ description: This option ensures anti VLAN spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
+ vf-mac-anti-spoof-check:
+ type: boolean
+ description: This option ensures anti MAC spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
+ vf-mirrors:
+ type: string
+ description: This option defines the set of Mirror objects which essentially mirrors the traffic from source to set of collector VNF Ports.
+ vf-broadcast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows all broadcast traffic to reach the VM
+ vf-unknown-multicast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows unknown multicast traffic to reach the VM
+ vf-unknown-unicast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows unknown unicast traffic to reach the VM
+ vf-insert-stag:
+ type: boolean
+ description: This option, if set to true, instructs to insert outer tag after traffic comes out of VM.
+ vf-link-status:
+ type: string
+ description: This option is used to set the link status. Valid values as of 1607 are on, off, and auto.
+ sriov-vfs:
+ description: |
+ Collection of SR-IOV Virtual Functions.
+ properties:
+ sriov-vf:
type: array
items:
- $ref: "#/definitions/routing-instance"
- site-pair-set:
+ $ref: "#/patchDefinitions/sriov-vf"
+ start-node-filter:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ subnet:
description: |
- Set of instances for probes used to measure service level agreements
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
###### Related Nodes
- - TO routing-instance (comprises site-pair-set, Many2Many)
- - FROM generic-vnf
+ - TO l3-network( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - SUBNET cannot be deleted if linked to L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST
required:
- - site-pair-set-id
+ - subnet-id
+ - dhcp-enabled
properties:
- site-pair-set-id:
+ subnet-id:
type: string
- description: Unique id of site pair set.
- resource-version:
+ description: Subnet ID, should be UUID.
+ subnet-name:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- routing-instances:
+ description: Name associated with the subnet.
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of this subnet
+ gateway-address:
+ type: string
+ description: gateway ip address
+ network-start-address:
+ type: string
+ description: network start address
+ cidr-mask:
+ type: string
+ description: cidr mask
+ ip-version:
+ type: string
+ description: ip version
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ dhcp-enabled:
+ type: boolean
+ dhcp-start:
+ type: string
+ description: the start address reserved for use by dhcp
+ dhcp-end:
+ type: string
+ description: the last address reserved for use by dhcp
+ subnets:
+ properties:
+ subnet:
type: array
- items:
- $ref: "#/definitions/routing-instance"
- relationship-list:
+ items:
+ $ref: "#/patchDefinitions/subnet"
+ tagged-inventory-item-list:
+ properties:
+ inventory-item:
type: array
- items:
- $ref: "#/definitions/relationship"
- site-pair-sets:
+ items:
+ $ref: "#/patchDefinitions/inventory-item"
+ tenant:
description: |
- Collection of sets of instances for probes related to generic-vnf
+ Openstack tenant
+ ###### Related Nodes
+ - TO cloud-region( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO group-assignment( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)
+ - TO l3-network( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO volume-group( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - FROM service-subscription( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)
+ - FROM vserver( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)
+ - TENANT cannot be deleted if linked to VSERVER
+ required:
+ - tenant-id
+ - tenant-name
properties:
- site-pair-set:
+ tenant-id:
+ type: string
+ description: Unique id relative to the cloud-region.
+ tenant-name:
+ type: string
+ description: Readable name of tenant
+ tenants:
+ description: |
+ Collection of openstack tenants.
+ properties:
+ tenant:
type: array
items:
- $ref: "#/definitions/site-pair-set"
+ $ref: "#/patchDefinitions/tenant"
+ tunnel-xconnect:
+ description: |
+ Represents the specifics of a tunnel cross connect piece of a resource that gets separately allotted
+ ###### Related Nodes
+ - TO allotted-resource( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)
+ required:
+ - id
+ - bandwidth-up-wan1
+ - bandwidth-down-wan1
+ - bandwidth-up-wan2
+ - bandwidth-down-wan2
+ properties:
+ id:
+ type: string
+ description: Allotted Resource id UUID assigned to this instance.
+ bandwidth-up-wan1:
+ type: string
+ description: The WAN uplink bandwidth for WAN1
+ bandwidth-down-wan1:
+ type: string
+ description: The WAN downlink bandwidth for WAN1
+ bandwidth-up-wan2:
+ type: string
+ description: The WAN uplink bandwidth for WAN2
+ bandwidth-down-wan2:
+ type: string
+ description: The WAN downlink bandwidth for WAN2
+ tunnel-xconnects:
+ description: |
+ This object is used to store the specific tunnel cross connect aspects of an allotted resource
+ properties:
+ tunnel-xconnect:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/tunnel-xconnect"
+ update:
+ description: |
+ Serves a PATCH like function. Does not enforce concurrency control. Clear each usage with AAI team.
+ required:
+ - update-node-type
+ properties:
+ update-node-type:
+ type: string
+ update-node-key:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/update-node-key"
+ update-node-uri:
+ type: string
+ action:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/action"
+ update-node-key:
+ properties:
+ key-name:
+ type: string
+ key-value:
+ type: string
+ vce:
+ description: |
+ Virtual Customer Edge Router, used specifically for Gamma. This object is deprecated.
+ ###### Related Nodes
+ - TO availability-zone( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - TO complex( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)
+ - TO vserver( vce tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM entitlement( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM license( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM port-group( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)
+ - VCE is DELETED when these are DELETED ENTITLEMENT,LICENSE,PORT-GROUP
+ required:
+ - vnf-id
+ - vnf-name
+ - vnf-type
+ properties:
+ vnf-id:
+ type: string
+ description: Unique id of VNF. This is unique across the graph.
+ vnf-name:
+ type: string
+ description: Name of VNF.
+ vnf-name2:
+ type: string
+ description: Alternate name of VNF.
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ service-id:
+ type: string
+ description: Unique identifier of service, does not strictly map to ASDC services, SOON TO BE DEPRECATED.
+ regional-resource-zone:
+ type: string
+ description: Regional way of organizing pservers, source of truth should define values
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ operational-state:
+ type: string
+ description: Indicator for whether the resource is considered operational
+ license-key:
+ type: string
+ description: OBSOLETE - do not use
+ equipment-role:
+ type: string
+ description: Network role being played by this VNF
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ vpe-id:
+ type: string
+ description: Unique ID of VPE connected to this VCE.
+ v6-vce-wan-address:
+ type: string
+ description: Valid v6 IP address for the WAN Link on this router. Implied length of /64.
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure vce, also used for troubleshooting and is IP used for traps generated by VCE.
+ vces:
+ description: |
+ Collection of Virtual Customer Edge Routers, used specifically for Gamma. This object is deprecated.
+ properties:
+ vce:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vce"
+ vf-module:
+ description: |
+ a deployment unit of VNFCs
+ ###### Related Nodes
+ - TO generic-vnf( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO l3-network( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)
+ - TO vnfc( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)
+ - TO volume-group( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)
+ - TO vserver( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)
+ - VF-MODULE cannot be deleted if linked to VNFC
+ required:
+ - vf-module-id
+ - is-base-vf-module
+ properties:
+ vf-module-id:
+ type: string
+ description: Unique ID of vf-module.
+ vf-module-name:
+ type: string
+ description: Name of vf-module
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance.
+ orchestration-status:
+ type: string
+ description: orchestration status of this vf-module, mastered by MSO
+ is-base-vf-module:
+ type: boolean
+ vf-modules:
+ description: |
+ Collection of vf-modules, a deployment unit of VNFCs
+ properties:
+ vf-module:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vf-module"
+ vig-server:
+ description: |
+ vig-server contains information about a vig server used for IPSec-configuration. Populated by SDN-C from 1607
+ ###### Related Nodes
+ - TO ipsec-configuration( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)
+ required:
+ - vig-address-type
+ properties:
+ vig-address-type:
+ type: string
+ description: indicates whether the VIG is for AVPN or INTERNET
+ ipaddress-v4-vig:
+ type: string
+ description: v4 IP of the vig server
+ ipaddress-v6-vig:
+ type: string
+ description: v6 IP of the vig server
+ vig-servers:
+ properties:
+ vig-server:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vig-server"
+ vip-ipv4-address-list:
+ description: |
+ IPv4 Address Range
+ ###### Related Nodes
+ - TO cloud-region( vip-ipv4-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO instance-group( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO subnet( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv4-address-list, MANY2MANY)
+ required:
+ - vip-ipv4-address
+ properties:
+ vip-ipv4-address:
+ type: string
+ description: IP address
+ vip-ipv4-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 32 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ vip-ipv6-address-list:
+ description: |
+ IPv6 Address Range
+ ###### Related Nodes
+ - TO cloud-region( vip-ipv6-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO instance-group( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO subnet( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv6-address-list, MANY2MANY)
+ required:
+ - vip-ipv6-address
+ properties:
+ vip-ipv6-address:
+ type: string
+ description: IP address
+ vip-ipv6-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 128 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ virtual-data-center:
+ description: |
+ Virtual organization of cloud infrastructure elements in a data center context
+ ###### Related Nodes
+ - FROM connector( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ required:
+ - vdc-id
+ - vdc-name
+ properties:
+ vdc-id:
+ type: string
+ description: Unique ID of the vdc
+ vdc-name:
+ type: string
+ description: Name of the virtual data center
+ virtual-data-centers:
+ description: |
+ Virtual organization of cloud infrastructure elements in a data center context
+ properties:
+ virtual-data-center:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/virtual-data-center"
+ vlan:
+ description: |
+ Definition of vlan
+ ###### Related Nodes
+ - TO l-interface( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)
+ - TO logical-link( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - TO multicast-configuration( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ - VLAN is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST
+ - VLAN deletion means associated objects of these types are also DELETED:LOGICAL-LINK
+ required:
+ - vlan-interface
+ properties:
+ vlan-interface:
+ type: string
+ description: String that identifies the interface
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ vlans:
+ properties:
+ vlan:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vlan"
+ vnf:
+ description: |
+ Abstract vnf class
+ required:
+ - vnf-id
+ properties:
+ vnf-id:
+ type: string
+ description: Unique id of VNF. This is unique across the graph.
+ vnf-image:
+ description: |
+ Image object that pertain to a VNF that doesn't have associated vservers. This is a kludge.
+ ###### Related Nodes
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)
+ - VNF-IMAGE cannot be deleted if linked to GENERIC-VNF
+ required:
+ - vnf-image-uuid
+ - application
+ - application-vendor
+ properties:
+ vnf-image-uuid:
+ type: string
+ description: Unique ID of this asset
+ application:
+ type: string
+ description: The application that the image instantiates.
+ application-vendor:
+ type: string
+ description: The vendor of the application.
+ application-version:
+ type: string
+ description: The version of the application.
+ selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ vnf-images:
+ description: |
+ Collection of image objects that pertain to a VNF that doesn't have associated vservers. This is a kludge.
+ properties:
+ vnf-image:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vnf-image"
+ vnfc:
+ description: |
+ ###### Related Nodes
+ - TO generic-vnf( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vserver( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)
+ required:
+ - vnfc-name
+ - vnfc-function-code
+ - vnfc-type
+ - in-maint
+ - is-closed-loop-disabled
+ properties:
+ vnfc-name:
+ type: string
+ description: Unique ID of vnfc.
+ vnfc-function-code:
+ type: string
+ description: function code
+ vnfc-type:
+ type: string
+ description: type
+ prov-status:
+ type: string
+ description: prov status of this vnfc
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by APP-C
+ ipaddress-v4-oam-vip:
+ type: string
+ description: Oam V4 vip address of this vnfc
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
+ group-notation:
+ type: string
+ description: Group notation of VNFC
+ vnfcs:
+ description: |
+ virtual network components associated with a vserver from application controller.
+ properties:
+ vnfc:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vnfc"
+ volume:
+ description: |
+ Ephemeral Block storage volume.
+ ###### Related Nodes
+ - FROM vserver (PARENT of volume, vserver tosca.relationships.AttachesTo volume)
+ required:
+ - volume-id
+ - volume-selflink
+ properties:
+ volume-id:
+ type: string
+ description: Unique ID of block storage volume relative to the vserver.
+ volume-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ volume-group:
+ description: |
+ Persistent block-level storage.
+ ###### Related Nodes
+ - TO cloud-region( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO complex( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ required:
+ - volume-group-id
+ - volume-group-name
+ - vnf-type
+ properties:
+ volume-group-id:
+ type: string
+ description: Unique ID of volume-group.
+ volume-group-name:
+ type: string
+ description: Name of the volume group.
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this volume-group
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ orchestration-status:
+ type: string
+ description: Orchestration status of this volume-group
+ persona-model-customization-id:
+ type: string
+ description: captures the id of all the configuration used to customize the resource for the service.
+ vf-module-persona-model-customization-id:
+ type: string
+ description: helps relate the volume group to the vf-module whose components will require the volume group
+ volume-groups:
+ description: |
+ Collection of persistent block-level storage.
+ properties:
+ volume-group:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/volume-group"
+ volumes:
+ description: |
+ Collection of ephemeral Block storage volumes.
+ properties:
+ volume:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/volume"
+ vpls-pe:
+ description: |
+ VPLS Provider Edge routers.
+ ###### Related Nodes
+ - TO complex( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO ctag-pool( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - VPLS-PE is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
+ required:
+ - equipment-name
+ properties:
+ equipment-name:
+ type: string
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by VPE (v4-loopback0-ip-address).
+ equipment-role:
+ type: string
+ description: Client should send valid enumerated value, e.g., VPLS-PE.
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Temporary location for stag to get to VCE
+ vpls-pes:
+ description: |
+ Collection of VPLS Provider Edge routers
+ properties:
+ vpls-pe:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vpls-pe"
vpn-binding:
description: |
VPN binding
- ###### Default Delete Scope
- ERROR_4_IN_EDGES_OR_CASCADE
###### Related Nodes
- - FROM l3-network
- - FROM logical-link
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - VPN-BINDING cannot be deleted if linked to L3-NETWORK,LOGICAL-LINK
required:
- vpn-id
- vpn-name
@@ -39625,106 +56610,737 @@ definitions:
route-target-role:
type: string
description: Role assigned to this route target
+ vpn-bindings:
+ properties:
+ vpn-binding:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vpn-binding"
+ vserver:
+ description: |
+ Virtual Servers, aka virtual machine or VM.
+ ###### Related Nodes
+ - TO tenant( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)
+ - TO flavor( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)
+ - TO image( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)
+ - TO pserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)
+ - TO snapshot( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)
+ - TO volume (CHILD of vserver, vserver tosca.relationships.AttachesTo volume, ONE2MANY)
+ - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM vce( vce tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)
+ - FROM vnfc( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)
+ - VSERVER is DELETED when these are DELETED L-INTERFACE
+ - VSERVER deletion means associated objects of these types are also DELETED:VOLUME
+ required:
+ - vserver-id
+ - vserver-name
+ - vserver-selflink
+ - in-maint
+ - is-closed-loop-disabled
+ properties:
+ vserver-id:
+ type: string
+ description: Unique identifier for this vserver relative to its tenant
+ vserver-name:
+ type: string
+ description: Name of vserver
+ vserver-name2:
+ type: string
+ description: Alternative name of vserver
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ vserver-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
+ vservers:
+ description: |
+ Collection of virtual Servers, aka virtual machines or VMs.
+ properties:
+ vserver:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/vserver"
+ zone:
+ description: |
+ A zone is a grouping of assets in a location homing to the same connections into the CBB
+ ###### Related Nodes
+ - TO complex( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM pnf( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ required:
+ - zone-id
+ - zone-name
+ - design-type
+ - zone-context
+ properties:
+ zone-id:
+ type: string
+ description: Code assigned by AIC to the zone
+ zone-name:
+ type: string
+ description: English name associated with the zone
+ design-type:
+ type: string
+ description: Design of zone [Medium/Large?]
+ zone-context:
+ type: string
+ description: Context of zone [production/test]
+ status:
+ type: string
+ description: Status of a zone.
+ zones:
+ description: |
+ Collection of zones
+ properties:
+ zone:
+ type: array
+ items:
+ $ref: "#/patchDefinitions/zone"
+getDefinitions:
+ aai-internal:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ action:
+ properties:
+ action-type:
+ type: string
+ action-data:
+ type: array
+ items:
+ $ref: "#/getDefinitions/action-data"
+ action-data:
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ actions:
+ description: |
+ APIs that are more action related than REST (e.g., notify, update).
+ properties:
+ update:
+ type: object
+ $ref: "#/getDefinitions/update"
+ notify:
+ type: object
+ $ref: "#/getDefinitions/notify"
+ allotted-resource:
+ description: |
+ Represents a slice or partial piece of a resource that gets separately allotted
+ ###### Related Nodes
+ - TO generic-vnf( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY)
+ - TO instance-group( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO l3-network( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY)
+ - TO vlan( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY)
+ - TO service-instance( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM tunnel-xconnect( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY)
+ - ALLOTTED-RESOURCE is DELETED when these are DELETED TUNNEL-XCONNECT
+ required:
+ - id
+ properties:
+ id:
+ type: string
+ description: Allotted Resource id UUID assigned to this instance.
+ description:
+ type: string
+ description: The descriptive information assigned to this allotted resource instance
+ selflink:
+ type: string
+ description: Link back to more information in the controller
+ persona-model-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ persona-model-customization-id:
+ type: string
+ description: captures the id of all the configuration used to customize the resource for the service.
+ resource-version:
+ type: string
+ description: Concurrency value
+ tunnel-xconnects:
+ type: array
+ items:
+ $ref: "#/getDefinitions/tunnel-xconnect"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ allotted-resources:
+ description: |
+ This object is used to store slices of services being offered
+ properties:
+ allotted-resource:
+ type: array
+ items:
+ $ref: "#/getDefinitions/allotted-resource"
+ availability-zone:
+ description: |
+ Availability zone, a collection of compute hosts/pservers
+ ###### Related Nodes
+ - TO complex( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO service-capability( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - TO cloud-region( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM ctag-pool( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM dvs-switch( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - FROM pserver( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)
+ - FROM vce( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - AVAILABILITY-ZONE cannot be deleted if linked to CTAG-POOL,DVS-SWITCH,GENERIC-VNF,PSERVER,VCE
+ required:
+ - availability-zone-name
+ - hypervisor-type
+ properties:
+ availability-zone-name:
+ type: string
+ description: Name of the availability zone. Unique across a cloud region
+ hypervisor-type:
+ type: string
+ description: Type of hypervisor. Source of truth should define valid values.
+ operational-state:
+ type: string
+ description: State that indicates whether the availability zone should be used, etc. Source of truth should define valid values.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- description: l3-networks relate to vpn-bindings
- vpn-bindings:
+ $ref: "#/getDefinitions/relationship"
+ availability-zones:
+ description: |
+ Collection of availability zones
properties:
- vpn-binding:
+ availability-zone:
type: array
items:
- $ref: "#/definitions/vpn-binding"
- vpls-pe:
+ $ref: "#/getDefinitions/availability-zone"
+ az-and-dvs-switches:
+ properties:
+ dvs-switches:
+ type: object
+ $ref: "#/getDefinitions/dvs-switches"
+ availability-zone:
+ type: object
+ $ref: "#/getDefinitions/availability-zone"
+ business:
+ description: |
+ Namespace for business related constructs
+ properties:
+ connectors:
+ type: array
+ items:
+ $ref: "#/getDefinitions/connector"
+ customers:
+ type: array
+ items:
+ $ref: "#/getDefinitions/customer"
+ class-of-service:
description: |
- VPLS Provider Edge routers.
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
###### Related Nodes
- - TO complex (Many2Many)
- - TO ctag-pool (Many2Many)
- - TO p-interface (comprises vpls-pe, Many2Many)
- - TO lag-interface (comprises vpls-pe, Many2Many)
+ - TO site-pair( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)
required:
- - equipment-name
+ - cos
properties:
- equipment-name:
+ cos:
type: string
- prov-status:
+ description: unique identifier of probe
+ probe-id:
type: string
- description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
- ipv4-oam-address:
+ description: identifier of probe
+ probe-type:
type: string
- description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by VPE (v4-loopback0-ip-address).
- equipment-role:
+ description: type of probe
+ resource-version:
type: string
- description: Client should send valid enumerated value, e.g., VPLS-PE.
- vlan-id-outer:
- type: integer
- format: int64
- description: Temporary location for stag to get to VCE
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ classes-of-service:
+ description: |
+ class-of-service of probe
+ properties:
+ class-of-service:
+ type: array
+ items:
+ $ref: "#/getDefinitions/class-of-service"
+ cloud-infrastructure:
+ description: |
+ Namespace for cloud infrastructure.
+ properties:
+ complexes:
+ type: array
+ items:
+ $ref: "#/getDefinitions/complex"
+ cloud-regions:
+ type: array
+ items:
+ $ref: "#/getDefinitions/cloud-region"
+ network-profiles:
+ type: array
+ items:
+ $ref: "#/getDefinitions/network-profile"
+ pservers:
+ type: array
+ items:
+ $ref: "#/getDefinitions/pserver"
+ virtual-data-centers:
+ type: array
+ items:
+ $ref: "#/getDefinitions/virtual-data-center"
+ cloud-region:
+ description: |
+ cloud-region designates an installation of a cloud cluster or region or instantiation.
+ ###### Related Nodes
+ - TO complex( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO l3-network( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO zone( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM dvs-switch( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM flavor( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM group-assignment( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM image( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM snapshot( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM volume-group( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn cloud-region, MANY2MANY)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)
+ - CLOUD-REGION cannot be deleted if linked to DVS-SWITCH,FLAVOR,GROUP-ASSIGNMENT,IMAGE,OAM-NETWORK,SNAPSHOT,TENANT,VOLUME-GROUP
+ - CLOUD-REGION is DELETED when these are DELETED AVAILABILITY-ZONE
+ required:
+ - cloud-owner
+ - cloud-region-id
+ properties:
+ cloud-owner:
+ type: string
+ description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+ cloud-region-id:
+ type: string
+ description: Identifier used by the vendor for the region. Second part of composite key
+ cloud-type:
+ type: string
+ description: Type of the cloud (e.g., openstack)
+ owner-defined-type:
+ type: string
+ description: Cloud-owner defined type indicator (e.g., dcp, lcp)
+ cloud-region-version:
+ type: string
+ description: Software version employed at the site. NOTE - THIS FIELD IS NOT KEPT UP TO DATE.
+ identity-url:
+ type: string
+ description: URL of the keystone identity service
+ cloud-zone:
+ type: string
+ description: Zone where the cloud is homed. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
+ complex-name:
+ type: string
+ description: complex name for cloud-region instance. NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ volume-groups:
+ type: array
+ items:
+ $ref: "#/getDefinitions/volume-group"
+ tenants:
+ type: array
+ items:
+ $ref: "#/getDefinitions/tenant"
+ flavors:
+ type: array
+ items:
+ $ref: "#/getDefinitions/flavor"
+ group-assignments:
+ type: array
+ items:
+ $ref: "#/getDefinitions/group-assignment"
+ snapshots:
+ type: array
+ items:
+ $ref: "#/getDefinitions/snapshot"
+ images:
+ type: array
+ items:
+ $ref: "#/getDefinitions/image"
+ dvs-switches:
+ type: array
+ items:
+ $ref: "#/getDefinitions/dvs-switch"
+ oam-networks:
+ type: array
+ items:
+ $ref: "#/getDefinitions/oam-network"
+ availability-zones:
+ type: array
+ items:
+ $ref: "#/getDefinitions/availability-zone"
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- p-interfaces:
+ $ref: "#/getDefinitions/relationship"
+ cloud-regions:
+ properties:
+ cloud-region:
+ type: array
+ items:
+ $ref: "#/getDefinitions/cloud-region"
+ complex:
+ description: |
+ Collection of physical locations that can house cloud-regions.
+ ###### Related Nodes
+ - TO l3-network( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM ctag-pool( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)
+ - FROM pnf( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM vce( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)
+ - FROM volume-group( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM vpls-pe( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM zone( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - COMPLEX cannot be deleted if linked to AVAILABILITY-ZONE,CLOUD-REGION,OAM-NETWORK,PNF,PSERVER,VCE,VOLUME-GROUP,VPLS-PE,ZONE
+ - COMPLEX is DELETED when these are DELETED CTAG-POOL
+ required:
+ - physical-location-id
+ - physical-location-type
+ - street1
+ - city
+ - postal-code
+ - country
+ - region
+ properties:
+ physical-location-id:
+ type: string
+ description: Unique identifier for physical location, e.g., CLLI
+ data-center-code:
+ type: string
+ description: Data center code which can be an alternate way to identify a complex
+ complex-name:
+ type: string
+ description: Gamma complex name for LCP instance.
+ identity-url:
+ type: string
+ description: URL of the keystone identity service
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ physical-location-type:
+ type: string
+ description: Type, e.g., central office, data center.
+ street1:
+ type: string
+ street2:
+ type: string
+ city:
+ type: string
+ state:
+ type: string
+ postal-code:
+ type: string
+ country:
+ type: string
+ region:
+ type: string
+ latitude:
+ type: string
+ longitude:
+ type: string
+ elevation:
+ type: string
+ lata:
+ type: string
+ ctag-pools:
type: array
items:
- $ref: "#/definitions/p-interface"
- lag-interfaces:
+ $ref: "#/getDefinitions/ctag-pool"
+ relationship-list:
type: array
items:
- $ref: "#/definitions/lag-interface"
- vpls-pes:
+ $ref: "#/getDefinitions/relationship"
+ complexes:
description: |
- Collection of VPLS Provider Edge routers
+ Collection of physical locations that can house cloud-regions.
properties:
- vpls-pe:
+ complex:
type: array
items:
- $ref: "#/definitions/vpls-pe"
- multicast-configuration:
+ $ref: "#/getDefinitions/complex"
+ configuration:
description: |
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Port Mirror Configuration.
###### Related Nodes
- - FROM vlan
+ - TO allotted-resource( configuration org.onap.relationships.inventory.Uses allotted-resource, ONE2ONE)
+ - TO logical-link( configuration org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo configuration, MANY2ONE)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses configuration, ONE2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses configuration, ONE2MANY)
+ - CONFIGURATION is DELETED when these are DELETED METADATUM
+ - CONFIGURATION deletion means associated objects of these types are also DELETED:ALLOTTED-RESOURCE,LOGICAL-LINK
required:
- - multicast-configuration-id
- - multicast-protocol
- - rp-type
+ - configuration-id
+ - configuration-type
+ - configuration-sub-type
+ - orchestration-status
+ - operational-status
+ - configuration-selflink
+ - model-customization-id
properties:
- multicast-configuration-id:
+ configuration-id:
type: string
- description: Unique id of multicast configuration.
- multicast-protocol:
+ description: UUID assigned to configuration.
+ management-option:
type: string
- description: protocol of multicast configuration
- rp-type:
+ description: Indicates the entity that will manage this feature. Could be an organization or the name of the application as well.
+ configuration-name:
type: string
- description: rp type of multicast configuration
+ description: Name of the configuration.
+ configuration-type:
+ type: string
+ description: port-mirroring-configuration.
+ configuration-sub-type:
+ type: string
+ description: vprobe, pprobe.
+ model-invariant-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ orchestration-status:
+ type: string
+ description: Orchestration status of the configuration.
+ operational-status:
+ type: string
+ description: Indicator for whether the resource is considered operational.
+ configuration-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details from SDN-GC.
+ model-customization-id:
+ type: string
+ description: id of the configuration used to customize the resource
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- multicast-configurations:
+ $ref: "#/getDefinitions/relationship"
+ metadata:
+ type: array
+ items:
+ $ref: "#/getDefinitions/metadatum"
+ configurations:
description: |
- multicast configuration of generic-vnf ip-address
+ Collection of configurations
properties:
- multicast-configuration:
+ configuration:
type: array
items:
- $ref: "#/definitions/multicast-configuration"
+ $ref: "#/getDefinitions/configuration"
+ connector:
+ description: |
+ Collection of resource instances used to connect a variety of disparate inventory widgets
+ ###### Related Nodes
+ - TO virtual-data-center( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)
+ - CONNECTOR is DELETED when these are DELETED METADATUM
+ required:
+ - resource-instance-id
+ properties:
+ resource-instance-id:
+ type: string
+ description: Unique id of resource instance.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ persona-model-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ metadata:
+ type: array
+ items:
+ $ref: "#/getDefinitions/metadatum"
+ connectors:
+ description: |
+ Collection of resource instances used to connect a variety of disparate inventory widgets
+ properties:
+ connector:
+ type: array
+ items:
+ $ref: "#/getDefinitions/connector"
+ constrained-element-set:
+ description: |
+ This is how we would capture constraints defining allowed sets of elements.
+ ###### Related Nodes
+ - TO model-constraint( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)
+ - TO model-element( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM element-choice-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)
+ - CONSTRAINED-ELEMENT-SET is DELETED when these are DELETED ELEMENT-CHOICE-SET
+ required:
+ - constrained-element-set-uuid
+ - constraint-type
+ - check-type
+ properties:
+ constrained-element-set-uuid:
+ type: string
+ constraint-type:
+ type: string
+ check-type:
+ type: string
+ resource-version:
+ type: string
+ element-choice-sets:
+ type: array
+ items:
+ $ref: "#/getDefinitions/element-choice-set"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ constrained-element-sets:
+ properties:
+ constrained-element-set:
+ type: array
+ items:
+ $ref: "#/getDefinitions/constrained-element-set"
+ ctag-assignment:
+ description: |
+ ###### Related Nodes
+ - TO l3-network( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses ctag-assignment, ONE2MANY)
+ required:
+ - vlan-id-inner
+ properties:
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: id.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ ctag-assignments:
+ properties:
+ ctag-assignment:
+ type: array
+ items:
+ $ref: "#/getDefinitions/ctag-assignment"
+ ctag-pool:
+ description: |
+ A collection of C tags (vlan tags) grouped for a specific purpose.
+ ###### Related Nodes
+ - TO complex( ctag-pool org.onap.relationships.inventory.BelongsTo complex, MANY2ONE)
+ - TO availability-zone( ctag-pool org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
+ - FROM vpls-pe( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)
+ required:
+ - target-pe
+ - availability-zone-name
+ - ctag-pool-purpose
+ properties:
+ target-pe:
+ type: string
+ description: The Target provider edge router
+ availability-zone-name:
+ type: string
+ description: Name of the availability zone
+ ctag-pool-purpose:
+ type: string
+ description: Describes what the intended purpose of this pool is.
+ ctag-values:
+ type: string
+ description: Comma separated list of ctags
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ ctag-pools:
+ properties:
+ ctag-pool:
+ type: array
+ items:
+ $ref: "#/getDefinitions/ctag-pool"
+ customer:
+ description: |
+ customer identifiers to provide linkage back to BSS information.
+ ###### Related Nodes
+ - FROM service-subscription( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)
+ - CUSTOMER is DELETED when these are DELETED SERVICE-SUBSCRIPTION
+ required:
+ - global-customer-id
+ - subscriber-name
+ - subscriber-type
+ properties:
+ global-customer-id:
+ type: string
+ description: Global customer id used across ECOMP to uniquely identify customer.
+ subscriber-name:
+ type: string
+ description: Subscriber name, an alternate way to retrieve a customer.
+ subscriber-type:
+ type: string
+ description: Subscriber type, a way to provide VID with only the INFRA customers.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ service-subscriptions:
+ type: array
+ items:
+ $ref: "#/getDefinitions/service-subscription"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ customers:
+ description: |
+ Collection of customer identifiers to provide linkage back to BSS information.
+ properties:
+ customer:
+ type: array
+ items:
+ $ref: "#/getDefinitions/customer"
cvlan-tag-entry:
required:
- cvlan-tag
@@ -39739,113 +57355,129 @@ definitions:
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
+ $ref: "#/getDefinitions/relationship"
cvlan-tags:
properties:
cvlan-tag-entry:
type: array
items:
- $ref: "#/definitions/cvlan-tag-entry"
- port-group:
+ $ref: "#/getDefinitions/cvlan-tag-entry"
+ dvs-switch:
description: |
- Used to capture the network interfaces of this VCE
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
+ Digital virtual switch metadata, used by SDN-C to configure VCEs. A&AI needs to receive this data from the PO deployment team and administer it using the provisioningTool.sh into A&AI.
###### Related Nodes
- - TO cvlan-tag (comprises port-group, Many2Many)
- - FROM vce (is composed of port-group)
+ - TO cloud-region( dvs-switch org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO availability-zone( dvs-switch org.onap.relationships.inventory.AppliesTo availability-zone, MANY2MANY)
required:
- - interface-id
- - orchestration-status
+ - switch-name
+ - vcenter-url
properties:
- interface-id:
- type: string
- description: Unique ID of the interface
- neutron-network-id:
- type: string
- description: Neutron network id of this Interface
- neutron-network-name:
+ switch-name:
type: string
- description: Neutron network name of this Interface
- interface-role:
+ description: DVS switch name
+ vcenter-url:
type: string
- description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
+ description: URL used to reach the vcenter
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- port-group-id:
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ dvs-switches:
+ description: |
+ Collection of digital virtual switch metadata used for vmWare VCEs and GenericVnfs.
+ properties:
+ dvs-switch:
+ type: array
+ items:
+ $ref: "#/getDefinitions/dvs-switch"
+ edge-prop-names:
+ description: |
+ Internal map to define the properties of an edge and interpret the map EdgeRules
+ properties:
+ edgeLabel:
type: string
- description: Unique ID for port group in vmware
- port-group-name:
+ direction:
type: string
- description: Likely to duplicate value of neutron network name
- switch-name:
+ multiplicityRule:
type: string
- description: DVS or standard switch name (should be non-null for port groups associated with DVS)
- orchestration-status:
+ isParent:
+ type: boolean
+ usesResource:
+ type: boolean
+ hasDelTarget:
+ type: boolean
+ SVC-INFRA:
+ type: boolean
+ SVC-INFRA-REV:
+ type: boolean
+ edge-tag-query-request:
+ properties:
+ edge-tag:
type: string
- description: Orchestration status of this VNF, mastered by MSO
- heat-stack-id:
+ result-detail:
type: string
- description: Heat stack id corresponding to this instance, managed by MSO
- mso-catalog-key:
+ start-node-type:
type: string
- description: Corresponds to the SDN-C catalog id used to configure this VCE
- cvlan-tags:
+ start-node-filter:
type: array
- items:
- $ref: "#/definitions/cvlan-tag-entry"
- relationship-list:
+ items:
+ $ref: "#/getDefinitions/start-node-filter"
+ include-node-filter:
type: array
- items:
- $ref: "#/definitions/relationship"
- port-groups:
+ items:
+ $ref: "#/getDefinitions/include-node-filter"
+ secondary-filter:
+ type: array
+ items:
+ $ref: "#/getDefinitions/secondary-filter"
+ edge-tag-query-result:
properties:
- port-group:
+ tagged-inventory-item-list:
type: array
items:
- $ref: "#/definitions/port-group"
- license:
+ $ref: "#/getDefinitions/tagged-inventory-item-list"
+ element-choice-set:
description: |
- Metadata for license group.
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ This is how we would capture constraints defining allowed sets of elements.
###### Related Nodes
- - FROM generic-vnf (is composed of license)
- - FROM vce (is composed of license)
+ - TO constrained-element-set( element-choice-set org.onap.relationships.inventory.BelongsTo constrained-element-set, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)
+ - ELEMENT-CHOICE-SET is DELETED when these are DELETED MODEL-ELEMENT
required:
- - group-uuid
- - resource-uuid
+ - element-choice-set-uuid
+ - element-choice-set-name
properties:
- group-uuid:
+ element-choice-set-uuid:
type: string
- description: Unique ID for the license group the resource belongs to, should be uuid.
- resource-uuid:
+ element-choice-set-name:
+ type: string
+ cardinality:
type: string
- description: Unique ID of a license resource.
resource-version:
type: string
- description: Concurrency value
+ model-elements:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model-element"
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- licenses:
- description: |
- Licenses to be allocated across resources, keyed by group-uuid and resource-uuid, related to license management
+ $ref: "#/getDefinitions/relationship"
+ element-choice-sets:
properties:
- license:
+ element-choice-set:
type: array
items:
- $ref: "#/definitions/license"
+ $ref: "#/getDefinitions/element-choice-set"
entitlement:
description: |
Metadata for entitlement group.
- ###### Default Delete Scope
- THIS_NODE_ONLY
###### Related Nodes
- - FROM generic-vnf (is composed of entitlement)
- - FROM vce (is composed of entitlement)
+ - TO generic-vnf( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vce( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
required:
- group-uuid
- resource-uuid
@@ -39862,7 +57494,7 @@ definitions:
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
+ $ref: "#/getDefinitions/relationship"
entitlements:
description: |
Entitlements, keyed by group-uuid and resource-uuid, related to license management
@@ -39870,24 +57502,471 @@ definitions:
entitlement:
type: array
items:
- $ref: "#/definitions/entitlement"
- vce:
+ $ref: "#/getDefinitions/entitlement"
+ esr-ems:
description: |
- Virtual Customer Edge Router, used specifically for Gamma. This object is deprecated.
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
+ Persist EMS address information used by EMS driver.
+ ###### Related Nodes
+ - TO esr-system-info (CHILD of esr-ems, esr-ems has esr-system-info, One2Many)
+ - ESR-EMS deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
+ required:
+ - ems-id
+ properties:
+ ems-id:
+ type: string
+ description: Unique ID of EMS.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ esr-system-info-list:
+ type: object
+ $ref: "#/getDefinitions/esr-system-info-list"
+ relationship-list:
+ type: object
+ $ref: "#/getDefinitions/relationship-list"
+ esr-ems-list:
+ properties:
+ esr-ems:
+ type: array
+ items:
+ $ref: "#/getDefinitions/esr-ems"
+ esr-system-info:
+ description: |
+ Persist common address information of external systems.
+ ###### Related Nodes
+ - FROM esr-ems (PARENT of esr-system-info, esr-ems has esr-system-info)
+ - FROM esr-vnfm (PARENT of esr-system-info, esr-vnfm has esr-system-info)
+ - FROM esr-thirdparty-sdnc (PARENT of esr-system-info, esr-thirdparty-sdnc has esr-system-info)
+ - FROM cloud-region (PARENT of esr-system-info, cloud-region has esr-system-info)
+ required:
+ - esr-system-info-id
+ - user-name
+ - password
+ - system-type
+ properties:
+ esr-system-info-id:
+ type: string
+ description: Unique ID of esr system info.
+ system-name:
+ type: string
+ description: name of external system.
+ type:
+ type: string
+ description: type of external systems.
+ vendor:
+ type: string
+ description: vendor of external systems.
+ version:
+ type: string
+ description: version of external systems.
+ service-url:
+ type: string
+ description: url used to access external systems.
+ user-name:
+ type: string
+ description: username used to access external systems.
+ password:
+ type: string
+ description: password used to access external systems.
+ system-type:
+ type: string
+ description: it could be vim/vnfm/thirdparty-sdnc/ems-resource/ems-performance/ems-alarm.
+ protocol:
+ type: string
+ description: protocol of third party SDNC, for example netconf/snmp.
+ ssl-cacert:
+ type: string
+ description: ca file content if enabled ssl on auth-url.
+ ssl-insecure:
+ type: boolean
+ description: Whether to verify VIM's certificate.
+ ip-address:
+ type: string
+ description: service IP of ftp server.
+ port:
+ type: string
+ description: service port of ftp server.
+ cloud-domain:
+ type: string
+ description: domain info for authentication.
+ default-tenant:
+ type: string
+ description: default tenant of VIM.
+ passive:
+ type: boolean
+ description: ftp passive mode or not.
+ remote-path:
+ type: string
+ description: resource or performance data file path.
+ system-status:
+ type: string
+ description: the status of external system.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ esr-system-info-list:
+ description: |
+ Collection of persistent block-level external system auth info.
+ properties:
+ esr-system-info:
+ type: array
+ items:
+ $ref: "#/getDefinitions/esr-system-info"
+ esr-thirdparty-sdnc:
+ description: |
+ Persist SDNC address information used by ONAP SDNC.
+ ###### Related Nodes
+ - TO esr-system-info (CHILD of esr-thirdparty-sdnc, esr-thirdparty-sdnc has esr-system-info, One2One)
+ - TO pnf( esr-thirdparty-sdnc has pnf, One2Many)
+ - ESR-THIRDPARTY-SDNC deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
+ required:
+ - thirdparty-sdnc-id
+ properties:
+ thirdparty-sdnc-id:
+ type: string
+ description: Unique ID of SDNC.
+ location:
+ type: string
+ description: used for DC type to indicate the location of SDNC, such as Core or Edge.
+ product-name:
+ type: string
+ description: password used to access SDNC server.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ esr-system-info-list:
+ type: object
+ $ref: "#/getDefinitions/esr-system-info-list"
+ relationship-list:
+ type: object
+ $ref: "#/getDefinitions/relationship-list"
+ esr-thirdparty-sdnc-list:
+ properties:
+ esr-thirdparty-sdnc:
+ type: array
+ items:
+ $ref: "#/getDefinitions/esr-thirdparty-sdnc"
+ esr-vnfm:
+ description: |
+ Persist VNFM address information used by VF-C.
+ ###### Related Nodes
+ - TO esr-system-info (CHILD of esr-vnfm, esr-vnfm has esr-system-info, One2One)
+ - ESR-VNFM deletion means associated objects of these types are also DELETED:ESR-SYSTEM-INFO
+ required:
+ - vnfm-id
+ properties:
+ vnfm-id:
+ type: string
+ description: Unique ID of VNFM.
+ vim-id:
+ type: string
+ description: indecate the VIM to deploy VNF.
+ certificate-url:
+ type: string
+ description: certificate url of VNFM.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ esr-system-info-list:
+ type: object
+ $ref: "#/getDefinitions/esr-system-info-list"
+ relationship-list:
+ type: object
+ $ref: "#/getDefinitions/relationship-list"
+ esr-vnfm-list:
+ properties:
+ esr-vnfm:
+ type: array
+ items:
+ $ref: "#/getDefinitions/esr-vnfm"
+ evc:
+ description: |
+ evc object is an optional child object of the Configuration object.
+ ###### Related Nodes
+ - TO configuration( evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)
+ required:
+ - evc-id
+ properties:
+ evc-id:
+ type: string
+ description: Unique/key field for the evc object
+ forwarding-path-topology:
+ type: string
+ description: Point-to-Point, Multi-Point
+ cir-value:
+ type: string
+ description: Commited Information Rate
+ cir-units:
+ type: string
+ description: CIR units
+ connection-diversity-group-id:
+ type: string
+ description: Diversity Group ID
+ service-hours:
+ type: string
+ description: formerly Performance Group
+ esp-evc-circuit-id:
+ type: string
+ description: EVC Circuit ID of ESP EVC
+ esp-evc-cir-value:
+ type: string
+ description: Committed Information Rate (For ESP)
+ esp-evc-cir-units:
+ type: string
+ description: CIR units (For ESP)
+ esp-itu-code:
+ type: string
+ description: Identifies ESP
+ collector-pop-clli:
+ type: string
+ description: Collector POP CLLI (from the hostname of the access pnf)
+ inter-connect-type-ingress:
+ type: string
+ description: Interconnect type on ingress side of EVC.
+ tagmode-access-ingress:
+ type: string
+ description: tagode for collector side of EVC
+ tagmode-access-egress:
+ type: string
+ description: tagMode for network side of EVC
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ evcs:
+ properties:
+ evc:
+ type: array
+ items:
+ $ref: "#/getDefinitions/evc"
+ external-system:
+ description: |
+ Namespace for external system.
+ properties:
+ esr-ems-list:
+ type: object
+ $ref: "#/getDefinitions/esr-ems-list"
+ esr-vnfm-list:
+ type: object
+ $ref: "#/getDefinitions/esr-vnfm-list"
+ esr-thirdparty-sdnc-list:
+ type: object
+ $ref: "#/getDefinitions/esr-thirdparty-sdnc-list"
+ extra-properties:
+ description: |
+ Extra properties for inventory item for response list
+ extra-property:
+ properties:
+ property-name:
+ type: string
+ flavor:
+ description: |
+ Openstack flavor.
+ ###### Related Nodes
+ - TO cloud-region( flavor org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)
+ - FLAVOR cannot be deleted if linked to VSERVER
+ required:
+ - flavor-id
+ - flavor-name
+ - flavor-selflink
+ properties:
+ flavor-id:
+ type: string
+ description: Flavor id, expected to be unique across cloud-region.
+ flavor-name:
+ type: string
+ description: Flavor name
+ flavor-vcpus:
+ type: integer
+ format: int32
+ description: Number of CPUs
+ flavor-ram:
+ type: integer
+ format: int32
+ description: Amount of memory
+ flavor-disk:
+ type: integer
+ format: int32
+ description: Disk space
+ flavor-ephemeral:
+ type: integer
+ format: int32
+ description: Amount of ephemeral disk space
+ flavor-swap:
+ type: string
+ description: amount of swap space allocation
+ flavor-is-public:
+ type: boolean
+ description: whether flavor is available to all users or private to the tenant it was created in.
+ flavor-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ flavor-disabled:
+ type: boolean
+ description: Boolean as to whether this flavor is no longer enabled
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ flavors:
+ description: |
+ Collection of openstack flavors.
+ properties:
+ flavor:
+ type: array
+ items:
+ $ref: "#/getDefinitions/flavor"
+ forwarder:
+ description: |
+ Entity describing a sequenced segment of forwarding path
+ ###### Related Nodes
+ - TO forwarding-path( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)
+ - TO l-interface( forwarder org.onap.relationships.inventory.ForwardsTo l-interface, MANY2ONE)
+ - TO configuration( forwarder org.onap.relationships.inventory.Uses configuration, ONE2ONE)
+ - TO lag-interface( forwarder org.onap.relationships.inventory.ForwardsTo lag-interface, MANY2ONE)
+ - TO p-interface( forwarder org.onap.relationships.inventory.ForwardsTo p-interface, MANY2ONE)
+ - FORWARDER deletion means associated objects of these types are also DELETED:CONFIGURATION
+ required:
+ - sequence
+ properties:
+ sequence:
+ type: integer
+ format: int32
+ description: Unique ID of this segmentation
+ forwarder-role:
+ type: string
+ description: ingress, intermediate, egress
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ forwarder-evc:
+ description: |
+ forwarder object is an optional child object of the Configuration object.
+ ###### Related Nodes
+ - TO configuration( forwarder-evc org.onap.relationships.inventory.BelongsTo configuration, ONE2ONE)
+ required:
+ - forwarder-evc-id
+ properties:
+ forwarder-evc-id:
+ type: string
+ description: Key for forwarder-evc object
+ circuit-id:
+ type: string
+ description: Circuit ID from customer/ESP/ingress end of EVC, or reference to beater circuit on gateway/network/egress end of EVC
+ ivlan:
+ type: string
+ description: Internal VLAN.
+ svlan:
+ type: string
+ description: SVLAN value for ingress of egress forwarder.
+ cvlan:
+ type: string
+ description: CVLAN value for ingress of egress forwarder.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ forwarder-evcs:
+ properties:
+ forwarder-evc:
+ type: array
+ items:
+ $ref: "#/getDefinitions/forwarder-evc"
+ forwarders:
+ properties:
+ forwarder:
+ type: array
+ items:
+ $ref: "#/getDefinitions/forwarder"
+ forwarding-path:
+ description: |
+ Entity that describes the sequenced forwarding path between interfaces of services or resources
###### Related Nodes
- - TO availability-zone (Many2Many)
- - TO complex (Many2Many)
- - TO port-group (comprises vce, Many2Many)
- - TO vserver (Many2Many)
- - TO service-instance (Many2Many)
- - TO entitlement (comprises vce, One2Many)
- - TO license (comprises vce, One2Many)
+ - TO service-instance( forwarding-path org.onap.relationships.inventory.AppliesTo service-instance, MANY2ONE)
+ - TO configuration( forwarding-path org.onap.relationships.inventory.Uses configuration, ONE2ONE)
+ - FROM forwarder( forwarder org.onap.relationships.inventory.BelongsTo forwarding-path, MANY2ONE)
+ - FORWARDING-PATH is DELETED when these are DELETED FORWARDER
+ - FORWARDING-PATH deletion means associated objects of these types are also DELETED:CONFIGURATION
+ required:
+ - forwarding-path-id
+ - forwarding-path-name
+ properties:
+ forwarding-path-id:
+ type: string
+ description: Unique ID of this FP
+ forwarding-path-name:
+ type: string
+ description: Name of the FP
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ selflink:
+ type: string
+ description: the self link for this FP
+ forwarders:
+ type: array
+ items:
+ $ref: "#/getDefinitions/forwarder"
+ forwarding-paths:
+ properties:
+ forwarding-path:
+ type: array
+ items:
+ $ref: "#/getDefinitions/forwarding-path"
+ generic-vnf:
+ description: |
+ General purpose VNF
+ ###### Related Nodes
+ - TO availability-zone( generic-vnf org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - TO instance-group( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO ipsec-configuration( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)
+ - TO l3-network( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO license-key-resource( generic-vnf org.onap.relationships.inventory.Uses license-key-resource, MANY2MANY)
+ - TO pserver( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)
+ - TO vnf-image( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)
+ - TO volume-group( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - TO vserver( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)
+ - TO virtual-data-center( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf generic-vnf, MANY2MANY)
+ - FROM entitlement( entitlement org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM lag-interface( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM license( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM network-profile( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)
+ - FROM site-pair-set( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)
+ - GENERIC-VNF is DELETED when these are DELETED ENTITLEMENT,VNFC,LAG-INTERFACE,LICENSE,L-INTERFACE,VF-MODULE
required:
- vnf-id
- vnf-name
- vnf-type
+ - in-maint
+ - is-closed-loop-disabled
properties:
vnf-id:
type: string
@@ -39903,7 +57982,7 @@ definitions:
description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
service-id:
type: string
- description: Unique identifier of service, does not strictly map to ASDC services, SOON TO BE DEPRECATED.
+ description: Unique identifier of service, does not necessarily map to ASDC service models. SOON TO BE DEPRECATED
regional-resource-zone:
type: string
description: Regional way of organizing pservers, source of truth should define values
@@ -39912,252 +57991,665 @@ definitions:
description: Trigger for operational monitoring of this resource by Service Assurance systems.
operational-state:
type: string
- description: Indicator for whether the resource is considered operational
+ description: Indicator for whether the resource is considered operational. Valid values are in-service-path and out-of-service-path.
license-key:
type: string
description: OBSOLETE - do not use
equipment-role:
type: string
- description: Network role being played by this VNF
+ description: Client should send valid enumerated value
orchestration-status:
type: string
- description: Orchestration status of this VNF, mastered by MSO
+ description: Orchestration status of this VNF, used by MSO.
heat-stack-id:
type: string
description: Heat stack id corresponding to this instance, managed by MSO
mso-catalog-key:
type: string
description: Corresponds to the SDN-C catalog id used to configure this VCE
- vpe-id:
- type: string
- description: Unique ID of VPE connected to this VCE.
- v6-vce-wan-address:
+ management-option:
type: string
- description: Valid v6 IP address for the WAN Link on this router. Implied length of /64.
+ description: identifier of managed by company or customer
ipv4-oam-address:
type: string
- description: Address tail-f uses to configure vce, also used for troubleshooting and is IP used for traps generated by VCE.
+ description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by generic-vnf.
+ ipv4-loopback0-address:
+ type: string
+ description: v4 Loopback0 address
+ nm-lan-v6-address:
+ type: string
+ description: v6 Loopback address
+ management-v6-address:
+ type: string
+ description: v6 management address
+ vcpu:
+ type: integer
+ format: int64
+ description: number of vcpus ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases
+ vcpu-units:
+ type: string
+ description: units associated with vcpu, used for VNFs with no vservers/flavors, to be used only in some usecases
+ vmemory:
+ type: integer
+ format: int64
+ description: number of GB of memory ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases
+ vmemory-units:
+ type: string
+ description: units associated with vmemory, used for VNFs with no vservers/flavors, to be used only in some usecases
+ vdisk:
+ type: integer
+ format: int64
+ description: number of vdisks ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases
+ vdisk-units:
+ type: string
+ description: units associated with vdisk, used for VNFs with no vservers/flavors, to be used only in some usecases
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- ipv4-loopback0-address:
+ summary-status:
type: string
- description: Loopback0 address
- entitlement-resource-uuid:
+ description: details regarding the generic-vnf operation, PLEASE DISCONTINUE USE OF THIS FIELD.
+ encrypted-access-flag:
+ type: boolean
+ description: indicates whether generic-vnf access uses SSH
+ persona-model-id:
type: string
- description: OBSOLETE - see child relationships
- port-groups:
+ description: the ASDC model id for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ persona-model-customization-id:
+ type: string
+ description: captures the id of all the configuration used to customize the resource for the service.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ as-number:
+ type: string
+ description: as-number of the VNF
+ regional-resource-subzone:
+ type: string
+ description: represents sub zone of the rr plane
+ selflink:
+ type: string
+ description: Path to the controller object.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/port-group"
+ $ref: "#/getDefinitions/relationship"
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l-interface"
+ lag-interfaces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/lag-interface"
+ vf-modules:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vf-module"
licenses:
type: array
items:
- $ref: "#/definitions/license"
+ $ref: "#/getDefinitions/license"
entitlements:
type: array
items:
- $ref: "#/definitions/entitlement"
+ $ref: "#/getDefinitions/entitlement"
+ generic-vnfs:
+ description: |
+ Collection of VNFs
+ properties:
+ generic-vnf:
+ type: array
+ items:
+ $ref: "#/getDefinitions/generic-vnf"
+ group-assignment:
+ description: |
+ Openstack group-assignment used to store exclusivity groups (EG).
+ ###### Related Nodes
+ - TO cloud-region( group-assignment org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)
+ required:
+ - group-id
+ - group-type
+ - group-name
+ properties:
+ group-id:
+ type: string
+ description: Group id, expected to be unique across cloud-region.
+ group-type:
+ type: string
+ description: Group type - the type of group this instance refers to
+ group-name:
+ type: string
+ description: Group name - name assigned to the group
+ group-description:
+ type: string
+ description: Group description - description of the group
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- vces:
+ $ref: "#/getDefinitions/relationship"
+ group-assignments:
description: |
- Collection of Virtual Customer Edge Routers, used specifically for Gamma. This object is deprecated.
+ Collection of openstack group assignments
properties:
- vce:
+ group-assignment:
type: array
items:
- $ref: "#/definitions/vce"
- vnfc:
+ $ref: "#/getDefinitions/group-assignment"
+ host-route:
description: |
- ###### Default Delete Scope
- THIS_NODE_ONLY
###### Related Nodes
- - FROM vserver
- - FROM vf-module
- - FROM generic-vnf
+ - TO subnet( host-route org.onap.relationships.inventory.BelongsTo subnet, MANY2ONE)
required:
- - vnfc-name
- - vnfc-function-code
- - vnfc-type
- - in-maint
- - is-closed-loop-disabled
+ - host-route-id
+ - route-prefix
+ - next-hop
properties:
- vnfc-name:
+ host-route-id:
type: string
- description: Unique ID of vnfc.
- vnfc-function-code:
+ description: host-route id
+ route-prefix:
type: string
- description: function code
- vnfc-type:
+ description: subnet prefix
+ next-hop:
type: string
- description: type
- prov-status:
+ description: Could be ip-address, hostname, or service-instance
+ next-hop-type:
type: string
- description: prov status of this vnfc
- orchestration-status:
+ description: Should be ip-address, hostname, or service-instance to match next-hop
+ resource-version:
type: string
- description: Orchestration status of this VNF, mastered by APP-C
- ipaddress-v4-oam-vip:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ host-routes:
+ properties:
+ host-route:
+ type: array
+ items:
+ $ref: "#/getDefinitions/host-route"
+ image:
+ description: |
+ Openstack image.
+ ###### Related Nodes
+ - TO cloud-region( image org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)
+ - IMAGE cannot be deleted if linked to VSERVER
+ - IMAGE is DELETED when these are DELETED METADATUM
+ required:
+ - image-id
+ - image-name
+ - image-os-distro
+ - image-os-version
+ - image-selflink
+ properties:
+ image-id:
type: string
- description: Oam V4 vip address of this vnfc
- in-maint:
- type: boolean
- is-closed-loop-disabled:
- type: boolean
- group-notation:
+ description: Image id, expected to be unique across cloud region
+ image-name:
type: string
- description: Group notation of VNFC
+ description: Image name
+ image-architecture:
+ type: string
+ description: Operating system architecture.
+ image-os-distro:
+ type: string
+ description: The common name of the operating system distribution in lowercase
+ image-os-version:
+ type: string
+ description: The operating system version as specified by the distributor.
+ application:
+ type: string
+ description: The application that the image instantiates.
+ application-vendor:
+ type: string
+ description: The vendor of the application.
+ application-version:
+ type: string
+ description: The version of the application.
+ image-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- vnfcs:
+ $ref: "#/getDefinitions/relationship"
+ metadata:
+ type: array
+ items:
+ $ref: "#/getDefinitions/metadatum"
+ images:
description: |
- virtual network components associated with a vserver from application controller.
+ Collectio of Openstack images.
properties:
- vnfc:
+ image:
type: array
items:
- $ref: "#/definitions/vnfc"
- subnet:
+ $ref: "#/getDefinitions/image"
+ include-node-filter:
+ properties:
+ include-node-type:
+ type: string
+ instance-filter:
+ description: |
+ InstanceFilter for performing a named-query or model query
+ instance-filters:
description: |
- ###### Default Delete Scope
- ERROR_IF_ANY_IN_EDGES
+ InstanceFilters for performing a named-query or model query
+ properties:
+ instance-filter:
+ type: array
+ items:
+ $ref: "#/getDefinitions/instance-filter"
+ instance-group:
+ description: |
+ General mechanism for grouping instances
###### Related Nodes
- - FROM l3-interface-ipv4-address-list
- - FROM l3-interface-ipv6-address-list
- - FROM l3-network (is composed of subnet)
+ - TO model( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM pnf( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
required:
- - subnet-id
- - dhcp-enabled
+ - id
+ - description
+ - type
properties:
- subnet-id:
+ id:
type: string
- description: Subnet ID, should be UUID.
- subnet-name:
+ description: Instance Group ID, UUID assigned to this instance.
+ description:
type: string
- description: Name associated with the subnet.
- neutron-subnet-id:
+ description: Descriptive text to help identify the usage of this instance-group
+ type:
type: string
- description: Neutron id of this subnet
- gateway-address:
+ description: Only valid value today is lower case ha for high availability
+ sub-type:
type: string
- description: gateway ip address
- network-start-address:
+ description: Valid values for ha type are [geo-activeactive, geo-activestandby, local-activeactive, local-activestandby]
+ resource-version:
type: string
- description: network start address
- cidr-mask:
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ instance-groups:
+ description: |
+ Collection of openstack route table references
+ properties:
+ instance-group:
+ type: array
+ items:
+ $ref: "#/getDefinitions/instance-group"
+ inventory:
+ properties:
+ search:
+ type: object
+ $ref: "#/getDefinitions/search"
+ actions:
+ type: object
+ $ref: "#/getDefinitions/actions"
+ cloud-infrastructure:
+ type: object
+ $ref: "#/getDefinitions/cloud-infrastructure"
+ business:
+ type: object
+ $ref: "#/getDefinitions/business"
+ service-design-and-creation:
+ type: object
+ $ref: "#/getDefinitions/service-design-and-creation"
+ network:
+ type: object
+ $ref: "#/getDefinitions/network"
+ aai-internal:
+ type: object
+ $ref: "#/getDefinitions/aai-internal"
+ nodes:
+ type: array
+ items:
+ $ref: "#/getDefinitions/aai-internal"
+ inventory-item:
+ properties:
+ inventory-item-type:
type: string
- description: cidr mask
- ip-version:
+ inventory-item-link:
type: string
- description: ip version
- orchestration-status:
+ inventory-item-data:
+ type: array
+ items:
+ $ref: "#/getDefinitions/inventory-item-data"
+ tagged-inventory-item-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/tagged-inventory-item-list"
+ inventory-item-data:
+ properties:
+ property-name:
type: string
- description: Orchestration status of this VNF, mastered by MSO
- dhcp-enabled:
- type: boolean
- dhcp-start:
+ property-value:
type: string
- description: the start address reserved for use by dhcp
- dhcp-end:
+ inventory-response-item:
+ description: |
+ Inventory item for response list
+ properties:
+ model-name:
type: string
- description: the last address reserved for use by dhcp
+ extra-properties:
+ type: object
+ $ref: "#/getDefinitions/extra-properties"
+ inventory-response-items:
+ type: object
+ $ref: "#/getDefinitions/inventory-response-items"
+ inventory-response-items:
+ description: |
+ Container for inventory items in response list
+ properties:
+ inventory-response-item:
+ type: array
+ items:
+ $ref: "#/getDefinitions/inventory-response-item"
+ ipsec-configuration:
+ description: |
+ IPSec configuration node will contain various configuration data for the NMTE VNF. This node will have an edge to the generic-vnf (vnf type = TE). Starting 1607, this data will be populated by SDN-C
+ ###### Related Nodes
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses ipsec-configuration, MANY2ONE)
+ - FROM vig-server( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)
+ - IPSEC-CONFIGURATION is DELETED when these are DELETED VIG-SERVER
+ required:
+ - ipsec-configuration-id
+ properties:
+ ipsec-configuration-id:
+ type: string
+ description: UUID of this configuration
+ requested-vig-address-type:
+ type: string
+ description: Indicate the type of VIG server like AVPN, INTERNET, BOTH
+ requested-encryption-strength:
+ type: string
+ description: Encryption values like 3des-cbc, des-cbc, aes-128-cbc, aes-192-cbc, aes-265-cbc
+ requested-dmz-type:
+ type: string
+ description: can offer a shared DMZ or a DMZ specific to a customer
+ shared-dmz-network-address:
+ type: string
+ description: Network address of shared DMZ
+ requested-customer-name:
+ type: string
+ description: If the DMZ is a custom DMZ, this field will indicate the customer information
+ ike-version:
+ type: string
+ description: can be 1 or 2
+ ikev1-authentication:
+ type: string
+ description: Contains values like md5, sha1, sha256, sha384
+ ikev1-encryption:
+ type: string
+ description: Encyption values like 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
+ ikev1-dh-group:
+ type: string
+ description: Diffie-Hellman group like DH-GROUP2, DH-GROUP5, DH-GROUP14
+ ikev1-am-group-id:
+ type: string
+ description: Group name defined in VIG for clients using aggressive mode
+ ikev1-am-password:
+ type: string
+ description: pre-shared key for the above group name
+ ikev1-sa-lifetime:
+ type: string
+ description: Lifetime for IKEv1 SA
+ ipsec-authentication:
+ type: string
+ description: md5, sha1, sha256, sha384
+ ipsec-encryption:
+ type: string
+ description: 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
+ ipsec-sa-lifetime:
+ type: string
+ description: Life time for IPSec SA
+ ipsec-pfs:
+ type: string
+ description: enable PFS or not
+ xauth-userid:
+ type: string
+ description: user ID for xAuth, sm-user, ,nmteHostName
+ xauth-user-password:
+ type: string
+ description: Encrypted using the Juniper $9$ algorithm
+ dpd-interval:
+ type: string
+ description: The time between DPD probe
+ dpd-frequency:
+ type: string
+ description: Maximum number of DPD before claiming the tunnel is down
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- subnets:
+ $ref: "#/getDefinitions/relationship"
+ vig-servers:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vig-server"
+ ipsec-configurations:
properties:
- subnet:
+ ipsec-configuration:
type: array
items:
- $ref: "#/definitions/subnet"
- ctag-assignment:
+ $ref: "#/getDefinitions/ipsec-configuration"
+ key-data:
+ properties:
+ key-name:
+ type: string
+ key-value:
+ type: string
+ l-interface:
description: |
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Logical interfaces, e.g., a vnic.
###### Related Nodes
- - FROM l3-network (is composed of ctag-assignment)
- - FROM service-instance
+ - TO generic-vnf( l-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO lag-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)
+ - TO logical-link( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)
+ - TO newvce( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)
+ - TO p-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)
+ - TO vserver( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - FROM sriov-vf( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)
+ - FROM vlan( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)
+ - L-INTERFACE is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST,SRIOV-VF,VLAN
+ - L-INTERFACE deletion means associated objects of these types are also DELETED:LOGICAL-LINK
required:
- - vlan-id-inner
+ - interface-name
properties:
- vlan-id-inner:
- type: integer
- format: int64
- description: id.
+ interface-name:
+ type: string
+ description: Name given to the interface
+ interface-role:
+ type: string
+ description: E.g., CUSTOMER, UPLINK, etc.
+ v6-wan-link-ip:
+ type: string
+ description: Questionably placed - v6 ip addr of this interface (is in vr-lan-interface from Mary B.
+ selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ interface-id:
+ type: string
+ description: ID of interface
+ macaddr:
+ type: string
+ description: MAC address for the interface
+ network-name:
+ type: string
+ description: Name of the network
+ management-option:
+ type: string
+ description: Whether A&AI should be managing this interface of not. Could have value like CUSTOMER
+ interface-description:
+ type: string
+ description: Human friendly text regarding this interface.
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ vlans:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vlan"
+ sriov-vfs:
+ type: array
+ items:
+ $ref: "#/getDefinitions/sriov-vf"
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- ctag-assignments:
+ $ref: "#/getDefinitions/relationship"
+ l3-interface-ipv4-address-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
+ l3-interface-ipv6-address-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
+ l-interfaces:
+ description: |
+ Collection of logical interfaces.
properties:
- ctag-assignment:
+ l-interface:
type: array
items:
- $ref: "#/definitions/ctag-assignment"
- segmentation-assignment:
+ $ref: "#/getDefinitions/l-interface"
+ l3-interface-ipv4-address-list:
description: |
- Openstack segmentation assignment.
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ IPv4 Address Range
###### Related Nodes
- - FROM l3-network (is composed of segmentation-assignment)
+ - TO l3-network( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - TO subnet( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - TO l-interface( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - TO vlan( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
required:
- - segmentation-id
+ - l3-interface-ipv4-address
properties:
- segmentation-id:
+ l3-interface-ipv4-address:
type: string
- description: Route Table Reference id, UUID assigned to this instance.
+ description: IP address
+ l3-interface-ipv4-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 32 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
resource-version:
type: string
- description: Concurrency value
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
+ type: string
+ description: Neutron network id of the interface that address belongs to
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of subnet that address belongs to
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- segmentation-assignments:
+ $ref: "#/getDefinitions/relationship"
+ l3-interface-ipv6-address-list:
description: |
- Collection of openstack segmentation assignments
+ IPv6 Address Range
+ ###### Related Nodes
+ - TO l3-network( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - TO subnet( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - TO l-interface( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo l-interface, MANY2ONE)
+ - TO vlan( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ required:
+ - l3-interface-ipv6-address
properties:
- segmentation-assignment:
+ l3-interface-ipv6-address:
+ type: string
+ description: IP address
+ l3-interface-ipv6-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 128 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
+ type: string
+ description: Neutron network id of the interface that address belongs to
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of subnet that address belongs to
+ relationship-list:
type: array
- items:
- $ref: "#/definitions/segmentation-assignment"
+ items:
+ $ref: "#/getDefinitions/relationship"
l3-network:
description: |
Generic network definition
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
- ###### Related Nodes
- - TO vpn-binding (Many2Many)
- - TO subnet (comprises l3-network, Many2Many)
- - TO service-instance (Many2Many)
- - TO ctag-assignment (comprises l3-network, Many2Many)
- - TO network-policy (Many2Many)
- - TO segmentation-assignment (comprises l3-network, One2Many)
- - TO route-table-reference (Many2Many)
- - FROM cloud-region
- - FROM complex
- - FROM generic-vnf
- - FROM l3-interface-ipv4-address-list
- - FROM l3-interface-ipv6-address-list
- - FROM tenant
- - FROM vf-module
- - FROM allotted-resource
+ ###### Related Nodes
+ - TO network-policy( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)
+ - TO route-table-reference( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)
+ - TO vpn-binding( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf l3-network, MANY2MANY)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM complex( complex org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf l3-network, MANY2MANY)
+ - FROM ctag-assignment( ctag-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM segmentation-assignment( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)
+ - FROM subnet( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)
+ - L3-NETWORK is DELETED when these are DELETED CTAG-ASSIGNMENT,SEGMENTATION-ASSIGNMENT,SUBNET
required:
- network-id
- network-name
@@ -40241,86 +58733,205 @@ definitions:
subnets:
type: array
items:
- $ref: "#/definitions/subnet"
+ $ref: "#/getDefinitions/subnet"
ctag-assignments:
type: array
items:
- $ref: "#/definitions/ctag-assignment"
+ $ref: "#/getDefinitions/ctag-assignment"
segmentation-assignments:
type: array
items:
- $ref: "#/definitions/segmentation-assignment"
+ $ref: "#/getDefinitions/segmentation-assignment"
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
+ $ref: "#/getDefinitions/relationship"
description: Relates to tenant (or is it a child of tenant), complex, service, vpn-binding
l3-networks:
properties:
l3-network:
type: array
items:
- $ref: "#/definitions/l3-network"
- network-policy:
+ $ref: "#/getDefinitions/l3-network"
+ lag-interface:
description: |
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Link aggregate interface
###### Related Nodes
- - FROM l3-network
+ - TO generic-vnf( lag-interface org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO lag-link( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)
+ - TO p-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)
+ - TO pnf( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - TO pserver( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - TO vpls-pe( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo lag-interface, MANY2ONE)
+ - LAG-INTERFACE is DELETED when these are DELETED L-INTERFACE
+ - LAG-INTERFACE deletion means associated objects of these types are also DELETED:LAG-LINK
required:
- - network-policy-id
+ - interface-name
properties:
- network-policy-id:
+ interface-name:
type: string
- description: UUID representing unique key to this instance
- network-policy-fqdn:
+ description: Name that identifies the link aggregate interface
+ interface-description:
type: string
- description: Contrail FQDN for the policy
- heat-stack-id:
+ description: Human friendly text regarding this interface.
+ resource-version:
type: string
- description: ID for the openStack Heat instance
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ interface-id:
+ type: string
+ description: ID of interface
+ interface-role:
+ type: string
+ description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l-interface"
+ lag-interfaces:
+ description: |
+ Collection of link aggregate interfaces.
+ properties:
+ lag-interface:
+ type: array
+ items:
+ $ref: "#/getDefinitions/lag-interface"
+ lag-link:
+ description: |
+ LAG links can connect lag-interfaces
+ ###### Related Nodes
+ - FROM lag-interface( lag-interface tosca.relationships.network.LinksTo lag-link, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)
+ required:
+ - link-name
+ properties:
+ link-name:
+ type: string
+ description: Alphabetical concatenation of lag-interface names
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- network-policies:
+ $ref: "#/getDefinitions/relationship"
+ lag-links:
+ description: |
+ Collection of link aggregation connections
properties:
- network-policy:
+ lag-link:
type: array
items:
- $ref: "#/definitions/network-policy"
- vf-module:
+ $ref: "#/getDefinitions/lag-link"
+ license:
description: |
- a deployment unit of VNFCs
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Metadata for license group.
###### Related Nodes
- - TO volume-group (One2One)
- - TO l3-network (Many2Many)
- - TO vnfc (One2Many)
- - FROM vserver
- - FROM generic-vnf (is composed of vf-module)
+ - TO generic-vnf( license org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vce( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
required:
- - vf-module-id
- - is-base-vf-module
+ - group-uuid
+ - resource-uuid
properties:
- vf-module-id:
+ group-uuid:
type: string
- description: Unique ID of vf-module.
- vf-module-name:
+ description: Unique ID for the license group the resource belongs to, should be uuid.
+ resource-uuid:
type: string
- description: Name of vf-module
- heat-stack-id:
+ description: Unique ID of a license resource.
+ resource-version:
type: string
- description: Heat stack id corresponding to this instance.
- orchestration-status:
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ licenses:
+ description: |
+ Licenses to be allocated across resources, keyed by group-uuid and resource-uuid, related to license management
+ properties:
+ license:
+ type: array
+ items:
+ $ref: "#/getDefinitions/license"
+ line-of-business:
+ description: |
+ describes a line-of-business
+ ###### Related Nodes
+ - TO generic-vnf( line-of-business org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)
+ required:
+ - line-of-business-name
+ properties:
+ line-of-business-name:
type: string
- description: orchestration status of this vf-module, mastered by MSO
- is-base-vf-module:
- type: boolean
+ description: Name of the line-of-business (product)
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ lines-of-business:
+ description: |
+ Collection of lines-of-business
+ properties:
+ line-of-business:
+ type: array
+ items:
+ $ref: "#/getDefinitions/line-of-business"
+ logical-link:
+ description: |
+ Logical links generally connect l-interfaces but are used to express logical connectivity between two points
+ ###### Related Nodes
+ - TO cloud-region( logical-link org.onap.relationships.inventory.LocatedIn cloud-region, MANY2MANY)
+ - TO generic-vnf( logical-link org.onap.relationships.inventory.BridgedTo generic-vnf, MANY2MANY)
+ - TO lag-link( logical-link org.onap.relationships.inventory.Uses lag-link, MANY2MANY)
+ - TO logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - TO pnf( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)
+ - TO pserver( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)
+ - TO vpn-binding( logical-link org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - TO virtual-data-center( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.LinksTo logical-link, MANY2MANY)
+ - FROM p-interface( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - FROM vlan( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ required:
+ - link-name
+ - link-type
+ properties:
+ link-name:
+ type: string
+ description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
+ link-type:
+ type: string
+ description: Type of logical link, e.g., evc
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ ip-version:
+ type: string
+ description: v4, v6, or ds for dual stack
+ routing-protocol:
+ type: string
+ description: For example, static or BGP
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
@@ -40333,254 +58944,513 @@ definitions:
model-version-id:
type: string
description: the ASDC model version for this resource or service model.
- persona-model-customization-id:
- type: string
- description: captures the id of all the configuration used to customize the resource for the service.
widget-model-id:
type: string
description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
widget-model-version:
type: string
description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
- contrail-service-instance-fqdn:
+ operational-status:
type: string
- description: the Contrail unique ID for a service-instance
- module-index:
- type: integer
- format: int32
- description: the index will track the number of modules of a given type that have been deployed in a VNF, starting with 0, and always choosing the lowest available digit
- selflink:
+ description: Indication of operational status of the logical link.
+ prov-status:
type: string
- description: Path to the controller object.
+ description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+ link-role:
+ type: string
+ description: Indication of the network use of the logical link.
+ link-name2:
+ type: string
+ description: Alias or alternate name (CLCI or D1 name).
+ link-id:
+ type: string
+ description: UUID of the logical-link, SDNC generates this.
+ circuit-id:
+ type: string
+ description: Circuit id
+ purpose:
+ type: string
+ description: Reason for this entity, role it is playing
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- vf-modules:
+ $ref: "#/getDefinitions/relationship"
+ logical-links:
description: |
- Collection of vf-modules, a deployment unit of VNFCs
+ Collection of logical connections
properties:
- vf-module:
+ logical-link:
type: array
items:
- $ref: "#/definitions/vf-module"
- generic-vnf:
+ $ref: "#/getDefinitions/logical-link"
+ metadata:
description: |
- General purpose VNF
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
- ###### Related Nodes
- - TO license-key-resource (Many2Many)
- - TO l-interface (comprises generic-vnf, Many2Many)
- - TO availability-zone (Many2Many)
- - TO lag-interface (comprises generic-vnf, Many2Many)
- - TO l3-network (Many2Many)
- - TO pserver (Many2Many)
- - TO vnf-image (Many2One)
- - TO vserver (One2Many)
- - TO service-instance (Many2Many)
- - TO site-pair-set (Many2Many)
- - TO network-profile (Many2Many)
- - TO ipsec-configuration (Many2One)
- - TO vf-module (comprises generic-vnf, One2Many)
- - TO volume-group (One2Many)
- - TO vnfc (One2Many)
- - TO instance-group (Many2Many)
- - TO entitlement (comprises generic-vnf, One2Many)
- - TO license (comprises generic-vnf, One2Many)
- - FROM virtual-data-center
- - FROM logical-link
- - FROM allotted-resource
+ Collection of metadatum (key/value pairs)
+ properties:
+ metadatum:
+ type: array
+ items:
+ $ref: "#/getDefinitions/metadatum"
+ metadatum:
+ description: |
+ Key/value pairs
+ ###### Related Nodes
+ - TO connector( metadatum org.onap.relationships.inventory.BelongsTo connector, MANY2ONE)
+ - TO image( metadatum org.onap.relationships.inventory.BelongsTo image, MANY2ONE)
+ - TO service-instance( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - TO model-ver( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
required:
- - vnf-id
- - vnf-name
- - vnf-type
- - in-maint
- - is-closed-loop-disabled
+ - metaname
+ - metaval
properties:
- vnf-id:
+ metaname:
type: string
- description: Unique id of VNF. This is unique across the graph.
- vnf-name:
+ metaval:
type: string
- description: Name of VNF.
- vnf-name2:
+ resource-version:
type: string
- description: Alternate name of VNF.
- vnf-type:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model:
+ description: |
+ Subgraph definition provided by ASDC to describe an inventory asset and its connections related to ASDC models, independent of version
+ ###### Related Nodes
+ - TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - FROM instance-group( instance-group org.onap.relationships.inventory.Targets model, MANY2MANY)
+ - FROM model-ver( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - FROM named-query( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)
+ - MODEL cannot be deleted if linked to INSTANCE-GROUP,NAMED-QUERY,NAMED-QUERY-ELEMENT
+ - MODEL is DELETED when these are DELETED MODEL-VER
+ required:
+ - model-invariant-id
+ - model-type
+ properties:
+ model-invariant-id:
type: string
- description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
- service-id:
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ model-type:
type: string
- description: Unique identifier of service, does not necessarily map to ASDC service models. SOON TO BE DEPRECATED
- regional-resource-zone:
+ description: Type of the model, e.g., service, resource, widget, etc.
+ resource-version:
type: string
- description: Regional way of organizing pservers, source of truth should define values
- prov-status:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-vers:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model-ver"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ model-and-named-query-search:
+ description: |
+ ModelAndNamedQuerySearch holds query-parameters and instance-properties for performing a named-query or model query
+ properties:
+ query-parameters:
+ type: object
+ $ref: "#/getDefinitions/query-parameters"
+ instance-filters:
+ type: object
+ $ref: "#/getDefinitions/instance-filters"
+ secondary-filts:
+ type: object
+ $ref: "#/getDefinitions/secondary-filts"
+ top-node-type:
type: string
- description: Trigger for operational monitoring of this resource by Service Assurance systems.
- operational-state:
+ secondary-filter-cut-point:
type: string
- description: Indicator for whether the resource is considered operational. Valid values are in-service-path and out-of-service-path.
- license-key:
+ model-constraint:
+ description: |
+ This is how we would capture constraints defining allowed sets of elements.
+ ###### Related Nodes
+ - TO model-element( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-constraint, MANY2ONE)
+ - MODEL-CONSTRAINT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET
+ required:
+ - model-constraint-uuid
+ - constrained-element-set-uuid-to-replace
+ properties:
+ model-constraint-uuid:
type: string
- description: OBSOLETE - do not use
- equipment-role:
+ constrained-element-set-uuid-to-replace:
type: string
- description: Client should send valid enumerated value
- orchestration-status:
+ constrained-element-sets:
+ type: array
+ items:
+ $ref: "#/getDefinitions/constrained-element-set"
+ resource-version:
type: string
- description: Orchestration status of this VNF, used by MSO.
- heat-stack-id:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-constraints:
+ properties:
+ model-constraint:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model-constraint"
+ model-element:
+ description: |
+ Defines how other models combine to make up a higher-level model.
+ ###### Related Nodes
+ - TO element-choice-set( model-element org.onap.relationships.inventory.BelongsTo element-choice-set, MANY2ONE)
+ - TO model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - TO model-ver( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE)
+ - TO model-ver( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - FROM constrained-element-set( constrained-element-set org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM model-constraint( model-constraint org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-element, MANY2ONE)
+ - MODEL-ELEMENT is DELETED when these are DELETED CONSTRAINED-ELEMENT-SET,MODEL-CONSTRAINT
+ required:
+ - model-element-uuid
+ - new-data-del-flag
+ - cardinality
+ properties:
+ model-element-uuid:
type: string
- description: Heat stack id corresponding to this instance, managed by MSO
- mso-catalog-key:
+ new-data-del-flag:
type: string
- description: Corresponds to the SDN-C catalog id used to configure this VCE
- management-option:
+ description: Indicates whether this element was created as part of instantiation from this model
+ cardinality:
type: string
- description: identifier of managed by company or customer
- ipv4-oam-address:
+ description: How many of this type of element are required/allowed
+ linkage-points:
type: string
- description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by generic-vnf.
- ipv4-loopback0-address:
+ resource-version:
type: string
- description: v4 Loopback0 address
- nm-lan-v6-address:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-elements:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model-element"
+ description: Defines how other models combine to make up a higher-level model
+ model-constraints:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model-constraint"
+ description: Describes new constraints on this model element that are not part of that model's definition
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ model-elements:
+ properties:
+ model-element:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model-element"
+ model-ver:
+ description: |
+ Subgraph definition provided by ASDC to describe a specific version of an inventory asset and its connections related to ASDC models
+ ###### Related Nodes
+ - TO model( model-ver org.onap.relationships.inventory.BelongsTo model, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.IsA model-ver, MANY2ONE)
+ - FROM model-element( model-element org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo model-ver, MANY2ONE)
+ - MODEL-VER cannot be deleted if linked to MODEL-ELEMENT
+ - MODEL-VER is DELETED when these are DELETED MODEL-ELEMENT,METADATUM
+ required:
+ - model-version-id
+ - model-name
+ - model-version
+ properties:
+ model-version-id:
type: string
- description: v6 Loopback address
- management-v6-address:
+ description: Unique identifier corresponding to one version of a model in ASDC
+ model-name:
type: string
- description: v6 management address
- vcpu:
- type: integer
- format: int64
- description: number of vcpus ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases
- vcpu-units:
+ description: Name of the model, which can change from version to version.
+ model-version:
type: string
- description: units associated with vcpu, used for VNFs with no vservers/flavors, to be used only in some usecases
- vmemory:
- type: integer
- format: int64
- description: number of GB of memory ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases
- vmemory-units:
+ description: Version
+ model-description:
type: string
- description: units associated with vmemory, used for VNFs with no vservers/flavors, to be used only in some usecases
- vdisk:
- type: integer
- format: int64
- description: number of vdisks ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases
- vdisk-units:
+ description: Description
+ resource-version:
type: string
- description: units associated with vdisk, used for VNFs with no vservers/flavors, to be used only in some usecases
- in-maint:
- type: boolean
- is-closed-loop-disabled:
- type: boolean
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-elements:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model-element"
+ metadata:
+ type: array
+ items:
+ $ref: "#/getDefinitions/metadatum"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ model-vers:
+ properties:
+ model-ver:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model-ver"
+ models:
+ description: |
+ Collection of subgraph definitions provided by ASDC to describe the inventory assets and their connections related to ASDC models
+ properties:
+ model:
+ type: array
+ items:
+ $ref: "#/getDefinitions/model"
+ multicast-configuration:
+ description: |
+ ###### Related Nodes
+ - FROM vlan( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)
+ required:
+ - multicast-configuration-id
+ - multicast-protocol
+ - rp-type
+ properties:
+ multicast-configuration-id:
+ type: string
+ description: Unique id of multicast configuration.
+ multicast-protocol:
+ type: string
+ description: protocol of multicast configuration
+ rp-type:
+ type: string
+ description: rp type of multicast configuration
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- summary-status:
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ multicast-configurations:
+ description: |
+ multicast configuration of generic-vnf ip-address
+ properties:
+ multicast-configuration:
+ type: array
+ items:
+ $ref: "#/getDefinitions/multicast-configuration"
+ named-queries:
+ properties:
+ named-query:
+ type: array
+ items:
+ $ref: "#/getDefinitions/named-query"
+ named-query:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - TO model( named-query org.onap.relationships.inventory.AppliesTo model, ONE2MANY)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - NAMED-QUERY is DELETED when these are DELETED NAMED-QUERY-ELEMENT
+ required:
+ - named-query-uuid
+ - named-query-name
+ - named-query-version
+ properties:
+ named-query-uuid:
type: string
- description: details regarding the generic-vnf operation, PLEASE DISCONTINUE USE OF THIS FIELD.
- encrypted-access-flag:
- type: boolean
- description: indicates whether generic-vnf access uses SSH
- persona-model-id:
+ named-query-name:
type: string
- description: the ASDC model id for this resource or service model.
- persona-model-version:
+ named-query-version:
type: string
- description: the ASDC model version for this resource or service model.
- model-version-id:
+ required-input-param:
type: string
- description: the ASDC model version for this resource or service model.
- persona-model-customization-id:
+ description:
type: string
- description: captures the id of all the configuration used to customize the resource for the service.
- widget-model-id:
+ resource-version:
type: string
- description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
- widget-model-version:
+ named-query-elements:
+ type: array
+ items:
+ $ref: "#/getDefinitions/named-query-element"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ named-query-element:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query( named-query-element org.onap.relationships.inventory.BelongsTo named-query, ONE2ONE)
+ - TO model( named-query-element org.onap.relationships.inventory.IsA model, MANY2ONE)
+ - TO named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM property-constraint( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM related-lookup( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - FROM named-query-element( named-query-element org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ - NAMED-QUERY-ELEMENT is DELETED when these are DELETED PROPERTY-CONSTRAINT,RELATED-LOOKUP
+ required:
+ - named-query-element-uuid
+ properties:
+ named-query-element-uuid:
type: string
- description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
- as-number:
+ property-collect-list:
type: string
- description: as-number of the VNF
- regional-resource-subzone:
+ resource-version:
type: string
- description: represents sub zone of the rr plane
- selflink:
+ property-limit-desc:
type: string
- description: Path to the controller object.
+ do-not-output:
+ type: string
+ named-query-elements:
+ type: array
+ items:
+ $ref: "#/getDefinitions/named-query-element"
+ related-lookups:
+ type: array
+ items:
+ $ref: "#/getDefinitions/related-lookup"
+ property-constraints:
+ type: array
+ items:
+ $ref: "#/getDefinitions/property-constraint"
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- l-interfaces:
+ $ref: "#/getDefinitions/relationship"
+ named-query-elements:
+ properties:
+ named-query-element:
+ type: array
+ items:
+ $ref: "#/getDefinitions/named-query-element"
+ network:
+ description: |
+ Namespace for network inventory resources.
+ properties:
+ logical-links:
type: array
items:
- $ref: "#/definitions/l-interface"
- lag-interfaces:
+ $ref: "#/getDefinitions/logical-link"
+ site-pair-sets:
type: array
items:
- $ref: "#/definitions/lag-interface"
- vf-modules:
+ $ref: "#/getDefinitions/site-pair-set"
+ vpn-bindings:
type: array
items:
- $ref: "#/definitions/vf-module"
- licenses:
+ $ref: "#/getDefinitions/vpn-binding"
+ vpls-pes:
type: array
items:
- $ref: "#/definitions/license"
- entitlements:
+ $ref: "#/getDefinitions/vpls-pe"
+ multicast-configurations:
type: array
items:
- $ref: "#/definitions/entitlement"
- generic-vnfs:
- description: |
- Collection of VNFs
+ $ref: "#/getDefinitions/multicast-configuration"
+ vces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vce"
+ vnfcs:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vnfc"
+ l3-networks:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l3-network"
+ network-policies:
+ type: array
+ items:
+ $ref: "#/getDefinitions/network-policy"
+ generic-vnfs:
+ type: array
+ items:
+ $ref: "#/getDefinitions/generic-vnf"
+ lag-links:
+ type: array
+ items:
+ $ref: "#/getDefinitions/lag-link"
+ newvces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/newvce"
+ pnfs:
+ type: array
+ items:
+ $ref: "#/getDefinitions/pnf"
+ physical-links:
+ type: array
+ items:
+ $ref: "#/getDefinitions/physical-link"
+ ipsec-configurations:
+ type: array
+ items:
+ $ref: "#/getDefinitions/ipsec-configuration"
+ route-table-references:
+ type: array
+ items:
+ $ref: "#/getDefinitions/route-table-reference"
+ instance-groups:
+ type: array
+ items:
+ $ref: "#/getDefinitions/instance-group"
+ zones:
+ type: array
+ items:
+ $ref: "#/getDefinitions/zone"
+ network-policies:
properties:
- generic-vnf:
+ network-policy:
type: array
items:
- $ref: "#/definitions/generic-vnf"
- lag-link:
+ $ref: "#/getDefinitions/network-policy"
+ network-policy:
description: |
- LAG links can connect lag-interfaces
- ###### Default Delete Scope
- THIS_NODE_ONLY
###### Related Nodes
- - FROM lag-interface
- - FROM logical-link
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses network-policy, MANY2MANY)
required:
- - link-name
+ - network-policy-id
properties:
- link-name:
+ network-policy-id:
type: string
- description: Alphabetical concatenation of lag-interface names
+ description: UUID representing unique key to this instance
+ network-policy-fqdn:
+ type: string
+ description: Contrail FQDN for the policy
+ heat-stack-id:
+ type: string
+ description: ID for the openStack Heat instance
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- lag-links:
+ $ref: "#/getDefinitions/relationship"
+ network-profile:
description: |
- Collection of link aggregation connections
+ Network profile populated by SDN-GP for SNMP
+ ###### Related Nodes
+ - TO generic-vnf( network-profile org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ required:
+ - nm-profile-name
properties:
- lag-link:
+ nm-profile-name:
+ type: string
+ description: Unique name of network profile.
+ community-string:
+ type: string
+ description: Encrypted SNMP community string
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ network-profiles:
+ description: |
+ Collection of network profiles
+ properties:
+ network-profile:
type: array
items:
- $ref: "#/definitions/lag-link"
+ $ref: "#/getDefinitions/network-profile"
newvce:
description: |
This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce.
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
###### Related Nodes
- - TO l-interface (comprises newvce, Many2Many)
+ - FROM l-interface( l-interface org.onap.relationships.inventory.BelongsTo newvce, MANY2ONE)
+ - NEWVCE is DELETED when these are DELETED L-INTERFACE
required:
- vnf-id2
- vnf-name
@@ -40631,11 +59501,11 @@ definitions:
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
+ $ref: "#/getDefinitions/relationship"
l-interfaces:
type: array
items:
- $ref: "#/definitions/l-interface"
+ $ref: "#/getDefinitions/l-interface"
newvces:
description: |
This object fills in the gaps from vce that were incorporated into generic-vnf. This object will be retired with vce.
@@ -40643,20 +59513,361 @@ definitions:
newvce:
type: array
items:
- $ref: "#/definitions/newvce"
+ $ref: "#/getDefinitions/newvce"
+ notification-event:
+ properties:
+ cambria.partition:
+ type: string
+ notification-event-header:
+ type: object
+ $ref: "#/getDefinitions/notification-event-header"
+ notification-event-header:
+ properties:
+ id:
+ type: string
+ timestamp:
+ type: string
+ source-name:
+ type: string
+ domain:
+ type: string
+ sequence-number:
+ type: string
+ severity:
+ type: string
+ event-type:
+ type: string
+ version:
+ type: string
+ action:
+ type: string
+ entity-type:
+ type: string
+ top-entity-type:
+ type: string
+ entity-link:
+ type: string
+ status:
+ type: string
+ notify:
+ required:
+ - event-id
+ properties:
+ event-id:
+ type: string
+ node-type:
+ type: string
+ event-trigger:
+ type: string
+ key-data:
+ type: array
+ items:
+ $ref: "#/getDefinitions/key-data"
+ selflink:
+ type: string
+ oam-network:
+ description: |
+ OAM network, to be deprecated shortly. Do not use for new purposes.
+ ###### Related Nodes
+ - TO cloud-region( oam-network org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO complex( oam-network org.onap.relationships.inventory.AppliesTo complex, MANY2MANY)
+ - TO service-capability( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ required:
+ - network-uuid
+ - network-name
+ - cvlan-tag
+ properties:
+ network-uuid:
+ type: string
+ description: UUID of the network. Unique across a cloud-region
+ network-name:
+ type: string
+ description: Name of the network.
+ cvlan-tag:
+ type: integer
+ format: int64
+ description: cvlan-id
+ ipv4-oam-gateway-address:
+ type: string
+ description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
+ ipv4-oam-gateway-address-prefix-length:
+ type: integer
+ format: int32
+ description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ oam-networks:
+ description: |
+ Collection of OAM networks, to be deprecated shortly. Do not use for new purposes.
+ properties:
+ oam-network:
+ type: array
+ items:
+ $ref: "#/getDefinitions/oam-network"
+ operational-environment:
+ description: |
+ It is a logical partition of the cloud which allows to have multiple environments in the production AIC.
+ ###### Related Nodes
+ - TO operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)
+ - FROM operational-environment( operational-environment org.onap.relationships.inventory.Uses operational-environment, ONE2ONE)
+ required:
+ - operational-environment-id
+ - operational-environment-name
+ - operational-environment-type
+ - operational-environment-status
+ - tenant-context
+ - workload-context
+ properties:
+ operational-environment-id:
+ type: string
+ description: UUID of an operational environment
+ operational-environment-name:
+ type: string
+ description: Operational Environment name
+ operational-environment-type:
+ type: string
+ description: Operational Environment Type.
+ operational-environment-status:
+ type: string
+ description: Status
+ tenant-context:
+ type: string
+ description: Tenant Context.
+ workload-context:
+ type: string
+ description: Workload Context.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ operational-environments:
+ description: |
+ a logical partition of the cloud which allows to have multiple environments in the production AIC.
+ properties:
+ operational-environment:
+ type: array
+ items:
+ $ref: "#/getDefinitions/operational-environment"
+ overloaded-model:
+ description: |
+ Allows for legacy POST of old-style and new-style models
+ required:
+ - model-invariant-id
+ - model-name-version-id
+ - model-type
+ - model-name
+ - model-id
+ - model-version
+ properties:
+ model-invariant-id:
+ type: string
+ description: Unique identifier corresponding to the main definition of a model in ASDC
+ model-name-version-id:
+ type: string
+ description: Unique identifier corresponding to one version of a model in ASDC
+ model-type:
+ type: string
+ description: Type of the model, e.g., service, resource, widget, etc.
+ model-name:
+ type: string
+ description: Name of the model, which can change from version to version.
+ model-id:
+ type: string
+ description: Invariant unique ID which does not change from version to version
+ model-version:
+ type: string
+ description: Version
+ model-description:
+ type: string
+ description: Description
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ model-vers:
+ type: object
+ $ref: "#/getDefinitions/model-vers"
+ relationship-list:
+ type: object
+ $ref: "#/getDefinitions/relationship-list"
+ owning-entities:
+ description: |
+ Collection of owning-entities
+ properties:
+ owning-entity:
+ type: array
+ items:
+ $ref: "#/getDefinitions/owning-entity"
+ owning-entity:
+ description: |
+ describes an owning-entity
+ ###### Related Nodes
+ - FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo owning-entity, MANY2ONE)
+ required:
+ - owning-entity-id
+ - owning-entity-name
+ properties:
+ owning-entity-id:
+ type: string
+ description: UUID of an owning entity
+ owning-entity-name:
+ type: string
+ description: Owning entity name
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ p-interface:
+ description: |
+ Physical interface (e.g., nic)
+ ###### Related Nodes
+ - TO logical-link( p-interface tosca.relationships.network.LinksTo logical-link, MANY2ONE)
+ - TO physical-link( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)
+ - TO pnf( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - TO pserver( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - TO vpls-pe( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM lag-interface( lag-interface org.onap.relationships.inventory.Uses p-interface, MANY2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.BindsTo p-interface, MANY2ONE)
+ - P-INTERFACE is DELETED when these are DELETED L-INTERFACE
+ - P-INTERFACE deletion means associated objects of these types are also DELETED:PHYSICAL-LINK
+ required:
+ - interface-name
+ properties:
+ interface-name:
+ type: string
+ description: Name that identifies the physical interface
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ port-description:
+ type: string
+ description: Nature of the services and connectivity on this port.
+ equipment-identifier:
+ type: string
+ description: CLEI or other specification for p-interface hardware.
+ interface-role:
+ type: string
+ description: Role specification for p-interface hardware.
+ interface-type:
+ type: string
+ description: Indicates the physical properties of the interface.
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l-interface"
+ p-interfaces:
+ description: |
+ Collection of physical interfaces.
+ properties:
+ p-interface:
+ type: array
+ items:
+ $ref: "#/getDefinitions/p-interface"
+ physical-link:
+ description: |
+ Collection of physical connections, typically between p-interfaces
+ ###### Related Nodes
+ - FROM p-interface( p-interface tosca.relationships.network.LinksTo physical-link, MANY2ONE)
+ required:
+ - link-name
+ properties:
+ link-name:
+ type: string
+ description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
+ speed-value:
+ type: string
+ description: Captures the numeric part of the speed
+ speed-units:
+ type: string
+ description: Captures the units corresponding to the speed
+ circuit-id:
+ type: string
+ description: Circuit it
+ dual-mode:
+ type: string
+ description: Dual access mode (e.g., primary, secondary
+ management-option:
+ type: string
+ description: To provide information on who manages this circuit. A&AI or 3rd party transport provider
+ service-provider-name:
+ type: string
+ description: Name of the service Provider on this link.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ physical-links:
+ description: |
+ Collection of physical connections, typically between p-interfaces
+ properties:
+ physical-link:
+ type: array
+ items:
+ $ref: "#/getDefinitions/physical-link"
+ platform:
+ description: |
+ describes a platform
+ ###### Related Nodes
+ - TO generic-vnf( platform org.onap.relationships.inventory.Uses generic-vnf, MANY2MANY)
+ required:
+ - platform-name
+ properties:
+ platform-name:
+ type: string
+ description: Name of the platform
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ platforms:
+ description: |
+ Collection of platforms
+ properties:
+ platform:
+ type: array
+ items:
+ $ref: "#/getDefinitions/platform"
pnf:
description: |
PNF represents a physical network function. typically equipment used in the D1 world.
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
###### Related Nodes
- - TO p-interface (comprises pnf, Many2Many)
- - TO lag-interface (comprises pnf, One2Many)
- - TO complex (Many2One)
- - TO instance-group (Many2Many)
- - TO zone (Many2One)
- - FROM logical-link
- - FROM service-instance
+ - TO complex( pnf org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO instance-group( pnf org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO zone( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pnf, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo pnf, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf pnf, ONE2MANY)
+ - PNF is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
required:
- pnf-name
- in-maint
@@ -40729,15 +59940,15 @@ definitions:
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
+ $ref: "#/getDefinitions/relationship"
p-interfaces:
type: array
items:
- $ref: "#/definitions/p-interface"
+ $ref: "#/getDefinitions/p-interface"
lag-interfaces:
type: array
items:
- $ref: "#/definitions/lag-interface"
+ $ref: "#/getDefinitions/lag-interface"
pnfs:
description: |
Collection of Physical Network Functions.
@@ -40745,183 +59956,371 @@ definitions:
pnf:
type: array
items:
- $ref: "#/definitions/pnf"
- physical-link:
+ $ref: "#/getDefinitions/pnf"
+ port-group:
description: |
- Collection of physical connections, typically between p-interfaces
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Used to capture the network interfaces of this VCE
###### Related Nodes
- - FROM p-interface
+ - TO vce( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM cvlan-tag( cvlan-tag org.onap.relationships.inventory.BelongsTo port-group, MANY2ONE)
+ - PORT-GROUP is DELETED when these are DELETED CVLAN-TAG
required:
- - link-name
+ - interface-id
+ - orchestration-status
properties:
- link-name:
+ interface-id:
type: string
- description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
- speed-value:
+ description: Unique ID of the interface
+ neutron-network-id:
type: string
- description: Captures the numeric part of the speed
- speed-units:
+ description: Neutron network id of this Interface
+ neutron-network-name:
type: string
- description: Captures the units corresponding to the speed
- circuit-id:
+ description: Neutron network name of this Interface
+ interface-role:
type: string
- description: Circuit it
- dual-mode:
+ description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
+ resource-version:
type: string
- description: Dual access mode (e.g., primary, secondary
- management-option:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ port-group-id:
type: string
- description: To provide information on who manages this circuit. A&AI or 3rd party transport provider
- service-provider-name:
+ description: Unique ID for port group in vmware
+ port-group-name:
type: string
- description: Name of the service Provider on this link.
- resource-version:
+ description: Likely to duplicate value of neutron network name
+ switch-name:
type: string
- description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ description: DVS or standard switch name (should be non-null for port groups associated with DVS)
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ cvlan-tags:
+ type: array
+ items:
+ $ref: "#/getDefinitions/cvlan-tag-entry"
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- physical-links:
- description: |
- Collection of physical connections, typically between p-interfaces
+ $ref: "#/getDefinitions/relationship"
+ port-groups:
properties:
- physical-link:
+ port-group:
type: array
items:
- $ref: "#/definitions/physical-link"
- vig-server:
+ $ref: "#/getDefinitions/port-group"
+ project:
description: |
- vig-server contains information about a vig server used for IPSec-configuration. Populated by SDN-C from 1607
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ describes the project
###### Related Nodes
- - FROM ipsec-configuration (is composed of vig-server)
+ - TO service-instance( project org.onap.relationships.inventory.Uses service-instance, ONE2MANY)
required:
- - vig-address-type
+ - project-name
properties:
- vig-address-type:
- type: string
- description: indicates whether the VIG is for AVPN or INTERNET
- ipaddress-v4-vig:
- type: string
- description: v4 IP of the vig server
- ipaddress-v6-vig:
+ project-name:
type: string
- description: v6 IP of the vig server
+ description: Name of the project deploying a service
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- vig-servers:
+ $ref: "#/getDefinitions/relationship"
+ projects:
+ description: |
+ Collection of projects
properties:
- vig-server:
+ project:
type: array
items:
- $ref: "#/definitions/vig-server"
- ipsec-configuration:
+ $ref: "#/getDefinitions/project"
+ properties:
description: |
- IPSec configuration node will contain various configuration data for the NMTE VNF. This node will have an edge to the generic-vnf (vnf type = TE). Starting 1607, this data will be populated by SDN-C
- ###### Default Delete Scope
- CASCADE_TO_CHILDREN
+ Property holder for query properties or instance properties
+ properties:
+ property-name:
+ type: string
+ property-value:
+ type: string
+ property-constraint:
+ description: |
+ TBD
###### Related Nodes
- - TO vig-server (comprises ipsec-configuration, One2Many)
- - FROM generic-vnf
+ - TO named-query-element( property-constraint org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
required:
- - ipsec-configuration-id
+ - property-constraint-uuid
+ - constraint-type
+ - property-name
+ - property-value
properties:
- ipsec-configuration-id:
+ property-constraint-uuid:
type: string
- description: UUID of this configuration
- requested-vig-address-type:
+ constraint-type:
type: string
- description: Indicate the type of VIG server like AVPN, INTERNET, BOTH
- requested-encryption-strength:
+ property-name:
type: string
- description: Encryption values like 3des-cbc, des-cbc, aes-128-cbc, aes-192-cbc, aes-265-cbc
- requested-dmz-type:
+ property-value:
type: string
- description: can offer a shared DMZ or a DMZ specific to a customer
- shared-dmz-network-address:
+ resource-version:
type: string
- description: Network address of shared DMZ
- requested-customer-name:
+ property-constraints:
+ properties:
+ property-constraint:
+ type: array
+ items:
+ $ref: "#/getDefinitions/property-constraint"
+ pserver:
+ description: |
+ Compute host whose hostname must be unique and must exactly match what is sent as a relationship to a vserver.
+ ###### Related Nodes
+ - TO group-assignment( pserver org.onap.relationships.inventory.MemberOf group-assignment, MANY2ONE)
+ - TO availability-zone( pserver org.onap.relationships.inventory.MemberOf availability-zone, MANY2ONE)
+ - TO cloud-region( pserver org.onap.relationships.inventory.LocatedIn cloud-region, MANY2ONE)
+ - TO complex( pserver org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO zone( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn pserver, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.BridgedTo pserver, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo pserver, MANY2ONE)
+ - FROM vserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)
+ - PSERVER cannot be deleted if linked to GENERIC-VNF,LOGICAL-LINK,VSERVER
+ - PSERVER is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
+ - PSERVER cannot be deleted if linked to GROUP-ASSIGNMENT
+ required:
+ - hostname
+ - in-maint
+ properties:
+ hostname:
type: string
- description: If the DMZ is a custom DMZ, this field will indicate the customer information
- ike-version:
+ description: Value from executing hostname on the compute node.
+ ptnii-equip-name:
type: string
- description: can be 1 or 2
- ikev1-authentication:
+ description: PTNII name
+ number-of-cpus:
+ type: integer
+ format: int32
+ description: Number of cpus
+ disk-in-gigabytes:
+ type: integer
+ format: int32
+ description: Disk size, in GBs
+ ram-in-megabytes:
+ type: integer
+ format: int32
+ description: RAM size, in MBs
+ equip-type:
type: string
- description: Contains values like md5, sha1, sha256, sha384
- ikev1-encryption:
+ description: Equipment type. Source of truth should define valid values.
+ equip-vendor:
type: string
- description: Encyption values like 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
- ikev1-dh-group:
+ description: Equipment vendor. Source of truth should define valid values.
+ equip-model:
type: string
- description: Diffie-Hellman group like DH-GROUP2, DH-GROUP5, DH-GROUP14
- ikev1-am-group-id:
+ description: Equipment model. Source of truth should define valid values.
+ fqdn:
type: string
- description: Group name defined in VIG for clients using aggressive mode
- ikev1-am-password:
+ description: Fully-qualified domain name
+ pserver-selflink:
type: string
- description: pre-shared key for the above group name
- ikev1-sa-lifetime:
+ description: URL to endpoint where AAI can get more details
+ ipv4-oam-address:
type: string
- description: Lifetime for IKEv1 SA
- ipsec-authentication:
+ description: Used to configure device, also used for troubleshooting and is IP used for traps generated by device.
+ serial-number:
type: string
- description: md5, sha1, sha256, sha384
- ipsec-encryption:
+ description: Serial number, may be queried
+ ipaddress-v4-loopback-0:
type: string
- description: 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
- ipsec-sa-lifetime:
+ description: IPV4 Loopback 0 address
+ ipaddress-v6-loopback-0:
type: string
- description: Life time for IPSec SA
- ipsec-pfs:
+ description: IPV6 Loopback 0 address
+ ipaddress-v4-aim:
type: string
- description: enable PFS or not
- xauth-userid:
+ description: IPV4 AIM address
+ ipaddress-v6-aim:
type: string
- description: user ID for xAuth, sm-user, ,nmteHostName
- xauth-user-password:
+ description: IPV6 AIM address
+ ipaddress-v6-oam:
type: string
- description: Encrypted using the Juniper $9$ algorithm
- dpd-interval:
+ description: IPV6 OAM address
+ inv-status:
type: string
- description: The time between DPD probe
- dpd-frequency:
+ description: CANOPI's inventory status. Only set with values exactly as defined by CANOPI.
+ pserver-id:
type: string
- description: Maximum number of DPD before claiming the tunnel is down
+ description: ID of Pserver
+ internet-topology:
+ type: string
+ description: internet topology of Pserver
+ in-maint:
+ type: boolean
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ pserver-name2:
+ type: string
+ description: alternative pserver name
+ purpose:
+ type: string
+ description: purpose of pserver
+ prov-status:
+ type: string
+ description: Prov Status of this device (not under canopi control) Valid values [PREPROV/NVTPROV/PROV]
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- vig-servers:
+ $ref: "#/getDefinitions/relationship"
+ p-interfaces:
type: array
items:
- $ref: "#/definitions/vig-server"
- ipsec-configurations:
+ $ref: "#/getDefinitions/p-interface"
+ lag-interfaces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/lag-interface"
+ pservers:
+ description: |
+ Collection of compute hosts.
properties:
- ipsec-configuration:
+ pserver:
type: array
items:
- $ref: "#/definitions/ipsec-configuration"
+ $ref: "#/getDefinitions/pserver"
+ query-parameters:
+ description: |
+ QueryParameters for performing a named-query or model query
+ properties:
+ named-query:
+ type: object
+ $ref: "#/getDefinitions/named-query"
+ overloaded-model:
+ type: object
+ $ref: "#/getDefinitions/overloaded-model"
+ related-lookup:
+ description: |
+ TBD
+ ###### Related Nodes
+ - TO named-query-element( related-lookup org.onap.relationships.inventory.BelongsTo named-query-element, MANY2ONE)
+ required:
+ - related-lookup-uuid
+ - source-node-type
+ - source-node-property
+ - target-node-type
+ - target-node-property
+ properties:
+ related-lookup-uuid:
+ type: string
+ source-node-type:
+ type: string
+ source-node-property:
+ type: string
+ target-node-type:
+ type: string
+ target-node-property:
+ type: string
+ property-collect-list:
+ type: string
+ resource-version:
+ type: string
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ related-lookups:
+ properties:
+ related-lookup:
+ type: array
+ items:
+ $ref: "#/getDefinitions/related-lookup"
+ related-to-property:
+ properties:
+ property-key:
+ type: string
+ description: Key part of a key/value pair
+ property-value:
+ type: string
+ description: Value part of a key/value pair
+ relationship:
+ properties:
+ related-to:
+ type: string
+ description: A keyword provided by A&AI to indicate type of node.
+ related-link:
+ type: string
+ description: URL to the object in A&AI.
+ relationship-data:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship-data"
+ related-to-property:
+ type: array
+ items:
+ $ref: "#/getDefinitions/related-to-property"
+ relationship-data:
+ required:
+ - relationship-key
+ - relationship-value
+ properties:
+ relationship-key:
+ type: string
+ description: A keyword provided by A&AI to indicate an attribute.
+ relationship-value:
+ type: string
+ description: Value of the attribute.
+ relationship-list:
+ properties:
+ relationship:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ reserved-prop-names:
+ description: |
+ Internal map to define some reserved properties of a vertex
+ properties:
+ last-mod-source-of-truth:
+ type: string
+ aai-node-type:
+ type: string
+ aai-created-ts:
+ type: integer
+ format: int64
+ aai-unique-key:
+ type: string
+ aai-last-mod-ts:
+ type: integer
+ format: int64
+ source-of-truth:
+ type: string
+ aai-uri:
+ type: string
+ response-list:
+ description: |
+ Response container for the results of a named-query or model query
+ properties:
+ inventory-response-items:
+ type: object
+ $ref: "#/getDefinitions/inventory-response-items"
+ result-data:
+ properties:
+ resource-type:
+ type: string
+ description: The specific type of node in the A&AI graph
+ resource-link:
+ type: string
+ description: The URL to the specific resource
route-table-reference:
description: |
Openstack route table reference.
- ###### Default Delete Scope
- THIS_NODE_ONLY
###### Related Nodes
- - FROM l3-network
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses route-table-reference, MANY2MANY)
required:
- route-table-reference-id
- route-table-reference-fqdn
@@ -40938,7 +60337,7 @@ definitions:
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
+ $ref: "#/getDefinitions/relationship"
route-table-references:
description: |
Collection of openstack route table references
@@ -40946,300 +60345,738 @@ definitions:
route-table-reference:
type: array
items:
- $ref: "#/definitions/route-table-reference"
- instance-group:
+ $ref: "#/getDefinitions/route-table-reference"
+ route-target:
description: |
- General mechanism for grouping instances
- ###### Default Delete Scope
- THIS_NODE_ONLY
+ Route target information
###### Related Nodes
- - TO model (Many2Many)
- - FROM pnf
- - FROM allotted-resource
- - FROM generic-vnf
- - FROM service-instance
+ - TO vpn-binding( route-target org.onap.relationships.inventory.BelongsTo vpn-binding, MANY2ONE)
required:
- - id
- - description
- - type
+ - global-route-target
+ - route-target-role
properties:
- id:
- type: string
- description: Instance Group ID, UUID assigned to this instance.
- description:
- type: string
- description: Descriptive text to help identify the usage of this instance-group
- type:
+ global-route-target:
type: string
- description: Only valid value today is lower case ha for high availability
- sub-type:
+ description: Number used to identify an RT, globally unique in the network
+ route-target-role:
type: string
- description: Valid values for ha type are [geo-activeactive, geo-activestandby, local-activeactive, local-activestandby]
+ description: Role assigned to this route target
resource-version:
type: string
- description: Concurrency value
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- instance-groups:
+ $ref: "#/getDefinitions/relationship"
+ route-targets:
description: |
- Collection of openstack route table references
+ Collection of route target information
properties:
- instance-group:
+ route-target:
type: array
items:
- $ref: "#/definitions/instance-group"
- zone:
+ $ref: "#/getDefinitions/route-target"
+ routing-instance:
description: |
- A zone is a grouping of assets in a location homing to the same connections into the CBB
- ###### Default Delete Scope
- THIS_NODE_ONLY
###### Related Nodes
- - TO complex (Many2One)
- - FROM cloud-region
- - FROM pserver
- - FROM pnf
+ - TO site-pair-set( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)
+ - FROM site-pair( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)
+ - ROUTING-INSTANCE is DELETED when these are DELETED SITE-PAIR
required:
- - zone-id
- - zone-name
- - design-type
- - zone-context
+ - routing-instance-id
properties:
- zone-id:
+ routing-instance-id:
type: string
- description: Code assigned by AIC to the zone
- zone-name:
+ description: Unique id of routing instance
+ rpm-owner:
type: string
- description: English name associated with the zone
- design-type:
+ description: rpm owner
+ resource-version:
type: string
- description: Design of zone [Medium/Large?]
- zone-context:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ site-pairs:
+ type: array
+ items:
+ $ref: "#/getDefinitions/site-pair"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ routing-instances:
+ description: |
+ set of probes related to generic-vnf routing instance
+ properties:
+ routing-instance:
+ type: array
+ items:
+ $ref: "#/getDefinitions/routing-instance"
+ sdn-zone-response:
+ properties:
+ oam-networks:
+ type: object
+ $ref: "#/getDefinitions/oam-networks"
+ az-and-dvs-switches:
+ type: array
+ items:
+ $ref: "#/getDefinitions/az-and-dvs-switches"
+ search:
+ properties:
+ edge-tag-query-result:
+ type: object
+ $ref: "#/getDefinitions/edge-tag-query-result"
+ edge-tag-query-request:
+ type: object
+ $ref: "#/getDefinitions/edge-tag-query-request"
+ search-results:
+ type: object
+ $ref: "#/getDefinitions/search-results"
+ sdn-zone-response:
+ type: object
+ $ref: "#/getDefinitions/sdn-zone-response"
+ search-results:
+ properties:
+ result-data:
+ type: array
+ items:
+ $ref: "#/getDefinitions/result-data"
+ secondary-filt:
+ description: |
+ SecondaryFilt for performing a named-query or model query
+ secondary-filter:
+ properties:
+ property-name:
type: string
- description: Context of zone [production/test]
- status:
+ filter-type:
type: string
- description: Status of a zone.
+ property-value:
+ type: string
+ secondary-filts:
+ description: |
+ SecondaryFilts for performing a named-query or model query
+ properties:
+ secondary-filt:
+ type: array
+ items:
+ $ref: "#/getDefinitions/secondary-filt"
+ segmentation-assignment:
+ description: |
+ Openstack segmentation assignment.
+ ###### Related Nodes
+ - TO l3-network( segmentation-assignment org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ required:
+ - segmentation-id
+ properties:
+ segmentation-id:
+ type: string
+ description: Route Table Reference id, UUID assigned to this instance.
resource-version:
type: string
description: Concurrency value
relationship-list:
type: array
items:
- $ref: "#/definitions/relationship"
- zones:
+ $ref: "#/getDefinitions/relationship"
+ segmentation-assignments:
description: |
- Collection of zones
+ Collection of openstack segmentation assignments
properties:
- zone:
+ segmentation-assignment:
type: array
items:
- $ref: "#/definitions/zone"
- network:
+ $ref: "#/getDefinitions/segmentation-assignment"
+ service:
description: |
- Namespace for network inventory resources.
+ Stand-in for service model definitions. Likely to be deprecated in favor of models from ASDC. Does not strictly map to ASDC services.
+ required:
+ - service-id
+ - service-description
properties:
- logical-links:
+ service-id:
+ type: string
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ service-description:
+ type: string
+ description: Description of the service
+ service-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ service-version:
+ type: string
+ description: service version
+ relationship-list:
type: array
items:
- $ref: "#/definitions/logical-link"
- site-pair-sets:
+ $ref: "#/getDefinitions/relationship"
+ service-capabilities:
+ description: |
+ Collection of service capabilities.
+ properties:
+ service-capability:
type: array
- items:
- $ref: "#/definitions/site-pair-set"
- vpn-bindings:
+ items:
+ $ref: "#/getDefinitions/service-capability"
+ service-capability:
+ description: |
+ Early definition of server/resource pairings, likely to be replaced by models. No new use should be made of this.
+ ###### Related Nodes
+ - FROM availability-zone( availability-zone org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - FROM oam-network( oam-network org.onap.relationships.inventory.AppliesTo service-capability, MANY2MANY)
+ - SERVICE-CAPABILITY cannot be deleted if linked to AVAILABILITY-ZONE,OAM-NETWORK
+ required:
+ - service-type
+ - vnf-type
+ properties:
+ service-type:
+ type: string
+ description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/vpn-binding"
- vpls-pes:
+ $ref: "#/getDefinitions/relationship"
+ service-design-and-creation:
+ description: |
+ Namespace for objects managed by ASDC
+ properties:
+ vnf-images:
type: array
items:
- $ref: "#/definitions/vpls-pe"
- multicast-configurations:
+ $ref: "#/getDefinitions/vnf-image"
+ services:
type: array
items:
- $ref: "#/definitions/multicast-configuration"
- vces:
+ $ref: "#/getDefinitions/service"
+ service-capabilities:
type: array
items:
- $ref: "#/definitions/vce"
- vnfcs:
+ $ref: "#/getDefinitions/service-capability"
+ models:
type: array
items:
- $ref: "#/definitions/vnfc"
- l3-networks:
+ $ref: "#/getDefinitions/model"
+ named-queries:
type: array
items:
- $ref: "#/definitions/l3-network"
- network-policies:
+ $ref: "#/getDefinitions/named-query"
+ service-instance:
+ description: |
+ Instance of a service
+ ###### Related Nodes
+ - TO generic-vnf( service-instance org.onap.relationships.inventory.ComposedOf generic-vnf, ONE2MANY)
+ - TO l3-network( service-instance org.onap.relationships.inventory.ComposedOf l3-network, ONE2MANY)
+ - TO allotted-resource( service-instance org.onap.relationships.inventory.Uses allotted-resource, MANY2MANY)
+ - TO connector( service-instance org.onap.relationships.inventory.Uses connector, MANY2MANY)
+ - TO ctag-assignment( service-instance org.onap.relationships.inventory.Uses ctag-assignment, ONE2MANY)
+ - TO cvlan-tag( service-instance org.onap.relationships.inventory.ComposedOf cvlan-tag, MANY2MANY)
+ - TO instance-group( service-instance org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO logical-link( service-instance org.onap.relationships.inventory.Uses logical-link, ONE2MANY)
+ - TO pnf( service-instance org.onap.relationships.inventory.ComposedOf pnf, ONE2MANY)
+ - TO service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)
+ - TO vlan( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)
+ - TO service-subscription( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)
+ - TO vce( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM metadatum( metadatum org.onap.relationships.inventory.BelongsTo service-instance, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf service-instance, ONE2MANY)
+ - SERVICE-INSTANCE is DELETED when these are DELETED ALLOTTED-RESOURCE,METADATUM
+ - SERVICE-INSTANCE deletion means associated objects of these types are also DELETED:LOGICAL-LINK
+ required:
+ - service-instance-id
+ properties:
+ service-instance-id:
+ type: string
+ description: Uniquely identifies this instance of a service
+ service-instance-name:
+ type: string
+ description: This field will store a name assigned to the service-instance.
+ persona-model-id:
+ type: string
+ description: the ASDC model id for this resource or service model.
+ persona-model-version:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ model-version-id:
+ type: string
+ description: the ASDC model version for this resource or service model.
+ widget-model-id:
+ type: string
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
+ type: string
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ bandwidth-total:
+ type: string
+ description: Indicates the total bandwidth to be used for this service.
+ bandwidth-up-wan1:
+ type: string
+ description: indicates the upstream bandwidth this service will use on the WAN1 port of the physical device.
+ bandwidth-down-wan1:
+ type: string
+ description: indicates the downstream bandwidth this service will use on the WAN1 port of the physical device.
+ bandwidth-up-wan2:
+ type: string
+ description: indicates the upstream bandwidth this service will use on the WAN2 port of the physical device.
+ bandwidth-down-wan2:
+ type: string
+ description: indicates the downstream bandwidth this service will use on the WAN2 port of the physical device.
+ vhn-portal-url:
+ type: string
+ description: URL customers will use to access the vHN Portal.
+ service-instance-location-id:
+ type: string
+ description: An identifier that customers assign to the location where this service is being used.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ selflink:
+ type: string
+ description: Path to the controller object.
+ orchestration-status:
+ type: string
+ description: Orchestration status of this service.
+ relationship-list:
type: array
items:
- $ref: "#/definitions/network-policy"
- generic-vnfs:
+ $ref: "#/getDefinitions/relationship"
+ metadata:
type: array
items:
- $ref: "#/definitions/generic-vnf"
- lag-links:
+ $ref: "#/getDefinitions/metadatum"
+ allotted-resources:
type: array
items:
- $ref: "#/definitions/lag-link"
- newvces:
+ $ref: "#/getDefinitions/allotted-resource"
+ service-instances:
+ description: |
+ Collection of service instances
+ properties:
+ service-instance:
type: array
- items:
- $ref: "#/definitions/newvce"
- pnfs:
+ items:
+ $ref: "#/getDefinitions/service-instance"
+ service-subscription:
+ description: |
+ Object that group service instances.
+ ###### Related Nodes
+ - TO customer( service-subscription org.onap.relationships.inventory.BelongsTo customer, MANY2ONE)
+ - TO tenant( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.BelongsTo service-subscription, MANY2ONE)
+ - SERVICE-SUBSCRIPTION is DELETED when these are DELETED SERVICE-INSTANCE
+ required:
+ - service-type
+ properties:
+ service-type:
+ type: string
+ description: Value defined by orchestration to identify this service across ECOMP.
+ temp-ub-sub-account-id:
+ type: string
+ description: This property will be deleted from A&AI in the near future. Only stop gap solution.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ service-instances:
type: array
items:
- $ref: "#/definitions/pnf"
- physical-links:
+ $ref: "#/getDefinitions/service-instance"
+ relationship-list:
type: array
items:
- $ref: "#/definitions/physical-link"
- ipsec-configurations:
+ $ref: "#/getDefinitions/relationship"
+ service-subscriptions:
+ description: |
+ Collection of objects that group service instances.
+ properties:
+ service-subscription:
type: array
- items:
- $ref: "#/definitions/ipsec-configuration"
- route-table-references:
+ items:
+ $ref: "#/getDefinitions/service-subscription"
+ services:
+ description: |
+ Collection of service model definitions. Likely to be deprecated in favor of models from ASDC.
+ properties:
+ service:
type: array
- items:
- $ref: "#/definitions/route-table-reference"
- instance-groups:
+ items:
+ $ref: "#/getDefinitions/service"
+ site-pair:
+ description: |
+ ###### Related Nodes
+ - TO routing-instance( site-pair org.onap.relationships.inventory.BelongsTo routing-instance, MANY2ONE)
+ - FROM class-of-service( class-of-service org.onap.relationships.inventory.BelongsTo site-pair, MANY2ONE)
+ - SITE-PAIR is DELETED when these are DELETED CLASS-OF-SERVICE
+ required:
+ - site-pair-id
+ properties:
+ site-pair-id:
+ type: string
+ description: unique identifier of probe
+ source-ip:
+ type: string
+ description: Prefix address
+ destination-ip:
+ type: string
+ description: Prefix address
+ ip-version:
+ type: string
+ description: ip version, v4, v6
+ destination-hostname:
+ type: string
+ description: Hostname of the destination equipment to which SLAs are measured against.
+ destination-equip-type:
+ type: string
+ description: The type of destinatination equipment. Could be Router, etc.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ classes-of-service:
type: array
items:
- $ref: "#/definitions/instance-group"
- zones:
+ $ref: "#/getDefinitions/class-of-service"
+ relationship-list:
type: array
items:
- $ref: "#/definitions/zone"
- inventory:
+ $ref: "#/getDefinitions/relationship"
+ site-pair-set:
+ description: |
+ Set of instances for probes used to measure service level agreements
+ ###### Related Nodes
+ - TO generic-vnf( site-pair-set org.onap.relationships.inventory.AppliesTo generic-vnf, MANY2MANY)
+ - FROM routing-instance( routing-instance org.onap.relationships.inventory.BelongsTo site-pair-set, MANY2ONE)
+ - SITE-PAIR-SET is DELETED when these are DELETED ROUTING-INSTANCE
+ required:
+ - site-pair-set-id
properties:
- search:
- type: object
- $ref: "#/definitions/search"
- actions:
- type: object
- $ref: "#/definitions/actions"
- cloud-infrastructure:
- type: object
- $ref: "#/definitions/cloud-infrastructure"
- business:
- type: object
- $ref: "#/definitions/business"
- service-design-and-creation:
- type: object
- $ref: "#/definitions/service-design-and-creation"
- network:
- type: object
- $ref: "#/definitions/network"
- aai-internal:
- type: object
- $ref: "#/definitions/aai-internal"
- nodes:
+ site-pair-set-id:
+ type: string
+ description: Unique id of site pair set.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ routing-instances:
type: array
items:
- $ref: "#/definitions/"
- edge-tag-query-result:
+ $ref: "#/getDefinitions/routing-instance"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ site-pair-sets:
+ description: |
+ Collection of sets of instances for probes related to generic-vnf
properties:
- tagged-inventory-item-list:
+ site-pair-set:
type: array
items:
- $ref: "#/definitions/tagged-inventory-item-list"
- tagged-inventory-item-list:
+ $ref: "#/getDefinitions/site-pair-set"
+ site-pairs:
+ description: |
+ probe within a set
properties:
- inventory-item:
+ site-pair:
type: array
items:
- $ref: "#/definitions/inventory-item"
- inventory-item:
+ $ref: "#/getDefinitions/site-pair"
+ snapshot:
+ description: |
+ Openstack snapshot
+ ###### Related Nodes
+ - TO cloud-region( snapshot org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - FROM vserver( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)
+ required:
+ - snapshot-id
properties:
- inventory-item-type:
+ snapshot-id:
type: string
- inventory-item-link:
+ description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
+ snapshot-name:
type: string
- inventory-item-data:
+ description: Snapshot name
+ snapshot-architecture:
+ type: string
+ description: Operating system architecture
+ snapshot-os-distro:
+ type: string
+ description: The common name of the operating system distribution in lowercase
+ snapshot-os-version:
+ type: string
+ description: The operating system version as specified by the distributor.
+ application:
+ type: string
+ description: The application that the image instantiates.
+ application-vendor:
+ type: string
+ description: The vendor of the application.
+ application-version:
+ type: string
+ description: The version of the application.
+ snapshot-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ prev-snapshot-id:
+ type: string
+ description: This field contains the UUID of the previous snapshot (if any).
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
type: array
- items:
- $ref: "#/definitions/inventory-item-data"
- tagged-inventory-item-list:
+ items:
+ $ref: "#/getDefinitions/relationship"
+ snapshots:
+ description: |
+ Collection of openstack snapshots
+ properties:
+ snapshot:
type: array
items:
- $ref: "#/definitions/tagged-inventory-item-list"
- inventory-item-data:
+ $ref: "#/getDefinitions/snapshot"
+ sriov-pf:
+ description: |
+ SR-IOV Physical Function
+ ###### Related Nodes
+ - TO p-interface( sriov-pf org.onap.relationships.inventory.BelongsTo p-interface, ONE2ONE)
+ - FROM sriov-vf( sriov-vf org.onap.relationships.inventory.Uses sriov-pf, MANY2ONE)
+ required:
+ - pf-pci-id
properties:
- property-name:
+ pf-pci-id:
type: string
- property-value:
+ description: Identifier for the sriov-pf
+ resource-version:
type: string
- edge-tag-query-request:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ sriov-pfs:
+ description: |
+ Collection of SR-IOV Physical Functions.
properties:
- edge-tag:
+ sriov-pf:
+ type: array
+ items:
+ $ref: "#/getDefinitions/sriov-pf"
+ sriov-vf:
+ description: |
+ SR-IOV Virtual Function (not to be confused with virtual network function)
+ ###### Related Nodes
+ - TO l-interface( sriov-vf org.onap.relationships.inventory.BelongsTo l-interface, ONE2ONE)
+ required:
+ - pci-id
+ properties:
+ pci-id:
type: string
- result-detail:
+ description: PCI ID used to identify the sriov-vf
+ vf-vlan-filter:
type: string
- start-node-type:
+ description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM.
+ vf-mac-filter:
type: string
- start-node-filter:
- type: array
- items:
- $ref: "#/definitions/start-node-filter"
- include-node-filter:
+ description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM.
+ vf-vlan-strip:
+ type: boolean
+ description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM.
+ vf-vlan-anti-spoof-check:
+ type: boolean
+ description: This option ensures anti VLAN spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
+ vf-mac-anti-spoof-check:
+ type: boolean
+ description: This option ensures anti MAC spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
+ vf-mirrors:
+ type: string
+ description: This option defines the set of Mirror objects which essentially mirrors the traffic from source to set of collector VNF Ports.
+ vf-broadcast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows all broadcast traffic to reach the VM
+ vf-unknown-multicast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows unknown multicast traffic to reach the VM
+ vf-unknown-unicast-allow:
+ type: boolean
+ description: This option, if set to true, sets the VF in promiscuous mode and allows unknown unicast traffic to reach the VM
+ vf-insert-stag:
+ type: boolean
+ description: This option, if set to true, instructs to insert outer tag after traffic comes out of VM.
+ vf-link-status:
+ type: string
+ description: This option is used to set the link status. Valid values as of 1607 are on, off, and auto.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
+ type: string
+ description: Neutron network id of the interface
+ relationship-list:
type: array
- items:
- $ref: "#/definitions/include-node-filter"
- secondary-filter:
+ items:
+ $ref: "#/getDefinitions/relationship"
+ sriov-vfs:
+ description: |
+ Collection of SR-IOV Virtual Functions.
+ properties:
+ sriov-vf:
type: array
items:
- $ref: "#/definitions/secondary-filter"
+ $ref: "#/getDefinitions/sriov-vf"
start-node-filter:
properties:
property-name:
type: string
property-value:
type: string
- include-node-filter:
+ subnet:
+ description: |
+ ###### Related Nodes
+ - TO l3-network( subnet org.onap.relationships.inventory.BelongsTo l3-network, MANY2ONE)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.network.MemberOf subnet, MANY2MANY)
+ - SUBNET cannot be deleted if linked to L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST
+ required:
+ - subnet-id
+ - dhcp-enabled
properties:
- include-node-type:
+ subnet-id:
type: string
- secondary-filter:
- properties:
- property-name:
+ description: Subnet ID, should be UUID.
+ subnet-name:
type: string
- filter-type:
+ description: Name associated with the subnet.
+ neutron-subnet-id:
type: string
- property-value:
+ description: Neutron id of this subnet
+ gateway-address:
type: string
- search-results:
+ description: gateway ip address
+ network-start-address:
+ type: string
+ description: network start address
+ cidr-mask:
+ type: string
+ description: cidr mask
+ ip-version:
+ type: string
+ description: ip version
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ dhcp-enabled:
+ type: boolean
+ dhcp-start:
+ type: string
+ description: the start address reserved for use by dhcp
+ dhcp-end:
+ type: string
+ description: the last address reserved for use by dhcp
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ subnets:
properties:
- result-data:
+ subnet:
type: array
items:
- $ref: "#/definitions/result-data"
- result-data:
+ $ref: "#/getDefinitions/subnet"
+ tagged-inventory-item-list:
properties:
- resource-type:
+ inventory-item:
+ type: array
+ items:
+ $ref: "#/getDefinitions/inventory-item"
+ tenant:
+ description: |
+ Openstack tenant
+ ###### Related Nodes
+ - TO cloud-region( tenant org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO group-assignment( tenant org.onap.relationships.inventory.MemberOf group-assignment, MANY2MANY)
+ - TO l3-network( tenant org.onap.relationships.inventory.Uses l3-network, MANY2MANY)
+ - TO volume-group( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - FROM service-subscription( service-subscription org.onap.relationships.inventory.Uses tenant, MANY2MANY)
+ - FROM vserver( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)
+ - TENANT cannot be deleted if linked to VSERVER
+ required:
+ - tenant-id
+ - tenant-name
+ properties:
+ tenant-id:
type: string
- description: The specific type of node in the A&AI graph
- resource-link:
+ description: Unique id relative to the cloud-region.
+ tenant-name:
type: string
- description: The URL to the specific resource
- sdn-zone-response:
+ description: Readable name of tenant
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ vservers:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vserver"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ tenants:
+ description: |
+ Collection of openstack tenants.
properties:
- oam-networks:
- type: object
- $ref: "#/definitions/oam-networks"
- az-and-dvs-switches:
+ tenant:
type: array
items:
- $ref: "#/definitions/az-and-dvs-switches"
- az-and-dvs-switches:
+ $ref: "#/getDefinitions/tenant"
+ tunnel-xconnect:
+ description: |
+ Represents the specifics of a tunnel cross connect piece of a resource that gets separately allotted
+ ###### Related Nodes
+ - TO allotted-resource( tunnel-xconnect org.onap.relationships.inventory.BelongsTo allotted-resource, ONE2ONE)
+ required:
+ - id
+ - bandwidth-up-wan1
+ - bandwidth-down-wan1
+ - bandwidth-up-wan2
+ - bandwidth-down-wan2
properties:
- dvs-switches:
- type: object
- $ref: "#/definitions/dvs-switches"
- availability-zone:
- type: object
- $ref: "#/definitions/availability-zone"
+ id:
+ type: string
+ description: Allotted Resource id UUID assigned to this instance.
+ bandwidth-up-wan1:
+ type: string
+ description: The WAN uplink bandwidth for WAN1
+ bandwidth-down-wan1:
+ type: string
+ description: The WAN downlink bandwidth for WAN1
+ bandwidth-up-wan2:
+ type: string
+ description: The WAN uplink bandwidth for WAN2
+ bandwidth-down-wan2:
+ type: string
+ description: The WAN downlink bandwidth for WAN2
+ resource-version:
+ type: string
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ tunnel-xconnects:
+ description: |
+ This object is used to store the specific tunnel cross connect aspects of an allotted resource
+ properties:
+ tunnel-xconnect:
+ type: array
+ items:
+ $ref: "#/getDefinitions/tunnel-xconnect"
update:
description: |
Serves a PATCH like function. Does not enforce concurrency control. Clear each usage with AAI team.
@@ -41251,268 +61088,788 @@ definitions:
update-node-key:
type: array
items:
- $ref: "#/definitions/update-node-key"
+ $ref: "#/getDefinitions/update-node-key"
update-node-uri:
type: string
action:
type: array
items:
- $ref: "#/definitions/action"
- action:
- properties:
- action-type:
- type: string
- action-data:
- type: array
- items:
- $ref: "#/definitions/action-data"
- action-data:
- properties:
- property-name:
- type: string
- property-value:
- type: string
+ $ref: "#/getDefinitions/action"
update-node-key:
properties:
key-name:
type: string
key-value:
type: string
- notify:
+ vce:
+ description: |
+ Virtual Customer Edge Router, used specifically for Gamma. This object is deprecated.
+ ###### Related Nodes
+ - TO availability-zone( vce org.onap.relationships.inventory.Uses availability-zone, MANY2MANY)
+ - TO complex( vce org.onap.relationships.inventory.LocatedIn complex, MANY2MANY)
+ - TO vserver( vce tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM entitlement( entitlement org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM license( license org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM port-group( port-group org.onap.relationships.inventory.BelongsTo vce, MANY2ONE)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vce, ONE2MANY)
+ - VCE is DELETED when these are DELETED ENTITLEMENT,LICENSE,PORT-GROUP
required:
- - event-id
+ - vnf-id
+ - vnf-name
+ - vnf-type
properties:
- event-id:
+ vnf-id:
type: string
- node-type:
+ description: Unique id of VNF. This is unique across the graph.
+ vnf-name:
type: string
- event-trigger:
+ description: Name of VNF.
+ vnf-name2:
type: string
- key-data:
- type: array
- items:
- $ref: "#/definitions/key-data"
- selflink:
+ description: Alternate name of VNF.
+ vnf-type:
type: string
- key-data:
- properties:
- key-name:
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ service-id:
type: string
- key-value:
+ description: Unique identifier of service, does not strictly map to ASDC services, SOON TO BE DEPRECATED.
+ regional-resource-zone:
type: string
- notification-event:
- properties:
- cambria.partition:
+ description: Regional way of organizing pservers, source of truth should define values
+ prov-status:
type: string
- notification-event-header:
- type: object
- $ref: "#/definitions/notification-event-header"
- notification-event-header:
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ operational-state:
+ type: string
+ description: Indicator for whether the resource is considered operational
+ license-key:
+ type: string
+ description: OBSOLETE - do not use
+ equipment-role:
+ type: string
+ description: Network role being played by this VNF
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by MSO
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this instance, managed by MSO
+ mso-catalog-key:
+ type: string
+ description: Corresponds to the SDN-C catalog id used to configure this VCE
+ vpe-id:
+ type: string
+ description: Unique ID of VPE connected to this VCE.
+ v6-vce-wan-address:
+ type: string
+ description: Valid v6 IP address for the WAN Link on this router. Implied length of /64.
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure vce, also used for troubleshooting and is IP used for traps generated by VCE.
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ ipv4-loopback0-address:
+ type: string
+ description: Loopback0 address
+ entitlement-resource-uuid:
+ type: string
+ description: OBSOLETE - see child relationships
+ port-groups:
+ type: array
+ items:
+ $ref: "#/getDefinitions/port-group"
+ licenses:
+ type: array
+ items:
+ $ref: "#/getDefinitions/license"
+ entitlements:
+ type: array
+ items:
+ $ref: "#/getDefinitions/entitlement"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ vces:
+ description: |
+ Collection of Virtual Customer Edge Routers, used specifically for Gamma. This object is deprecated.
properties:
- id:
+ vce:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vce"
+ vf-module:
+ description: |
+ a deployment unit of VNFCs
+ ###### Related Nodes
+ - TO generic-vnf( vf-module org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO l3-network( vf-module org.onap.relationships.inventory.DependsOn l3-network, MANY2MANY)
+ - TO vnfc( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)
+ - TO volume-group( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)
+ - TO vserver( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)
+ - VF-MODULE cannot be deleted if linked to VNFC
+ required:
+ - vf-module-id
+ - is-base-vf-module
+ properties:
+ vf-module-id:
type: string
- timestamp:
+ description: Unique ID of vf-module.
+ vf-module-name:
type: string
- source-name:
+ description: Name of vf-module
+ heat-stack-id:
type: string
- domain:
+ description: Heat stack id corresponding to this instance.
+ orchestration-status:
type: string
- sequence-number:
+ description: orchestration status of this vf-module, mastered by MSO
+ is-base-vf-module:
+ type: boolean
+ resource-version:
type: string
- severity:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ persona-model-id:
type: string
- event-type:
+ description: the ASDC model id for this resource or service model.
+ persona-model-version:
type: string
- version:
+ description: the ASDC model version for this resource or service model.
+ model-version-id:
type: string
- action:
+ description: the ASDC model version for this resource or service model.
+ persona-model-customization-id:
type: string
- entity-type:
+ description: captures the id of all the configuration used to customize the resource for the service.
+ widget-model-id:
type: string
- top-entity-type:
+ description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+ widget-model-version:
type: string
- entity-link:
+ description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+ contrail-service-instance-fqdn:
type: string
- status:
+ description: the Contrail unique ID for a service-instance
+ module-index:
+ type: integer
+ format: int32
+ description: the index will track the number of modules of a given type that have been deployed in a VNF, starting with 0, and always choosing the lowest available digit
+ selflink:
type: string
- reserved-prop-names:
+ description: Path to the controller object.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ vf-modules:
description: |
- Internal map to define some reserved properties of a vertex
+ Collection of vf-modules, a deployment unit of VNFCs
properties:
- last-mod-source-of-truth:
+ vf-module:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vf-module"
+ vig-server:
+ description: |
+ vig-server contains information about a vig server used for IPSec-configuration. Populated by SDN-C from 1607
+ ###### Related Nodes
+ - TO ipsec-configuration( vig-server org.onap.relationships.inventory.BelongsTo ipsec-configuration, MANY2ONE)
+ required:
+ - vig-address-type
+ properties:
+ vig-address-type:
type: string
- aai-node-type:
+ description: indicates whether the VIG is for AVPN or INTERNET
+ ipaddress-v4-vig:
type: string
- aai-created-ts:
+ description: v4 IP of the vig server
+ ipaddress-v6-vig:
+ type: string
+ description: v6 IP of the vig server
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ vig-servers:
+ properties:
+ vig-server:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vig-server"
+ vip-ipv4-address-list:
+ description: |
+ IPv4 Address Range
+ ###### Related Nodes
+ - TO cloud-region( vip-ipv4-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO instance-group( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO subnet( vip-ipv4-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv4-address-list, MANY2MANY)
+ required:
+ - vip-ipv4-address
+ properties:
+ vip-ipv4-address:
+ type: string
+ description: IP address
+ vip-ipv4-prefix-length:
type: integer
format: int64
- aai-unique-key:
- type: string
- aai-last-mod-ts:
+ description: Prefix length, 32 for single address
+ vlan-id-inner:
type: integer
format: int64
- source-of-truth:
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ resource-version:
type: string
- aai-uri:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
type: string
- edge-prop-names:
+ description: Neutron network id of the interface that address belongs to
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of subnet that address belongs to
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ vip-ipv6-address-list:
description: |
- Internal map to define the properties of an edge and interpret the map EdgeRules
+ IPv6 Address Range
+ ###### Related Nodes
+ - TO cloud-region( vip-ipv6-address-list org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO instance-group( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf instance-group, MANY2MANY)
+ - TO subnet( vip-ipv6-address-list org.onap.relationships.inventory.MemberOf subnet, MANY2MANY)
+ - FROM vnfc( vnfc org.onap.relationships.inventory.Uses vip-ipv6-address-list, MANY2MANY)
+ required:
+ - vip-ipv6-address
properties:
- edgeLabel:
+ vip-ipv6-address:
type: string
- direction:
+ description: IP address
+ vip-ipv6-prefix-length:
+ type: integer
+ format: int64
+ description: Prefix length, 128 for single address
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ is-floating:
+ type: boolean
+ description: Indicator of fixed or floating address
+ resource-version:
type: string
- multiplicityRule:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ neutron-network-id:
type: string
- isParent:
- type: boolean
- usesResource:
- type: boolean
- hasDelTarget:
- type: boolean
- SVC-INFRA:
- type: boolean
- SVC-INFRA-REV:
- type: boolean
- model-and-named-query-search:
+ description: Neutron network id of the interface that address belongs to
+ neutron-subnet-id:
+ type: string
+ description: Neutron id of subnet that address belongs to
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ virtual-data-center:
description: |
- ModelAndNamedQuerySearch holds query-parameters and instance-properties for performing a named-query or model query
+ Virtual organization of cloud infrastructure elements in a data center context
+ ###### Related Nodes
+ - FROM connector( connector org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.LocatedIn virtual-data-center, MANY2MANY)
+ required:
+ - vdc-id
+ - vdc-name
properties:
- query-parameters:
- type: object
- $ref: "#/definitions/query-parameters"
- instance-filters:
- type: object
- $ref: "#/definitions/instance-filters"
- secondary-filts:
- type: object
- $ref: "#/definitions/secondary-filts"
- top-node-type:
+ vdc-id:
type: string
- secondary-filter-cut-point:
+ description: Unique ID of the vdc
+ vdc-name:
type: string
- query-parameters:
+ description: Name of the virtual data center
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ virtual-data-centers:
description: |
- QueryParameters for performing a named-query or model query
+ Virtual organization of cloud infrastructure elements in a data center context
properties:
- named-query:
- type: object
- $ref: "#/definitions/named-query"
- overloaded-model:
- type: object
- $ref: "#/definitions/overloaded-model"
- overloaded-model:
+ virtual-data-center:
+ type: array
+ items:
+ $ref: "#/getDefinitions/virtual-data-center"
+ vlan:
description: |
- Allows for legacy POST of old-style and new-style models
+ Definition of vlan
+ ###### Related Nodes
+ - TO l-interface( vlan tosca.relationships.network.LinksTo l-interface, MANY2ONE)
+ - TO logical-link( vlan org.onap.relationships.inventory.Uses logical-link, MANY2MANY)
+ - TO multicast-configuration( vlan org.onap.relationships.inventory.Uses multicast-configuration, MANY2MANY)
+ - FROM allotted-resource( allotted-resource org.onap.relationships.inventory.PartOf vlan, MANY2MANY)
+ - FROM service-instance( service-instance org.onap.relationships.inventory.ComposedOf vlan, ONE2MANY)
+ - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list org.onap.relationships.inventory.BelongsTo vlan, MANY2ONE)
+ - VLAN is DELETED when these are DELETED L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST
+ - VLAN deletion means associated objects of these types are also DELETED:LOGICAL-LINK
required:
- - model-invariant-id
- - model-name-version-id
- - model-type
- - model-name
- - model-id
- - model-version
+ - vlan-interface
properties:
- model-invariant-id:
+ vlan-interface:
type: string
- description: Unique identifier corresponding to the main definition of a model in ASDC
- model-name-version-id:
+ description: String that identifies the interface
+ vlan-id-inner:
+ type: integer
+ format: int64
+ description: Inner VLAN tag
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Outer VLAN tag
+ resource-version:
type: string
- description: Unique identifier corresponding to one version of a model in ASDC
- model-type:
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ speed-value:
type: string
- description: Type of the model, e.g., service, resource, widget, etc.
- model-name:
+ description: Captures the numeric part of the speed
+ speed-units:
type: string
- description: Name of the model, which can change from version to version.
- model-id:
+ description: Captures the units corresponding to the speed
+ vlan-description:
type: string
- description: Invariant unique ID which does not change from version to version
- model-version:
+ description: Used to describe (the service associated with) the vlan
+ backdoor-connection:
type: string
- description: Version
- model-description:
+ description: Whether customer is going to use this VLAN for backdoor connection to another customer premise device.
+ vpn-id:
type: string
- description: Description
+ description: This indicates the customers VPN ID associated with this vlan
+ orchestration-status:
+ type: string
+ description: Status of a vnf's vlan interface, on which the customer circuit resides, mastered by SDN-C.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ l3-interface-ipv4-address-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
+ l3-interface-ipv6-address-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
+ vlans:
+ properties:
+ vlan:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vlan"
+ vnf:
+ description: |
+ Abstract vnf class
+ required:
+ - vnf-id
+ properties:
+ vnf-id:
+ type: string
+ description: Unique id of VNF. This is unique across the graph.
+ vnf-image:
+ description: |
+ Image object that pertain to a VNF that doesn't have associated vservers. This is a kludge.
+ ###### Related Nodes
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.Uses vnf-image, MANY2ONE)
+ - VNF-IMAGE cannot be deleted if linked to GENERIC-VNF
+ required:
+ - vnf-image-uuid
+ - application
+ - application-vendor
+ properties:
+ vnf-image-uuid:
+ type: string
+ description: Unique ID of this asset
+ application:
+ type: string
+ description: The application that the image instantiates.
+ application-vendor:
+ type: string
+ description: The vendor of the application.
+ application-version:
+ type: string
+ description: The version of the application.
+ selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
resource-version:
type: string
description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
- model-vers:
- type: object
- $ref: "#/definitions/model-vers"
relationship-list:
- type: object
- $ref: "#/definitions/relationship-list"
- instance-filters:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ vnf-images:
description: |
- InstanceFilters for performing a named-query or model query
+ Collection of image objects that pertain to a VNF that doesn't have associated vservers. This is a kludge.
properties:
- instance-filter:
+ vnf-image:
type: array
items:
- $ref: "#/definitions/instance-filter"
- instance-filter:
+ $ref: "#/getDefinitions/vnf-image"
+ vnfc:
description: |
- InstanceFilter for performing a named-query or model query
- secondary-filts:
+ ###### Related Nodes
+ - TO generic-vnf( vnfc org.onap.relationships.inventory.BelongsTo generic-vnf, MANY2ONE)
+ - TO vserver( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses vnfc, ONE2MANY)
+ required:
+ - vnfc-name
+ - vnfc-function-code
+ - vnfc-type
+ - in-maint
+ - is-closed-loop-disabled
+ properties:
+ vnfc-name:
+ type: string
+ description: Unique ID of vnfc.
+ vnfc-function-code:
+ type: string
+ description: function code
+ vnfc-type:
+ type: string
+ description: type
+ prov-status:
+ type: string
+ description: prov status of this vnfc
+ orchestration-status:
+ type: string
+ description: Orchestration status of this VNF, mastered by APP-C
+ ipaddress-v4-oam-vip:
+ type: string
+ description: Oam V4 vip address of this vnfc
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
+ group-notation:
+ type: string
+ description: Group notation of VNFC
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ vnfcs:
description: |
- SecondaryFilts for performing a named-query or model query
+ virtual network components associated with a vserver from application controller.
properties:
- secondary-filt:
+ vnfc:
type: array
items:
- $ref: "#/definitions/secondary-filt"
- secondary-filt:
+ $ref: "#/getDefinitions/vnfc"
+ volume:
description: |
- SecondaryFilt for performing a named-query or model query
- properties:
+ Ephemeral Block storage volume.
+ ###### Related Nodes
+ - FROM vserver (PARENT of volume, vserver tosca.relationships.AttachesTo volume)
+ required:
+ - volume-id
+ - volume-selflink
+ properties:
+ volume-id:
+ type: string
+ description: Unique ID of block storage volume relative to the vserver.
+ volume-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ volume-group:
description: |
- Property holder for query properties or instance properties
+ Persistent block-level storage.
+ ###### Related Nodes
+ - TO cloud-region( volume-group org.onap.relationships.inventory.BelongsTo cloud-region, MANY2ONE)
+ - TO complex( volume-group org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM generic-vnf( generic-vnf org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses volume-group, ONE2ONE)
+ - FROM tenant( tenant org.onap.relationships.inventory.DependsOn volume-group, ONE2MANY)
+ required:
+ - volume-group-id
+ - volume-group-name
+ - vnf-type
properties:
- property-name:
+ volume-group-id:
type: string
- property-value:
+ description: Unique ID of volume-group.
+ volume-group-name:
type: string
- response-list:
+ description: Name of the volume group.
+ heat-stack-id:
+ type: string
+ description: Heat stack id corresponding to this volume-group
+ vnf-type:
+ type: string
+ description: String capturing type of vnf, that was intended to identify the ASDC resource. This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+ orchestration-status:
+ type: string
+ description: Orchestration status of this volume-group
+ persona-model-customization-id:
+ type: string
+ description: captures the id of all the configuration used to customize the resource for the service.
+ vf-module-persona-model-customization-id:
+ type: string
+ description: helps relate the volume group to the vf-module whose components will require the volume group
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ volume-groups:
description: |
- Response container for the results of a named-query or model query
+ Collection of persistent block-level storage.
properties:
- inventory-response-items:
- type: object
- $ref: "#/definitions/inventory-response-items"
- inventory-response-items:
+ volume-group:
+ type: array
+ items:
+ $ref: "#/getDefinitions/volume-group"
+ volumes:
description: |
- Container for inventory items in response list
+ Collection of ephemeral Block storage volumes.
properties:
- inventory-response-item:
+ volume:
type: array
items:
- $ref: "#/definitions/inventory-response-item"
- inventory-response-item:
+ $ref: "#/getDefinitions/volume"
+ vpls-pe:
description: |
- Inventory item for response list
+ VPLS Provider Edge routers.
+ ###### Related Nodes
+ - TO complex( vpls-pe org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - TO ctag-pool( vpls-pe org.onap.relationships.inventory.Uses ctag-pool, MANY2MANY)
+ - FROM lag-interface( lag-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - FROM p-interface( p-interface tosca.relationships.network.BindsTo vpls-pe, MANY2ONE)
+ - VPLS-PE is DELETED when these are DELETED LAG-INTERFACE,P-INTERFACE
+ required:
+ - equipment-name
properties:
- model-name:
+ equipment-name:
type: string
- extra-properties:
- type: object
- $ref: "#/definitions/extra-properties"
- inventory-response-items:
- type: object
- $ref: "#/definitions/inventory-response-items"
- extra-properties:
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+ ipv4-oam-address:
+ type: string
+ description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by VPE (v4-loopback0-ip-address).
+ equipment-role:
+ type: string
+ description: Client should send valid enumerated value, e.g., VPLS-PE.
+ vlan-id-outer:
+ type: integer
+ format: int64
+ description: Temporary location for stag to get to VCE
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ p-interfaces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/p-interface"
+ lag-interfaces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/lag-interface"
+ vpls-pes:
description: |
- Extra properties for inventory item for response list
- extra-property:
+ Collection of VPLS Provider Edge routers
properties:
- property-name:
+ vpls-pe:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vpls-pe"
+ vpn-binding:
+ description: |
+ VPN binding
+ ###### Related Nodes
+ - FROM l3-network( l3-network org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - FROM logical-link( logical-link org.onap.relationships.inventory.Uses vpn-binding, MANY2MANY)
+ - VPN-BINDING cannot be deleted if linked to L3-NETWORK,LOGICAL-LINK
+ required:
+ - vpn-id
+ - vpn-name
+ - global-route-target
+ - route-target-role
+ properties:
+ vpn-id:
type: string
- vnf:
+ description: VPN ID, globally unique within A&AI
+ vpn-name:
+ type: string
+ description: VPN Name
+ global-route-target:
+ type: string
+ description: Number used to identify a VPN, globally unique in the network
+ vpn-platform:
+ type: string
+ description: the platform associated with the VPN example AVPN, Mobility
+ vpn-type:
+ type: string
+ description: Type of the vpn, should be taken from enumerated/valid values
+ route-distinguisher:
+ type: string
+ description: Used to distinguish the distinct VPN routes of separate customers who connect to the provider in an MPLS network.
+ route-target-role:
+ type: string
+ description: Role assigned to this route target
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ description: l3-networks relate to vpn-bindings
+ vpn-bindings:
+ properties:
+ vpn-binding:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vpn-binding"
+ vserver:
description: |
- Abstract vnf class
+ Virtual Servers, aka virtual machine or VM.
+ ###### Related Nodes
+ - TO tenant( vserver org.onap.relationships.inventory.BelongsTo tenant, MANY2ONE)
+ - TO flavor( vserver org.onap.relationships.inventory.Uses flavor, MANY2ONE)
+ - TO image( vserver org.onap.relationships.inventory.Uses image, MANY2ONE)
+ - TO pserver( vserver tosca.relationships.HostedOn pserver, MANY2ONE)
+ - TO snapshot( vserver org.onap.relationships.inventory.Uses snapshot, ONE2ONE)
+ - TO volume (CHILD of vserver, vserver tosca.relationships.AttachesTo volume, ONE2MANY)
+ - FROM generic-vnf( generic-vnf tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM vce( vce tosca.relationships.HostedOn vserver, ONE2MANY)
+ - FROM l-interface( l-interface tosca.relationships.network.BindsTo vserver, MANY2ONE)
+ - FROM vf-module( vf-module org.onap.relationships.inventory.Uses vserver, ONE2MANY)
+ - FROM vnfc( vnfc tosca.relationships.HostedOn vserver, ONE2MANY)
+ - VSERVER is DELETED when these are DELETED L-INTERFACE
+ - VSERVER deletion means associated objects of these types are also DELETED:VOLUME
required:
- - vnf-id
+ - vserver-id
+ - vserver-name
+ - vserver-selflink
+ - in-maint
+ - is-closed-loop-disabled
properties:
- vnf-id:
+ vserver-id:
type: string
- description: Unique id of VNF. This is unique across the graph.
+ description: Unique identifier for this vserver relative to its tenant
+ vserver-name:
+ type: string
+ description: Name of vserver
+ vserver-name2:
+ type: string
+ description: Alternative name of vserver
+ prov-status:
+ type: string
+ description: Trigger for operational monitoring of this resource by Service Assurance systems.
+ vserver-selflink:
+ type: string
+ description: URL to endpoint where AAI can get more details
+ in-maint:
+ type: boolean
+ is-closed-loop-disabled:
+ type: boolean
+ resource-version:
+ type: string
+ description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+ volumes:
+ type: array
+ items:
+ $ref: "#/getDefinitions/volume"
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ l-interfaces:
+ type: array
+ items:
+ $ref: "#/getDefinitions/l-interface"
+ vservers:
+ description: |
+ Collection of virtual Servers, aka virtual machines or VMs.
+ properties:
+ vserver:
+ type: array
+ items:
+ $ref: "#/getDefinitions/vserver"
+ zone:
+ description: |
+ A zone is a grouping of assets in a location homing to the same connections into the CBB
+ ###### Related Nodes
+ - TO complex( zone org.onap.relationships.inventory.LocatedIn complex, MANY2ONE)
+ - FROM cloud-region( cloud-region org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM pnf( pnf org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ - FROM pserver( pserver org.onap.relationships.inventory.LocatedIn zone, MANY2ONE)
+ required:
+ - zone-id
+ - zone-name
+ - design-type
+ - zone-context
+ properties:
+ zone-id:
+ type: string
+ description: Code assigned by AIC to the zone
+ zone-name:
+ type: string
+ description: English name associated with the zone
+ design-type:
+ type: string
+ description: Design of zone [Medium/Large?]
+ zone-context:
+ type: string
+ description: Context of zone [production/test]
+ status:
+ type: string
+ description: Status of a zone.
+ resource-version:
+ type: string
+ description: Concurrency value
+ relationship-list:
+ type: array
+ items:
+ $ref: "#/getDefinitions/relationship"
+ zones:
+ description: |
+ Collection of zones
+ properties:
+ zone:
+ type: array
+ items:
+ $ref: "#/getDefinitions/zone"
diff --git a/pom.xml b/pom.xml
index 130a9627..d794c98c 100644
--- a/pom.xml
+++ b/pom.xml
@@ -20,6 +20,7 @@
<module>aai-core</module>
<module>aai-auth</module>
<module>aai-utils</module>
+ <module>aai-client-loadbalancer</module>
</modules>
<properties>